Is Amazon Web Services down?

Last checked 1m ago
Current status
Amazon Web Services is having a partial outage

2 active incidents: Multiple services — Bahrain: Increased Connectivity Issues…, Multiple services — UAE: Increased Error Rates

Get alerts when Amazon Web Services breaks →

Free · no credit card

Official status page: https://status.aws.amazon.com · Polled every 5 minutes · 9053 components tracked

Real-time Amazon Web Services status, recent outages, and incident history — pulled directly from Amazon Web Services's official status page at https://status.aws.amazon.com every 5 minutes. Pingoru tracks 9053 Amazon Web Services services and has captured 40 incidents in the last 90 days (100.00% uptime). Get email, Slack, Discord, or webhook alerts the moment Amazon Web Services reports a new incident — free for 5 monitors, no credit card.

Users who monitor Amazon Web Services also follow these Cloud Infrastructure services: DigitalOcean Cisco Umbrella Wasabi Vercel Hetzner HashiCorp Egnyte Dyn Genesys Cloud Linode View all 6,000+ providers
Amazon Web Services uptime 100.00% uptime · past 90 days
Mon Wed Fri
JanFebMarApr
Less More

Recent outages & incidents

Past 7 days
  1. Amazon Elastic Compute Cloud (EC2) — eu-west-3: Service is operating normally: [RESOLVED] Increased Connectivity Issues
    Resolved 38m
    Started Apr 27, 2026, 11:27 AM UTC · Resolved Apr 27, 2026, 12:05 PM UTC
    Amazon Elastic Compute Cloud (EC2) — eu-west-3
    2 updates · show timeline
    • monitoring · Apr 27, 2026, 11:27 AM UTC

      We are investigating instance connectivity issues in a single Availability Zone (euw3-az2) in the EU-WEST-3 Region.

    • resolved · Apr 27, 2026, 12:05 PM UTC

      Between 3:58 AM and 4:40 AM PDT, we experienced increased error rates and increased launch failures for EC2 instances in a single Availability Zone (euw3-az2) in the EU-WEST-3 Region. During this time, customers attempting to launch new EC2 instances in the affected Availability Zone would have experienced launch failures. Additionally, a subset of existing EC2 instances and EBS volumes in this Availability Zone were impacted and became unreachable. We have identified the root cause to be a loss of power to infrastructure within the affected Availability Zone. Engineers were engaged at 4:02 AM and immediately began working to restore power and assess the scope of impact. By 4:20 AM, power was successfully restored to the affected infrastructure. We then focused our efforts on recovering impacted EC2 instances and EBS volumes. By 4:40 AM, all impacted EC2 instances and EBS volumes had been fully recovered and were operating normally. No additional action is required for EC2 instances and EBS volumes that were impacted during the power loss event, as these have been fully recovered. The issue has been resolved and the service is operating normally.

    Latest: Between 3:58 AM and 4:40 AM PDT, we experienced increased error rates and increased launch failures for EC2 instances in a single Availability Zone (euw3-az2) in the EU-WEST-3 Regi…

  2. Amazon Elastic Compute Cloud — Paris: [RESOLVED] Increased Connectivity Issues
    Resolved 1d 5h
    Started Apr 27, 2026, 11:27 AM UTC · Resolved Apr 28, 2026, 05:02 PM UTC
    Amazon Elastic Compute Cloud — Paris
    2 updates · show timeline
    • monitoring · Apr 27, 2026, 11:27 AM UTC

      We are investigating instance connectivity issues in a single Availability Zone (euw3-az2) in the EU-WEST-3 Region.

    • monitoring · Apr 27, 2026, 12:05 PM UTC

      Between 3:58 AM and 4:40 AM PDT, we experienced increased error rates and increased launch failures for EC2 instances in a single Availability Zone (euw3-az2) in the EU-WEST-3 Region. During this time, customers attempting to launch new EC2 instances in the affected Availability Zone would have experienced launch failures. Additionally, a subset of existing EC2 instances and EBS volumes in this Availability Zone were impacted and became unreachable. We have identified the root cause to be a loss of power to infrastructure within the affected Availability Zone. Engineers were engaged at 4:02 AM and immediately began working to restore power and assess the scope of impact. By 4:20 AM, power was successfully restored to the affected infrastructure. We then focused our efforts on recovering impacted EC2 instances and EBS volumes. By 4:40 AM, all impacted EC2 instances and EBS volumes had been fully recovered and were operating normally. No additional action is required for EC2 instances and EBS volumes that were impacted during the power loss event, as these have been fully recovered. The issue has been resolved and the service is operating normally.

    Latest: Between 3:58 AM and 4:40 AM PDT, we experienced increased error rates and increased launch failures for EC2 instances in a single Availability Zone (euw3-az2) in the EU-WEST-3 Regi…

