whyhammoud

@mathio28 @heroku @herokustatus around 30 minutes ago

@whyhammoud @heroku @herokustatus When did this start for you? I noticed around 8:15 UTC

@heroku @herokustatus I am getting H99 "Platform error" on all of my node.js apps What's up?

@heroku we deserve full transparency on what’s happened over the last 2 days. What caused the disruptions? What are you doing to prevent this from happening again? It's time to own up and provide clear answers. Your customers rely on you! @andyinthecloud @herokustatus

Our applications were heavily affected for over 9 hours in total over two consecutive days. I think we deserve transparency. @heroku @herokustatus @asksalesforce please provide answers to following questions: 1.What happened on 08.10.2024? 2.Why did it happen? 3.What actions have you taken to prevent reoccurrence? (that did not work) 4.Why did your status page show the issue 1.5 hours after it started? (The problem started at 4:27 PM UTC, and it was noticed and reported on the status page at 6:10 PM UTC) 5.What was the scope of the outage? 6.What happened on 09.10.2024? 7.Why did it happen? 8.What actions have you taken to prevent recurrence (and will it be effective this time)? 9.Why did your status page show the issue 40 minutes after it started? (The problem started at 1:06 PM UTC, and it was noticed and reported on the status page at 1:46 PM UTC) 10.What was the scope of the outage?

@jesstyping @nunotomas @JuraszekMateusz @heroku @digitalocean @render I've switched to digital ocean last night. But I'm willing to explore other options like render at the moment!

@nunotomas @whyhammoud @JuraszekMateusz @heroku @digitalocean Hi Nuno and others on this thread -- happy to chat about @render if you want to investigate other PaaS options. If you give it a quick spin, I'd be curious to hear your thoughts on our DX, and any missing features.

@nicocary @robaldred @JaimeIniestaDev @willtew @heroku @digitalocean glad i did this yesterday!

@robaldred @JaimeIniestaDev @willtew @heroku Migrating to @digitalocean as we speak 🫣

@heroku same issue as yesterday. Can't access my apps. All based in EU region :(

@andyinthecloud @heroku @Devoxx I hope they discussed the unacceptable downtime that occurred yesterday

This conference is packed full of great speakers and the cinema venue is perfect! The @heroku team are getting ready for another fantastic day @DevOxx Belgium!

@heroku Hi, could we have a post-mortem of yesterday's incident, why did it take you 1h+ to report the ongoing incident ? Why did it take almost 5h to resolve it ? What happened and what measure did you take to avoid this from happening again.

@herokustatus That's it? this is all we get? What was the issue? How will you fix all the broken trusts with our customers? 4+ hours downtime.. insanity! @salesforce @heroku

Resolved: Routing failures on Common Runtime, EU region status.heroku.com/incidents/2684

@dbdebarros @digitalocean @heroku annoying part is that now i have to move 300 subdomain configs to DO, i hope i can find an API that lets me do that

@whyhammoud @digitalocean @heroku Consider using DOs app platform as a good heroku alternative.

Currently migrating to @digitalocean after 3+ hours of downtime in @heroku and zero communication! #heroku #digitalocean #PaaS

@robaldred @herokustatus no, and currently working not to be on heroku at all.. already migrated some of our frontend apps to @digitalocean

Update: Routing failures on Common Runtime, EU region status.heroku.com/incidents/2684

@asksalesforce can you at least communicate the issue with us? estimate time to be up and running again? is it possible and how can we maybe switch to another region until the issue is fixed?

@whyhammoud I have shared the feedback with the team & we are looking into it. ^PK

That’s it. After over 3 hours of downtime, we’re officially done with @heroku. We can't afford to keep our business at the mercy of a platform that can’t ensure stability or even communicate issues in a timely manner. @herokustatus @salesforce

@heroku @herokustatus @salesforce Our business demands reliability, and this outage was the final straw. Time to move to a platform that takes uptime seriously! #heroku #herokuoutage

@InharAldalur @heroku i had an incident 2 months ago with theri heroku postgres.. with 2 major incidents and downtime, its time to leave heroku once and for all!

@heroku is the perfect example of not evolving product... one day was nice but now it's terrible... moving fisify servers to another provider soon

@acoelhosantos @heroku @herokustatus completely unacceptable.. i don't have no info to communicate with our customers.. for them, our system is down.. i have no idea how we are going to fix the broken trust! 3 hours, WOW

@heroku @herokustatus 3h and still the routing issues persist. Can you share more about the investigation? What are the likely causes, what are your mitigations, what are possible solutions? Estimated full recovery time?

@JuraszekMateusz @heroku @herokustatus unbelievable! i wonder if they will provide us a proper explanation at one point!

@heroku @herokustatus "Engineers are still monitoring the issue. We'll update as we have more details." I am monitoring the issue, my entire team is monitoring the issue and our users are monitoring the f* issue. You could start fixing the issue, please.

@asksalesforce @asksalesforce @salesforce @heroku @herokustatus how is this response helpful really?? heroku status has been sharing the same message since the start of the incident!!!

@whyhammoud Hi, I apologize for any interruptions to your service. Please visit sforce.co/4dGJHkx for updates. ^RG

🚨 Almost 2 hours of downtime on Heroku and they didn’t even report the issue on the status page until an hour after it occurred?! This is unacceptable! @heroku @herokustatus @salesforce