Multi-region uptime monitoring

Confirm outages.
Respond with confidence.

Know when something breaks. Understand why. Monitor your services, bring your team together, and keep customers informed from one workspace.

10 monitors freeNo credit card
From signal to action
Example workspaceIllustrative data · Pro checks

INC-1042 · HTTP monitor

Checkout API

checkout.acme.dev

Confirmed outage

2 of 3 regions confirm the failure

Two consecutive failures per region. One-minute checks in this example.

  • VirginiaHTTP 503
  • FrankfurtHTTP 503
  • OregonHTTP 200
Team notifiedEmail deliveredSlack delivered
Multiple regions. One confirmed incident.
Real context, before your team responds.

Built around the incident

From the first signal.
To the next customer update.

Set up your first monitor
01 / Detect

Your services. In clear view.

Monitor websites, APIs, TCP services, host reachability, and SSL certificates from one workspace.

Monitor overviewIllustrative data

Checkout API

HTTP

Investigating

Public website

HTTP

Operational

TLS certificate

SSL

Valid
02 / Respond

Evidence travels with the alert.

Regional results and delivery history give your team a shared starting point.

Checkout API is down

INC-1042 · Example alert

HTTP 503 confirmed in Virginia and Frankfurt.

Email deliveredSlack delivered
03 / Communicate

Keep customers in the loop.

Publish clear updates on a branded status page. Monitor targets stay private.

Explore the customer status page

Acme Cloud · Example update

Investigating checkout errors

Our team is working to restore service.

Checkout API09:43 UTC

Independent checks. One shared decision.

One failed path isn't the whole picture.

Require repeated failures across regions before confirming an outage. Compare the signals below to see why a temporary failure doesn't have to become an alert.

Regional confirmation network

Checkout API · Illustrative Pro checks

Compare example signals

Fictional data · Checks one minute apart · Two consecutive failures in two regions required.

  • Virginia

    First check
    503
    Next check
    503
  • Frankfurt

    First check
    503
    Next check
    503
  • Oregon

    First check
    200
    Next check
    200

Shared confirmation rule

2 of 3 regions confirm the outage

Virginia and Frankfurt fail twice. The outage is confirmed and the team receives Email and Slack alerts.

HTTP 200 = successful response · HTTP 503 = service unavailable. The team can publish a customer update on the connected status page.

Simple pricing

Start free. Scale when reliability matters more.

Every plan includes monitoring, incident management, alert delivery, and status pages. Create a free workspace first; request Pro or Business from Billing & usage when you need more capacity.

Free

For personal projects and small services.

$0forever
Start for free
  • 10 monitors
  • Checks every 5 minutes
  • 3 regions per monitor
  • 1 status page
  • Up to 5 members

No credit card required

Business

For production operations across larger teams.

$99per month
Create a free workspace
  • 500 monitors
  • Checks every minute
  • Up to 16 regions
  • 50 status pages
  • Up to 100 members

Start free, request an upgrade later

Every plan includesIncident managementAlert deliveryStatus pages

Pay annually on Pro or Business and receive two months at no additional cost.

Compare every feature

FAQ

Before you start.

Browse all answers
What is included for free?

The Free plan includes 10 monitors, checks every five minutes, three regions per monitor, one status page, and up to five members. No credit card is required.

Will a single failed check alert my team?

You configure the failure threshold and regional confirmation rule. The example above requires two consecutive failures in two of three regions before confirming an outage and sending an alert.

Where can I receive alerts?

Send alerts through email and Slack. Notification rules control which events are delivered, and delivery history helps you see what was sent.

What happens after I create an account?

You create a workspace for your team or project, then add your first monitor and configure its checks. The Organization field is simply the name of that workspace.

How do I upgrade?

Every account starts with a free workspace. Request Pro or Business from Billing & usage when you need faster checks or more capacity. Paid-plan changes are managed by the platform team.

Will customers see my monitor targets?

Public status pages show the service names and updates you publish without exposing private monitor targets or workspace data.

Ready for your first check

Your next outage should not be a surprise.

Create your workspace and start monitoring in minutes.

Start monitoring for free

10 monitors free · No credit card required