System status
Component health and 90-day availability. Served from every collector, so it stays up when the console does not.
me-central
collector. Last updated 19 Oct 2026, 09:14 UTC.| Component | Status | 90d |
|---|---|---|
| Collector — ru-central | operational | 99.99% |
| Collector — eu-central | operational | 100.00% |
| Collector — uk-south | operational | 99.98% |
| Collector — tr-west | operational | 99.96% |
| Collector — me-central | elevated latency | 98.84% |
| Aggregation — eu-west | operational | 100.00% |
| Aggregation — us-east | operational | 99.99% |
| Aggregation — ap-southeast | operational | 99.97% |
| HTTP API | operational | 99.99% |
| Alert delivery | operational | 100.00% |
| Console | operational | 99.98% |
| Bulk export | operational | 99.91% |
Recent incidents
Elevated latency, me-central collector
A transit change in Dubai added roughly 70 ms to the upstream channel. The collector spooled and replayed; no samples were lost, and dashboards backfilled within four minutes of recovery.
Upstream channel flapping on ru-central
The collector reconnected to aggregation roughly every two minutes for just over an hour, caused by an idle timeout on an intermediate device shorter than our keepalive. Keepalive on the upstream channel is now 25 s and adaptive. Agent-side ingest was unaffected throughout.
Certificate rotation rejected reconnecting collectors
A rotation on eu-west completed out of order, so collectors reconnecting inside a 26-minute window were rejected at the TLS layer. All spooled and replayed. Rotation is now gated on a successful handshake from an out-of-band canary.
Subscribe
Status changes publish as an Atom feed and as webhooks:
https://status.srvpulse.net/feed.atom.