Skip to main content

Independent monitoring

Amazon Web Services status

Operational

Merlonix has monitored Amazon Web Services around the clock and recorded every status change we observed. Below is a 30-day timeline of those observations, followed by incident and maintenance details from the latest recorded snapshot.

Snapshot as observed by Merlonix at Oct 17, 2026, 08:31 AM UTC. This is a point-in-time snapshot, not real-time — see the live vendor board for the current minute-by-minute status.

Independent monitoring by Merlonix. Not affiliated with, endorsed by, or an official status page of Amazon Web Services. All observations are Merlonix’s own, sampled independently from Amazon Web Services’s published status source. Amazon Web Services is a trademark of its respective owner and is named here only to describe what we monitor.
We’ve recorded only 8 status observations for Amazon Web Services so far — not yet enough history to publish a full, dependable 30-day record. The timeline below shows what we have; treat it as preliminary.

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.

OperationalDegradedPartial outageMajor outageMaintenanceNo data

Observations recorded

8

distinct status changes over 26 days we have data for

Most recent change

Oct 5, 2026

last time the observed status changed

Days by observed status

  • Operational24d
  • Degraded2d

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.

Incidents and maintenance in the latest snapshot

Entries from Amazon Web Services’s latest recorded status snapshot may include active incidents, resolved notices or scheduled maintenance.

For incident counts and recent examples across the historical window, read the 30-day vendor status digest. The digest has its own dated snapshot and counts scheduled maintenance separately.

Reduce alert noise during Amazon Web Services incidents.

When a monitored asset has Amazon Web Services listed as a dependency, Merlonix suppresses its alert notifications while the vendor reports degradation or an outage. The alert stays visible in your dashboard.

How vendor-aware alerting works →