Multi-location website monitoring from 171+ checkpoints

See whether an outage hits every visitor or only one region, such as a failing CDN edge or network route. Uptimia checks from 171+ checkpoints in 70+ countries, logs the location of every check and re-checks each failure from other checkpoints.

Start free trial → See what one location misses
30-day free trial No credit card GDPR-ready

Outages a single location misses

Common failures as visitors in six cities would see them in the same minute. A monitor in Frankfurt alone catches only the origin server outage.

The first three rows each mean a call to a different company (your host, your CDN or your DNS provider), while the routing fault in the fourth is a carrier's problem that usually clears on its own. Uptimia logs every check with its checkpoint location, so you can see which regions failed. A monitor bound to one region pages you when that region's checkpoints agree.

How checks rotate across checkpoints

One checkpoint runs each check. When it fails, other checkpoints from the same list re-check before anyone is paged.

  • Rotation Each interval, one checkpoint from the monitor's list runs the check, and the next interval usually goes to another. At 1-minute checks, that is 1,440 readings a day from across the selection.

  • Backup checks A failed check is re-run from up to 3 other checkpoints in the same list, never the one that failed. If only that checkpoint's route is bad, the backups pass and the failure stays in the log.

  • Recovery A single passing check closes the incident, so the all-clear goes out as soon as one checkpoint reaches your site again.

On a monitor that checks from all locations, backup checks come from the whole list too. A failure seen in only one region is usually not reproduced by those backup checks, so it stays in the log and no incident opens. To be paged for it, add a separate monitor bound to that region. How false alarms are filtered out →

Where location data appears

Each check is logged under a checkpoint location, which appears on the incident page, in Monitoring Logs and in the CSV export.

Detecting checkpoints table

Each checkpoint that confirmed the failure, with its flag, IP address, the time it was confirmed and the error. Below it, the response headers, body and traceroute captured at failure.

Locations filter and column

Narrow the log to one region or tick single countries. Every row shows the checkpoint's flag and location, and a click opens the check's details.

Location on every exported row

The export honours your filters and date range, with Name, Type, Location, Time, Status and Duration per check. Attach it to the ticket you open with your host or CDN.

Check your site from six continentswith a location logged on every result.

Uptimia re-runs a failed check from other checkpoints before alerting you and logs the location of every check.

Start your free 30-day trial →
30 days free no credit card cancel anytime

Alerts for the regions you serve

You decide how many checkpoints must agree and which region they check from. The alert names the checkpoints that confirmed the failure.

Backup checks before every alert

You set how many other checkpoints must see the failure before the incident opens, up to 3. The default of 3 keeps one checkpoint's bad route from paging you. Set it lower to be paged sooner.

A monitor per region you sell in

Bind a monitor to a built-in profile such as Asia or South America. Its backup checks come from that region too, so a failure seen only in that region is confirmed and you are paged.

Alerts that name the checkpoints

The alert email opens with Down since, Error and Confirmed by N locations, then a table of the checkpoints that confirmed it, each with its flag and status, so you can see where the failure was confirmed without opening the dashboard.

  • Confirmed inside the region. On a monitor bound to South America, a failure that only South America sees still gets confirmed 3 of 3.
  • The incident records the failure details. It lists the checkpoints that confirmed the failure with their IP addresses, the time it was confirmed and the error, plus the headers, body and traceroute captured at failure.
  • Everyone alerted gets the recovery notice. The all-clear goes to each person who got the alert and says how long the outage lasted.
How false alarms are filtered out → Explore downtime alerts →
Recovered · one passing check from Lima closes it all-clear sent
Location profiles

Pick checkpoints by region or country

Every monitor with a Locations tab can check from all checkpoints, a saved profile or a custom selection. Seven profiles are built in, and you can save any selection you tick as your own.

  • EU / GDPR keeps checks inside the EEA. The built-in profile uses checkpoints in EU member states plus Iceland, Liechtenstein and Norway, and nothing outside them.
  • Save your own. Tick checkpoints in the region grid, name the set, and apply it to every monitor that should match in one action.
  • EU accounts start on Europe. A new monitor on an EU-region account checks from European checkpoints until you widen it.
Explore monitor configuration →
Locations

Checkpoints on six continents

São Paulo gets a 502. On a worldwide monitor the backup check runs from another checkpoint, here London, gets a 200, and the failure is logged without opening an incident. Bind the same check to South America and the backup checks fail too, so the incident is confirmed and you are paged.

  • Each check is logged with its checkpoint. Filter the log by region or country and export it as CSV.
  • Worldwide monitors need backup checkpoints to agree. A failed check is re-run from other checkpoints in the pool. If any backup check passes, the failure stays in the log and no incident opens.
  • A region can have its own monitor. Bind a monitor to a regional profile and its backup checks come from that region, so an outage there is confirmed and you are paged.
