AWS SageMaker Outage History
10 incidents recorded over the last 365 days, 8 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 SageMaker Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Jul 15, 2026 | AWS Service Issue in eu-central-1Elevated connectivity issues with a single Avalability zone | 2h 13m | Resolved |
| Jun 30, 2026 | AWS Service Issue in eu-north-1Increased Error Rates and Latencies | 51 min | Resolved |
| May 8, 2026 | AWS Service Issue in us-east-1Increased Error Rate and Latency | 26h 38m | Resolved |
| Mar 7, 2026 | AWS Service Issue in eu-central-2Increased Error Rates | 1h 10m | 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 |
| Jan 28, 2026 | AWS Service Issue in eu-west-1Elevated latencies for network change propagation | 2h 8m | Resolved |
| Oct 20, 2025 | AWS Service Issue in us-east-1Increased Error Rates and Latencies | 15h 42m | Resolved |
| Sep 25, 2025 | AWS Service Issue in eu-north-1SQS Increased API Error Rates | 7h 28m | Resolved |
| Sep 11, 2025 | AWS Service Issue in us-east-1Increased API Error Rates | 30 min | Resolved |
How to Read This AWS SageMaker 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 AWS SageMaker 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 AWS SageMaker outage in this window ran 1d 2h, against a mean recovery of 7h 5m. If you depend on AWS SageMaker 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.