Is it down right now?

Live status for 407 popular services, checked on demand from our London server. No user reports, no crowd-sourced guesswork — just a real request and what came back.

Developer & infrastructure

GitHub
github.com
checking…
GitLab
gitlab.com
checking…
Cloudflare
cloudflare.com
checking…
AWS
aws.amazon.com
checking…
Microsoft Azure
azure.microsoft.com
checking…
Google Cloud
cloud.google.com
checking…
DigitalOcean
digitalocean.com
checking…
Heroku
heroku.com
checking…
Vercel
vercel.com
checking…
Netlify
netlify.com
checking…
npm
npmjs.com
checking…
Docker Hub
docker.com
checking…
Stack Overflow
stackoverflow.com
checking…
OpenAI
openai.com
checking…
Claude
claude.ai
checking…
GoDaddy
godaddy.com
checking…
Namecheap
namecheap.com
checking…
WordPress.com
wordpress.com
checking…
Shopify
shopify.com
checking…
Wix
wix.com
checking…
Squarespace
squarespace.com
checking…
IONOS
ionos.co.uk
checking…
Fasthosts
fasthosts.co.uk
checking…
Bitbucket
bitbucket.org
checking…
Jira
jira.com
checking…
Atlassian
atlassian.com
checking…
CircleCI
circleci.com
checking…
Travis CI
travis-ci.com
checking…
Sentry
sentry.io
checking…
Datadog
datadoghq.com
checking…
New Relic
newrelic.com
checking…
PagerDuty
pagerduty.com
checking…
Twilio
twilio.com
checking…
SendGrid
sendgrid.com
checking…
Mailchimp
mailchimp.com
checking…
HubSpot
hubspot.com
checking…
Zendesk
zendesk.com
checking…
Intercom
intercom.com
checking…
Supabase
supabase.com
checking…
Firebase
firebase.google.com
checking…
MongoDB Atlas
mongodb.com
checking…
Railway
railway.app
checking…
Render
render.com
checking…
Fly.io
fly.io
checking…
Akamai / Linode
linode.com
checking…
Hetzner
hetzner.com
checking…
OVHcloud UK
ovh.co.uk
checking…
SiteGround
siteground.com
checking…
Bluehost
bluehost.com
checking…
Hostinger
hostinger.com
checking…
123 Reg
123-reg.co.uk
checking…
Krystal
krystal.uk
checking…

How these checks work

Every service on this page is checked the same way: we open a real HTTPS connection from our server, send an ICMP ping at the same time, and record the status code and timings that come back. Results are cached for 60 seconds so that a surge of visitors during an outage does not add load to a service that is already struggling.

We deliberately do not use user reports. Report-based sites spike whenever something unrelated goes wrong — a popular game patch, a mobile network wobble, a rumour — and they cannot tell you why a site is unreachable. A direct check can: it distinguishes a DNS failure from a refused connection from an expired certificate.

One honest caveat: a service can be up at the edge and broken for its users. A login system, a payment processor or a regional CDN node can fail while the home page still returns HTTP 200. If a page here says "up" but the service is not working for you, that is worth knowing too — it narrows the fault to a specific subsystem.