Fleet
Every node in the network, with its current state and 30-day availability. Nodes named for their region carry a sequence number because more than one may run in the same location.
| Node | Location | Role | State | 30d | Median |
|---|---|---|---|---|---|
| russia4 | Central Russia | Edge | operational | 99.94% | 31 ms |
| russia2 | Northwest Russia | Edge | operational | 99.97% | 27 ms |
| finland2 | Helsinki | Edge + origin | operational | 99.99% | 12 ms |
| germany1 | Frankfurt | Origin | operational | 99.98% | 9 ms |
| nl3 | Amsterdam | Edge | operational | 99.96% | 11 ms |
| poland1 | Warsaw | Edge | degraded | 99.41% | 24 ms |
| turkey1 | Istanbul | Edge | operational | 99.92% | 38 ms |
| kz2 | Almaty | Edge | operational | 99.89% | 44 ms |
Roles
- Edge
- Terminates client connections and serves cached objects. Runs the probe set assigned to its region.
- Origin
- Holds the authoritative copy of published objects and answers cache fill requests from edge nodes.
- Edge + origin
- Both, on the same host. Used where regional demand does not yet justify separate machines.
Planned work
poland1 is running on reduced capacity while its upstream link is reprovisioned. Traffic is served from nl3 in the meantime; no action is needed from users. Estimated return to full capacity is mid-September.
No other maintenance is scheduled.