Create an uptime test, paste the URL, choose an interval and the status codes that count as healthy, then turn on an alert channel.
Most people finish their first monitor in about a minute:
Open a project and click Create New Uptime Test.
Name the test, enter the Target URL, and leave the test enabled.
Choose a check interval of 1, 5, 10, or 30 minutes and select your geographic testing locations.
Set the healthy HTTP status codes (such as 200–299). Optionally add a Response Time limit and a body string match.
Click Set Alert, turn on email, Slack, Microsoft Teams, desktop notifications, or a webhook, set the consecutive failure count, and click Test Alert to verify delivery.
How do I prevent false alarms from momentary network blips?
Configure a consecutive failure count on each alert channel (such as 2 or 3 consecutive failures) before an alert fires, and use maintenance windows during planned work.
How do I track TTFB and response latency across regions?
Combine multi-region uptime checks (which log response time and DNS resolve time on every run) with Real User Monitoring (RUM) to slice TTFB and LCP by country and device.
How can I tell if my website is down for everyone or just me?
Try the site on another device or connection and check it from other locations. If it works elsewhere, the issue may be local to your device, network, DNS or region.
Why does my website keep going down and coming back up?
Intermittent downtime can result from hosting, network, DNS, traffic or application issues. Record when and where failures occur, then compare those details with provider logs and recent changes.
Why does my website say “not secure,” and how do I fix it?
A browser may warn that a connection is not secure if the site or its SSL/TLS certificate is misconfigured, expired or does not match the hostname. Check the exact warning and contact your provider if needed.