Cloud outage history: AWS, Azure, Google Cloud, Alibaba, Huawei, Tencent
Every incident posted on the official status pages of six clouds, kept as a running log. Including Alibaba, Huawei and Tencent Cloud, which global status trackers skip.
18 incidents logged · updated Nov 22, 2026, 10:34 UTCLive status for all six clouds →
November 2026
InformationalAWS · Nov 15, 2026, 12:38 UTC · 2.3 h
Increased Connectivity issues in US-EAST-1
Multiple servicesus-east-1
InformationalAWS · Nov 15, 2026, 12:38 UTC · 2.3 h
Increased Connectivity issues in US-EAST-1
Between 3:05 AM and 6:10 AM PST we experienced signup errors, authentication issues, and connectivity issues in the US-EAST-1 Region. Customers using IAM Identity Center for authentication into the AWS Console, or for authentication into other AWS Services such as Kiro, Connect, etc would have been affected during this time. Engineers were automatically engaged at 3:10 AM PST and immediately began investigating the root cause, while in parallel working to mitigate both impacts. At 5:20, we fully mitigated the issue affecting authentication, and most AWS Services observed full recovery at th…
Official status page ↗InformationalAWS · Nov 11, 2026, 15:40 UTC · 5.5 h
Elevated API issues and Launch Failures
EC2ap-northeast-1
InformationalAWS · Nov 11, 2026, 15:40 UTC · 5.5 h
Elevated API issues and Launch Failures
InformationalAWS · Nov 6, 2026, 22:51 UTC · 2.4 h
Elevated Launch Failures
EC2us-west-2
InformationalAWS · Nov 6, 2026, 22:51 UTC · 2.4 h
Elevated Launch Failures
Between 2:35 PM and 4:21 PM PST, we experienced elevated EC2 instance launch failures affecting all AZs (usw2-az1, usw2-az2, usw2-az3, usw2-az4) in the US-WEST-2 Region. EC2 Instance Launches, AWS services that instantiated new instances, as well as services such as DataSync or AWS Backup which require new instances to support data transfers to or from the US-WEST-2 Region were affected. Our engineers were automatically engaged and immediately began investigating the root cause. We identified the issue to be caused by a subsystem that supports EBS Volumes required during instance launch. We…
Official status page ↗DegradedTencent Cloud · Nov 6, 2026, 16:00 UTC · 24 h
[Issue] TokenHub in Guangzhou
TokenHubGuangzhou
DegradedTencent Cloud · Nov 6, 2026, 16:00 UTC · 24 h
[Issue] TokenHub in Guangzhou
[service recovery] Guangzhou: TokenHub related services have returned to normal, thank you for your understanding and support!
Official status page ↗DegradedTencent Cloud · Nov 2, 2026, 16:00 UTC · 24 h
[Issue] TokenHub in Guangzhou
TokenHubGuangzhou
DegradedTencent Cloud · Nov 2, 2026, 16:00 UTC · 24 h
[Issue] TokenHub in Guangzhou
[Issue resolved] We have resolved the problems with tokenhub in ap-guangzhou. The services are operating normally now.
Official status page ↗October 2026
InformationalAWS · Oct 30, 2026, 01:28 UTC · 0 min
Increased invoke error rates
Apigatewayus-west-2
InformationalAWS · Oct 30, 2026, 01:28 UTC · 0 min
Increased invoke error rates
Between 7:27 AM and 8:47 AM PDT, and between 10:47 AM and 4:15 PM PDT, we experienced intermittent invoke error rates and latencies for HTTP APIs in the US-WEST-2 Region. During this time, customers would have observed increased latency or errors when invoking HTTP APIs, with elevated errors occurring between 3:12 PM and 3:45 PM PDT. This represented the period of highest customer impact with the majority of affected customers experiencing errors or increased latencies during this window. Majority of retry attempts for affected requests were succeeding. We communicated to impacted customers…
Official status page ↗DegradedGoogle Cloud · Oct 20, 2026, 06:00 UTC · 6.1 h
Multiple services were experiencing issues in the europe-west2 region.
AlloyDB for PostgreSQLApigeeBigQuery Data Transfer ServiceCloud Data Fusioneurope-west2+34
DegradedGoogle Cloud · Oct 20, 2026, 06:00 UTC · 6.1 h
Multiple services were experiencing issues in the europe-west2 region.
# Incident Report ## Summary On Monday, 19 Oct 2026 at 22:53 US/Pacific (Tuesday, 20 Oct 2026, 06:53 BST), a data center facility that hosts europe-west2-b, a zone within the europe-west2 cloud region, experienced an external electrical power disruption. This resulted in service unavailability for workloads located in this zone. The subsequent failover of these workloads to unaffected zones and alternate regions caused transient latency and elevated error rates across the broader europe-west2 region. The resolution of the main impact was completed within 6 hours and 8 minutes. ## Root Cause…
Official status page ↗DegradedTencent Cloud · Oct 14, 2026, 16:00 UTC · 24 h
[Issue] TokenHub in Guangzhou
TokenHubGuangzhou
DegradedTencent Cloud · Oct 14, 2026, 16:00 UTC · 24 h
[Issue] TokenHub in Guangzhou
DeepSeek V4 Pro and DeepSeek V4.1 Flash services have returned to normal. Thank you for your understanding and support!
Official status page ↗DegradedTencent Cloud · Oct 14, 2026, 16:00 UTC · 24 h
[Issue] TokenHub in Singapore
TokenHubSingapore
DegradedTencent Cloud · Oct 14, 2026, 16:00 UTC · 24 h
[Issue] TokenHub in Singapore
DeepSeek V4 Pro and DeepSeek V4.1 Flash services have returned to normal. Thank you for your understanding and support!
Official status page ↗DegradedGoogle Cloud · Oct 8, 2026, 11:00 UTC · 29.8 h
Google Cloud Storage (GCS) customers experienced elevated latencies and error rates when performing upload or write operations.
Google Cloud Storageus-central1
DegradedGoogle Cloud · Oct 8, 2026, 11:00 UTC · 29.8 h
Google Cloud Storage (GCS) customers experienced elevated latencies and error rates when performing upload or write operations.
## Incident Report ## Date/Time of the Issue (All time US/Pacific) **Incident First Occurrence** Incident Start: 08 October 2026 04:00 Incident End: 08 October 2026 16:30 Duration: 12 hours, 30 minutes **Incident Recurrence** Recurrence Start: 09 October 2026 04:05 Recurrence End: 09 October 2026 09:46 Duration: 5 hours, 41 minutes **Total Duration:** 18 hours, 11 minutes ## Summary On Thursday, 08 October 2026, Google Cloud Storage experienced elevated write latency and write error rates while performing upload or write operations in the us-central1 region for a duration of 12 hours, 30 mi…
Official status page ↗InformationalAWS · Oct 4, 2026, 16:14 UTC · 2.7 h
Elevated packet loss
Internetconnectivityeu-south-2
InformationalAWS · Oct 4, 2026, 16:14 UTC · 2.7 h
Elevated packet loss
Between 8:48 AM and 11:28 AM PDT, we experienced elevated packet loss within a single Availability Zone (eus2-az1) in the EU-SOUTH-2 Region. This issue resulted in elevated API latencies and error rates for multiple workflows and AWS Services. We were automatically alerted to the issue at 8:54 AM, and immediately began work to identify the root cause while taking multiple parallel paths to mitigate the issue. By 10:00 AM, our mitigation efforts had led to some improvements. By 10:38 AM, we identified the root cause as related to a networking configuration change that we were able to revert…
Official status page ↗September 2026
DegradedMicrosoft Azure · Sep 30, 2026, 20:30 UTC · 5.8 h
Network Connectivity – Gateway service degradation in multiple regions
DegradedMicrosoft Azure · Sep 30, 2026, 20:30 UTC · 5.8 h
Network Connectivity – Gateway service degradation in multiple regions
Watch our 'Azure Incident Retrospective' video about this incident: https://aka.ms/air/7Q30-010 What happened? Between 20:30 UTC on 30 September 2026 and 02:15 UTC on 1 October 2026, customers using several Azure networking services – including Azure ExpressRoute Gateway, Azure Application Gateway, Azure Firewall, Azure Bastion, Azure Virtual WAN, and Azure VPN Gateway – experienced intermittent failures when performing service management operations. In addition, a subset of upgraded Azure ExpressRoute gateways could not retrieve their required configuration from the control plane service,…
Official status page ↗DegradedMicrosoft Azure · Sep 29, 2026, 10:03 UTC · 5.9 h
Azure OpenAI Service, Foundry Agent Service, Foundry Models, and Azure AI services – Intermittent request failures and latency in Sweden Central
DegradedMicrosoft Azure · Sep 29, 2026, 10:03 UTC · 5.9 h
Azure OpenAI Service, Foundry Agent Service, Foundry Models, and Azure AI services – Intermittent request failures and latency in Sweden Central
Watch our 'Azure Incident Retrospective' video about this incident: https://aka.ms/air/7QL5-Z50 What happened? Between 10:03 UTC and 15:58 UTC on 29 September 2026, a platform issue resulted in impact to Azure OpenAI Service, Foundry Agent Service, Foundry Models, and Azure AI services in the Sweden Central region. Impacted customers experienced intermittent request failures, increased latency, and/or HTTP 500 and 503 errors when submitting requests to affected models and data plane APIs hosted in this region. Note that the Azure OpenAI Service processes customer requests through model eng…
Official status page ↗InformationalAWS · Sep 21, 2026, 23:26 UTC · 58 min
Increased Error Rates
EC2us-east-1
InformationalAWS · Sep 21, 2026, 23:26 UTC · 58 min
Increased Error Rates
Between 3:49 PM and 5:06 PM PDT, we experienced increased error rates affecting new instance launches in the US-EAST-1 Region. During this time, customers may have experienced elevated error rates when attempting to launch new EC2 instances through RunInstances, CreateFleet, and related EC2 launch workflows. AWS services that launch EC2 instances on behalf of customers, including Amazon ECS, AWS Fargate, Amazon EMR, amongst others were also impacted during this period. We identified the root cause as a recent deployment to a subsystem within the EC2 service responsible for processing instan…
Official status page ↗InformationalAWS · Sep 3, 2026, 21:49 UTC · 2.3 h
Increased API Error Rates
Multiple servicesus-west-2
InformationalAWS · Sep 3, 2026, 21:49 UTC · 2.3 h
Increased API Error Rates
Between 2:12 PM and 3:18 PM PDT, we experienced increased API error rates affecting the STS AssumeRoleWithSAML and AssumeRoleWithWebIdentity APIs in the US-WEST-2 Region. The root cause was determined to be due to an issue with an STS subsystem responsible for communicating with external identity providers. Other AWS Services that rely on these identity federation protocols were also affected. At 3:18 PM, we observed signs of recovery and continued to monitor to ensure stability and full recovery. The issue is resolved and the service is operating normally at this time.
Official status page ↗DegradedGoogle Cloud · Sep 1, 2026, 14:42 UTC · 4.2 h
Multiple products in us-central1-b are experiencing network service degradation.
AlloyDB for PostgreSQLApigeeCloud FilestoreCloud Firestorenam5us-central1+12
DegradedGoogle Cloud · Sep 1, 2026, 14:42 UTC · 4.2 h
Multiple products in us-central1-b are experiencing network service degradation.
## Addendum to Incident Report This addendum extends the Detailed Description of Impact from the previous message. Though only two clusters in a datacenter in us-central1-b and us-central1-f experienced network isolation, a few regional products with a dependency on the affected datacenter were also affected. Between 07:41 and 11:52 US/Pacific on Tuesday, September 1, 2026, the following products were affected: - **Compute Engine VMs**: VMs running in the affected data center lost network connectivity to resources located outside of their datacenter. From a Compute Engine perspective, this…
Official status page ↗March 2026
OutageAWS · Mar 2, 2026, 05:56 UTC · ongoing
Region Availability
Multiple servicesme-south-1
OutageAWS · Mar 2, 2026, 05:56 UTC · ongoing
Region Availability
We are providing an update on the disruption affecting the Middle East (Bahrain) (me-south-1) Region. The damage to our infrastructure spanned multiple Availability Zones and exceeded what our regional and multi-AZ services are designed to withstand. After a thorough assessment, we have determined that we are unable to restore access to the resources and data hosted exclusively in this Region. When the first Availability Zone was damaged in March, we began recommending that customers migrate their workloads to other Regions, and most did so before the Region became unavailable following the…
Official status page ↗OutageAWS · Mar 1, 2026, 12:51 UTC · ongoing
Region Availability
Multiple servicesme-central-1
OutageAWS · Mar 1, 2026, 12:51 UTC · ongoing
Region Availability
We are providing an update on the disruption affecting the Middle East (UAE) (me-central-1) Region. After a thorough assessment, we have determined that we are unable to restore access to the resources and data hosted exclusively in the mec1-az2 Availability Zone. We continue to work on recovering regional resources, as well as zonal resources hosted in the other affected Availability Zones (mec1-az1 and mec1-az3). Since the disruption began in March, most customers have been able to re-establish their operations in other Regions by restoring backups or copying data that remained accessible…
Official status page ↗About this data
- Collected from each provider's official status feed every 30 minutes and kept here after it drops off their pages. Times are UTC.
- Microsoft Azure's public history covers only major incidents with a Post Incident Review, so it shows fewer than the other clouds.
- Alibaba, Huawei and Tencent Cloud: incidents from their international status pages.
- An incident on a status page doesn't mean every customer was affected. Check the services and regions.
List prices are the start. Your bill is the rest.
Mofis reads your real bills from 12 clouds, discounts included, and an AI cloud architect tells you what to cut.