Website Uptime Test and Uptime Checker

Run a website uptime test

What the uptime checker shows you

A page that "loads in the browser" can still be slow, redirecting in a loop or one week from an expired certificate. The test breaks the request into the steps that actually happen, so you see where time goes and what is about to fail.

DNS lookup. How long the resolver took to return an address, and which address it returned. A slow or failing lookup points to the DNS provider or a wrong record, not the server.
TCP connect. Time to open a connection to port 443 or 80. A long connect usually means distance, a congested network or a server close to its connection limit.
TLS handshake. Time to agree on encryption and validate the certificate. Above roughly 300 ms often means a missing session cache or a long certificate chain.
First byte. Time from sending the request to the first byte of the answer. This is mostly your application and database working. Under 200 ms is fast, above 800 ms deserves a look.
Status code. 200 is healthy. 301 and 302 are redirects, 403 and 404 mean the address or permissions are wrong, 500 to 504 mean the server or a proxy in front of it failed.
Redirect chain. Every hop from the address you entered to the final page. Each hop adds a full round trip, and a chain like http to https to www to a language path costs real time on mobile.
Certificate days left. Issuer and the number of days until the certificate expires.
Domain expiry date. When the domain registration ends, from registry data where the registry publishes it.
Keyword found. For the Keyword on page type, whether your text (for example "Add to cart") is present in the response.

One region in full, the rest after you create an account

The test runs from the regions that monitor sites every day, US East and EU Central. The first region result is shown in full on the result page. The second region detail, a 24 hour response time chart, alert rules and a status page preview for the same site open after you create an account. Each visitor can run a few checks per day, which keeps the tool fast for everyone.

How to read a website uptime checker result

Start with the status code. If it is not 200 (or the redirect you expect), nothing else matters yet. Next look at the total time and which step takes the largest share. A slow DNS lookup is fixed at the DNS provider. A slow connect points to distance or network capacity, so compare regions. A slow TLS handshake points to certificate and server configuration. A slow first byte points to the application: caching, database queries, a cold start after a deploy.

Then look at the dates. A certificate with fewer than 14 days left needs attention today, because automatic renewal has probably failed already. A domain with fewer than 30 days left should be renewed, and auto renewal on the registrar should be checked. Our ssl certificate monitoring and domain expiration monitoring pages explain both in depth.

A one-off website uptime checker versus monitoring every minute

A single test tells you how the site behaves right now, from one place. It cannot tell you that checkout went down at 3:12 at night for eleven minutes, that response time doubles every day at 9:00, or that a renewal failed last Tuesday. Outages are short and random. A site with 99.9 percent uptime is still down about 43.8 minutes a month, usually in several short pieces that nobody sees.

Continuous monitoring runs the same test every minute (every 30 seconds on Team and above) from two regions. A monitor is marked down only after the second region confirms, so you are not woken up by one lost packet. When it fails, UptimePilot alerts you by email, SMS, Slack, Microsoft Teams or webhook, keeps an incident log, and can update a public status page. You also get uptime percent and response time percentiles in reports. See website monitoring for the full picture, and website performance monitoring for speed over time.

Turn this test into a monitor

Every plan runs all check types, including the ones in this test, with multi-region confirmation, maintenance windows and escalation.

Starter, $49 a month or $24 a month billed yearly. 50 monitors, checks every minute, 30 SMS alerts a month, 1 status page, 90 days of history.
Team, $99 a month or $49 a month billed yearly. 200 monitors, checks every 30 seconds, 150 SMS alerts a month, 5 status pages with custom domain, monthly SLA PDF.
Business, $249 a month or $124 a month billed yearly. 1,000 monitors, 500 SMS alerts a month, 20 password protected status pages, white-label client reports and REST API.
Enterprise, $599 a month or $299 a month billed yearly. 3,000 monitors, 1,500 SMS alerts a month, 50 status pages, SSO (SAML) and audit log.

All limits are on uptime monitoring pricing. Yearly billing saves 50 percent.

See pricing

01

Is the website uptime test really without a card?

Yes. No card required to run a check. You can run a few checks per day as a visitor. Creating an account opens the other region detail and the chart for the same site.

02

Why does the result show a different time than my browser?

Your browser reuses connections, caches DNS and may sit close to the server. The test starts from a clean connection in a monitoring region, which is what a new visitor experiences.

03

Which addresses can I test?

Any public website on ports 80 or 443. Private, local and reserved addresses are blocked for safety, also when a redirect points to them.

04

What does a keyword check prove that a status code does not?

A server can return 200 with an error page, an empty template or a maintenance notice. A keyword check confirms that the content you care about is actually on the page.

05

How is this different from monitoring?

The test runs once, now. Monitoring repeats it every minute or every 30 seconds from two regions, confirms failures and alerts the right person.

Check your site now, then monitor it every minute

Enter a URL and see every step of the request in seconds.

Website uptime test for any URL, results in seconds