Checking your site from 22 locations without 22 times the false alarms

A check from one place proves one thing: that place can reach your site. Your users sit in São Paulo, Jakarta and Johannesburg too. A CDN edge can fail in one city. A routing problem can cut off one region. A firewall rule can block a whole country by mistake.

Uptrack used to check from three regions: Europe, the US and India. That caught a lot, but not a broken edge in Sydney or a bad route into Brazil. Today HTTP and keyword monitors run from 22 locations on six continents.

More locations bring a risk: more places where one bad network hop looks like an outage. This post shows how we add the coverage without adding noise.

Where we check from

Nuremberg, Ashburn and Hyderabad are the core locations. They run every monitor type. The other 19 cities run HTTP and keyword checks.

More locations, not more noise

The 22 locations form 11 areas. Each area is two nearby cities: London and Paris, Singapore and Jakarta, Sydney and Melbourne, and so on. In each check interval one city per area checks your site, and the two cities take turns.

So a 30-second monitor is checked from every area every 30 seconds, and from every city once a minute. Your site gets one request per area per interval, not one per city. The core locations check on every interval.

How a failure gets confirmed

1. Same-city re-check. When one of the 19 added cities sees a failure, it checks again at once. A one-off network blip clears here.
2. Consecutive failures. The failure must repeat for your number of consecutive checks, from 2 to 5.
3. Several locations. Several locations must see the failure before we alert you. One unlucky city never pages you.

The idea is older than the 22 locations. Why alert confirmation matters explains the consecutive-failure rule, and how we built multi-region consensus tells the story of the first three regions.

Other tools solve the same problem in different ways (from their public docs, October 2026):

A blocked city is not an outage

More locations also meet more bot protection. Some sites challenge or rate-limit traffic from certain networks, and a check from that city gets an HTTP 403 or 429 while every other location sees the site up.

Uptrack does not call that an outage. When only one city is refused and the others see your site up, that city is marked as blocked for your site. The other city of the same area takes its turns, so the area stays covered. A real outage looks different: errors and timeouts from several places at once.

Failures caused by bot protection also say so. Instead of a bare “HTTP 403”, the message names the protection that answered.

What runs where

Pro includes 12 locations that you pick. Team and Business include all 22. The full plan comparison is on the pricing page.

Try it on any site

The Is this website down? tool checks any URL from all 22 locations and groups the answers by continent. No account needed.

If you use Claude, the same check works from a chat: ask “is example.com down?” and the Uptrack connector answers with every location.

Not for you if

• You need ping, DNS or TCP checks from 22 locations. Those run from the 3 core locations.
• You need a traceroute or a full timing breakdown per city. The 19 added cities report total time and HTTP status.
• You want a free plan. Uptrack is paid-only, from $3/mo.

FAQ