Skip to content
OutageDeck

Incident detail

Heroku Feature Degradation

Resolved incidentMinor1 affected service

Timeline window

to

Get alerted the next time Heroku breaks

Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Set up free alertsHow Heroku alerts work

Timeline

Incident updates

Every update on the official status source, oldest to newest, exactly as it appeared there.

  1. Investigating

    Heroku engineers are investigating.

  2. Monitoring

    Node.js builds are currently experiencing elevated error rates due to issues with an upstream dependency.

  3. Resolved

    Incident resolved.

  4. Monitoring

    At this time most upstream errors and been triaged. In case of errors building nodejs packages, continue to retry. The team will post an additional update once all systems are back to normal.

  5. Monitoring

    Most upstream errors have now been addressed. If you encounter errors while building Node.js packages, please retry the build. We will provide an additional update once normal operations have been fully restored.

  6. Monitoring

    The upstream errors have been resolved, and normal operations have been restored. This incident is now resolved.

Keep exploring

More from Heroku

Neighboring incidents on Heroku's timeline and the rest of their record on OutageDeck.

← Older incident

Heroku Platform Maintenance

All Heroku incidentsHeroku live status