See every checkpoint location →
171+ checkpoints · 70+ countries 6 continents

Also included

Scheduled reports

Uptime and response time for every monitor, delivered daily, weekly, monthly, quarterly or yearly as PDF, HTML or CSV.

Weekly · Monday 08:00
MonitorUptime
shop.caldmont.com99.93%
api.caldmont.com100%
www.caldmont.com100%
Weekly · PDF · public share link

Public status pages

A public page with each monitor's state and uptime percentage, on your own domain.

status.example.com All systems operational
caldmont.com100%
shop.caldmont.com99.93%

Recovery notices

When the site is back, everyone who got the alert is told, along with how long it was down.

Checkout is DOWN14:05
Checkout is UPUP again after 14 min

Maintenance windows

Schedule planned work and checks pause during the window, so a deploy inside it doesn't page anyone.

00:00Window · 02:00–03:0024:00
Window open → checks paused

Published checkpoint IP list

The full checkpoint address list, IPv4 and IPv6, as plain text or ready-made nginx map syntax. Allowlist all of it.

IPv4IPv6nginx map
203.0.113.17203.0.113.52198.51.100.9… IPv4 · IPv6 · nginx map

One dashboard for everything

Multi-location uptime checks share one account and one alerting setup with your SSL, domain, speed and server monitors.

www.caldmont.com🇩🇪 🇬🇧 🇺🇸 🇧🇷 🇸🇬 🇦🇺UPTIME shop.caldmont.com🇩🇪 🇺🇸SPEED api.caldmont.comSSL

Regional failures and what Uptimia shows

Cases where your site's response depends on where the request comes from, with the monitor settings to use for each.

Example 1CDN outage

A CDN edge failing for South America

Your CDN serves South America from its São Paulo edge, and that edge returns 502 for 40 minutes. Frankfurt and New York keep getting cached pages, so a monitor there stays green the whole time.

Monitor settings LocationsSouth America (7) Outage confirmation3 backup checks Check intervalEvery 1 minute
What you see and what happens →
What you see
The incident lists the checkpoints that confirmed the 502, with their IP addresses and the time it was confirmed. The response headers and body captured at failure show the CDN's own error page, so you know the request never reached your server.
What happens
Every checkpoint in the South America profile goes through the same edge, so the backup checks agree and you are paged. A second monitor on the same URL, checking from everywhere, covers the rest of the world. When the edge recovers, one passing check closes the incident.
Example 2Geo-blocking

Countries you block at the firewall

You block Russia and China at the WAF, the firewall in front of your site. A checkpoint in either country gets a 403 block page, and a monitor that includes those checkpoints logs the 403 as an outage, even though the block is intentional.

Monitor settings LocationsCustom selection Outage confirmation3 backup checks Check intervalEvery 1 minute
What you see and what happens →
What you see
Save the selection as a profile and every monitor that needs it uses the same list. The checkpoints you left out never check those monitors, so the block never shows up as an incident.
What happens
Blocking a country on purpose doesn't open false incidents. If a WAF rule later misfires against a region you do serve, Monitoring Logs show the 403 next to the checkpoint location. To let the checks through, allowlist the full published IP list, IPv4 and IPv6.
Example 3DNS change

A DNS change still spreading

You move the site to a new server and switch the old one off. Resolvers in Japan and Australia hold the old record until its TTL runs out, so their visitors reach a server that no longer answers.

Monitor settings LocationsAll probes Outage confirmation3 backup checks Check intervalEvery 1 minute
What you see and what happens →
What you see
Filter Monitoring Logs to Japan and Australia and the stale cities stand out, one row per check with city, time and status. Each check runs from whichever checkpoint picks it up first, so over a day the rows spread across many cities. Once Tokyo and Sydney show Up again, the change has reached them.
What happens
Most of the world already gets the new record, so the backup checks pass and no incident opens. The failed checks stay in the log as evidence, and you are not paged for a change you made on purpose.
Example 4Location profile

Shop customers in Germany and the US

Your buyers are in Germany and the United States, so you care how fast the shop loads in Frankfurt. Readings from Singapore get mixed into the same response-time chart and pull the number away from what your buyers see.

Monitor settings LocationsEurope + North America (134) Outage confirmation3 backup checks Check intervalEvery 1 minute
What you see and what happens →
What you see
Regular checks and backup checks both run from checkpoints in the markets you sell in. The response-time chart is built only from checks by those 134 checkpoints, so slow responses from Asia don't raise it.
What happens
One bulk action puts the profile on every uptime, speed, SSL and transaction monitor in the shop. An outage pages you only when European or North American checkpoints agree.

See which regions can reach your siteand which ones can't.

