Node profile
About this host
Operational detail for ru-01, published so that integrators can
reason about cache behaviour and expected latency.
Placement
| Region | eu-east |
|---|---|
| Node | ru-01 |
| Role | Edge cache / TLS termination |
| Transport | HTTP/2 over TLS 1.2–1.3 |
| Address family | IPv4 |
Cache behaviour
Objects are keyed on the full request URI including query string. Responses carrying
Cache-Control: private, no-store or a Set-Cookie
header are never retained. Revalidation uses If-None-Match where the origin
supplies a strong ETag.
Purge requests are accepted only from the control plane; there is no public purge endpoint on the node itself.
Draining
Before maintenance, a node is removed from the region alias and left to bleed existing keep-alive connections. Because endpoints hold no session state, a drained node can be returned to service without a warm-up period beyond cache repopulation.
Contact
Operational issues affecting this endpoint should be raised through the usual support
channel with the node identifier ru-01 and an approximate timestamp.