Know it's down before your customers do.
Most teams learn about downtime from an angry email. UptimeStatus checks your endpoints every 30 seconds from six regions and tells you first.
Checked around the clock, from where your users are.
Human error, a bad deploy, an expired card at your host: sites go down for mundane reasons at inconvenient times. Refreshing the page yourself does not scale past the first incident.
UptimeStatus probes each monitor on the schedule you choose, records what it saw, and treats a failure as an event with a timeline, not a line in a log you will read tomorrow.
Every failure comes with the evidence.
An alert that says "DOWN" starts a debugging session. An alert that says "HTTP 502 in 84ms from Frankfurt at 03:12" nearly ends one.
Each check stores its status code, response time, error message, and probe region. When something breaks you scroll the check history and watch it happen, instead of guessing from memory.
What uptime monitoring includes.
- Checks every 30 seconds on the Pro plan, from six global regions. Self-hosted installs choose their own interval and worker regions.
- HTTP, TCP, and ping monitor a URL, a raw port, or a host. Each check type gets its own page under Features.
- Full result history status code, response time, error message, and probe region stored for every single check.
- Automatic incidents a failing monitor opens a timeline incident, notifies your channels, and updates your status page.
- Maintenance windows schedule planned work so your status page shows maintenance instead of an outage.
- Response-time tracking every check records latency, so slowdowns are visible long before a hard failure.
Scriptable from day one.
Monitors are records in an API, not rows in someone else's dashboard. Create them from your deploy pipeline, your CLI, or a one-off script, and trigger an out-of-band check whenever you want a second opinion.
The same API powers the dashboard, so anything you can click, you can automate.
curl -X POST https://uptime-status.org/api/monitors \ -H 'Content-Type: application/json' \ -d '{ "name": "Public API", "url": "https://api.yourcompany.com/health", "type": "uptime", "check_interval_seconds": 30 }'
Uptime monitoring, answered.
How fast will I know my site is down?
Pro checks run as often as every 30 seconds, so detection plus notification typically lands within a minute of the failure. Self-hosted installs control their own interval floor.
What counts as "down"?
A check fails when the endpoint does not return a successful response in time: connection errors, timeouts, and unexpected HTTP status codes all open an incident. Every failure stores the status code and error message so you can see exactly what the probe saw.
Do I need to install an agent?
No. Uptime checks probe from the outside, exactly like your users reach you. If you also want CPU and memory metrics from inside a server, the optional server metrics agent covers that separately.
Can I monitor endpoints behind a firewall?
Self-host the open-source version inside your network and your checks run from wherever you deploy the workers. The hosted plan probes from the public internet.
What happens during planned deploys?
Create a maintenance window. Your status page shows scheduled maintenance for that period instead of an outage, and the incident timeline stays clean.
Pairs well with.
Performance monitoring
Automatic p95 regression detection against a 7-day baseline catches slowdowns before they become outages.
Learn moreStatus pages
A branded status page on your own domain answers “is it down?” before support tickets do.
Learn moreNotifications
Email, Slack, PagerDuty, Opsgenie, SMS, and six more channels, routed the way your team works.
Learn moreStart monitoring in under 2 minutes.
No credit card required for the self-hosted, open-source version.