TILLDEV · SYSTEM STATUS
LIVEUPDATED 3S AGO

Service outage

2/5 OPERATIONAL · 2 IDLE · PROBED EVERY 5 MIN

90 DAYS AGOAGGREGATE HEALTH SIGNALNOW
95.56%
Uptime · 90d
26ms
Mean latency
2/5
Operational
90+
Days clean

Components5 MONITORED

DashboardWeb app at tilldev.dev and customer subdomains.
90d100.00%
Operational
Event ingestSDK event submission endpoints.
90d100.00%
7ms
Operational
Metadata storeProjects, users, settings (Postgres).
90d100.00%
Idle · cost-safe
Events warehousePer-event analytical storage (ClickHouse).
90d95.56%
45ms
Service outageping returned 530
Issue searchFull-text search across issues and events.
90d100.00%
Idle · cost-safe

Incident timelineLAST 30 DAYS

NO INCIDENTS LOGGED
A flat line is a good line. 90 days without a reported disruption.

How we measureMETHODOLOGY

ACTIVE PROBES

An out-of-band worker hits each subsystem directly — SELECT 1 on Postgres, /ping on ClickHouse, /health on the ingest gateway. No synthetic transactions, no guesswork.

THRESHOLDS

Each probe is hard-capped at an 8s timeout. A slow-but-alive response reads degraded; only a failed call reads outage. We don't catastrophize a transient blip.

SIGNAL

Every check is written to an append-only log kept for 90 days. The trace above is that history, drawn as a single worst-of-all-subsystems signal — the same rollup that lights the banner.

COST-SAFE

Our database scales to zero when idle. Rather than wake it every few minutes just to check, we probe it only while real traffic is flowing — so an untouched subsystem reads idle · cost-safe, never a fabricated green.

UPDATED 3S AGO · 90-DAY RETENTIONSUBSCRIBE VIA JSON →