13 ms·
Yeah, seems to be Amazon, not Heroku this time.
by webbruce 13y ago
Yeah, seems to be Amazon, not Heroku this time.
- chubot 13y agoNote from last time: https://status.heroku.com/incidents/151 https://status.heroku.com/incidents/151 "This post will reference the AWS services that we use behind the scenes so that we can be very specific. Note that although we will be discussing various AWS service failures, we don't blame them for what our customers experienced in any way. Heroku takes 100% of the responsibility for the downtime affecting our customers last week." In other words, they shouldn't be exposing AWS outages to users (although as as long as they use a single cloud provider that's impossible to avoid in general.)