4 ms·
Just to verify my understanding: * This is a multi-region (us-east1, us-central1, europe-west1, asia-northeast1 and asia-east1) outage (yeesh) * Incident bega
by gtaylor 9y ago
Just to verify my understanding:
* This is a multi-region (us-east1, us-central1, europe-west1, asia-northeast1 and asia-east1) outage (yeesh)
* Incident began at Incident began at 2017-08-29 18:35 PDT. At the time of this comment, we're over 13 hours (??)
Correct?
- leesalminen 9y agoFor what it's worth, my load balancer in us-central-1 is unaffected.
- Thaxll 9y agoDoesn't seems to affect that much?
- Danack 9y agoI can't comment as to multi-region, but we saw issues last night at around 6pm UTC, which look similar to the ongoing issues we are seeing.
- jlgaddis 9y agoThe status page linked to here says that the issue spans multiple regions (across multiple continents!).
- wwayer 9y agoIt's now past 12:00 US/Pacific and the incident is still ongoing. I'm thinking that they don't have as many customers as they'd like us to believe. There's been very little discussion and no outrage. If AWS had an incident lasting this long, there would be a lot more noise.
- user5994461 9y agoIf AWS had an incident this long, there would be no noise and no public post about it. And the customer support would keep repeating have you try buying bigger instances?
- cloudcomp 9y agoI think you're alone on this opinion