All Systems Operational
Website Operational
Platform Analysis ? Operational
Classic Analysis ? Operational
GitHub Operational
AWS ec2-us-east-1 Operational
AWS s3-us-standard Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
System Metrics Month Week Day
Error Rate
Fetching
Analysis processing time
Fetching
Past Incidents
Apr 28, 2017

No incidents reported today.

Apr 27, 2017
Resolved - This incident has been resolved.
Apr 27, 10:42 EDT
Monitoring - We've manually moved the service to the log position before the error occurred. This means we are no longer re-processing old work and the service's performance is back to normal. Unfortunately, we do now have to catch up on the backlog of work from that point.

Analysis results are currently delayed by 30 minutes and we expect to recover within the next hour.
Apr 27, 10:11 EDT
Identified - One of our services responsible for writing analysis results to the database, has encountered an error managing its position in its log of work to process. This has resulted in it re-processing from an older point in time. This re-processing is safe, but means we are unable to get to current work at this time.

Users may be experiencing builds that don't appear to start or finish. We're currently investigating ways to manually move the service to the correct position in the log.
Apr 27, 09:44 EDT
Apr 26, 2017

No incidents reported.

Apr 25, 2017

No incidents reported.

Apr 24, 2017

No incidents reported.

Apr 23, 2017

No incidents reported.

Apr 22, 2017

No incidents reported.

Apr 21, 2017

No incidents reported.

Apr 20, 2017

No incidents reported.

Apr 19, 2017

No incidents reported.

Apr 18, 2017

No incidents reported.

Apr 17, 2017

No incidents reported.

Apr 16, 2017

No incidents reported.

Apr 15, 2017

No incidents reported.

Apr 14, 2017

No incidents reported.