See the full Amazon Web Services outage history

38 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Sign up free to unlock full history

10 free monitors · No credit card

Outage history

Past 30 days · 37 incidents
  • Amazon Elastic Compute Cloud (EC2) — eu-west-3: Service is operating normally: [RESOLVED] Increased Connectivity Issues Resolved
    Started Apr 27, 2026, 11:27 AM UTC · Resolved Apr 27, 2026, 12:05 PM UTC · 38m
  • Amazon Elastic Compute Cloud — Paris: [RESOLVED] Increased Connectivity Issues Resolved
    Started Apr 27, 2026, 11:27 AM UTC · Resolved Apr 28, 2026, 05:02 PM UTC · 1d 5h
  • Service impact: Increased Connectivity Issues and API Error Rates Resolved
    Started Mar 03, 2026, 04:40 PM UTC · Resolved Apr 21, 2026, 06:36 PM UTC · 49d 1h
  • Service disruption: Increased Error Rates Resolved
    Started Mar 03, 2026, 04:14 PM UTC · Resolved Apr 21, 2026, 06:36 PM UTC · 49d 2h
  • Service impact: Increased Connectivity Issues and API Error Rates Resolved
    Started Mar 03, 2026, 02:02 PM UTC · Resolved Apr 21, 2026, 06:36 PM UTC · 49d 4h
  • Service disruption: Increased Error Rates Resolved
    Started Mar 03, 2026, 12:58 PM UTC · Resolved Apr 21, 2026, 06:36 PM UTC · 49d 5h
  • Service impact: Increased Connectivity Issues and API Error Rates Resolved
    Started Mar 03, 2026, 11:10 AM UTC · Resolved Apr 21, 2026, 06:36 PM UTC · 49d 7h
  • Service impact: Increased Connectivity Issues and API Error Rates Resolved
    Started Mar 03, 2026, 06:27 AM UTC · Resolved Apr 21, 2026, 06:36 PM UTC · 49d 12h

See Amazon Web Services in your Pingoru dashboard

Monitor Amazon Web Services alongside every other service your stack depends on — same alerts, same timeline, same calendar — all in one place.

Every status page, one dashboard

Add Amazon Web Services to your Pingoru monitors and it sits next to AWS, Stripe, GitHub, and every other vendor in your stack — a single dashboard for the live status of every cloud and SaaS provider you depend on. One subscription, one inbox, every incident.

Incident timeline, this provider or all of them

Every Amazon Web Services incident — when it started, when it resolved, which services were affected, how bad it was, how long it lasted — laid out in one feed you can scan in 30 seconds. Filter to just Amazon Web Services or see every provider at once.

Maintenance calendar

Scheduled Amazon Web Services maintenance windows land in the same calendar as every other vendor you depend on — see what's running now, what's coming up, and a calendar view. Plan around your vendors instead of being caught out by them.

Every Amazon Web Services status change, one inbox

Pingoru watches Amazon Web Services's official status page every 5 minutes and delivers incident, resolution, and maintenance events to your email, Slack, Discord, Teams, or webhook.

Only alert on the services you use

Amazon Web Services reports on 9053 services. Subscribe to the ones you actually use — everything else stays silent.

Email + Slack + Discord + Teams

Signed webhooks on every plan. Route Amazon Web Services alerts wherever your team already lives — no per-integration billing, no tier-gating the channels that matter.

Maintenance, not surprises

Upcoming Amazon Web Services maintenance windows appear in your maintenance calendar days in advance. Plan deploys and rollouts around them instead of finding out during an incident.

Fine-grained alert control

Per-monitor switches for opened, updated, resolved, and maintenance events. Silence the noisy Amazon Web Services services without silencing the monitor entirely.

Invite your team

Premium includes 10 team seats. Everyone watching Amazon Web Services from the same account, with per-user notification preferences for any monitor.

Get notified on Amazon Web Services status changes

Pingoru watches Amazon Web Services's official status page and sends your team instant alerts when incidents open, change severity, or resolve. Route notifications to email, Slack, Discord, or a webhook — wherever your team already lives.

