russia4
Current
| Metric | Value | Window |
|---|---|---|
| Availability | 99.94% | 30 days |
| Response, median | 31 ms | 24 hours |
| Response, p95 | 88 ms | 24 hours |
| Cache hit ratio | 91.2% | 24 hours |
| Probe targets | 148 | current |
| Last incident | degraded | 28 Jul 2026 |
What runs here
russia4 is a regional edge node. It terminates client connections, serves cached objects from origin, and runs the scheduled reachability probes assigned to this region.
Probe traffic is continuous by design: each target in the regional set is checked on a fixed interval, and results are shipped to the collector as they are produced. Cache fill happens on miss, so egress follows client demand rather than a schedule.
The node holds no customer data at rest. Cached objects expire according to origin headers and are dropped on restart.
Maintenance
Planned work is announced at least 72 hours ahead on the fleet page and by mail to account contacts. Nodes are drained before restart, so open connections finish rather than reset.
Something wrong that this page does not show? Write to noc@afinabs.com with the node name and a timestamp in UTC.