Early access. Checks run from one region today, more landing.
Uptime monitoring that tells you what broke.
Checks, a status page, and one alert per outage that says what failed, since when, and what to check first. Flat prices. No per seat fees.
5 monitors free. No credit card. The first 100 workspaces get Solo free for a year.
Monitors
5 up, 1 down, checked from 3 regions
- Marketing sitehttps://example.com1 minute128 ms
- Checkout APIhttps://api.example.com/health30 seconds212 ms
- Nightly export jobheartbeat, every 24 hours24 hours
- Postgres portdb.example.com:54325 minutes9 ms
- Certificateexample.com30 minutes
- Legacy adminhttps://admin.example.com1 minute
Checkout API
99.98%
last 30 days
response time, last 24 checks
Legacy admin is down
Returned 502 from the server in front of the app. Check the app container first, then the deploy at 9:42.
On watch right now, counted from our own database
- 7
- Monitors watched
- 130
- Checks in the last 24 hours
- 1
- Incidents caught
- 1
- Probe regions
We monitor our own services and uploadworthy.com with it since October 31, 2026. See the live status page.
Catch downtime before your users do.
Six kinds of checks, from every 30 seconds to every half hour.
Website and API
A URL that must answer with a good status code, within the time you set.
Keyword
A page that must contain, or must not contain, a piece of text.
Port
A host and port that must accept a connection: database, mail, SSH.
SSL certificate
A certificate that must be valid and not expire within your window.
DNS
A name that must resolve, optionally to the addresses you expect.
Cron heartbeat
A job that pings a URL on schedule, with numbers you want watched.
One alert per outage
The alert explains itself.
Most monitors tell you something is down. Ours reads the evidence the checks already have and writes it back in plain words: what failed, since when, what it points to, and the first thing to check. One message when it breaks, one when it recovers, nothing in between.
- Confirmation check before anyone is paged
- Your other monitors named, so you know what is not affected
- Raw evidence kept under the note
api.example.com is down
Down for 4 minutes from 3 of 3 regions. The server accepts the connection but the load balancer returns 502, which usually means the app behind it crashed or is restarting.
Check first: the app container, then the deploy that landed at 9:42. The marketing site and the database port are fine.
Status page set to Investigating at 9:47. We will send one more message when it recovers, and nothing in between.
Example Co. status
- Website100.000% over 90 days
- API99.982% over 90 days
- Background jobs99.991% over 90 days
- Database100.000% over 90 days
Status pages
A status page that stays up when you do not.
Components follow your monitors. Incidents open and close on their own with a 90 day history, and you add a note when you want to. Included on every plan, with your own address.
See ours, liveCron jobs and servers
Infrastructure numbers, no agent to install.
Your job pings a URL when it runs. Send a few numbers with it, disk, memory, queue depth, rows exported, and set a threshold. Late or over the line, you get one message that says which.
pg_dump mydb | gzip > /backups/$(date +%F).sql.gz
# tell Infrachamp the job ran, with the numbers you care about
curl -s -X POST https://infrachamp.com/api/hb/<your-token> \
-H 'content-type: application/json' \
-d "{\"disk_percent\": $(df --output=pcent / | tail -1 | tr -dc 0-9),
\"backup_mb\": $(du -m /backups | tail -1 | cut -f1)}"Alerts where your team already is
Switching from another tool?
Add your monitors by URL today; CSV import is on the way. Here is how the plans compare, as published in October 2026.
Switching from Pingdom
No free tier, entry plans priced for enterprise accounts.
Switching from UptimeRobot
Free plan no longer allowed for commercial use since November 2024.
Switching from Freshping
Shut down on 6 March 2026 with about two weeks' notice.
Switching from Better Stack
Priced per responder seat, so the bill grows with the team.
Flat plans. No per seat fees.
Pick by how much you monitor, not by how many people get paged. Nothing is charged during early access.
Free
$0
- •5 monitors
- •Checks every 5 minutes
- •1 status page
- •Email alerts
- •Plain language incident notes
Solo
$12a month
- •25 monitors
- •Checks every minute
- •1 status page
- •Email, Slack and webhook alerts
- •Plain language incident notes
- •90 days of history
Team
Most teams$49a month, or $490 a year
- •100 monitors
- •Checks every 30 seconds
- •3 status pages
- •SMS and phone call alerts
- •On call rotation
- •Unlimited seats, no per person fee
- •1 year of history
Questions
- Is this live today?
- Yes. Monitoring, alerts, incidents and status pages run now. We call it early access because features are still landing weekly and we open accounts in batches to keep the service healthy.
- Where do the checks run from?
- From probe locations on more than one cloud provider, with new regions being added. An outage is called only after a confirmation check agrees, which is what keeps false alarms out of your sleep.
- Do you charge per seat?
- No. Every plan has unlimited people. You pay for how much you monitor and how often.
- How does the alert know what to check?
- From the evidence the checks already collect: which regions failed, the response code and headers, whether the port answers, whether DNS and the certificate resolve, and which of your other monitors are fine. The note reads that evidence back in plain words. It does not guess beyond it.
- Can I bring monitors from another tool?
- Add each monitor by URL today; checks start within a minute. CSV import from UptimeRobot, Pingdom and Better Stack is being built and lands during early access.
- What does it cost?
- Free for five monitors. Solo is $12 a month, Team is $49 a month or $490 a year. Nothing is charged during early access, and the first 100 workspaces get Solo free for a year.
Start monitoring in a minute.
Five monitors free, no card, and a status page from day one. Add your email under Alerts and the first outage will explain itself.