Skip to main content
Back to Features
Uptime monitoring

Uptime monitoring that catches downtime before customers do

You get an alert when your site stops answering. Checks run from the global locations you choose, every 30 seconds to 24 hours depending on your plan, and brief network blips are retried before anyone is alerted, so one dropped request doesn't wake your team.

Multi-location checks
Set up in about a minute
Free plan, no credit card
4 monitors · checks from multiple global locations
MonitorStatusUptime 30dResponseChecked
shop.acme.ioDown98.71%timeoutnow
app.acme.ioUp99.98%142ms30s
blog.acme.devUp100%88ms1m
api.acme.comUp99.95%210ms30s
1 monitor down · shop.acme.io failed after 4 attempts
Free includes 3 monitors with 15-minute checks and email alerts.Compare all plans

A rolling SLA you can actually report

WebPixie tracks uptime over time and rolls it into an SLA figure, with the incident count and response trend behind it, so you have a number to share instead of a guess.

30-day uptime

99.98%

Incidents

2

MTTR

4m

Avg response

138ms

Full uptimePartial downtimeOutage

The SLA is calculated on an industry-standard basis that excludes periods when monitoring was paused, so the figure reflects real availability.

Checked from multiple global locations

Checks can run from multiple global locations, and paid plans use the monitor’s other selected locations to verify network-related failures before opening an incident.

Monitorapp.acme.io
London142msUp
Istanbul168msUp
New York121msUp

Each check validates more than a 200

You can set the HTTP method, headers, expected status code, a body keyword, and authentication, so a check confirms the page is actually working.

MethodGET
Expected status200
Request headersAuthorization, X-Api-Key
Keyword match"Welcome back"
AuthenticationBasic
Interval1 min

Up to four attempts, then a second opinion

A network failure must survive up to four check attempts with exponential backoff before an incident is considered. On paid plans, WebPixie also verifies from the monitor’s other selected locations before opening one.

Check failstimeout
Retry 1
Retry 2
Retry 3
Verifyother location
Incident opens
Accelerated re-checksfaster recovery

Applies to network failures such as timeouts and connection errors. Status code or keyword mismatches open an incident on the first attempt. If cross-location verification passes, no incident opens. Once an incident opens, accelerated re-checks run on every plan to detect recovery sooner.

How WebPixie watches your uptime

WebPixie runs uptime checks from multiple global locations on a schedule and alerts you when a check confirms a failure. There is no agent to install, no DNS changes, and no server access needed. Every check verifies the HTTP response code, response time, HTTPS connectivity, and any custom keyword you configure. Over time you get uptime statistics, SLA reports that exclude unmonitored periods, and 30-day trends, so you can measure reliability and track mean time to recovery. While an incident is open, WebPixie re-checks the monitor more often than its normal interval to catch recovery sooner and time the outage.

Network-related failures, like timeouts or connection errors, go through up to 4 check attempts with exponential backoff. On paid plans, if all attempts fail on a monitor checked from more than one location, WebPixie also runs verification checks from its other locations before opening an incident, so a momentary flicker on one route does not wake you at 3am. When a failure is confirmed, alerts go out by email on every plan, and through integrations such as Slack and webhooks on higher plans.

Checks can run from multiple global locations, such as London and New York, which are ready by default. This gives you visibility from more than one network path when reachability problems are regional. We run active monitoring probes in dozens of locations, and if you need another one, our Support team opens it for you within 24 hours on paid plans.

The full configuration options are in the uptime monitoring setup guide in the docs.

01

No more refreshing the homepage to check if it is working

Automated checks tell you what manual refreshing cannot

Most downtime starts predictably: a deploy goes wrong, a memory leak builds, a DNS record changes. WebPixie lets you set a check interval from 30 seconds to 24 hours depending on your plan, so high-priority monitors run often and low-priority ones run sparingly. When a check fails, an alert routes to your preferred channel.

02

Alerts for real outages, not 3am false alarms

Up to four check attempts, then cross-location verification

Network-related failures, like timeouts or connection errors, go through up to 4 check attempts with exponential backoff. On paid plans, if all attempts fail on a monitor with more than one location, WebPixie also verifies from its other locations before opening an incident, so a momentary flicker does not wake you. For a monitor that flickers, you can also send the alert only after several failed checks in a row. Alerts go out by email on every plan, and through integrations such as Slack and webhooks on higher plans.

03

You see a page getting slower before it times out

Response time is recorded on every check

Every check records how long the response took. Each monitor shows a response-time chart with minimum, average and maximum over the range you pick, such as the last 30 days, so a page that keeps getting slower is visible before it starts timing out.

04

Checks from multiple global locations

A regional outage hits one path, not the others

A site can look fine from one location while being unreachable from another. WebPixie checks from multiple global locations, such as London and New York, which are ready by default. Need another location? On paid plans, Support opens it within 24 hours. Regional reachability problems are easier to review this way.

05

What uptime monitoring checks, and what it does not

HTTP availability vs the rest of the WebPixie suite

Uptime monitoring checks HTTP and HTTPS reachability using the HTTP method, headers, expected status code, and authentication you configure, plus response times and a body keyword that confirms the page is functioning correctly, so a page that returns 200 with an error message still fails. An expired SSL certificate or lapsed domain will make the HTTPS check fail, so uptime sees the symptom once the site is already down. What it cannot do is warn you ahead of expiry, or surface a changed DNS record or a broken link on a deeper page as a cause-level finding.

You can set up uptime monitoring in about a minute

Free plan, no credit card. 3 monitors with no time limit.

Everything you need to monitor a website. In one workspace.

A quick look at other WebPixie features.

