Heroku Status

Production

99.92%
last
month

Development

99.76%
last
month

All Systems Operational

All Systems Operational

On April 3rd, starting at 07:00 UTC (00:00 PDT), and continuing until 08:00 UTC (1 hour), Heroku will be performing service update to the build system. During this time builds will be disabled. We will provide an update when we begin and complete the service update.

Scheduled

Mon Mar 30, 201523:34 UTC

On April 3rd, starting at 07:00 UTC (00:00 PDT), and continuing until 08:00 UTC (1 hour), Heroku will be performing service update to the build system. During this time builds will be disabled. We will provide an update when we begin and complete the service update.

Issue

On April 1, 2015 starting at 20:00 UTC (1pm PDT), and continuing for 30 minutes until 20:30 UTC, Heroku will be performing a service update to the logplex cluster. During this time, changes to log streams, including logging for newly created apps, will be delayed until the service update is complete.

Scheduled

Thu Mar 26, 201517:44 UTC

On April 1, 2015 starting at 20:00 UTC (1pm PDT), and continuing for 30 minutes until 20:30 UTC, Heroku will be performing a service update to the logplex cluster. During this time, changes to log streams, including logging for newly created apps, will be delayed until the service update is complete.
We will provide an update when we begin and complete the service update.

Resolved

Update

The update has completed. We are monitoring the platform to ensure database metrics are working correctly.

Maintenance

Wed Mar 25, 201517:09 UTC

Our scheduled service update is beginning now. During this time, dashboard metrics will be unavailable, and some metrics data will be lost. We will post an update when the work is complete.

Scheduled

Tue Mar 24, 201520:28 UTC

On March 25, 2015 starting at 12 PM PDT (17:00 UTC), and continuing until 2 PM PDT (19:00 UTC, 2 hours), Heroku will be performing a service update to the dashboard metrics system. During this time, dashboard metrics will be unavailable, and some metrics data will be lost. We will provide an update when we begin and complete the service update.

Resolved

Monitoring

Wed Mar 11, 201504:15 UTC

The hobby database interface is now stable. We will continue to monitor to ensure there are no further issues.

Issue

Wed Mar 11, 201503:59 UTC

Our engineers have identified an issue triggered by a change in the hobby tier management interface. We are no longer seeing any customer impact and our engineers will continue to monitor the interface to ensure it is working correctly.

Issue

Resolved

Thu Feb 26, 201521:21 UTC

This incident is now resolved.

Monitoring

Thu Feb 26, 201521:06 UTC

We've now restored or reprovisioned all affected log channels. Logs for affected applications during this incident were not recoverable and will be missing. We're now monitoring to confirm that all is as it should be.

Update

Thu Feb 26, 201520:41 UTC

We're continuing to work toward restoring the lost log channels. We'll update again in an hour or earlier if the issue is resolved sooner.

Update

Thu Feb 26, 201519:40 UTC

We're continuing to work toward restoring the lost log channels. We'll update again in an hour or earlier if the issue is resolved sooner.

Update

Thu Feb 26, 201518:40 UTC

We're continuing to work toward restoring the lost log channels. We'll update again in an hour or earlier if the issue is resolved sooner.

Update

Thu Feb 26, 201518:09 UTC

We've identified the issue as being related to loss of some log channel information affecting some applications. We're continuing to work toward restoring the lost log channel information.

Issue

Thu Feb 26, 201517:35 UTC

We've detected an issue that is preventing logging from working in some cases. We're currently working to resolve the issue.

After investigation the Scheduler add-on was still performing within the expectations set by the add-on documentation [here](https://devcenter.heroku.com/articles/scheduler). Preventative measures have been taken by our engineering team to ensure the add-on will continue to perform within expectations.

False-alarm

Thu Feb 26, 201504:57 UTC

After investigation the Scheduler add-on was still performing within the expectations set by the add-on documentation [here](https://devcenter.heroku.com/articles/scheduler). Preventative measures have been taken by our engineering team to ensure the add-on will continue to perform within expectations.
This incident is resolved as a false alarm.

Investigating

Thu Feb 26, 201504:12 UTC

Heroku engineers are investigating issues with availability of the Heroku Scheduler add-on.