EM-20261104-ASAW
OutageHigh severity
AWS: Network Connectivity Drop
Nov 4, 2026 · Provider · reported by IODA (Georgia Tech), Provider status pages (Statuspage)
Status
Confirmed
Since : 1 provider status page acknowledged it.
- First Signal
- Nov 04 09:35 UTCC111 IODA (Georgia Tech)
- Page Born
- Nov 04 12:08 UTCsecond source joined
- Last Signal
- Nov 04 12:08 UTC58 min before snapshot
- Sources
- 21 official · 1 research, news or crowd
- Lasted
- 3 hoursso far
Life Of This Page
- 1BornA second, independent provider or measurement sees it.
- 2DevelopingReports and measurements join.
- 3Confirmed · NowA provider status page acknowledges it.
- 4ResolvedNot yetEvery provider marks it resolved and 6 hours pass quietly, or 24 hours pass with no new signal.
- 5ArchivedNot yet30 days after resolved. Read only; the link keeps working. Reopens if it comes back.
The address and ID never change. A correction is logged, never overwritten. If two pages turn out to be one incident, the later one points to the earlier.
Outage Lifecycle
- First Report: reachedNov 04 09:35 UTCC111 IODA (Georgia Tech)
- Corroborated: reachedNov 04 12:08 UTC2 independent sources
- Acknowledged: reachedNov 04 12:08 UTCC123 status page
- Network Check: not yetNot yetNo network data for this provider
- Restored: not yetNot yetStill open
Timeline
Point at a mark to read it. Squares are signals, colored by severity; every one is also listed under Signals.
Signals
- Ela tic: mOLTP PrivateLink connectivity i ue (opens source in a new tab) investigating. All private link traffic for AWS and Azure going to the Serverless intake-v2 endpoint (`.apm`) is not being accepted at the moment. Non private link traffic is flowing normally. We're working on a solution… High severityProvider StatusC123 Provider status pages (Statuspage)
- Connectivity drop: AMAZON-02 -- Ontario (Amazon.com, Inc.) (opens source in a new tab) 2 IODA alerts in 6 hours (1 critical), signals: bgp. Entity type: geoasn. Med severityMeasurementC111 IODA (Georgia Tech)