Live Cloud Health
AWS
Outage detected
Updated 4:18:44 PM
Azure
Status unknown
Updated 4:17:44 PM
AT&T
Operational
Updated 4:16:44 PM
CenturyLink
Operational
Updated 4:15:44 PM
Cloudflare
Operational
Updated 4:14:44 PM
Comcast
Operational
Updated 4:13:44 PM
CrowdStrike
Operational
Updated 4:12:44 PM
DigitalOcean
Operational
Updated 4:11:44 PM
Dropbox
Operational
Updated 4:10:44 PM
Fastly
Operational
Updated 4:09:44 PM
GitHub
Operational
Updated 4:08:44 PM
Google Cloud
Operational
Updated 4:07:44 PM
IBM Cloud
Operational
Updated 4:06:44 PM
Linode
Operational
Updated 4:05:44 PM
Oracle
Operational
Updated 4:04:44 PM
Rackspace
Operational
Updated 4:03:44 PM
Salesforce
Operational
Updated 4:02:44 PM
Shopify
Operational
Updated 4:01:44 PM
Slack
Operational
Updated 4:00:44 PM
Spectrum
Operational
Updated 3:59:44 PM
T-Mobile
Operational
Updated 3:58:44 PM
Verizon
Operational
Updated 3:57:44 PM
Vultr
Operational
Updated 3:56:44 PM
Zoom
Operational
Updated 3:55:44 PM
Provider Reliability Breakdown
21
209h
9h 57m
50h
Azure
Historical Outage Timeline
21 resultsHardware/Cooling Meltdown
US-East-1 (N. Virginia)
Data center overheating caused catastrophic cascading server shutdowns. Impaired thousands of NYC fintech apps, e-commerce stores, and logistics systems relying on standard East Coast pools.
Resource Provisioning Failure
East US / Global
Critical issues in cluster management prevented NYC small businesses from deploying new cloud instances or scaling existing web apps on Azure Front Door.
Control Plane Failure
US-East / Multi-Region
Widespread OCI authentication drops. Heavy disruptions across local corporate enterprise Resource Planning (ERP) tools and NetSuite instances.
AI Platform Outage
Global / API
Vertex AI and Gemini API endpoints threw consecutive 5xx errors. Directly broke automated customer service chatbots and local SaaS features utilizing LLMs.
DevOps / Control Plane
Multi-Region (US-East heavy)
Deployment pipelines failed globally. Engineering teams across New York tech firms were unable to ship software patches or manage Kubernetes clusters.
Cellular Core Routing Collapse
USA (NYC Epicenter)
Massive cellular data failure pushing iPhones into 'SOS Mode'. NYC small businesses lost cellular card processors, delivery dispatch tools, and standard local point-of-sale systems.
HTTP Traffic Drop (Config Error)
Global Edge / NYC PoP
A rogue bot-management configuration update knocked roughly 28% of global HTTP web requests offline. Hit high-density media, publishing, and financial sites stationed in Manhattan instantly.
Total Infrastructure Blackout
Global / OCI
A brief but absolute total drop in connectivity across Oracle Cloud nodes, triggering quick automated alerts and failover alarms in data centers.
DNS Management Failure
US-East-1
Internal network routing issues broke DynamoDB tables and standard domain resolution, locking consumer applications and payment processors out of cloud storage.
Authentication Lockout
Global Core
Severity One core security outage that locked administrators entirely out of their CLI consoles, delaying all emergency database updates across localized hybrid infrastructures.
Database Error Spikes
US-East-4 (N. Virginia)
High elevated error rates hitting AlloyDB and backend connection layers, lagging analytical microservices operating for East Coast regional platforms.
Network Transit Disruption
Global Backbone
Cascading network failure impacting major visual/audio web properties like Spotify and Snapchat, causing massive digital workspace lag for NYC remote teams.
Control Plane Flood
Multi-Region / UI
Automated system retries accidentally flooded login systems following minor router maintenance, completely taking down dashboard control tools for half a day.
Physical Networking Layer Fault
East US 2
Hardware failures inside a primary East Coast facility caused slow data retrieval and packet loss over a grueling 50-hour window for un-replicated local storage assets.
Power Substation Incident
South Central US / Transit
Power grid flickers disrupted backup generator transfers during the holiday shopping rush, affecting cross-regional database queries originating from NYC retail backends.
DNS Config Corruption
Global Storage Core
Corrupted pointer files dropped active links to cloud-hosted storage blocks, rendering large-scale data modeling and Databricks clusters inaccessible to financial quants.
Anycast Routing Leak
Global Transit / Edge
Traffic was incorrectly funneled away from optimal nodes, forcing New York City end-users to experience steep latency penalties and gateway time-out errors.
Streaming Ingestion Lag
US-East-1
A core failure within AWS Kinesis choked real-time data streaming pipelines, causing major telemetry gaps for modern small-business monitoring apps.
Kernel Update Crash (Blue Screen)
Global Impact
While not a cloud hosting failure, a security patch crashed 8.5 million host Windows systems. Paralyzed flights out of JFK/LaGuardia, froze banking terminals, and downed local retail systems.
VPC Instantiation Error
Global VPC Layer
Newly spun up virtual server instances failed to generate active network links, blocking instant scaling defenses for platforms fighting organic regional traffic spikes.
Core Routing Interruption
Global Backbone
Brief routing issue causing temporary access drops to regional enterprise cloud environments.
Website Health
This page checks whether the tools and websites your business depends on are up and running, so you hear about problems before your customers do. When a payment processor, booking site, or delivery app goes down, every minute offline can cost you sales and trust. Use this tracker to see which services are having trouble, how long the outages last, and what to do next to keep your business running.
SMB Action Plan
Before an Outage
- Identify your critical cloud dependencies
- Set up offline payment backups (cash, manual card imprinters)
- Document failover procedures for staff
- Bookmark provider status pages
During an Outage
- Check this tracker to confirm scope
- Switch to backup systems immediately
- Post updates on social media for customers
- Document downtime for SLA claims
After an Outage
- Review what failed and why
- Update your backup procedures
- Consider multi-provider redundancy
- File SLA credit claims if applicable