MERLONIX

Independent monitoring

Amazon Web Services status

Major outage

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 and any incidents Amazon Web Services reported.

Snapshot as observed by Merlonix at Jul 7, 2026, 06:58 PM 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 10 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

10

distinct status changes over 25 days we have data for

Most recent change

Jul 7, 2026

last time the observed status changed

Days by observed status

  • Major outage25d

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

    major

    Scope: Increased Error Rates

    investigatingsince Apr 30, 2026Amazon Web Services source ↗

  • Service disruption: Increased Connectivity Issues and API Error Rates

    major

    Scope: Increased Connectivity Issues and API Error Rates

    investigatingsince Apr 30, 2026Amazon Web Services source ↗

  • Service impact: Increased Connectivity Issues and API Error Rates

    Scope: Increased Connectivity Issues and API Error Rates

    investigatingsince Mar 3, 2026Amazon Web Services source ↗

  • Service disruption: Increased Error Rates

    major

    Scope: Increased Error Rates

    investigatingsince Mar 3, 2026Amazon Web Services source ↗

  • Service impact: Increased Connectivity Issues and API Error Rates

    Scope: Increased Connectivity Issues and API Error Rates

    investigatingsince Mar 3, 2026Amazon Web Services source ↗

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.

Start free for 14 daysOr start free — $0, no card

How vendor-aware alerting works →

Other vendors we monitor

AnthropicCloudflareGitHubGoogle CloudMicrosoft AzureOpenAIAll vendor status →