Website monitoring that confirms an outage before it alerts you
Check that your site answers with the right status code, shows the right content, and responds fast. A failure is re-checked from other locations first, so one bad network path does not wake you up.
Why you need to know before your customers do
A website can fail without anyone on your team noticing. The server may be up while the page returns a 500 error, a deploy may have broken the homepage, or a slow database may make every request take ten seconds. Customers notice first, and they rarely report it.
Website monitoring requests your site on a schedule and judges the response: the status code, the content, and the time it took. When a check fails you are told within minutes, or within a minute on a paid plan.
The other half of the job is not crying wolf. A single probe can fail because of a network problem between it and your site. If every such blip paged you, you would soon stop reading alerts.
How website monitoring works
Add your URL
Create an HTTP monitor with your site address and choose how often to check.
Describe a healthy response
Only status 200 counts as success unless you add other codes. A keyword monitor can also require or forbid text on the page.
A failed check is repeated
After a failure, the check is re-run from a different probe location, up to three attempts in total.
An incident opens once locations agree
An incident opens only when 3 probes in at least 2 regions have failed. If a repeat check succeeds, no incident is opened.
What you configure
A website monitor checks the things that tell you a site is really working:
- Expected status codes, and whether redirects are followed
- Keyword checks: text the page must contain or must not contain, up to 20 keywords
- A timeout of 5 to 60 seconds, shorter than the check interval
- A slow response alert with your own threshold, as a separate incident from downtime
- SSL certificate validity, so an expired or invalid certificate fails the check
- Custom headers, if your site needs them
URL: https://www.example.com
Method: GET
Expected status: 200
Keyword: contains "Sign in"
Interval: 1 minute (Pro) or 30 seconds (Scale)What alerts you get
Each check records DNS, TCP, TLS, and server time separately, so an alert comes with a clue about where the time went. P50, P95, and P99 response times show the slow tail that an average hides.
Incidents and recoveries go to email, Slack, Telegram, Pushover, and webhooks, on every plan. Recovery is confirmed the same way as failure, from several locations.
- The site must be reachable from the internet. Private and internal addresses are not accepted.
- If you use a firewall or WAF, allow the UptimeIO-Monitor/1.0 user agent.
Which plans include it
HTTP and keyword monitoring are on every plan. Free includes 50 monitors with 5-minute checks. Pro includes 100 monitors with 1-minute checks for $15 a month billed annually, or $19 billed monthly. Scale includes 300 monitors with 30-second checks for $39 a month billed annually, or $49 billed monthly.
Pro and Scale can also choose which locations a monitor checks from. On Free, locations are selected automatically.
- HTTP monitoring docs: Status codes, redirects, timeouts, and slow response alerts.
- Keyword monitoring docs: Check page content as well as status.
Frequently asked questions
What is website monitoring?
Website monitoring requests your site on a schedule and checks the status code, the content, and the response time. You are alerted when a check fails or the site becomes slow, so you hear about problems before your customers report them.
How often does UptimeIO check my website?
Every 5 minutes on the Free plan, every minute on Pro and every 30 seconds on Scale. The 30-second interval on Scale is the shortest on any plan.
What counts as down?
A check fails when the response status is not one of your expected codes, when the request times out, or when the connection or certificate fails. By default only status 200 passes. A site is declared down only after the failure is confirmed: 3 probes in at least 2 regions must have failed.
Will I get false alerts from one probe having a network problem?
No. A failed check is repeated from different probe locations. If a repeat check succeeds, no incident is opened. Recovery is confirmed from several locations too.
Is there a free plan?
Yes. Free includes 50 monitors with 5-minute checks, SSL expiry warnings, and email, Slack, Telegram, Pushover, and webhook alerts.
Can I check that my page shows the right content?
Yes. A keyword monitor makes the same request and searches the response body for text you require or forbid, up to 20 keywords. It sees the HTML your server returns, not content added later by JavaScript.
Guides
Related
- API monitoring: Endpoints with methods, headers, and auth.
- SSL certificate monitoring: Warnings before a certificate expires.
- Status pages: Show customers your live status.
- UptimeRobot alternative: How UptimeIO compares on website checks.
- Pingdom alternative: A permanent free plan instead of a trial.
- SLA uptime calculator: Turn an uptime target into allowed downtime.
- Downtime cost calculator: Estimate what an outage costs you.
- Pricing: Plan limits and prices.
Start monitoring in a few minutes
Free plan · 50 monitors · No credit card required