HTTP and API
Check response codes, response time, content, headers, and JSON assertions.
API monitoring →
Uptime monitoring
Monitor websites, APIs, and network services.
Create checks for the systems you operate and view them beside the third-party providers they depend on.
You can review the monitor settings before saving.
Choose the check that matches the service.
Ping and TCP
Test network reachability or confirm that a TCP port accepts a connection.
DNS
Monitor common record types, expected values, and public resolver answers.
DNS monitoring →Domain expiry
Track registration and expiry dates using WHOIS with RDAP fallback.
Domain monitoring →Basic SSL health
Watch expiry, hostname validity, the served chain, and basic TLS health.
SSL monitoring →Heartbeat
Have a scheduled job call ServiceAlert and alert when an expected heartbeat is missed.
Multiple locations
Confirm failures from more than one region.
Run a monitor from more than one ServiceAlert region. A per-monitor quorum can require one, most, or all configured locations to agree before an incident opens.
- Compare response time by location.
- Reduce alerts caused by a single probe or carrier problem.
- Confirm an outage is real before anyone is paged.
Synthetic transactions
Test more than a single endpoint.
Build ordered HTTP steps or browser actions for login, checkout, and other important paths. Results show which step or assertion failed.
- HTTP steps for APIs and straightforward request sequences.
- Browser steps for JavaScript, cookies, and page interactions.
- Assertions for response data, URLs, titles, text, and selectors.
Provider context
View your checks beside provider status.
Group checks into a monitored service and record the third-party providers it depends on. During an incident, responders can compare owned monitor failures with current provider information.
Read about dependency monitoring →Start with one URL.
Create the first monitor, or compare plan limits before you begin.