← Back to context

Comment by otterley

3 hours ago

> One more than one occasion there are AWS URLs, including redirects inside the console, that include US East 1 in the URL that were only spotted during an outage. Manually changing it to an different region allowed us to get around it

Yeah, that tracks. The Console has often been wonky like that.

> I've seen US East 1 outages cause autoscaling issues in other regions including failing to start new EC2s

Do you mean scaling failed due to insufficient capacity, or something else? ICE errors I get (thundering herd of attempted capacity shifting); but otherwise, that sounds implausible, and I respectfully believe you are mistaken about cause and effect. Happy to evaluate a causal chain of evidence that proves you correct, though.

> I respectfully believe you are mistaken about cause and effect

You are allowed to be wrong.

  • I am, but I need to be convinced of my mistake here, given my internal knowledge of how EC2 works.

    How do you know for certain that they are causally connected? Take me through it.

    • My documentation for events from 2018 at this point are limited, and trying to go back through the lists of events demonstrates the limited reporting for some things deemed "non-critical" such as the early 2019 connectivity issues with EU West 2 when the London fibres were cut and services such as Workspaces experienced an outage.

      I will do better at saving exact details for internet strangers in future.