Website monitoring for modern teams
Monitor your websites.
Know when something goes wrong.
Monitor uptime, response time, SSL health, and incidents from one place. Get notified when a website goes down and when it recovers.
One failed check Check 3
The next check passes, so no incident is opened and nobody is paged.
Three failures in a row Checks 6 to 8
An incident opens as Investigating and your down alert is sent.
Two passes in a row Checks 9 and 10
The incident resolves and your recovery alert is sent.
Defaults shown: 3 failures to open, 2 passes to resolve. Both are configurable per monitor.
What it watches
Six capabilities, all of them in the product today.
- Uptime monitoring
- HTTP and HTTPS checks on a schedule. Choose an interval from 1 to 60 minutes (the shortest available depends on your plan) and the status codes that count as healthy.
- Response time
- Every check records how long the response took. Successful responses slower than 3 seconds show as degraded instead of down.
- Incident detection
- An incident opens only after consecutive failed checks, not one transient error, and resolves after consecutive passes.
- SSL monitoring
- HTTPS monitors inspect the certificate and alert you 30, 14, 7 and 3 days before it expires.
- Notifications
- Email alerts and webhooks when a monitor goes down, when it recovers, and when a certificate is close to expiring.
- Public status pages
- A page your customers can open to see service status, 90-day history and incident updates, with your branding.
How it works
From a URL to an alert, with the confirmation step that keeps alerts trustworthy.
Step 1: Add your website
Enter the URL you want to monitor. A new monitor is checked straight away.
Step 2: We check it automatically
A monitoring worker on our servers requests the URL on your interval, not from your browser.
Step 3: We confirm real failures
Consecutive failed checks are counted before anything is declared down, so a single hiccup does not wake anyone.
Step 4: You get notified
One alert when an incident is detected and another when the service recovers.
One failed request is not an outage
Website Monitor evaluates consecutive checks before it opens an incident, then tracks recovery separately.
Investigating
Opened automatically after the configured number of consecutive failed checks. The first message states what was observed, never a guessed cause.
Identified
You publish an update once you know what is wrong.
Monitoring
A fix is in place and you are watching to confirm it holds.
Resolved
Closed automatically after the configured number of consecutive passing checks, with the total downtime recorded.
Incident updates you publish appear on your status page, so the people affected hear it from you, in order.
A status page your customers can open
Give people a clear view of service health instead of answering the same question in your inbox.
- Service status and groups
- Show each service with its current status, and group related services together.
- Uptime and incident history
- A 90-day uptime bar per service and a history of incidents with their updates.
- Your branding
- Logo, accent color, theme, footer text and links to your website and support.
- A public URL
- Every status page lives at its own address. Choose whether search engines may index it.
Some systems are degraded
- WebsiteOperational
- APIOperational
- CheckoutDegraded
Checkout is returning HTTP 503 errors
Investigating. Checkout failed 3 consecutive health checks. We are investigating.
Certificates, before they expire
SSL checks run alongside uptime checks, so an expiring certificate is a warning, not an outage.
HTTPS monitors inspect the certificate on every check. When the days remaining cross a threshold, you are alerted once for that threshold, and again if the certificate actually expires. Certificate health is tracked independently of whether the site is otherwise up.
Who it is for
Anyone who runs something on the web and wants to hear about problems first.
- SaaS teams
- Find out about an outage before your customers write in, and point them to a status page while you fix it.
- Developers
- Watch the endpoints you ship, receive webhooks in your own tooling and read monitors and incidents over the API.
- Freelancers and agencies
- Keep an eye on client sites and give each client a status page they can open.
- Ecommerce businesses
- Know when the storefront or checkout stops responding, and when a certificate is about to lapse.
- Startups
- Get dependable alerting without running monitoring infrastructure of your own.
- Website owners
- Add a URL, choose where alerts go and leave it running.
Built to be trusted with your alerts
What the system actually does, described without superlatives.
- Checks run on the server
- Requests come from our monitoring worker, never your visitors' browsers, so results do not depend on anyone's device or network.
- Outbound requests are restricted
- Every target is resolved and validated before it is contacted. Private and internal addresses are refused, and redirects are checked again at each hop.
- Your data is scoped to your organization
- Monitors, incidents, status pages and settings are authorized against your organization on the server for every request.
- Credentials are stored hashed
- Passwords are stored as hashes, session tokens are stored hashed, and the session cookie is HttpOnly and SameSite.
- Incidents are stored, not inferred
- Incident state lives in the database, so a restart does not forget an open incident or open a duplicate.
- Notifications are tracked
- Each alert is recorded before it is sent, retried with backoff on temporary failures, and delivered once per channel.
Common questions
- Will one failed check mark my site as down?
- No. An incident opens after a configurable number of consecutive failures (3 by default), and it resolves after a configurable number of consecutive passes (2 by default).
- Where do checks run from?
- From our monitoring server, from a single location. A result shows how your site looks from there, not from every region.
- Do I need to install anything?
- No. Monitors request a public URL from outside, so there is no agent to install. Private and internal addresses cannot be monitored.
- Can my customers see a status page?
- Yes. Each status page has its own public URL that you can share or link from your site.
Know when something goes wrong.
Start monitoring your websites before your users have to tell you something is broken.