Codecov
All Systems Operational
Web App Operational
Browser Extension Operational
Report Processing Operational
Notification Processing ? Operational
Uploaders Operational
Bash ? Operational
Python Operational
Node Operational
Perl Operational
Haskell Operational
3rd Party Services Operational
GitHub Operational
Atlassian Bitbucket API Operational
Heroku ? Operational
Redis Labs AWS/us-east-1-3.1 ? Operational
DNSimple Name Servers Operational
Stripe API ? Operational
AWS cloudFront Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
System Metrics Month Week Day
Median Response Time
Fetching
Reports in Queue
Fetching
Past Incidents
Feb 21, 2017

No incidents reported today.

Feb 20, 2017

No incidents reported.

Feb 19, 2017

No incidents reported.

Feb 18, 2017

No incidents reported.

Feb 17, 2017

No incidents reported.

Feb 16, 2017

No incidents reported.

Feb 15, 2017
Resolved - Database is back and functional. We will continue to monitor, but things look "200 Ok".
Feb 15, 18:11 UTC
Update - Looks like the new database was not promoted properly #fail
We are spinning up a new one and migrating again.
Feb 15, 17:28 UTC
Identified - Awaiting feedback from @heroku support on our database being in a read-only state.
Given the read-only state of the database: functionality is restricted to read-only.
Feb 15, 17:20 UTC
Update - Our database is upgraded, but in a read-only state. Working with Heroku staff to resolve.
Feb 15, 16:42 UTC
Update - We are migrating data to a larger database instance, which we hope will resolve this issue. Again sorry for the issue and we appreciate your patience.

This happened unexpectedly and we continue to review what was the first event that cased the database to fail.
Feb 15, 14:37 UTC
Investigating - Our database is having issues serving requests suddenly. Still working hard to resolve. Thank you
Feb 15, 14:20 UTC
Update - Database issues continue. We are working hard to resolve. Thank you for your patience.
Feb 15, 12:33 UTC
Update - We identified the issue to be long running queries during refreshing. We have disabled this functionality at the moment as we look into the issue.

Refreshing your repositories/teams will be disabled. Please navigate directly to repositories or teams which bypasses the refreshing agent.
Feb 15, 11:42 UTC
Identified - After investigating the issue more, it appears to be long running queries on the database. Working to resolve these issues.
Feb 15, 11:34 UTC
Investigating - We are seeing an large amount of connections with GitHub timing out.
Feb 15, 11:10 UTC
Feb 14, 2017

No incidents reported.

Feb 13, 2017

No incidents reported.

Feb 12, 2017

No incidents reported.

Feb 11, 2017

No incidents reported.

Feb 10, 2017

No incidents reported.

Feb 9, 2017

No incidents reported.

Feb 8, 2017

No incidents reported.

Feb 7, 2017

No incidents reported.