CompaniesAmazon Web ServicesMonthly reportsFebruary 2026
Amazon Web Services in February 2026: incidents, uptime and changes
4incidents posted
0labelled major or critical
100%free of major/critical
98.32%free of any incident
0price changes
0notable page changes
Vendor-reported outage time 0 min, incident time 11 h 16 min. Derived from the incidents the vendor posted on its own status page, not measured by us. A minute counts as an outage minute when a major or critical incident (as the vendor labelled it) was open; incident minutes include minor ones too. Maintenance and incidents marked "no impact" are left out, overlapping incidents are merged, a resolved incident counts for at most 7 days, and one still open with no resolution counts for at most 24 hours. Last 90 days.
By vendor label: Minor 4
Incidents 4
| Incident | Impact | Started | Duration | Status | Day |
|---|---|---|---|---|---|
| Network Connectivity (sa-east-1) | Minor | 0 min | resolved | 02-07 | |
| Increased Error Rates and Latencies (global) | Minor | 7.1 h | resolved | 02-10 | |
| AWS Direct Connect connectivity loss (us-east-1) | Minor | 1.6 h | resolved | 02-21 | |
| Intermittent missing or delayed EC2 instance and status check metrics (us-east-1) | Minor | 2.6 h | resolved | 02-25 |
CVEs published
- CVE-2026-1777 Cleartext transmission of sensitive materials in aws/sagemaker-python-sdk (CVSS 7.2)
- CVE-2026-1778 TLS disabled by default in select aws/sagemaker-python-sdk configurations (CVSS 5.9)
Cite this
Amazon Web Services posted 4 status incidents in February 2026 (0 major or critical); 0 price changes and 0 notable page changes observed.
- Title
- Amazon Web Services in February 2026
- Vendor
- Amazon Web Services
- Date
- URL
- https://rewindex.com/company/aws/2026/02