Heroku
Heroku is a platform as a service (PaaS) that enables developers to build, run, and operate applications entirely in the cloud.
Homepage: https://www.heroku.com/
Status Page: https://status.heroku.com/
Open Incidents
No open incidents
Scheduled Incidents
No scheduled incidents
Previous Incidents
PGBackups maintenance on December 22, 2016 from 21:30 UTC to 22:00 UTC
2016-12-21 01:41:33| Action | Date | Description |
|---|---|---|
| Resolved | 2016-12-22 21:43:24 | This maintenance is complete. All platform functionality has returned to normal. |
| Maintenance | 2016-12-22 21:35:47 | The scheduled maintenance is now underway. We'll post more updates as necessary or when the maintenance is complete. |
| Scheduled | 2016-12-21 01:41:33 | On Thursday 22, 2016 starting at 21:30 UTC, and continuing until 22:00 UTC (30 minutes), Heroku will be performing maintenance on pg:backups. Backups scheduled for 21:00 UTC may be cancelled and those in progress during the maintenance window will be interrupted. Backups scheduled for 22:00 UTC may also be delayed. Additionally, all CLI commands under `heroku pg:backups` will be unavailable during this maintenance window. It is important to note that your data will not be affected during this maintenance nor will any data loss occur. Only the ability to backup your database will be unavailable. We will provide an update when we begin and complete this maintenance. |
Delays in dynos status and starts
2016-12-20 19:45:56| Action | Date | Description |
|---|---|---|
| Resolved | 2016-12-20 19:58:49 | Dyno status updates and starts are behaving as expected with no sign of further problems. |
| Issue | 2016-12-20 19:45:56 | We are seeing delays in dyno status updates and starts. |
GitHub Sync deploy delays
2016-12-17 00:16:17| Action | Date | Description |
|---|---|---|
| Resolved | 2016-12-17 00:59:42 | This incident is now resolved. |
| Monitoring | 2016-12-17 00:49:47 | The underlying issue is resolved and the backlog has been worked through. GitHub Sync deploys are now working again. We're continuing to monitor to ensure all is working as expected. |
| Issue | 2016-12-17 00:16:17 | We've identified issues with GitHub Sync deploys that have caused a backlog. We're pausing GitHub Sync deploys while the underlying issue is resolved. Until this is resolved you may also see warning messages in your Heroku Dashboard. |
(US) Dyno Stability Errors
2016-12-16 10:00:51| Action | Date | Description |
|---|---|---|
| Resolved | 2016-12-16 12:17:52 | This issue is now resolved |
| Monitoring | 2016-12-16 12:06:17 | We have completed updating our US region and we will continue to monitor for any reoccurrences of Dyno instability. |
| Update | 2016-12-16 11:49:51 | Our engineers are continuing to update and monitor our US region. If you are experiencing Dyno instability due to segmentation faults, you can use the CLI command `heroku restart`, to relocate your Dynos to an updated Dyno host. |
| Update | 2016-12-16 11:23:18 | We are continuing to update our US region and monitor for any reoccurrences of Dyno instability. |
| Update | 2016-12-16 10:31:15 | Our engineers have identified the cause of the Dyno segmentation fault errors and are implementing the fix across our US region. |
| Issue | 2016-12-16 10:00:51 | We are investigating an increase in segmentation fault errors in apps across the US region. |
Heroku Connect Sync failures
2016-12-16 08:13:58| Action | Date | Description |
|---|---|---|
| Resolved | 2016-12-16 09:32:09 | This issue has been resolved. |
| Monitoring | 2016-12-16 09:18:50 | Heroku Connect sync has been restored and we are monitoring to ensure it is working correctly. |
| Issue | 2016-12-16 08:13:58 | We have confirmed issues with Heroku Connect Sync and are working on a solution. |
(US) Increased Dyno Start Latency
2016-12-16 01:52:42| Action | Date | Description |
|---|---|---|
| Resolved | 2016-12-16 01:52:42 | This issues has been resolved. |
(EU) EU Region Network Latency
2016-12-15 01:43:26| Action | Date | Description |
|---|---|---|
| Resolved | 2016-12-15 03:53:54 | Application dynos have been moved from affected areas, latencies and error rates have returned to normal. This incident has been resolved. We will be posting a public post-mortem on this incident once our internal follow-up has been completed. |
| Update | 2016-12-15 02:35:34 | We are observing dynos crashing as apps encounter network errors. Our engineers are attempting to work around known bad areas to bring dynos up again. |
| Update | 2016-12-15 02:03:13 | We have isolated the cause to an networking issue in the EU region. At the moment we are working with our upstream provider for a fix. We'll keep this incident open in the meantime and will update once the fix is completed. Updates will also be posted to the Europe tab of the AWS Service Health Dashboard: https://status.aws.amazon.com/ |
| Issue | 2016-12-15 01:43:26 | We are observing increased latency in the EU region. Network connections from dynos in the EU region to services also seem to be impacted. We are looking into a cause. |
(Spaces) Connection issues in Private Spaces apps
2016-12-13 21:45:12| Action | Date | Description |
|---|---|---|
| Resolved | 2016-12-13 22:46:24 | All Spaces have been rolled back, this issue has been resolved. |
| Update | 2016-12-13 22:33:46 | Almost all Private Spaces have been rolled back. |
| Issue | 2016-12-13 21:45:12 | A recent Private Spaces upgrade is resulting in an infrequent router crash, closing any active connections to a specific Dyno at the time. We are currently rolling back the upgrade. |
Heroku Postgres Hobby database errors
2016-12-13 17:15:06| Action | Date | Description |
|---|---|---|
| Resolved | 2016-12-13 17:23:11 | The cause of the problem has been discovered and a fix has been pushed out. |
| Retroactive | 2016-12-13 17:15:06 | An issue was detected involving administrative operations against Heroku Postgres Hobby databases. The databases themselves were operating normally, but administrative functionality wasn't working properly (e.g., actions taken in the dashboard UI and `heroku pg` CLI commands). We're working on solving the issue. |
Build failures
2016-12-12 21:41:04| Action | Date | Description |
|---|---|---|
| Resolved | 2016-12-12 22:04:48 | This has been resolved. Auto-builds are now behaving as expected. |
| Monitoring | 2016-12-12 21:58:47 | Build error levels have subsided, returning to normal. We are now monitoring to ensure this issue has been resolved. |
| Issue | 2016-12-12 21:41:04 | The issue has been identified as only affecting our auto-build services: Git Sync and CI. This does not appear to be affecting manual builds (using `git push heroku master`). |