Uptime monitoring
that asks a second region first.
Your site is checked every 5 minutes on Free, every minute from Solo, every 30 seconds from Team when you choose it, from two regions. One blip in one place sends no alert; an outage sends one alert with what each region saw.
- Free: every 5 minutes
- Solo: every minute
- Team: every 30 seconds when you choose it
How it works
Add a site and the rest runs by itself.
Add your site
Paste one address or a list of them. Each site starts with a page, a certificate and a DNS check, from every region, with nothing to install.
Two regions check it
The page passes on a 2xx answer, and can be asked to contain a piece of text, which catches a page that answers but shows an error. Each region records its answer and its time.
Down only when both agree
One region failing is a regional issue: recorded, no alert. When a second region confirms it, you get one alert with what each region saw, and another when fresh checks pass.
What you get
No alert for a blip
A site is called down only when at least two regions fail to get a valid answer. A check that could not be made shows as data unavailable, never as up.
Response time per region
Every check keeps its time, region by region, so a site that slows in one place shows it before it falls over.
Planned work left out of uptime
Planned maintenance is left out of uptime and holds alerts back, while the checks keep running and keep their evidence.
More than a page, from Solo
API checks with assertions on the status, headers, JSON values and response time, TCP port and reachability checks, and alerts for a sustained slowdown.
Which plans include it
Uptime checks from every region are on every plan, Free included; the plan sets how often.
- FreeIncludedChecks every 5 minutes
- SoloIncludedChecks every minute
- TeamIncludedChecks every 30 seconds when you choose it
- AgencyIncludedChecks every 30 seconds when you choose it
- Agency PlusIncludedChecks every 30 seconds when you choose it
Questions about uptime monitoring
How often is my site checked?
Checks run every 5 minutes on Free, every minute from Solo, every 30 seconds from Team when you choose it.
Why does one failing region not send an alert?
Because one region can fail for reasons that have nothing to do with your site. Beamfar records it as a regional issue and alerts only when a second region confirms the failure.
What counts as down?
At least two regions failing to get a valid answer: no answer, a timeout, an error status, or a page that is missing the text you asked it to contain. A check that could not be made is shown as data unavailable, never counted as up.
Where do the checks come from?
From Falkenstein (Germany) and Helsinki (Finland). The addresses to allow in a firewall are in the help centre, under which checks a site gets.
Does planned maintenance count as downtime?
No. During a maintenance window the checks keep running, alerts are held back and the time is left out of uptime.
Related guides
- Two-region confirmation and false alarmsWhy single-location checks raise false alarms, how re-checks and multi-region confirmation differ and what each costs.
- How often should you check a website?How the check interval sets the delay before you learn of an outage, with the formulas and what to choose per site type.
- Where the minutes go between outage and alertWhere the minutes go between an outage and your alert, and what to set up.
Hear about outages, with the proof.
Add your sites: checking starts as soon as you do.
No card for the Free plan.