Start monitoring Amazon Web Services free

Monitor Amazon Web Services along with everything else

Pingoru tracks 6,000+ cloud and SaaS status pages in one dashboard. Add Amazon Web Services and every other provider you depend on — AWS, Stripe, GitHub, Cloudflare, OpenAI — and get a single view of the health of every service your app depends on.

Browse the full service directory

Track Amazon Web Services uptime & incident history

See 90 days of Amazon Web Services uptime at a glance, with every past incident linked to its component and update timeline. Export the history as CSV or JSON for SLA reports, postmortems, or vendor evaluations — data your team actually needs, not marketing numbers.

See Amazon Web Services uptime history

Frequently asked questions

What is Amazon Web Services's uptime?
Over the last 90 days, Amazon Web Services reported 100.00% uptime on its official status page. That figure is calculated from the public incident timeline at https://status.aws.amazon.com — each minute of degraded, partial-outage, or major-outage status counts against the total. Sign up to Pingoru free to see Amazon Web Services's uptime history rolling forward in real time.
Has Amazon Web Services had outages in 2026?
Yes — Amazon Web Services has had 38 incidents reported on its official status page so far in 2026. The full timeline (start times, durations, components affected) is shown above on this page. Pingoru re-checks the status page every 5 minutes so the count stays current.
When was the last Amazon Web Services outage?
The most recent Amazon Web Services incident was "Amazon Elastic Compute Cloud (EC2) — eu-west-3: Service is operating normally: [RESOLVED] Increased Connectivity Issues", which started on April 27, 2026 and was resolved on April 27, 2026. Pingoru captured this directly from https://status.aws.amazon.com. See the full incident card above for affected components and the update timeline.
How often does Amazon Web Services have outages?
Based on the last 90 days, Amazon Web Services averages 12.7 reported incidents per month on its official status page. Pingoru tracks each one with start time, duration, severity, and affected components — so you can see the pattern at a glance instead of digging through the vendor's archive.
Where is Amazon Web Services's status page?
Amazon Web Services's official status page is https://status.aws.amazon.com. Pingoru polls it every 5 minutes and renders the same data here, alongside every other cloud or SaaS provider you depend on — so you can spot multi-vendor incidents (e.g. AWS + Stripe + Cloudflare degrading at the same minute) without flipping between tabs.
Is Amazon Web Services down right now?
Amazon Web Services is having a partial outage. Pingoru checks the official status page every 5 minutes and flips this headline the moment Amazon Web Services reports a change. Current status is based on 9053 tracked services.
How does Pingoru know if Amazon Web Services is down?
We read https://status.aws.amazon.com directly, using Amazon Web Services's own status page. If the vendor reports an incident, you see it within one check cycle — not after someone manually marks the page as down.
Where can I get notified when Amazon Web Services has an outage?
Create a free Pingoru account and add Amazon Web Services as a monitor. You can filter to specific services, pick severity thresholds, and route alerts via email, Slack, Discord, or a webhook.
Amazon Web Services's status page says the service is up, but I'm having issues — what's wrong?
Three common reasons: • A real Amazon Web Services incident that hasn't been acknowledged on their public status page yet — vendor status pages are updated manually and typically lag the first customer reports by 10–30 minutes. • A regional or account-scoped issue affecting a subset of customers — these rarely trigger a global status-page change. • A local problem: ISP / DNS / your own software. Try reproducing from a mobile data connection and from a different network to isolate. If you suspect a real Amazon Web Services issue that isn't reflected yet, contact their support to escalate. Subscribing here means you get the alert the moment they do post an update.
Where does Pingoru get the official Amazon Web Services status?
We use Amazon Web Services's own status page at https://status.aws.amazon.com. Nothing is read in a way the vendor hasn't explicitly made public — we use the same data their own dashboard uses. So our data is as accurate as what you'd see loading the status page yourself, but rolled into one dashboard alongside every other service you depend on.
What does "Partial Outage" mean?
Amazon Web Services has a partial outage — one or more components are down, but the rest of the service is operational.

Stop finding out from your users.

We watch Amazon Web Services's official status page every 5 minutes. The moment they report an incident, you get an email — often before the outage is widely noticed.

Monitor Amazon Web Services free →

10 monitors free · email alerts · no credit card

Want the full picture first? See everything Pingoru does →