Independent monitoring
Amazon Web Services status
OperationalMerlonix has monitored Amazon Web Services around the clock and recorded every status change we observed. Below is a 30-day timeline of those observations and any incidents Amazon Web Services reported.
Snapshot as observed by Merlonix at Sep 11, 2026, 08:30 AM UTC. This is a point-in-time snapshot, not real-time — see the live vendor board for the current minute-by-minute status.
30-day observation timeline
Each cell is one UTC day, coloured by the most severe status we observed that day. A “degraded” day reflects Amazon Web Services’s own published component-level status and may mean a single component was affected while the overall service was fine.
Observations recorded
34
distinct status changes over 28 days we have data for
Most recent change
Sep 6, 2026
last time the observed status changed
Days by observed status
- Operational6d
- Major outage22d
What Merlonix monitors for Amazon Web Services
Merlonix polls Amazon Web Services's published status source around the clock and records every change we observe — overall status, component-level incidents, and their start/resolve times. The timeline and incidents below are Merlonix's own observations, sampled independently of Amazon Web Services.
Recent incidents Amazon Web Services reported
Service disruption: Increased Error Rates
majorScope: Increased Error Rates
Service disruption: Increased Connectivity Issues and API Error Rates
majorScope: Increased Connectivity Issues and API Error Rates
Service impact: Increased Connectivity Issues and API Error Rates
Scope: Increased Connectivity Issues and API Error Rates
Service disruption: Increased Error Rates
majorScope: Increased Error Rates
Service impact: Increased Connectivity Issues and API Error Rates
Scope: Increased Connectivity Issues and API Error Rates
Get alerted the moment Amazon Web Services has a bad day.
Merlonix watches Amazon Web Services and your other upstreams around the clock and suppresses the false alerts they would otherwise trigger on your own sites — so you only get paged when the problem is actually yours.
Other vendors we monitor