Snowflake: AWS - US East2 (Ohio): MI-20220728
AWS us-east-2 outage, Jul 28, 2022 · 25 vendors, 26 incidents
Snowflake’s incident started in the same window without naming AWS (timing only, not evidence of a link). (timing only, posted +4 min vs the first vendor naming AWS)
“…AWS - US East2 (Ohio): MI-20220728 Current status: We've coordinated with our third-party service provider to implement the fix for this issue, and we've monitored the environment to confirm that serv…”
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["AWS us-east-2<br/>own incident not archived"]:::inferred
h1["Within an hour<br/>5 vendors, 2 blamed AWS<br/>Elastic Cloud, Coralogix, Confluent, Aptible +1"]:::blames
root --> h1
h4["1 to 4 hours later<br/>1 vendor, 1 blamed AWS<br/>Stream (GetStream)"]:::blames
root --> h4
me["Snowflake (this incident)<br/>posted +4 min"]:::me
root -.->|"same window"| meFull event: timeline, evidence and all vendors →
Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.
Timeline of updates
- resolved
Current status: We've coordinated with our third-party service provider to implement the fix for this issue, and we've monitored the environment to confirm that service was restored. If you experience additional issues or have questions, please open a support case via Snowflake Community. Customer experience: Customers hosted in the specified regions may have experienced delays while attempting to access or use Snowflake services and features. Incident start time: 09:56 PT July 28, 2022 Incident end time: 12:21 PT July 28, 2022 A root cause analysis (RCA) document will be published within ten business days.
From Snowflake’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Impact, status and times are the vendor’s own, as last archived. View on status.snowflake.com (opens in new tab).