Website and infrastructure monitoring

See what's happening from the outside.

Sentinel monitors websites, APIs and the infrastructure behind them from 15 regions on six continents. Every check runs from every region, so when something breaks you can see where, and whether it's your service or the network in between.

15s
Fastest check interval
15
Regions on every check
6
Continents
10
Monitors free, no card

Monitoring

More than an uptime check.

A site can answer 200 OK with a broken page, a certificate a week from expiring and a backup job that quietly stopped on Tuesday. Sentinel watches each layer on its own, so every service gets the checks it needs.

Global monitoring

Every check.
Every region.

Plenty of monitors rotate checks between locations, so each result is one place's opinion. Sentinel doesn't rotate. All 15 regions check every monitor in every interval, spread out so they never arrive as one burst.

A failure becomes a pattern you can read. Global or confined to one part of the world, and how response times compare from Seoul to São Paulo.

How multi-region monitoring works →

Sentinel's network

15 regions · 6 continents

AshburnChicagoSeattleTorontoMexico CitySão PauloLondonFrankfurtTel AvivJohannesburgMumbaiSingaporeTokyoSeoulSydney

Outage confirmation

One failed check isn't an outage.

Routes flap, and a single data center loses its connection now and then. Sentinel opens an incident only when at least half the regions fail, with three or more of them on at least two continents. It closes once failures drop below that line.

When a service is known to blip, give its monitor a confirmation period and a recovery period of its own.

How Sentinel confirms an outage →

Alert decision

Regions checked
15
Failing
1 (Frankfurt)
Needed for an outage
8, on two continents
Verdict
Regional, no alert

Frankfurt's timeouts stay on the monitor for you to see. Nobody gets paged.

Incident evidence

See what happened, not just that it failed.

A red dot starts an investigation. Sentinel keeps what every region observed around it, so you start from evidence.

Incident management →

Results by region

Each region's latest status and response time sit side by side on the monitor, instead of one blended number.

Request phases

DNS, TCP, TLS, TTFB, download

Response time split into its phases, so a slow check shows where the time went.

Observed failure reasons

Connection refused, DNS failures, TLS errors, timeouts and HTTP errors, recorded the way each region saw them.

Incident timeline

The failing checks, the confirmation and the recovery, kept with the incident so the history is there when someone asks what happened.

Traceroute

Captured automatically

When an incident opens, Sentinel records the network path to the target.

How it works

Monitoring in 30 seconds.

  1. 01

    Add what you want to watch

    A URL, a hostname or a port, and the checks that matter for it.

  2. 02

    Sentinel starts checking

    From all 15 regions, as often as every 15 seconds depending on your plan.

  3. 03

    A failure comes with evidence

    Regional results, request phases and what each region saw, before anyone starts guessing.

  4. 04

    The right people hear about it

    Email, SMS, chat, PagerDuty or webhooks, and a status page when customers need to know too.

FAQ

Fair questions.

Still have questions? Get in touch.

What can Sentinel monitor?

HTTP and HTTPS uptime, page content and keywords, server errors on pages that return 200, JSON APIs, SSL certificates, DNS records, domain expiration, ICMP ping, TCP ports, heartbeats, cron jobs, and x402 and MPP payment endpoints.

Who is Sentinel built for?

Developers, DevOps and platform teams who need an outside view of the sites and services they run. SaaS and ecommerce teams use it too, and so do agencies and freelancers looking after client sites.

Does every check run from all 15 regions?

Yes, on every plan, the free plan included. Every region checks once in each interval, so no region sits an interval out. The checks are spread out rather than sent together, so your server never gets fifteen requests in the same instant.

How does Sentinel decide a site is down?

An incident opens when at least half the regions fail and the failures include three or more regions on at least two continents. It closes once failures drop below that. Each monitor can also wait out short blips with its own confirmation and recovery periods.

How often does Sentinel check?

Every 15 seconds on Business, 30 seconds on Pro, one minute on Starter and five minutes on Free.

Can I manage Sentinel without the dashboard?

Yes. There's a REST API, a CLI, a Terraform provider and an MCP server for AI assistants, and a GitHub app that marks deploys and pauses checks during deploy windows.

How will I be alerted?

By email, SMS, Slack, Microsoft Teams, Discord, Telegram, PagerDuty or signed webhooks. You choose which channels each monitor uses.

Is there a free plan?

Yes. The free plan has 10 monitors and needs no card. Paid plans include a 14-day trial, and they need a card, trials included.

See your stack from the outside.

Your first monitor, checked from 15 regions, in 30 seconds.

No card for the free plan · 14-day trial on paid plans · Cancel anytime