When it breaks, your status page says so.
Sentivel checks your sites and APIs, updates your status page the moment something fails, and pages whoever is on call.
Free for 10 monitors and a status page on your own domain. No card.
All systems operational
Updated 14:02
api.acme.com answers 503 from Dublin. One failure, so nothing changes yet.
When Stripe breaks, say it’s Stripe.
Tell Sentivel which parts of your product run on which providers. When one of them has an incident, your status page names it and says what may be affected. When they recover, the advisory comes down by itself.
It’s optional. A status page with monitors and no providers linked is a complete setup.
How advisories workSome services may be affected
We're aware of an ongoing issue with Stripe, a service we rely on. Some functionality may be affected until it's resolved.
Written by Sentivel, word for word. You can replace it with your own. See every provider we follow
One bad check stays one bad check.
A failed check is tried again, then from another region. Your status page only changes when the failure is real.
Websites and APIs, keyword and JSON checks, TCP ports, DNS records, game servers, and heartbeats for cron jobs.
A network blip
- 14:02:10Dublin: 503
- 14:02:12Dublin, again: 200
- Nothing changes. Nobody is paged.
A real outage
- 14:02:10Dublin: 503
- 14:02:12Dublin, again: 503
- 14:02:40Virginia: 503
- 14:03:00Incident opens. Status page updates.
Page one person. Escalate if they don’t answer.
Set who hears first and who’s next. The moment someone acknowledges, the ladder stops.
Email, Slack, Discord and webhooks on every plan. Text and phone calls from Pro.
- Right awayMaya, on callText and Slack
- After 5 minutesMayaPhone call
- After 10 minutesSam, backupText and phone call
Maya acknowledged at 14:05. Nobody else was paged.
Set it up by asking.
Connect Claude, Cursor or any MCP client to Sentivel and describe what you want. Everything it does goes through the same permissions as your team.
There’s a REST API for everything else. Read the docs
Used sentivel_create_http_monitor, sentivel_set_status_page_layout
Done. api.acme.com is checked every five minutes, and “API” is now on status.acme.com. It reads operational after its first few healthy checks.
Free for 10 monitors and a status page on your own domain.
Paid plans start at $5 a month, billed yearly, for faster checks and longer history.
Compare plansSentivel is made by a small team in London. If something is missing, confusing or broken, write to us and the people who build it will answer.
hello@sentivel.comQuestions people ask first
- Do I need a card to start?
- No. The Free plan never asks for one. A card is only needed to start a 14-day Pro trial or to upgrade.
- Can it use my own domain?
- Yes, on every plan. Point a CNAME such as status.yourcompany.com at us and HTTPS is set up automatically.
- What happens if Sentivel goes down?
- Your status page is served from a cache at the edge, so it keeps loading if our servers don’t. Every public page is also copied to mirror.sentivel.com, on separate infrastructure, every 15 minutes.
- I already use Statuspage or Instatus.
- Import your components, incident history and subscribers from the dashboard. Monitors are added separately, one URL at a time or a whole list at once.
- How is this different from an uptime monitor?
- An uptime monitor tells you something broke. Sentivel also tells your customers, through a status page that updates from the same checks, and pages whoever is on call.
- Where is my data stored?
- In the EU, in Ireland. The full list of companies that process data for us is in our privacy policy.
