Amazon Marketplace Web Service Outage History

Amazon Marketplace Web Service partial outage · 2 active incidents View live status →

Amazon Marketplace Web Service had 12 outages in the last 2 years totaling 2966h 29m of downtime — averaging 0.5 incidents per month.

There were 12 Amazon Marketplace Web Service outages since March 1, 2026 totaling 2966h 29m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.aws.amazon.com

Major June 13, 2026

Amazon Bedrock — N. Virginia: [RESOLVED] Fable 5 and Mythos 5 Access

Detected by Pingoru
Jun 13, 2026, 01:26 AM UTC
Resolved
Jun 16, 2026, 06:05 PM UTC
Duration
3d 16h
Affected: Amazon Bedrock — N. Virginia
Timeline · 2 updates
  1. monitoring Jun 13, 2026, 01:26 AM UTC

    To support compliance with the US Government export control directive, Anthropic has asked us to revoke access to Claude Fable 5 and Claude Mythos 5 for all users in all regions. All other models, including Opus4.8, are not affected and you can continue using them in full confidence. Please view the Anthropic statement for further details: https://www.anthropic.com/news/fable-mythos-access

  2. monitoring Jun 15, 2026, 06:13 PM UTC

    Claude Fable 5 and Claude Mythos 5 models remain unavailable for all users in all regions. We are resolving this Health event. For further details please view the Anthropic statement .

Read the full incident report →

Major June 6, 2026

AWS Internet Connectivity — Sao Paulo: [RESOLVED] Internet Connectivity Issues

Detected by Pingoru
Jun 06, 2026, 04:24 AM UTC
Resolved
Jun 07, 2026, 04:21 AM UTC
Duration
23h 56m
Affected: AWS Internet Connectivity — Sao Paulo
Timeline · 1 update
  1. monitoring Jun 06, 2026, 04:24 AM UTC

    Between 5:50 PM and 7:15 PM PDT, we experienced connectivity issues that may have impacted Internet performance for some customers in the SA-EAST-1 Region. During this time, connectivity to instances and services within the Region was not affected. Our engineering team was automatically engaged at 5:51 PM PDT and immediately began investigating the issue. We identified the root cause and implemented a fix, which mitigated the issue at 7:15 PM PDT. The issue has been resolved and the service is operating normally.

Read the full incident report →

Minor June 6, 2026

INTERNETCONNECTIVITY — sa-east-1: Service impact: Internet Connectivity Issues

Detected by Pingoru
Jun 06, 2026, 04:24 AM UTC
Resolved
Jun 06, 2026, 04:24 AM UTC
Duration
Affected: INTERNETCONNECTIVITY — sa-east-1
Timeline · 1 update
  1. resolved Jun 06, 2026, 04:24 AM UTC

    Between 5:50 PM and 7:15 PM PDT, we experienced connectivity issues that may have impacted Internet performance for some customers in the SA-EAST-1 Region. During this time, connectivity to instances and services within the Region was not affected. Our engineering team was automatically engaged at 5:51 PM PDT and immediately began investigating the issue. We identified the root cause and implemented a fix, which mitigated the issue at 7:15 PM PDT. The issue has been resolved and the service is operating normally.

Read the full incident report →

Major May 22, 2026

Amazon Route 53: [RESOLVED] Increased API Error Rates

Detected by Pingoru
May 22, 2026, 11:38 PM UTC
Resolved
May 24, 2026, 12:11 AM UTC
Duration
1d
Affected: Amazon Route 53
Timeline · 2 updates
  1. monitoring May 22, 2026, 11:38 PM UTC

    We are investigating increased error rates for Route53 API calls.

  2. monitoring May 23, 2026, 12:13 AM UTC

    Between 4:00 PM and 4:46 PM, we experienced increased error rates for the Route53 APIs. This issue did not impact resolution of existing DNS records. Engineers were automatically engaged and immediately began investigating the issue. During this time, customers may have received 500s for Route53 APIs and the Route53 Management Console. We have identified the root cause and have mitigated this issue. Other AWS Services that call the Route53 APIs in their workflows may also have been impacted during this time. We recommend retrying any failed operations or stuck workflows. We do not expect recurrence of this issue. The issue has been resolved and the service is operating normally.

Read the full incident report →