Bind a monitor to the regions you sell in and get paged when checkpoints there agree.

Start your free 30-day trial →
30 days free no credit card cancel anytime

How multi-location monitoring works

Uptimia checks your website from 171+ checkpoints in 70+ countries and logs a checkpoint location for every check. When one checkpoint reports a failure, others from the same list re-check before an incident opens, and the alert lists the checkpoints that confirmed it.

01Why does the monitoring location matter?+
Each region reaches your site by its own path. CDNs serve each region from different nodes, geo-DNS hands out different answers by location, and network routes fail one at a time, so a check that passes from Frankfurt is no evidence that visitors in Singapore can load the page. With checks from many locations, you see what visitors in each region get from their side of the network.
02How many locations does Uptimia check from?+
171+ checkpoints in 70+ countries, across six continents (90 in Europe, 44 in North America, 23 in Asia, 7 in South America, 7 in Oceania, 5 in the Middle East and 3 in Africa). The checkpoints page lists every city, and the monitor editor's Locations tab shows the same live list. See every checkpoint location →
03Can I choose which locations check my site?+
Yes, per monitor. The Locations tab offers All probes, Saved profile and Custom selection. Seven profiles are built in (Europe, North America, Asia, South America, Oceania, Middle East & Africa, EU / GDPR); the Middle East and Africa share one because each alone has fewer than the 6 checkpoints a profile needs. You can save your own from any selection and apply it to up to 500 monitors in one action.
04Does every location check my site on every interval?+
No. Each interval, one checkpoint from the monitor's list picks up the check, and the next interval is usually taken by another. A monitor checked every minute gets 1,440 checks a day from across the selection. When a check fails, the backup checks come from other checkpoints in the same list.
05Do more locations mean more false alarms?+
No. On a website, SSL, speed or transaction monitor, a failed check opens an incident only after 1 to 3 other checkpoints from the same list (3 by default) fail too, so one checkpoint's network blip stays in the log and doesn't page you. API and DNS monitors count the first check in that number, so at 1 they open on the first failure. Adding locations doesn't change these rules.
06What happens when only one region sees a failure?+
Uptimia re-checks from other checkpoints in the monitor's list. If enough of them confirm, the incident opens and the alert lists the checkpoints that confirmed it. If the re-checks pass, the failed check stays in Monitoring Logs as a data point and nobody is woken up. To be paged for a failure only one region sees, give that region its own monitor on a regional profile, so its re-checks come from the same region.
07Can I monitor from a single country?+
Yes, when the country has at least 6 checkpoints (the United States has 38, Germany 13, the United Kingdom 9, France 6, Australia 6). A custom selection needs 6 or more so a failure can be confirmed from checkpoints other than the one that failed. Some nearby cities share one server (London and Dublin can also run from the Paris server), so for a smaller country add its neighbours and pick checkpoints in different regions.
08Does the alert say where the site failed?+
Yes. The alert email's key facts read Down since, Error and Confirmed by N locations, followed by a 'Checkpoints that detected the incident' table with each confirming location's flag, error and status. The incident page adds a Detecting checkpoints table (location, IP address, the time it was confirmed and the error) plus the response headers, body and traceroute captured at failure.
09My firewall or CDN blocks the checkpoints. What do I allowlist?+
The full list of checkpoint addresses is published at uptimia.com/monitoring-checkpoint-ips as plain text, IPv4 and IPv6, and at /monitoring-checkpoint-ips-whitelist in nginx map syntax. Allowlist the whole list in both protocols, not single cities, because some checkpoints share a nearby server and backup checks can come from other locations. Exempt the Uptimia User-Agent from bot rules. If you block certain countries on purpose, leave their checkpoints out of the monitor's selection.
10Does the response-time chart show each location separately?+
No. The chart draws one series for all of a monitor's locations. Per-location numbers live in Monitoring Logs and the CSV export, both filterable by location. To give a region its own chart and average, add a monitor bound to that region's profile.
11Which monitor types have a location setting?+
Uptime, speed, SSL, transaction, API and DNS monitors. DNS monitors draw from the 88 checkpoints that carry the DNS tooling, and each sweep queries your nameservers from one of them in rotation. Domain, virus, blacklist, heartbeat and server monitors don't depend on where they run from. Real User Monitoring has no checkpoints at all, because its timings come from your visitors' own browsers.
12What does the free plan include?+
The free plan watches 1 website at 5-minute intervals, checked from the same global network with the same location profiles. The 30-day trial removes the limits. You get every monitor type and checks as often as every 30 seconds, with no credit card.

Start checking from six continents

Outages are confirmed from other checkpoints before anyone is paged, and every reading is logged and filterable by location.

Start free trial →
30-day free trial Checks from six continents Per-location logs and CSV export No credit card
The first checks land within a minute of signup.