How upzo works
Upzo watches your websites around the clock and tells you the moment one goes down — before your customers notice, before support tickets arrive, before anyone has to ask "is the site down?".
This page explains what upzo does in detail. If you just want the short version, start here.
The problem it solves
When a website goes down, there are usually two ways you find out:
- A customer tells you.
- You happen to check.
Neither is good. Customers who hit a broken site often don't complain — they leave. And manual checking doesn't scale, especially across multiple products, environments, or client sites.
Upzo is the third option: you find out immediately, automatically, from a system that never sleeps.
What upzo monitors
You give upzo up to 5 URLs. These can be anything publicly reachable:
- Your main marketing site
- Your app or product URL
- A customer-facing API endpoint
- A staging or pre-production environment
- A client's site you're responsible for
Every URL is checked independently, on its own schedule.
How the checks work
Every 60 seconds, upzo sends a request to each of your URLs and records the response.
A URL is considered up if it returns a successful HTTP response within the expected time window.
A URL is considered down if it fails two consecutive checks. The two-check rule is intentional — it filters out the brief, transient hiccups that happen on any network and aren't worth waking you up for. If the second check also fails, that's a real incident, and alerts go out immediately.
When the URL recovers and returns a successful response, upzo sends a second round of alerts so you know it's back without having to check.
The dashboard
Your dashboard shows all your monitored URLs at a glance. For each one you can see:
- Current status — up or down, right now
- Response time — how long the last check took
- Uptime — percentage over the past 30 days
- Incident history — a full log of every outage: when it started, how long it lasted, what error was returned
The dashboard updates in real time. You don't need to refresh.
How alerts reach you
When an incident is detected, upzo sends alerts through whichever channels you've enabled.
Email — a plain, direct message with the URL, the time it went down, and the HTTP error or timeout reason. No formatting noise. Arrives within seconds of the second failed check.
SMS — a short text message to your mobile number with the same information. Useful if you're away from a screen or want a backup to email.
You can enable one or both. You can update your alert settings at any time from your account — changes take effect immediately.
When the site recovers, you get a matching recovery alert on the same channels, so you know the incident is over without having to log in to check.
What you do with an alert
Upzo's job ends at the alert. What you do next depends on your setup — restart a server, call a developer, roll back a deployment, contact a host. Upzo doesn't try to fix anything, and it doesn't integrate with your infrastructure. It's a clean, single-purpose tool.
That's by design. The alert is reliable precisely because the system is simple.
What happens to your data
Upzo keeps your full incident history for as long as your account is active. Nothing is automatically pruned. If you want to review an outage from six months ago, it's there.
If you cancel or your trial ends without subscribing, your account stays accessible and your data is kept intact. Monitoring pauses, but nothing is deleted. You can export your data at any time from account settings.
Who it's for
Upzo is a good fit if you:
- Run a SaaS product, agency, or any business where website uptime matters
- Want a simple, low-maintenance monitoring tool without a learning curve
- Need to keep an eye on a small number of URLs — your own or a client's
- Want to be the first to know, not the last
It's not the right tool if you need to monitor dozens of URLs, require advanced alerting rules, or want deep infrastructure monitoring. Upzo does one thing and keeps it simple.