Status
Updated every 60 s from the nodes themselves, not from a third-party prober. Times are UTC.
Nodes
| Node | Location | State | 30d uptime | p50 / p95 RTT | Cache hit |
|---|---|---|---|---|---|
uk1 | London | operational | 99.98% | 12 / 34 ms | 94.1% |
nl1 | Amsterdam | operational | 99.99% | 9 / 27 ms | 96.3% |
nl2 | Amsterdam | operational | 99.97% | 9 / 29 ms | 95.8% |
nl3 | Amsterdam | operational | 99.99% | 10 / 26 ms | 95.1% |
nl4 | Amsterdam | operational | 99.94% | 10 / 31 ms | 93.7% |
nl5 | Amsterdam | operational | 99.98% | 9 / 28 ms | 95.4% |
de1 | Frankfurt | operational | 99.99% | 8 / 22 ms | 96.9% |
ch1 | Zurich | operational | 99.91% | 11 / 30 ms | 89.2% |
bg1 | Sofia | operational | 99.88% | 14 / 41 ms | 87.6% |
pl1 | Warsaw | operational | 99.96% | 11 / 29 ms | 94.8% |
ru1 | Moscow | degraded | 97.20% | 18 / 260 ms | 91.4% |
ch1 and bg1 joined on 2026-08-04, so their hit ratio is still filling up. A cold node looks worse than it is for roughly two weeks.
Incident history
Two of three upstreams started dropping inbound sessions. Node kept serving from cache. We are not moving it out of the pool because cache hits are unaffected and it is the only node with usable latency inside RU.
Planned. The node moved to a new address. Sessions established on the old IP were drained rather than cut, so the window looked longer than the actual switch. Old address stays reachable until 2026-09-01.
Brotli level 11 on large objects pinned both nodes at 100% during a customer's release. Lowered to 6 for objects over 1 MB. This is why that default exists.
Announced in December, removed on schedule. Four accounts were still calling v0 and got 410 for a day before we reached them. Our fault for not paging harder.