Skip to main content
awsdown

Is Amazon SQS down?

OperationalLast checked Jul 12, 2026, 4:39 AM UTC

Last 90 days

100% uptime · 1 incident
2026-04-14: operational2026-04-15: operational2026-04-16: operational2026-04-17: operational2026-04-18: operational2026-04-19: operational2026-04-20: operational2026-04-21: operational2026-04-22: operational2026-04-23: operational2026-04-24: operational2026-04-25: operational2026-04-26: operational2026-04-27: operational2026-04-28: operational2026-04-29: operational2026-04-30: operational2026-05-01: operational2026-05-02: operational2026-05-03: operational2026-05-04: operational2026-05-05: operational2026-05-06: operational2026-05-07: operational2026-05-08: operational2026-05-09: operational2026-05-10: operational2026-05-11: operational2026-05-12: operational2026-05-13: operational2026-05-14: operational2026-05-15: operational2026-05-16: operational2026-05-17: operational2026-05-18: operational2026-05-19: operational2026-05-20: operational2026-05-21: operational2026-05-22: operational2026-05-23: operational2026-05-24: operational2026-05-25: operational2026-05-26: operational2026-05-27: operational2026-05-28: operational2026-05-29: operational2026-05-30: operational2026-05-31: operational2026-06-01: operational2026-06-02: operational2026-06-03: operational2026-06-04: operational2026-06-05: operational2026-06-06: operational2026-06-07: operational2026-06-08: operational2026-06-09: operational2026-06-10: operational2026-06-11: operational2026-06-12: operational2026-06-13: operational2026-06-14: operational2026-06-15: operational2026-06-16: degraded2026-06-17: operational2026-06-18: operational2026-06-19: operational2026-06-20: operational2026-06-21: operational2026-06-22: operational2026-06-23: operational2026-06-24: operational2026-06-25: operational2026-06-26: operational2026-06-27: operational2026-06-28: operational2026-06-29: operational2026-06-30: operational2026-07-01: operational2026-07-02: operational2026-07-03: operational2026-07-04: operational2026-07-05: operational2026-07-06: operational2026-07-07: operational2026-07-08: operational2026-07-09: operational2026-07-10: operational2026-07-11: operational2026-07-12: operational
2026-04-142026-07-12

What Amazon SQS does - and how it fails

This AWS service is monitored continuously - the status above reflects our latest check of AWS health data for it. Incidents typically surface as elevated error rates or latency in a single region before they appear anywhere else.

  • Elevated error rates or latency in a single region
  • Partial impairment affecting a subset of API operations
  • Upstream dependency incidents (networking, IAM, storage) surfacing here

Recent Amazon SQS incidents

  • Message delivery delays for SQS in us-west-2

    June 16, 2026 · 1h

    A subset of SQS queues in US West (Oregon) experienced increased delivery latency for ~1 hour.

Full analyses live in the post-mortem archive.

Amazon SQS questions

Is this service down right now?

The live status at the top of this page reflects the most recent health check. If it shows Operational but you see errors, the issue may be limited to your region, account, or configuration.

Can downtime on this service earn an SLA credit?

Most AWS services carry a tiered SLA paying 10–100% of the month’s charges when monthly uptime drops below the committed target. Credits must be claimed through AWS Support within roughly 60 days.

Get alerted when Amazon SQS breaks

Instant email the moment we detect an incident - affected services and regions included.

Get outage alerts