Heroku vs. Cloud 66

Compare the status, incidents stats and history between Heroku and Cloud 66

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.

Heroku

Heroku current official status is Operational

Statistics

1
Incidents in the last 7 days
3
Incidents in the last 30 days
10
Incidents in the last 90 days

Latest incidents

Resolved Stopped processes continue to produce logs

Engineers have identified that affected applications are isolated to a subset of Basic dynos in the US region of the Common Runtime. Other dyno types, Heroku services, Dashboard, and CLI are not af...

Resolved Investigating issues with dyno formations and autoscaling

Triage and remediation of DNS and Applications states have been completed.

Resolved Investigating an issue with access to Heroku services

Build's Release Phase are operating normally.

Cloud 66

Cloud 66 current official status is Operational

Statistics

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

Latest incidents

Resolved Google login issues

Google authentication issues is having issues causing login and access issues for our systems and customers. We are investigating the impact and mitigation strategies.

Resolved Kubernetes Cluster Scale/Creation

We are aware of problems when scaling/creating Kubernetes clusters. This appears to be caused by new rate limits imposed by docker hub. The team are working on a solution.

Resolved Stuck Deployments

We are currently investigating a number of stuck deployments.

about 1 year ago Official incident report

Never again lose time looking in the wrong place

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