All Systems Operational

About This Site

At Skedulo, transparency is one of our guiding principles. Our mission is to provide you a stable and reliable service, and part of that promise is keeping you fully informed whenever issues arise.

Below, you’ll find the current status of Skedulo, as well as any recent issues or incidents we may have had. If you're experiencing any problems related to Skedulo and don’t see anything about it below, please contact us at support@skedulo.com.

Skedulo Classic   ? Operational
Skedulo Website   ? Operational
Skedulo New Web App   ? Operational
Skedulo API   ? Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Skedulo Classic Response Time
Fetching
Skedulo Classic Uptime ?
Fetching
Skedulo New Web App Response Time
Fetching
Skedulo New Web App Uptime ?
Fetching
Skedulo API Response Time
Fetching
Skedulo API Uptime ?
Fetching
Past Incidents
Oct 16, 2018

No incidents reported today.

Oct 15, 2018

No incidents reported.

Oct 14, 2018
Completed - Configuration change complete and verified.
Oct 14, 19:14 AEST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 14, 19:00 AEST
Scheduled - We will be applying some database configuration changes to better support our internal stream-processing system.

During this time the Skedulo applications will not be taken offline but you may encounter higher levels of:
- Unavailability
- Errors
- Request durations
Oct 12, 10:52 AEST
Oct 13, 2018

No incidents reported.

Oct 12, 2018

No incidents reported.

Oct 11, 2018

No incidents reported.

Oct 10, 2018

No incidents reported.

Oct 9, 2018

No incidents reported.

Oct 8, 2018

No incidents reported.

Oct 7, 2018

No incidents reported.

Oct 6, 2018

No incidents reported.

Oct 5, 2018

No incidents reported.

Oct 4, 2018

No incidents reported.

Oct 3, 2018

No incidents reported.

Oct 2, 2018
Resolved - A configuration error affected the performance of our backend system healing itself from from an unexpected Instance loss.

Some services were affected for up to 5 minutes, and during this time users may have faced full or partial unavailability, increased error rates or increased request duration.

Service was promptly restored by automated processes and we're now investigating further to prevent this issue causing such an impact in the future.
Oct 2, 14:48 AEST