Uptime Monitors
Checks that never blink.
Watch every website, API, certificate, domain and scheduled job from regions in India and around the world. A failure is confirmed from more than one location before anyone is woken up, so a single network wobble never turns into a 3 am call.
- api.shopkart.in/checkoutAPI · POST212 ms99.98%
- shopkart.inHTTPS · keyword388 ms100%
- payments.shopkart.inAPI · GET1.42 s99.91%
- SSL · shopkart.inCertificate61 daysvalid
- nightly-invoice-exportCron heartbeatlate 14 m98.7%
- db-primary:5432TCP port3 ms100%
Monitor list with live response times and regional results
How it works
Set up in four beats.
- 01
Add an endpoint
Paste a URL, an API route, a host and port, or create a heartbeat URL for a cron job.
- 02
Choose regions and interval
Pick up to 10 regions and check every 30 seconds, 1 minute or 5 minutes.
- 03
Define what down means
Expected status codes, a keyword that must appear, a JSON field to assert or a response time ceiling.
- 04
Route the alert
Send confirmed failures to an on-call schedule, a Slack channel, Teams or plain email.
Capabilities
What you get with Uptime Monitors.
HTTP and HTTPS
Status code, redirects, headers and full response time for every page that earns you money.
API checks
Any method, custom headers, bearer tokens, request bodies and JSON assertions on the response.
Keyword checks
Alert when "Add to cart" disappears or when "Internal Server Error" shows up on a 200 page.
SSL expiry
Warnings at 30, 14 and 7 days, plus alerts for broken chains and hostname mismatches.
Domain expiry
WHOIS-based renewal reminders so a forgotten card never takes the whole brand offline.
Ping and TCP ports
Reachability for servers, databases, mail servers and anything that listens on a port.
Cron heartbeats
Your job pings a unique URL when it finishes. If the ping is late or missing, you hear about it.
Multi-region confirmation
A monitor is marked down only when two or more regions agree, which removes most false alarms.
Maintenance windows
Silence alerts during planned work, and keep those minutes out of your SLA numbers.
Specifications
The details engineers ask about.
- Check interval
- 30 s on Team and Scale, 60 s on Free
- Regions
- Mumbai, Delhi, Bengaluru, Singapore, Tokyo, Sydney, Frankfurt, London, N. Virginia, Oregon
- Request methods
- GET, POST, PUT, PATCH, DELETE, HEAD
- Authentication
- Basic auth, bearer token, custom headers
- Timeout
- Configurable from 1 to 30 seconds
- Confirmation
- Down only when 2 or more regions agree
FAQ
Uptime Monitors questions
Will a single failed check page my team?
No. A monitor is only marked down when at least two regions see the failure. One-off timeouts are recorded but do not alert.
Can I monitor endpoints behind a login?
Yes. Add basic auth, a bearer token or any custom header, and send a request body for POST endpoints.
How do cron heartbeats work?
Each heartbeat monitor gets a unique URL. Your job calls it on success. If the call does not arrive within the grace period you set, the monitor goes down.
Same pulse
Works together with
60 bpm 10 monitors · 1-minute checks · free, no time limit