Cloud Providers Health Report - February 2023
Mar 2, 2023
Check our February 2023 health report on the top most popular cloud providers. We analyze the health of the cloud providers based on the number of outages and problems during the month. The source of the data is made available by the cloud providers themselves via their status page. We normalize it and use it to generate the report.
Please analyze the information with a grain of salt as each provider has their own framework for reporting incidents, and in no way one provider having more outages, means that they are worse than any other. Also we are comparing providers with very different sizes and market share.
In this report, we compare AWS, Azure, DigitalOcean, Fly.io, Google Cloud, Heroku, Linode, Netlify, Vercel according to their reported outages.
AWS
Metrics
- Total Incidents
-
6
0 MAJOR 6 MINOR - Total Outage Time
- ~15.2 hours
- Average Outage Time Per Incident
- 130 minutes
- Weekday with most problems
- Thursday with 3 outages
List of Outages
- 02/02MINORElevated CloudFront latencies and error rates for IPv6 traffic
- 02/02MINORIncreased error rates when accessing Cost Explorer, Budgets, and Cost and Usage Reports
- 07/02MINORIncreased Publish API Latencies and Errors
- 10/02MINORConnectivity issues affecting some instances
- 23/02MINORNetwork Connectivity
- 26/02MINORIncreased Error Rates for AWS Snowball
Azure
Metrics
- Total Incidents
-
3
0 MAJOR 3 MINOR - Total Outage Time
- ~36.4 hours
- Average Outage Time Per Incident
- 364 minutes
- Weekday with most problems
- Wednesday with 3 outages
List of Outages
- 02/02MINORAzure Synapse Analytics - Errors when attempting to create clusters - Investigating
- 07/02MINORDatacenter Cooling Event - Southeast Asia
- 24/02MINORSign-In Issues - Conditional Access Policies Based on GeoIP Location
DigitalOcean
Metrics
- Total Incidents
-
7
0 MAJOR 7 MINOR - Total Outage Time
- ~39.9 hours
- Average Outage Time Per Incident
- 342 minutes
- Weekday with most problems
- Thursday and Monday with 3 outages
List of Outages
- 02/02MINORLON1 Networking
- 03/02MINOREvent Processing in FRA1
- 06/02MINOREvents Failures in BLR1
- 06/02MINORSpaces Availability in FRA1
- 09/02MINORApp Platform CDN
- 13/02MINORLoad Balancer creation in NYC1
- 16/02MINORApp Platform and Container Registry
Fly.io
Metrics
- Total Incidents
-
11
0 MAJOR 11 MINOR - Total Outage Time
- ~63.8 hours
- Average Outage Time Per Incident
- 348 minutes
- Weekday with most problems
- Saturday with 3 outages
List of Outages
- 03/02MINOREdge routing issue
- 04/02MINORRelease command issue
- 04/02MINORUnable the schedule remote builder causing errors
- 07/02MINORFlycast connectivity broken from certain (new) hosts
- 09/02MINORDelayed state causing proxying / deployment issues
- 11/02MINORCapacity needed in YUL
- 15/02MINORNetwork connectivity issues in SCL region.
- 16/02MINORDNS Resolution for fly.dev occasionally failing
- 24/02MINORMachine API Unavailable on some hosts/regions.
- 26/02MINORCapacity Issues in AMS region
- 27/02MINORStatics are broken
Google Cloud
Metrics
- Total Incidents
-
23
1 MAJOR 22 MINOR - Total Outage Time
- ~459.9 hours
- Average Outage Time Per Incident
- 1199 minutes
- Weekday with most problems
- Wednesday with 9 outages
List of Outages
- 01/02MINORWe've received a report of an issue with Container Registry
- 02/02MINORUS: Chronicle Security Information and Event Management (SIEM) is experiencing issue with Indicator of Compromise (IOC) matches.
- 02/02MINORPotential higher latency for Google Cloud Networking users in asia-southeast2 region
- 02/02MINORHigh control-plane latency in southamerica-east1
- 05/02MINORGoogle are currently investigating a issue Google cloud networking, Google App Engine.
- 06/02MINOReurope-west9: Increased 500 Errors for GCLB traffic
- 08/02MINORGoogle Kubernetes Engine, Google Cloud Dataproc and Google Cloud Composer are experiencing elevated error rates.
- 08/02MINORGoogle Kubernetes Engine Autopilot cluster creation, Google Cloud Dataproc serverless job submission and Google Cloud Composer environment creation are experiencing elevated error rates.
- 08/02MINORGoogle App Engine Flex users experiencing issues with deploying some applications using gcloud 417.0.0
- 08/02MINORLatency for some Google Cloud Networking users in asia-southeast2 region
- 08/02MINORSecurity Assertion Markup Language (SAML) authentication workflows not present for some customers
- 08/02MINORus-central1: Vertex AI Batch Prediction, Vertex AI Matching Engine, Vertex AI Online Prediction are experiencing issues with cluster deployments
- 09/02MINORGKE Autoscaler may be experiencing issues with scale up for customer in us-west1
- 09/02MINORGlobal: Google Cloud Storage returns 410 HTTP response when performing resumable uploads
- 15/02MINORZonal: Google Compute Engine experiencing VM operation failures in us-central1-c
- 16/02MINORCloud Logs bigquery exports delayed
- 16/02MINORGoogle Cloud Console customers might experience Cloud Billing data delays
- 17/02MINORIssues with Cloud Retail Search API
- 18/02MINORCloud Build issues with Github
- 22/02MINOReurope-north1: Data Fusion Instance creation failures
- 23/02MINORCloud Marketplace customers may experience API Library products are not being displayed
- 26/02MINORFile access issues for non-root users for Cloud Filestore
- 27/02MAJORMultiple services are being impacted globally within Google Cloud
Heroku
Metrics
- Total Incidents
-
2
2 MAJOR 0 MINOR - Total Outage Time
- ~5.5 hours
- Average Outage Time Per Incident
- 164 minutes
- Weekday with most problems
- Wednesday and Saturday with 1 outage
List of Outages
- 01/02MAJORInability to connect to Heroku Postgres on Basic plans
- 25/02MAJORService disruption for eco dynos in US Common Runtime apps in the VA region
Linode
Metrics
- Total Incidents
-
4
1 MAJOR 3 MINOR - Total Outage Time
- ~34.5 hours
- Average Outage Time Per Incident
- 517 minutes
- Weekday with most problems
- Thursday and Sunday and Tuesday and Friday with 1 outage
List of Outages
- 02/02MINORService Issue - API Gateway Timeouts
- 12/02MINORConnectivity Issue - US-West
- 21/02MINORConnectivity Issue - Fremont
- 24/02MAJORConnectivity Issue - Newark
Netlify
Metrics
- Total Incidents
-
5
1 MAJOR 4 MINOR - Total Outage Time
- ~5.2 hours
- Average Outage Time Per Incident
- 62 minutes
- Weekday with most problems
- Thursday with 2 outages
List of Outages
- 06/02MINORInvestigating reports of build failures
- 09/02MINORIncreased failures in Edge Function Builds
- 14/02MINORDelay in processing DNS Records
- 16/02MINORErrors in the Netlify UI
- 17/02MAJORErrors with builds
Vercel
Metrics
- Total Incidents
-
6
0 MAJOR 6 MINOR - Total Outage Time
- ~9.8 hours
- Average Outage Time Per Incident
- 98 minutes
- Weekday with most problems
- Wednesday with 2 outages
List of Outages
- 01/02MINORBuilds And Deployments Degraded
- 03/02MINORDegraded Build Processing
- 07/02MINOREmail Notifications Degradation
- 08/02MINORDelayed Build Logs Delivery
- 13/02MINORIncreased TLS handshake failures in arn1 region
- 16/02MINORBuilds And Deployments Degraded
The simplest way to monitor outages in cloud services
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 2509 services available
Integrations with
Related articles
Setup in 5 minutes or less
Try it out! How much time you'll save your team, by having the outages information close to them?
- 14-day free trial
- No credit card required to start
- Cancel anytime
- +2000 services available