Website and API over HTTPS
We request your page and look at the status code and how long it took. You can pick the method, send headers and expect a specific code.
Monitoring
Six ways to know your things are still standing.
A site can answer “200 OK” and be broken inside. That is why we check more than one thing, and confirm before shouting.
Keyword
We check that a text still appears. If “Add to cart” disappears, the shop opens but does not sell.
Ping and port
For things that do not speak HTTP: a mail server, a database, a service on its own port.
Cron and heartbeat
The other way round: we wait for your job to call us. If the nightly backup stops running, you find out the next day.
SSL certificate
We warn you 30 days before it expires, and again when few days remain.
DNS and domain
We watch the records and the domain expiry date.
No false alarms
We confirm before waking you up.
A network blip is not an outage. We require three failed checks in a row before alerting, and two good ones to close the incident.
- Checks from several locations
- Scheduled maintenance windows
- Immediate retry before declaring an outage
10:42:03 tienda-ejemplo.com 200 214 ms 10:43:03 tienda-ejemplo.com 503 failure 1 of 3 — no alert 10:44:03 tienda-ejemplo.com 503 failure 2 of 3 — no alert 10:45:03 tienda-ejemplo.com 503 CONFIRMED → alert sent 10:52:03 tienda-ejemplo.com 200 198 ms 10:53:03 tienda-ejemplo.com 200 RESOLVED → 8 min down
Questions about monitoring
Where do you check my site from?
From several network locations. A failure is confirmed when it fails in more than one, so a single broken route does not become a false alarm.
What is keyword monitoring?
We check that a specific text still appears on your page, such as “Add to cart”. A site can answer 200 and still be broken inside.
Can I watch a cron job or a backup?
Yes. We give you a URL your task must call when it finishes. If it does not call on time, we alert you.