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.

Live AWS SageMaker status96.72% uptime history

Every Recorded AWS SageMaker Incident

AWS SageMaker incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 4, 2026AWS Internet Connectivity Issue in eu-south-2Elevated packet loss2h 41mResolved
Sep 21, 2026Amazon Elastic Compute Cloud Issue in us-east-1Increased Error Rates57 minResolved
Jul 15, 2026AWS Service Issue in eu-central-1Elevated connectivity issues with a single Avalability zone2h 13mResolved
Jun 30, 2026AWS Service Issue in eu-north-1Increased Error Rates and Latencies51 minResolved
May 8, 2026AWS Service Issue in us-east-1Increased Error Rate and Latency26h 38mResolved
Mar 7, 2026AWS Service Issue in eu-central-2Increased Error Rates1h 10mResolved
Mar 2, 2026AWS Service Issue in me-south-1Region Availability—Investigating
Mar 1, 2026AWS Service Issue in me-central-1Region Availability—Investigating
Jan 28, 2026AWS Service Issue in eu-west-1Elevated latencies for network change propagation2h 8mResolved
Oct 20, 2025AWS Service Issue in us-east-1Increased Error Rates and Latencies15h 42mResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next AWS SageMaker incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

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 6h 33m. 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.