Monitoring · Available on All tiers

One bad route shouldn't page you at 3am.

Check from up to 3 independent regions at once, and only alert when every one of them agrees your site is actually down.

Start Free → See pricing

Free forever plan, no card required.

Why it matters

Distributed multi-region checks

A single-region monitor can't tell the difference between "the site is down" and "the network between here and there had a bad five seconds." That's how teams end up desensitized to alerts — or worse, asleep through a real outage because the tool cried wolf too many times before. Picture a Tuesday afternoon: a transit provider three hops from your single check location has a rough five minutes, your monitor flips to Down, and the whole on-call rotation gets paged over nothing. Watch that happen twice more in a month and the next real outage gets a shrug instead of a scramble, because everyone's learned the alert probably doesn't mean anything. Checking from multiple independent regions and requiring them to agree removes that ambiguity — a page only fires when the failure is real from more than one vantage point, which is the only way to build a monitor your team still trusts by the hundredth alert. It's the same reason a doctor takes your blood pressure more than once before diagnosing hypertension — one reading in isolation just isn't enough evidence to act on. That's not paranoia — it's just matching the level of certainty to the size of the decision being made, which for a page that wakes someone up is worth getting right.

Confirmed, not guessed

A monitor only flips to Down once every region you've selected agrees — not the first region to report trouble, not a majority vote, all of them. A partial failure names the specific region that failed instead of a blanket "down," so if only your European runner can't reach the site, the incident says exactly that instead of implying the whole thing is offline everywhere at once. It's a conservative bar on purpose — better to wait the extra few seconds for full agreement than to page someone over what turns out to be nothing. Think of it as a jury needing a unanimous verdict rather than a simple majority before handing down anything as serious as a page.

Runners, not a single vantage point

Checks execute on independent runner servers assigned to a region, dispatched round-robin — never through your own network path, never through the API server itself. That separation matters: if a check ran on the same infrastructure serving your dashboard, a problem with UptimeLuna's own network could masquerade as your site being down, or hide a real outage behind a false all-clear. Independent runners mean the result reflects what an actual visitor in that region would see. It's the kind of separation that's easy to overlook until the one time it actually matters, and by then it's too late to add. Nobody wants their monitoring tool's own hiccup mistaken for their product's outage, and this is exactly what prevents that mix-up.

Scales with your plan

1 region on Free, 2 on Starter, 3 on Team — upgrade only when you actually need the extra confirmation. A side project checked from one region is still miles ahead of no monitoring at all; a business where downtime costs real money is usually worth the jump to Starter or Team, where a second or third region turns "probably down" into a confirmed incident before anyone gets paged for nothing. Either way, the choice of how much confirmation to pay for is yours, not a fixed default baked into the product. Most teams start on Free to prove the alerts work at all, then add regions once actual customers are depending on the uptime.

FAQ

Distributed multi-region checks, answered.

How many regions can I check from?

1 region on Free, 2 on Starter, and 3 on Team — upgrade only when you actually need the extra cross-region confirmation. On Starter and Team you also choose which regions to check from, so you can pick vantage points that actually matter for where your customers are, rather than being assigned a fixed set with no control over it. It's worth picking regions closest to where your actual traffic comes from rather than just defaulting to whatever's listed first. Switching which regions a monitor checks from is a settings change, not a support ticket.

What happens when regions disagree?

A monitor only flips to Down once every region you've selected agrees. If only some regions fail, the incident names the specific region affected instead of a blanket "down," so you can tell at a glance whether you're looking at a real outage or a routing problem local to one part of the world — a distinction that saves a lot of unnecessary troubleshooting. It also means you don't have to manually cross-reference multiple dashboards or tools just to figure out where a failure is actually happening. You'll never have to guess whether "down" meant everywhere or just somewhere.

Does checking from more regions slow down how fast I find out?

No — every selected region checks on the same interval as your plan, down to 30 seconds on Team, and they run in parallel rather than in sequence. Confirming across regions typically adds only the time for the slowest region's check to return, which is still far faster than waiting for a customer to notice and tell you. In practice, most confirmed incidents are reported within the same minute the underlying failure started, region-agreement included. There's no tradeoff to weigh here between speed and accuracy — you get both.

Get Started

Distributed multi-region checks. Free, starting now.

Start Free →