HTTP checks from where your customers are.
Every monitor is checked from Mumbai, Hyderabad and Delhi, every minute on paid plans and every 30 seconds on Agency. Check a page, an API endpoint or a webhook, and decide exactly what healthy means.
Decide what healthy means
By default anything outside 200–399 is a failure. Set the codes you expect, and add a keyword the page must or must not contain, so a cached error page that returns 200 still counts as down.
| Rule | Example | Fails when |
|---|---|---|
| Status codes | 200-299, 404 | Any other code |
| Must contain | Add to cart | Text is missing |
| Must not contain | Service Unavailable | Text appears |
| Timeout | 10 s | No answer in time |
APIs, webhooks and login-protected pages
Choose the method, add custom headers and a request body. Check the endpoint your checkout depends on, not just the home page.
POST /v1/checkout/health
Authorization: Bearer ••••••••
Content-Type: application/json
{"cart": "probe", "pay": "upi"}See where the time goes
Every check records DNS, connect, TLS and time to first byte, per city. When Delhi is slow and Mumbai isn't, you can see whether it's DNS, the network or your server.
SSL expiry, before it bites
Every HTTPS check reads the certificate. You're warned 30, 14, 7, 3 and 1 day before it expires, once per threshold, and alerted right away if it becomes invalid.
Issuer: Let's Encrypt · warned at 30 days, next warning at 7 days
Questions about monitoring
Something else? Talk to us.
Start monitoring in 2 minutes
Free plan, no card needed. Paste a URL and your first check runs from three cities.