Know your site is down
before your customers tell you.
We check your sites every few minutes from our servers. When one stops responding, you get an email — with the time in your own timezone and what actually went wrong.
- 5 monitors free
- No credit card
- First check within a minute
My Blog
priyablog.com
What we found just now
The page did not load. Your domain, server and certificate are all fine — this looks like a problem with the site itself.
- Domain name41 ms
- Server connection189 ms
- Secure certificate96 ms
- Web pagetimeout
Website monitoring for developers and businesses
- SaaS
- E-commerce
- Agencies
- Startups
- Freelancers
60s
Fastest check interval
2
Failures before we alert
5
Monitors on the free plan
90 days
Of check history kept
The problem
An alert is just the beginning.
Most people find out their site is down from an angry customer — and then spend the next twenty minutes guessing whether it is their server, their DNS, their certificate, or something they depend on.
One tap in the alert answers all of it, in plain words.
- Sees exactly what broke — domain, server, certificate, or the page itself
- Checks whether your own device can reach it, too
- Tells you if a service you depend on is having issues
- Explains it in plain words, not a status code
How it works
Add a site. We do the watching.
- 1
You add a URL
Give it a name and choose how often to check — from every minute to every hour.
- 2
We check it, and wait for a pattern
Every check is recorded. We wait for two failures in a row before calling it down, so one blip does not wake you.
- 3
You get one email, with the cause
Not one per failed check — one per outage, with what broke and a one-tap link to check it yourself.
Key features
What you get
Everything below is built and working today.
Checks as often as every minute
Pick the interval per site — every minute for a shop, every ten for a blog. We record the response time of every single check.
Alerts you can trust
We never alert on a single blip. A site has to fail twice in a row before we call it down, so a one-second hiccup does not wake you at 3 AM.
Times in your timezone
An alert says “went down at 2:20 AM”, not a UTC timestamp you have to convert while half asleep.
What broke, not just that it broke
Timeout, DNS failure, refused connection, bad certificate, or the wrong status code — each is reported for what it is.
Check it yourself, from the email
One tap in the alert runs a fresh check and tells you in plain words which part is broken — your domain, your server, your certificate or the page — and whether your own phone can reach the site when we cannot.
Response times over time
A site that is slowly getting slower never technically goes down. Charts with p95 response times show the problem weeks before the outage.
A record of every outage
Each incident is logged with when it started, when it recovered, how long it lasted and what caused it.
Alerts for the tools you depend on
Subscribe to Cloudflare, GitHub, Stripe, OpenAI, Claude and more — we watch their own status pages and email you the moment one goes down, right alongside your own sites.
Dependencies
Your site does not fail alone.
A perfectly healthy server does not help if Cloudflare, GitHub, Stripe or another platform you depend on is down. Subscribe to the ones your site relies on, and we watch their status pages alongside your own — and tell you if one caused your outage.
- Cloudflare
- GitHub
- Stripe
- OpenAI
- Claude
- + more
example.com
HealthyServices you depend on
- CloudflareDegraded
- GitHubOperational
- StripeOperational
- OpenAIOutage
If one of these was disrupted at the same time as your outage, your alert email says so — instead of leaving you to check each status page yourself.
What we do not do yet
Alerts are email only, and checks run from one location. We would rather tell you now than have you find out after signing up — here is the full list and what we are building next.