DigitalOcean vs. Heroku

Compare the status, incidents stats and history between DigitalOcean and Heroku

Every service has different practices when updating its status page, so compare these stats with a grain of salt. E.g., one service can be more aggressive when updating its status page than other so that they will have more incidents, but it doesn't mean it is worse than the other.

DigitalOcean

DigitalOcean current official status is Operational

Statistics

1
Incidents in the last 7 days
4
Incidents in the last 30 days
20
Incidents in the last 90 days

Latest incidents

Resolved Latest AWS SDK/CLI updates incompatible with Spaces

DigitalOcean Spaces Customers using the latest versions (released on Jan 15, 2025) of the AWS CLI or any AWS SDK, or relying on a tool or application that depends on any of these versions of the AW...

Resolved Reconciling Kubernetes Clusters

Our Engineering team is currently investigating an issue with Managed Kubernetes clusters. During this time, some users may experience delays when provisioning Kubernetes clusters, specifically ver...

Resolved Network Connectivity in SFO3 Region

Our engineering team is investigating an issue related to the SFO3 network maintenance here: https://status.digitalocean.com/incidents/lf0njg8ysj0w During this time users may experience connectivi...

Heroku

Heroku current official status is Operational

Statistics

0
Incidents in the last 7 days
1
Incidents in the last 30 days
7
Incidents in the last 90 days

Latest incidents

Resolved Investigating an issue with data.heroku.com

Beginning at 15:35 UTC on 2025-01-09, data.heroku.com is not available for customers in all regions, including Dataclips. Customers experienced redirect loops when attempting to authenticate. Our e...

Resolved Yarn Install Build Timeout Errors for Ruby Apps

Our engineers have identified the issue and are working to fix the problem with `yarn install` build timeouts in Ruby builds.

Resolved Node.js Build Timeout Errors

Customers experiencing build timeouts using Node.js 20 can temporarily workaround the issue by running `heroku config:set UV_USE_IO_URING=0`. Our engineers have identified the issue and are wor...

Never again lose time looking in the wrong place

14-day free trial · No credit card required · No code required