Live  /  Providers  /  Amazon Web Services

Amazon Web Services

aws.amazon.comNo open incidents

Independent assessment — SquidGrid is not affiliated with Amazon Web Services. Provider-published information is labeled as such; SquidGrid’s own measurements are observations of network paths, not determinations of fault.

Cloud & hosting · SquidGrid tracks Amazon Web Services’s own status and independently measures the internet paths that reach it, so you can tell a provider-side problem from a problem on the route to it.

Public — what Amazon Web Services is reporting

Current & recent incidents

Resolved

[RESOLVED] Elevated packet loss — Spain

2026-10-04 18:56 UTC · source

Resolved

Region Availability — UAE

2026-09-15 10:27 UTC · source

Resolved

Region Availability — Bahrain

2026-09-15 10:22 UTC · source

Incident titles and states as published by the provider. Times in UTC.

Track record

SquidGrid has archived 8 incidents from Amazon Web Services’s own status page since 2026-03-01: 6 in the last 90 days, against 0 in the 90 days before.

Recent incidents in the archive

Computed by SquidGrid from the incidents Amazon Web Services published. Their own page shows only recent history; this archive keeps every one.

Independent path health

A status page tells you what Amazon Web Services has published. SquidGrid independently observes the actual routes from its own worldwide fleet against their own baselines — so when a path moves off its usual range before (or without) a status post, you still see it, and you see where.

SquidGrid’s own measurement fleet is watching 13,636 internet paths that cross Amazon Web Services’s network, observed from 58 countries. At last check (01:30 UTC), every measured path within its usual range. Signed-in customers see which paths, the carrier on each side, and the added latency.

SquidGrid is not affiliated with Amazon Web Services.