Asset Type

Know it's down before your customers tell you.

Uptime and response-time monitoring for every website and endpoint you point Kllyroo at — and when the site is served from a host Kllyroo already watches, downtime gets a root cause attached instead of just a red dot.

← Back to platform overview

2core signals: uptime & response time

223signatures available when self-hosted

5channels for a downtime alert

What's Tracked

Uptime and response time, checked continuously.

Every configured website is checked on a regular interval for reachability and response time. A check that fails or slows past a configured threshold fires an alert — and if the site happens to be served from a host that Kllyroo's agent already monitors, the downtime alert can be joined to whatever's actually happening on that server, instead of standing alone.

Website	Status	Response
app.example.com	up	142ms
api.example.com	down	timeout
status.example.com	up	88ms

✦ Correlated with server-13

api.example.com is down because server-13's nginx worker pool is exhausted — same root cause, one incident.

Where We Stand

Scope, honestly.

What's covered

Uptime checks on a regular interval, with response-time tracking
Downtime alerting through the same notification channels as every other asset type
Correlation with the underlying server's own signatures and incidents, when the site is self-hosted on a monitored host

On the roadmap

Active TLS certificate expiry checks — not built yet
Multi-step synthetic transaction monitoring (e.g. simulated login flows) — a single uptime check today, not a scripted journey
Multi-region checks — checks run from where the agent is deployed, not from a distributed probe network

Pairs Well With

Related capabilities

Get In Touch

Reach us directly.

Offices in India and the US — reach out and we'll get back to you.