DrumbeatsIs it down?
Live, independently measured status for the developer services you depend on. Each page shows what our probes see right now, 30 days of uptime and outage history, and the vendor's own status feed next to it.
How these pages work
Every 5 minutes, from Europe
Each service is requested every five minutes from our own infrastructure in Europe. We probe the endpoint the service actually serves (the registry, the API, the edge) and say on every page exactly which URL and status code we expect.
Failures are confirmed before we report them
When a check fails we immediately re-check from US East, then again from Europe 30 seconds later. Only when all three agree do we count a failure. One isolated failure is a blip; two or more in a row are an incident. If the confirming region is unreachable we say so rather than guessing.
Blocked is not down
Some sites answer automated requests with a bot challenge or a rate limit. We record those as blocked, never as outages: being unable to reach something is not the same as it being unavailable.
Uptime you can reproduce
Uptime is successful checks divided by counted checks over our scheduled samples. Downtime is the number of confirmed failed checks times five minutes. Gaps in our own coverage are drawn as gaps, not interpolated.
Checking your own site instead? Use the website down checker. Our probe identifies itself as DrumbeatsUptimeBot; vendors can opt out via robots.txt or email.
Monitor your own services the same way
Uptime checks from multiple regions, cron and background-job heartbeats, and alerts to Slack, email or webhooks. Free for up to 50 monitors.
Start monitoring free