- Level
- confirmed
- Worst impact
- Degraded
- Components
- BEDROCK
- Regions
- us-east-1
- Down Index
- 53of 100
What to do
Check whether you use AWS BEDROCK in us-east-1. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 2d 16h it lasted.
Anything that failed between 2026-06-13 01:26 UTC and 2026-06-15 18:13 UTC may need a replay.Subscribe to AWS's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=aws works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from AWS 2
- investigating
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 Opus 4.8, are not affected and you can continue using them in full confidence. Please view the Anthropic statement for further details.
provider
- investigating
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 .
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-d50192452d
Is AWS still down?
No, this incident was resolved 2026-06-15 18:13 UTC. For AWS's live state, see https://down.guide/aws.
How long did it last?
2d 16h, from 2026-06-13 01:26 UTC to 2026-06-15 18:13 UTC, by the times AWS posted.
What was affected?
AWS named BEDROCK in us-east-1.
What caused it?
AWS hasn't published a root cause. If it does, it shows here.
Where does this come from?
AWS's official status page, https://health.aws.amazon.com/health/status, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.