Transit gateway or network interconnect

Cases, by severity

1. IL-0362 PagerDuty could not dispatch notifications for 18 minutes when a peering point shared by two AWS regions degradedPagerDuty · 2013 · sev1

   Root cause Cloud provider outage

2. IL-0349 IONOS Private Cloud in Berlin lost management access, storage and VM internet routing after a VLAN changeIONOS Cloud · 2026

   Root cause Operator error

3. IL-0341 Traffic between Cloudflare and AWS us-east-1 had high latency, packet loss and origin failures for almost four hoursCloudflare · 2025

   Root cause Capacity exhaustion

4. IL-0361 Job searches on seek.com.au failed for 16 minutes as a Transit Gateway silently dropped 9001-byte packetsSEEK · 2021

   Root cause Configuration change

5. IL-0223 A connection surge congested the devices between AWS's internal and main networks in us-east-1, breaking EC2 APIsAmazon Web Services · 2021

   Root cause Software defect

6. IL-0336 AWS Direct Connect traffic into the Tokyo Region had packet loss and intermittent connectivity for about six hoursAmazon Web Services · 2021

   Root cause Software defect

7. IL-0220 An overloaded AWS Transit Gateway dropped packets on 4 January 2021, and Slack's web tier saturated and went downSlack · 2021

   Root cause Cloud provider outage