Website monitoring
FastPing requests your pages over HTTPS, validates the certificate, checks the status code and measures the time to first byte. It does not run JavaScript. When something breaks, it checks again before it alerts you.
Check details
- Monitor type
- Website (HTTP)
- Target
- URL
- Fastest interval
- 30 seconds
- Before a down alert
- A second check after 20 seconds
- Checked from
- Helsinki, Finland (EU)
How it works
- Each check resolves your domain, connects, validates the TLS certificate and requests the URL, following up to 5 redirects.
- The final status code is compared with what you expect: any 2xx or 3xx by default, or exact codes such as 200 or 204.
- A failed check is repeated 20 seconds later. Only a second failure opens an incident and sends an alert.
- When the site answers again, you get a recovery alert with the total downtime.
What FastPing checks
- Availability and status codes
Down when the server does not answer, or answers with an error or a code outside your list.
- Response time
Time to first byte, charted for the last 24 hours, with an optional warning threshold.
- Certificates
HTTPS checks fail on expired, self-signed or incomplete certificate chains, exactly as API clients do.
- Redirects
Up to 5 redirects are followed, or switch that off to verify that a redirect, such as HTTP to HTTPS, is in place.
- Page content
Add a keyword monitor to be alerted when a text disappears from a page, or an error message appears.
Set it up
Sign up, choose Website (HTTP) and paste your URL. Pick the check interval and alert channels, then save. The first check runs immediately.
Frequently asked questions
If your question is not here, write to us. We reply by email, usually within one business day.
Contact supportHow often can FastPing check my website?
Every 5 minutes on the free plan. Paid plans can check every minute, or every 30 seconds for up to 500 monitors.
Where are the checks made from?
From one server in Helsinki, Finland. Response times include the network distance from Helsinki to your server, so a site hosted far away shows higher times than its local visitors see.
Will one slow request wake me up at night?
No. A failed check is repeated 20 seconds later and you are only alerted when both fail. Slow responses can be reported as warnings instead of outages.
Can FastPing check pages behind a login?
Pages that need an Authorization header can be checked with an API (JSON) monitor, which sends custom headers. Login forms that rely on cookies are not supported.
Related monitoring
- API monitoringCustom requests with headers and bodies, JSON value assertions and response-time warnings.
- SSL certificate monitoringExpiry warnings and alerts for broken chains, hostname mismatches and self-signed certificates.
- Domain expiry monitoringRegistration expiry dates straight from the registry, with warnings 30 days ahead.
Start with the free plan
3 monitors, checks every 5 minutes and 1 status page. No payment details needed.