Heroku: We’ve Heard Your Feedback
blog.heroku.com
Heroku: We’ve Heard Your Feedback
1–10 of 151 posts
Re: Heroku: We’ve Heard Your Feedback
#2Posting this at 5pm on a Friday sounds about right, yeah?
Re: Heroku: We’ve Heard Your Feedback
#3Heroku has always been the opposite of transparent.
I still don't forget how they handled the Intelligent Routing fiasco from back in the day.
Re: Heroku: We’ve Heard Your Feedback
#4> I started as Heroku GM a few weeks ago with intense enthusiasm to be a part of such a storied team.
Wow talk about terrible timing.
Re: Heroku: We’ve Heard Your Feedback
#5Posting this at 5pm on a Friday sounds about right, yeah?
That isn’t a very charitable take. It’s been 24x7 for them, the acknowledgement is most welcome, in my opinion. I’m not sure waiting until Monday 9AM Pacific just to avoid these type of comments would be the right choice. The internet is 24x7 after all.
Re: Heroku: We’ve Heard Your Feedback
#6>The Heroku team and their colleagues have worked around the clock, including nights and weekends
Can someone more familiar with an event like this tell me what they are working so hard on? I imagine securing the vulnerable service and resetting various credentials doesn't take that much work.
Re: Heroku: We’ve Heard Your Feedback
#7Heroku has always been the opposite of transparent. I still don't forget how they handled the Intelligent Routing fiasco from back in the day.
Maybe that’ll change, there’s a new Sheriff in town as the saying goes? Bob was previously General Manager of AWS Elastic Kubernetes (EKS) which seemed to have a good reputation and to engage with its customers pretty well.
Re: Heroku: We’ve Heard Your Feedback
#8>The Heroku team and their colleagues have worked around the clock, including nights and weekends Can someone more familiar with an event like this tell me what they are working so hard on? I imagine securing the vulnerable service and resetting various credentials doesn't take that much work.
One quick example: combing through logs which can go back months or years can be expensive in time, especially if those are stored in something like Glacier and need to be pulled back into a system which permits analysis.
Re: Heroku: We’ve Heard Your Feedback
#9Posting this at 5pm on a Friday sounds about right, yeah?
That isn’t a very charitable take. It’s been 24x7 for them, the acknowledgement is most welcome, in my opinion. I’m not sure waiting until Monday 9AM Pacific just to avoid these type of comments would be the right choice. The internet is 24x7 after all.
[deleted]
Re: Heroku: We’ve Heard Your Feedback
#10>The Heroku team and their colleagues have worked around the clock, including nights and weekends Can someone more familiar with an event like this tell me what they are working so hard on? I imagine securing the vulnerable service and resetting various credentials doesn't take that much work.
Besides that, lots of incident response work to figure out the scope and impact of the breach, I'd imagine.