Why teams choose WebPixie for uptime

Up to four attempts, then verified from another location

Up to four check attempts with exponential backoff filter out transient network noise. On paid plans, WebPixie also verifies from the monitor’s other selected locations before opening an incident.

Multiple locations, independent network paths

Checks can run from multiple independent locations, such as London and New York, so regional reachability problems are easier to separate from one-path network noise.

Check intervals from 30 seconds to 24 hours

You pick the interval each monitor needs, from 30 seconds to 24 hours, with the fastest intervals available on higher plans.

Frequently Asked Questions

Common questions about uptime monitoring.

WebPixie notices an outage on the next scheduled check, so the check interval you set for each monitor decides how quickly a failure is seen. The interval can be anything from 30 seconds to 24 hours, depending on your plan. Check options such as the method, headers, status codes, keywords and authentication are available on every plan. After a failing check, a timeout or connection error is retried in place and, on paid plans, verified from the monitor's other selected locations, which adds a short delay but keeps blips from paging you. A wrong status code or a keyword mismatch counts as down on the first check. The notification goes out as soon as the failure is confirmed, and the open incident is then re-checked more often so recovery is seen sooner. Endpoints that page people work best with a short interval, while low-risk pages can stay on a longer one. You can see how checks are confirmed under uptime monitoring and the interval for each plan on the pricing page.

WebPixie keeps network blips from opening incidents with two layers of protection: in-place retries for timeouts and connection errors, and verification from other locations on paid plans. First, when an uptime check hits a network-related failure such as a timeout or a connection error, WebPixie makes up to 4 check attempts with exponential backoff, so a brief blip does not open an incident. Second, on paid plans, if all attempts still fail, WebPixie runs verification checks from the monitor’s other selected locations before opening an incident. A monitor with a single location has no other location to verify from, so it is best to select at least two for the endpoints that page people. If the site is reachable from those locations, no incident opens and the failed check is recorded as unverified rather than confirmed down, and it is left out of your uptime percentage instead of counting as downtime. Failures that are not network-related, like an unexpected status code or a keyword mismatch, open an incident on the first attempt, because they reflect a real response from the server. For an endpoint that flaps, you can set the monitor to notify only after several failed checks in a row. You also control what counts as up: an accepted status-code list, keyword checks for content that must or must not appear, and a configurable request timeout all shape the verdict. When a failure is confirmed, it flows into incident management with a severity and a type, and you get one notification when the incident opens and one when it closes, not one per failed check. When checks recover, the incident closes automatically and is marked resolved. Per-plan check intervals are on the pricing page.

WebPixie marks a site as down when an uptime check fails the response rules configured for that monitor. A failure can come from a timeout, connection error, unexpected HTTP status code, missing body keyword, or another expected condition that does not match. Uptime monitoring supports custom HTTP methods, headers, expected status codes, authentication, and keyword validation, so “down” can mean more than a simple 500 error. For network-related failures such as timeouts or connection errors, WebPixie makes up to 4 check attempts with exponential backoff before confirming the failure. On paid plans, if all attempts still fail, WebPixie also runs verification checks from the monitor’s other selected locations before opening an incident, which reduces false positives further. Failures from deterministic conditions, such as an unexpected status code or a missing keyword, open an incident on the first failed check without retry. If the issue is confirmed, WebPixie creates or updates an incident and sends notifications through the channels available on your plan. Check intervals and location availability are plan-based, and you can compare them on the pricing page.

WebPixie keeps checking your site around the clock, so an outage at night or on a weekend is caught on the next scheduled check and emailed to you. Checks run from multiple global locations on the interval you set for each monitor, from every 30 seconds to once a day depending on your plan. A timeout or connection error is retried before anyone is alerted, and on paid plans WebPixie also re-checks from the monitor's other selected locations, so a brief network blip does not send a false alarm. Once the site is down, WebPixie checks it more often to spot the recovery sooner, then emails you again when it is back. Email alerts come with every plan; paid plans add Slack, and higher plans add webhooks. If you already use Slack on your phone, that alert is hard to miss. On paid plans each outage is also kept in incident management with its duration. You can read how checks work on uptime monitoring and compare alert channels on the pricing page.

Yes. Every uptime check records how long your landing page takes to respond, so you can see a page getting slower over days or weeks before it starts timing out. Uptime monitoring measures server response time from the monitoring locations you select, and each monitor shows a response-time chart with minimum, average and maximum values for the date range you pick. If a response takes longer than the timeout you set, up to 15 seconds, the check counts the page as down and you get an alert. This measures how fast the server answers, not how long the full page takes to render in a browser. For your homepage, the Main Page Analyzer also breaks the response into DNS lookup, connection, TLS and time to first byte, and records the browser load time. Lighthouse-based performance scoring is in development and coming soon.

WebPixie runs uptime checks from multiple global locations, such as London and New York. You choose which locations each monitor uses, up to your plan’s limit, and on paid plans you can request additional regions through support; they are usually opened within 24 hours. These locations help verify whether your website is reachable from more than one network path, which is useful when a problem affects only a specific region, provider, or route. Each uptime monitoring check can validate response status, response time, expected content, and other configured conditions before an incident is created. If no region is selected, WebPixie assigns one automatically. Multi-location checks and cross-location verification (available on paid plans for monitors with more than one location) are especially useful for customer-facing sites, agencies managing client domains, and teams that need clearer evidence before escalating an outage. You can compare plan coverage on the pricing page.

You can start watching your key pages today

Free plan, no credit card. Multi-location checks with cross-location verification on paid plans.

Related free tools

From the blog

Latest guides and updates