Between checks
As often as once a minute.
Checks as often as every minute, outages confirmed on the second failed check, an alert by email, Slack, Teams or Telegram, and a status page with your logo on it.
A preview of the workspace overview: twelve monitored sites, one of them down with an open incident.
As often as once a minute.
A second failure confirms it.
See the pattern over time.
Reach the people who respond.
One workspace. Every critical endpoint.
Checked from several regions. Every live region confirms an outage before the incident opens.
HTTP, TCP, DNS, ping, mail servers, browser flows and cron heartbeats. One timeout is noted; two in a row open an incident and the alert goes to email, Slack, Teams, Discord, Telegram, a webhook or your phone.
Your logo, theme and domain, 90 days of uptime bars per site, maintenance notices and email subscribers.
Owners, admins, site admins who get only the sites you assign, and viewers who see everything and change nothing.
The check that opens an incident records what it saw: the DNS answer, the connection, the TLS handshake, each timing phase and the response. One plain sentence names the cause, so nobody starts by guessing.
Once a day each site is read from the outside for what no uptime check sees: a noindex tag that reached production, an analytics tag that vanished, WordPress plugins with known vulnerabilities, API keys and source maps left in public scripts.
Heedery learns each site’s usual response time from the last seven days. When it gets clearly slower, suddenly or week over week, you hear about it before it turns into an outage.
PageSpeed is measured for you and a drop is logged as a change. Claude reads the stored report and writes a short plan: what to fix first, what it should bring and how to do it on your stack.
A REST API and an MCP server over the same workspace. Connect Claude or Cursor and ask what is down, read an incident or add a monitor without opening the dashboard.
Paste the API key of your UptimeRobot or Better Stack account. Heedery shows what will come over, what changes on the way and why, and creates only what you tick.
Every site is checked on its own schedule, down to once a minute: HTTP with DNS, connect, TLS and first-byte timing, TCP and UDP ports, DNS lookups, ICMP ping, and SMTP, IMAP or POP3 servers. Browser flows walk through a site in a real browser and cron jobs ping a heartbeat URL. A single timeout is usually the network, so nothing is reported until the next check fails too.
pay.acme.com did not answer within 10 s. Nothing is sent yet.
The next check fails too. The incident opens and the status page shows Checkout as down.
Microsoft Teams message in #ops, right away or after the delay set on that channel.
Two good checks in a row. The incident closes after 2 min and #ops hears about that too.
Each status page has its own address, name, logo and theme, scheduled maintenance and an announcement banner, and 90 days of uptime bars per site. Visitors can subscribe to hear about incidents and maintenance by email. SSL and domain expiry are checked daily so renewals stop being surprises.
The Heedery app for iPhone and Android gets a push the moment an incident opens. It is marked time-sensitive, so it gets through Focus, and a tap opens the incident to acknowledge it. On Pro and up, an escalation policy decides who hears next and when, and an on-call schedule decides who that is this week.
From Team up, each client can get a monthly report by email: a PDF with their logo, uptime against the target you agreed, downtime, incidents, response times and the month day by day. Their status page can go white label: no “Powered by”, their domain and favicon, and subscriber emails sent from their own address.
Target metUptime was 99.92% vs 99.9%
Invite the team and give each person a role: owners manage billing and people, admins manage every site, site admins get the sites you assign and nothing else, and viewers see everything without changing a thing.
DNS records and the certificate from Pro, page content and PageSpeed from Team. Every change is logged; you pick which ones alert.
From Pro, CI reports each deploy with one request. It is marked on the charts, and an incident that starts within 30 minutes names it.
Claude writes the status update from the incident’s facts, and the postmortem once it is resolved. You check it, edit it and publish; nothing goes out on its own.
Choose by the sites you monitor and the people on your team.
Save up to 21% with yearly billing
For a personal project or a small shop.
Free, no card required
Start for freeFor a freelancer or a small team with a few sites.
$132 billed yearly
Get ProFor product teams that run a few services.
$384 billed yearly
Get TeamFor agencies that run status pages for their clients.
$984 billed yearly
Get Agency1,000 monitors · Unlimited team members · SLA
No trial needed: Starter is free with no card. A paid plan's button creates your account, then takes you to the plan's checkout; it starts as soon as the payment goes through. Or start free and pick a plan later under Settings → Plan.
Prices in USD, excluding VAT. Every plan includes the public status page with unlimited viewers. White label is per status page: $49 a page a month on Pro, $29 on Team, and on Agency 5 pages are included and each further one is $19.
With one-minute checks an outage is confirmed by the second failed check, so within about two minutes. Email goes out right away; Slack, Teams, Discord, Telegram and webhooks right away or after the delay you set on the channel.
Setup, alerts, billing or a plan for your company: a person reads every message and answers within one working day.
The first check runs within a minute.
Start for free20 monitors free, No card required
See what a status page looks like