Skip to content
StatusOwlDocs

Monitoring regions

Every monitor checks from one region. Multi-region checking is built and deployed but capped at one region per monitor on every plan — here is exactly where it stands.

Last updated
Multi-region checking is not available

Every monitor on every plan — Free, Starter, Growth and Scale — checks from one region. There is no plan you can buy, and no setting you can change, that raises this today.

If you need checks from several vantage points, StatusOwl is not currently the right tool and we would rather you knew that before signing up than after.

What actually exists

Multi-region checking is not vapour. It is built and running:

  • Monitors carry a region list rather than a single region.
  • Checking nodes are assigned to regions.
  • The scheduler already dispatches a monitor's check per region.
  • Results are written per region, so the data model holds one row per region per interval.

What is missing is node capacity in enough locations to promise it. Rather than sell three regions and route them all through one datacentre, the per-monitor region limit is set to 1 across the board until the capacity is real.

You can read the current state of it on the roadmap, where it sits under "Up next" with this same explanation.

What you get instead

False positives are filtered by time, not by geography. A monitor's consecutive-failure counter has to reach three before an incident opens on your status page. A single transient failure never publishes anything. See Automatic incidents.

That is a weaker filter than regional agreement — a genuine network problem between the checking node and your origin will still produce three failures in a row. It is honest to call this a limitation rather than a design choice.

Dedicated and self-hosted nodes. If the problem you are solving is "the shared checking pool cannot reach my service" rather than "I want a global view", a dedicated node solves it. Dedicated single-tenant nodes are available on Starter and above — 1 on Starter, 3 on Growth, unlimited on Scale — and include nodes you run inside your own network. That gets a check onto the right side of your firewall, which multi-region would not have done anyway.

If you try to set more than one region

The API rejects it. Creating or updating a monitor with more regions than your plan allows returns a 403 naming the limit:

json
{ "error": "Region limit exceeded. Your plan allows 1 region(s) per monitor." }

The regions field is present on the Monitors API response and will contain exactly one entry.

What to do if you need this today

Be direct about it: use a monitoring product that ships multi-region checking, and — if you still want StatusOwl's status page — keep the two separate. StatusOwl has no way to receive another product's alerts: the webhook integration is outbound only, and the public API is read-only, so there is nothing to pipe results into today. Hyperping and Better Stack both do multi-region checking well.

We would rather send you somewhere that solves your problem than have you find out after you have wired everything up.

See also