Uptime, API and browser monitoring
Know it brokebefore your customers do.
Know It Broke checks your websites, APIs, servers and scheduled jobs, as often as every minute. When one stops working it tells the right person at once, and tells them again when it is back.
- Secrets encrypted with AES-256
- Card details held by Stripe
- Single sign-on on every plan
- Two-step sign-in
- No trackers
- How it is kept safe
An example of the board
1 of 3 needs you
Checkout API is downCheckout API
HTTPSign-in flow
BrowserNightly backup
HeartbeatAn example board. Each card is a node: one thing being watched.
How it works
From broken to told, in about a minute
- 09:41A check fails
The API answers 503. One bad answer could be a blip, so nobody is woken yet.
- 09:42It is checked again
A minute later it fails a second time. Two in a row means down.
- 09:42The right person hears
The alert goes to whoever is on for that time of day: Slack by day, a pager by night.
- 09:48It comes back
The next check passes. Everyone is told it is back up, and how long it was down.
Times are an example. Checks run as often as every minute.
What it watches
Five kinds of node
Website or API
Calls an address and judges the answer: status, text in the body, a value in the JSON, a header, how long it took. Send your own method, headers and body.
Browser flow
A real Chromium opens your site and does what a customer does: clicks, types, waits for text. It stops at the first step that fails and keeps a picture.
Port
Checks that a server still accepts connections. For databases, mail servers and anything else that is not a web page.
DNS record
Checks a domain still points where it should. A, AAAA, CNAME, MX, TXT or NS, with the value you expect.
Heartbeat
The other way round. Your backup or scheduled job calls an address when it finishes. If the call does not come, you hear about it. More on cron job monitoring
Browser flows
Test the journey, not only the page
A page can answer 200 and still be broken. A browser flow signs in, adds to the basket, or submits the form, the way a person would.
You build it from plain steps. No scripts to write. When a step fails you see which one, why, and a picture of the page at that moment.
- Open example.com/login0.6 s
- Type into #email0.1 s
- Type into #password0.1 s
- Click text=Sign in0.4 s
- See the text "Welcome back"1.6 s
5 steps passed in 2.8 s
Alerts
Tell the right person, not everyone
Send alerts to Slack, Discord or any webhook, by email through your own mail server, by text message, to PagerDuty, or to your own API with your own headers and body.
Alert groups decide who hears by time of day, so office hours go to the channel and three in the morning goes to whoever is on call. Every route has a "Send a test" button.
Status page
A public page your customers can check
Every account gets a status page at its own address. It shows which nodes are working and 60 days of history. You choose which nodes appear.
When something is wrong, publish a message and post updates as you go: investigating, cause found, watching the fix, resolved.
Card payments are failing
Cause found- Cause found 09:51
A bad release. We are rolling it back now.
- Investigating 09:44
We are looking into failed payments.
Website
WorkingGetting started
Watching in three steps
Add a node
Type an address and press "Test it" to see the result before you save. Add checks for what a good answer looks like.
Say who hears
Add a route, send it a test, and group routes by time of day if you want to.
Share your status page
Give customers the link. It keeps itself up to date.
Security
You are handing over your keys. They are kept like it.
A monitor has to hold API keys, passwords and alert tokens to do its job. That makes it a target, so Know It Broke was built around keeping them safe, not with security added afterwards.
Encrypted before it is stored
Every header value, request body, password and alert key is encrypted with AES-256-GCM. The key is kept apart from the database, so the database alone gives nothing away.
Saved once, then only dots
After you save a secret the console shows dots. It is never sent back to your browser, so it cannot be read off a screen, a screenshot or a shared session.
Single sign-on, or a second lock
Sign in through Microsoft Entra ID, Okta or Google Workspace on every plan, at no extra charge. Or keep your password and add a code from the authenticator app on your phone. No texts or emails to intercept.
Your card never comes near us
Stripe takes payment on its own page. No card number is ever sent to Know It Broke, so there is none here to leak.
Cannot be turned on your network
Checks name themselves and come from published address ranges. Private and internal addresses are refused, so nobody can aim it at the inside of a network.
Delete means delete
Remove your account and everything goes at once: nodes, history, alert routes and secrets. Your data is never sold or shared.
The details
Small things that matter at three in the morning
Nothing watching you
No analytics, no advert pixels, no scripts from anyone else. A strict browser policy refuses them.
Nothing to install
No agent, no plugin, nothing on your servers. Add an address and it is being watched.
Firewall friendly
Pick where each node runs from: UK, Germany, US East, US West, Singapore or Australia. The Setup page lists the address ranges to allow and how checks name themselves.
History you can read
Every run is kept for 30 days with its timing and the reason it failed. Daily uptime is kept for 90.
From £50 a month.Three plans.
Basic, at £50, holds 10 nodes with no browser flows. Standard, at £100, holds 25 nodes and 3 browser flows. Plus, at £250, holds 35 and 6. All three have every kind of alert and a status page. Cancel any time.