Frequently asked questions
How does World Wide Uptime check my site?
Each region card issues an HTTP(S) request from a Cloudflare Worker running in or near that region. We capture response status, TTFB, download time, redirect chain, SSL info and key response headers, then show them back to you.
Why does my site show "up" from some regions and "down" from others?
Real-world routing is not uniform. BGP peering changes, geo-blocking, Anycast CDN misroutes, or a bad origin behind a specific CDN PoP can all cause regional partial outages. That partial signal is usually the most valuable part of a check.
Do you store the domains I check?
Results are cached for 30 seconds at the edge so repeated checks are fast, and your most recent checks are saved in your browser's localStorage (on the History page). That's it. No accounts, no tracking, no selling data.
Is there an API?
Yes. GET https://api.worldwideuptime.com/check?url=example.com®ion=na-east returns a JSON RegionResult. The contract is documented on the Blog.
Why do I see 0ms for DNS / TCP / TLS sometimes?
Cloudflare Workers do not yet expose low-level DNS/TCP/TLS handshake timings to userland. We fall back to TTFB + download + total when the runtime doesn't give us the breakdown. As the runtime adds it, the waterfall fills in automatically.
How many checks can I run?
Free tier: 60 checks per minute per IP. Needs more? Drop us a line.