All Systems Operational
Managment interface Operational
Shared databases US-East-1 Operational
Shared databases EU-West-1 Operational
Backups Operational
Heroku Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Past Incidents
Apr 24, 2017

No incidents reported today.

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.

Apr 13, 2017

No incidents reported.

Apr 12, 2017
Resolved - FINALLY BACK! And with a fresh base backup this will Never Ever happen again.
Apr 12, 07:10 UTC
Update - Terribly sorry for this long outage.
Restore operation is still crunching WALs. Postgres does not have a progress indicator for this so we are just monitoring to see when it it finished. Should not be too long now.
Apr 11, 06:56 UTC
Monitoring - Devops made a configuration mistake during last restore and we have to re-do it. Unfortunately we have to restore from WALs which takes some time. Estimated time of completion is 2017-04-11 00:00.
Apr 10, 10:48 UTC
Investigating - We are currently investigating this issue.
Apr 10, 09:31 UTC
Apr 10, 2017
Resolved - Finally back online. Waiting for Post mortem from Softlayer.
Apr 10, 05:53 UTC
Identified - The data disk was corrupt. We're restoring from WAL logs, but it might take hours to restore them all.
Apr 9, 00:39 UTC
Update - Softlayer messed up somehow. They are working on it.
‚ÄčIt might be quicker to create a new instance in another region and restore from your most recent backup.
Apr 8, 13:58 UTC
Investigating - Softlayer is investigating an issue after a planned patch on their side.
Apr 8, 13:09 UTC