AWS Bedrock Outage History
5 incidents recorded over the last 365 days, 3 of them resolved, 2 still open. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded AWS Bedrock Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Jun 13, 2026 | AWS Service Issue in us-east-1Fable 5 and Mythos 5 Access | 64h 46m | Resolved |
| Apr 27, 2026 | AWS Service Issue in eu-west-3Increased Connectivity Issues | 38 min | Resolved |
| Mar 2, 2026 | AWS Service Issue in me-south-1Increased Error Rates | — | Investigating |
| Mar 1, 2026 | AWS Service Issue in me-central-1Increased Error Rates | — | Investigating |
| Oct 20, 2025 | AWS Service Issue in us-east-1Increased Error Rates and Latencies | 15h 42m | Resolved |
How to Read This Amazon Bedrock Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Amazon Bedrock acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Amazon Bedrock outage in this window ran 2d 16h, against a mean recovery of 1d 3h. If you depend on Amazon Bedrock in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.