Website & API
uptime monitoring.
Monitor websites, APIs and services from six global regions. Get downtime alerts, track response times and investigate what went wrong.
Start monitoring ↗Check more
than a homepage.
A page can respond while the service behind it is broken. Check status codes, expected content and JSON responses. Monitor TCP ports, DNS records, SSL certificates and scheduled jobs too.
Read the monitoring docs ↗Check availability and response time from your selected regions.
From failed check
to a useful answer.
Confirm the outage.
Checks fail from multiple regions. The response history shows when the problem started.
US West · US East · Western Europe
Alert your team.
Failed from 3 regions.
Open the incident to investigate.
Send notifications to the channels your team uses. Get a recovery notice when service returns.
Find the cause.
The spike happened just before the first 502 response.
AI connects the incident to server metrics and processes, giving you somewhere concrete to start.
Uptime monitoring.
With the context to act.
Response-time history
See whether a service slowed down before it failed. Compare checks across regions and review the incident timeline.
Server metrics
Connect availability to CPU, memory, disk and network usage. The Statance agent adds process-level context to your investigation.
Security monitoring
Review vulnerable software, end-of-life versions, suspicious processes and daily website scan findings alongside operational health.
Public status pages
Give customers a place to check service availability. Publish selected monitors on a public status page.
Know when
you’re down.
Match the check to the failure you need to catch.
Use HTTP status checks for availability, keyword checks for expected content and JSON assertions for API dependency health. TCP, DNS, SSL and heartbeat monitors cover other failure signals. Statance checks HTTP responses without rendering JavaScript; it does not currently run browser checkout journeys, ICMP ping or UDP checks.
Free checks run no faster than five minutes from one region. Pro supports one-minute checks and up to three regions; Business supports one-minute checks and up to six. The scheduler evaluates a majority of returned regional results. Check frequency is not a guaranteed notification-delivery time.
Take the next step after an alert.
Install the server agent to bring CPU, memory, disk and process context into the same account. Pro and Business add full security monitoring and automatic first-look incident notes. The AI assistant can query your available monitoring evidence; its conclusions depend on what you have actually connected and collected.
See the controlled outage experiment · Choose check frequency · Calculate your downtime budget