Uptime and heartbeats
Know whether the release held with availability checks.
MonitorsHeartbeatsIncidentsStatus pages
Watch availability, then coordinate the response.
HTTP, heartbeat, and TCP checks feed precomputed SLA windows and an activity history you can read at a glance. When something changes, the incident, maintenance, alerts, and status page all live in one place.
api.lube.work
live up degraded down
Uptime is your reliability early-warning system.
One connected loop, held on the stage this capability serves. The other stages stay as context so you can see what feeds in and what comes next.
BD
Discovery
Feedback
Product
Engineering
Release
Reliability
Evidence
Reliability
Know whether it held.
Available now
Incidents and status pages
Keep incident response and customer-facing status context together.
Web performance
Review Lighthouse report evidence against configured targets.
Test intelligence
Investigate test outcomes and flakiness evidence across runs.
Watch checks stream in and a failure surface itself.
Every monitor runs on an interval. New checks stream in from the right; when one goes down it flips red and pulses while the healthy monitors stay calm.
check feed
streaming- api.lube.workus-eastuplast 30 checks99.98%
- checkout-apieu-westdownlast 30 checks99.71%
- nightly-sync (heartbeat)internaluplast 30 checks100%
Measured, then coordinated.
Four rolling windows, already computed.
Every monitor carries 24h, 7d, 30d, and 90d availability with maintenance excluded, so a target is a real budget you can sort by.
24h / 7d / 30d / 90dmaintenance excludedsortable
availability
SLO 99.9%- 24h99.98%✓
- 7d99.95%✓
- 30d99.90%✓
- 90d99.82%!
One incident stays live, the rest are history.
Incidents sit on a timeline ordered by time. Only the active one pulses, so the thing still in flight is the thing you see first.
p1 to p4update timelinereopen chain
incident history
- Elevated 5xx on api#218 · p2 highresolved9d ago
- Certificate renewal#224 · p4 lowresolved5d ago
- Checkout API degradation#231 · p1 criticalactivenow
A check for every shape of dependency.
HTTP matches status codes or keywords, heartbeats catch the cron that quietly stopped, and TCP checks watch raw ports.
httpheartbeattcp
- api.lube.work99.98%
- nightly-sync (heartbeat)100%
- db:5432 (tcp)99.91%
Honest scope
Uptime covers HTTP, heartbeat, and TCP checks. There is no synthetic browser monitoring or multi-region probe selection, and the SLA windows are the fixed 24h / 7d / 30d / 90d set rather than arbitrary custom ranges.
Relate uptime back to the change.
Keep availability and incident context in one workspace.
Start free
Connect one service and its checks to start.