Cloud Service Status
Check the cloud before you debug your own code.
When half your stack starts throwing errors, the first question shouldn’t be “what did we deploy?” but “is the cloud down?”. Provider incidents at AWS, Azure, Cloudflare, or GitHub regularly masquerade as application bugs — failed deploys, 5xx spikes, DNS weirdness, stuck CI. This page gathers our live reachability checks for the major cloud and developer platforms, each probed every 15 minutes, so you can rule the provider layer in or out in seconds.
GitHub is the world’s largest code hosting platform, and its outages stall software teams globally — pushes fail, pull requests will not merge, and CI pipelines that fetch from GitHub break in cascade.
Cloudflare fronts a huge share of the web with CDN, DNS, and security services — which is why a single Cloudflare incident can make thousands of unrelated websites show 5xx errors simultaneously.
AWS is the largest cloud provider, hosting a substantial fraction of the internet. Its regional incidents — especially in us-east-1 — are infamous for taking down apps, smart devices, and websites that users never associated with Amazon.
Microsoft Azure is one of the largest cloud platforms, hosting a huge share of business apps and services. Its regional incidents can cascade into outages across many companies at once, and it shares an identity layer (Entra ID) with Microsoft 365, so sign-in problems sometimes span both.
Provider outages masquerade as your bugs
Cloud incidents rarely announce themselves. A regional AWS problem surfaces as your API timing out; a Cloudflare incident looks like your site is down even though your origin is healthy; a GitHub outage turns every CI pipeline red at once. Before rolling back a deploy, check the provider: if our probe struggles too, or the provider’s status page shows an incident, the fastest fix is usually to wait — or fail over — rather than to debug your own code.
Reachability is only the front door
Our checks test each provider’s public endpoint, which catches the big, global incidents. But cloud platforms are dozens of regional services, and most incidents are partial: one region, one product, one API. If our check is green and your workload still fails, drill into the provider’s per-service status dashboard (linked from each page here) and pin down the affected region — that specificity is exactly what your incident channel and your support ticket need.
Frequently Asked Questions
Which cloud and developer services are monitored here?
We keep dedicated pages for Amazon Web Services, Microsoft Azure, Cloudflare, and GitHub. Each shows an on-demand live check, the last 24 hours of scheduled checks, and a link to the provider’s own component-level status dashboard.
Our app is erroring but the cloud provider shows as up. What next?
Green reachability rules out a global outage, not a partial one. Check the provider’s regional status for the specific services you use, look at your own error rates by region, and search recent posts from other engineers — widespread partial incidents surface publicly within minutes.
Cloudflare is down — does that mean my site behind it is down too?
Usually yes for visitors, even though your origin server is fine: Cloudflare sits in front of your site, so its edge failing blocks traffic before it reaches you. During a confirmed Cloudflare incident you can temporarily point DNS straight at your origin — but weigh that against losing DDoS protection, and remember DNS changes take time to propagate.