Status

All systems operational.

Last check 7 seconds ago · 99.987% uptime over the last 90 days

▸ this status page runs on ChartlessOps watching itself. The same signal panel you’d see for your services.

Ingest Metrics pull from customer data sources

p50 pull320 ms

success rate (1h)99.998%

operational

Signal compute SLO budget rollups, threshold evaluation

p50 compute22 ms

success rate (1h)100.000%

operational

Alert routing PagerDuty, Slack, email, webhook

p50 delivery880 ms

delivery rate (1h)100.000%

operational

Dashboard / API UI + API for the panel

api p5038 ms

success rate (1h)99.996%

operational

YAML watcher Watches chartlessops.yml in customer repos

apply p5042 s

webhook deliver (1h)100.000%

operational

▸ Recent incidents

Last 90 days.

Brief pull delay in us-east — upstream Prometheus rate limit

2026-05-08 · 14:48−14:54 UTC · 6 min

us-east · impact: pull latency 280ms → 1.4s briefly resolved

One large customer’s Prometheus federation started rate-limiting our queries when their cluster hit a maintenance event. Pull latency for that customer briefly spiked. We added per-source backoff + jitter; no signal data was missed (we re-pull on backoff success).

YAML watcher webhook backlog

2026-03-28 · 09:14−09:42 UTC · 28 min

control-plane · impact: chartlessops.yml changes delayed up to 4 min resolved

GitHub webhook delivery to our control plane was backed up after a deploy. Customer YAML changes took 2–4 min to apply instead of the usual ~45s. Live signal evaluation was unaffected. Webhook ingest sharding was added in the next deploy.

Slack delivery delays

2026-02-19 · 11:32−11:48 UTC · 16 min

alert-routing · impact: Slack alerts delayed up to 9 min resolved

Slack webhook endpoint experienced elevated latency on their side. PagerDuty + email routing unaffected; our retry queue absorbed the backlog and all messages eventually delivered. Confirmed with Slack incident report.

All systems operational.

Per-region uptime.

Last 90 days.

Get notified.