Know why a website is down, not only that it is down.
Sentryx monitors customer-facing endpoints from outside your infrastructure. Each alert includes timing, response status, IP context, and the likely failure layer: DNS, TCP, TLS, or HTTP.
Monitor endpoints the way users reach them.
A failure can start in DNS, a closed port, TLS, an unexpected status code, a slow application, or missing page content. Each layer needs different evidence.
HTTP and keyword checks
Monitor status codes, response time, redirects, timeouts, and page content for websites, APIs, landing pages, and customer portals.
TCP, DNS, and SSL checks
Watch the layers that can fail before an application receives a request: DNS resolution, socket connectivity, certificate validity, and TLS handshake.
Alerts with context
Send email or Telegram alerts with the host, method, timestamp, IP, network context, likely failure layer, and recovery time.
Separate a real outage from internet noise.
A CDN edge, DNS route, WAF rule, or regional network path can fail for one checker while remaining reachable elsewhere. Peer-region evidence helps classify the event more accurately.
The primary check passes and the endpoint is reachable. No action is needed.
One path cannot reach the host while a peer region still sees it online. Investigate routing, CDN, or WAF behavior.
The primary failure and peer-region evidence agree that the endpoint is unavailable.