Major outage Amazon Web Services status
aws.amazon.com · AWS Health Dashboard (public current events)
FROM ALL SOURCES
Amazon Web Services' status page shows “Major outage” in UAE and Bahrain; the vendor is ongoing. User reports haven't spiked, so wide impact isn't visible yet.
confidence: medium Vendor: major issue · users: normal · routing: no data.
- Vendor status page Major outage · 2 open incidents
- User reports 0 in 15 min vs ~0 typical
- Routing / BGP AS16509: routing data not loaded on this view
- News & network weather 1 active / 3 recent mentions
- Providers it may run on (inferred) no mapped dependencies
- CISA KEV (context) no recent entries for this vendor
Regions mentioned: UAE, Bahrain
| Clock | Started | Running |
|---|---|---|
| Vendor clock when the vendor's open incident started | 264 days | |
| Crowd clock when user reports began rising above normal | not seen | n/a |
| Network clock when routing anomaly data first flagged it | not seen | n/a |
| ORBIT clock when our checker first recorded the change | 14 h 56 min |
Evidence
- Official page: Major outage (“2 open events on the AWS Health Dashboard”). evidence confidence: high
- Vendor stage: ongoing on “Multiple services: Region Availability (UAE)”. evidence confidence: high
- User reports are within normal range (0 in 15 min). evidence confidence: low
- 1 active network-weather event mentions Amazon Web Services. Overlap in time is coincidence, not causation. evidence confidence: low
What we don't know: what is happening inside Amazon Web Services' own systems, how many users are actually affected (reports are self-selected and unverified), and anything from routing / bgp, providers it may run on (inferred). Routing data shows reachability, not whether the app works.
Coincidence, not causation: signals that overlap in time are shown side by side, not as proof of cause.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Generated .
Cloudy_Day's take
Stage vs. health
The vendor's stage is “ongoing”. Stage tells you where they are in their process; health is what users experience. Right now vendor: major issue · users: normal · routing: no data. Vendor reports an issue we don't see in crowd or routing data (it may be partial or internal).
Who depends on whom
136 other services in our catalog may lean on Amazon Web Services, so trouble here can show up elsewhere first. Dependency chains are where single points of failure hide.
Identity & trust lens
Even without an identity system involved, outages push people toward workarounds: password resets, unofficial apps and “status” links in DMs. Each one is a trust decision. Use official channels.
For users
Check the official status page before changing settings or reinstalling. If you must act, use known-good bookmarks. Reporting what's broken on ORBIT helps everyone see the real footprint.
For security teams
Treat this as an availability event unless an official source says otherwise. Check which of your systems sit on Amazon Web Services, watch for outage-themed phishing aimed at your users, and log what you see with timestamps (all four clocks).
What to watch next
The vendor stage moving to “monitoring”, then “resolved”; the user-report curve falling back under baseline; and whether dependents start reporting issues.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Independent researcher; not affiliated with Amazon Web Services. No blame or attack claims without an official source. Generated .
ORBIT score
Severe storm
- official status: Major outage
Official status
Major outage Major outage
2 open events on the AWS Health Dashboard
Multiple services: Region Availability (UAE) major ongoing · started
Affects: UAE
Multiple services: Region Availability (Bahrain) major ongoing · started
Affects: Bahrain
From AWS Health Dashboard (public current events) · official page ↗
User reports
0 in the last 15 min
Typical: 0 per 15 min (24 h baseline) · 0 in 24 h
Network weather mentions
- AWS Bahrain: Multiple services — Region Availability Official incident (vendor status page) · chronic
- AWS UAE: Multiple services — Region Availability Official incident (vendor status page) · chronic
- AS16509 (AWS) BGP update churn +7.2σ vs 24h Technical measurement · active
From NetWeather's public sources. Shown for context: coincidence, not causation.
How to read this: official status comes from each provider's own public status page. User reports are unverified visitor reports. Things that happen at the same time are coincidence, not causation. Cloudy_Day is independent and not an official status source for any company listed.