MSK9 is our Moscow point of presence. It serves HLS and DASH segments, images and large files to viewers across Central Russia, the Caucasus and Central Asia with low first-byte latency.
Read the docsSystem statusEverything needed to move media from your origin to the player, without changes to your packaging pipeline.
HLS and MPEG-DASH segments are cached at the edge with manifest-aware TTLs, so live playlists stay fresh while segments stay hot.
A single shielding tier collapses concurrent misses into one origin request and keeps your storage egress predictable.
Time-limited tokens with optional IP and path binding protect premium content without a round trip to your backend.
Range requests and sliced caching make multi-gigabyte downloads resumable and cache-efficient.
Invalidate by URL, prefix or cache tag through the API. Purges propagate to the POP in under two seconds.
Per-request access logs are streamed to your collector in JSON, with cache status, bytes sent and upstream timing.
MSK9 is connected to regional carriers and exchange points. Routing is tuned for last-mile networks rather than for transit cost.
| Region | Typical latency | Protocols | State |
|---|---|---|---|
| Central Russia | 4–18 ms | HTTP/2, TLS 1.3 | Operational |
| South Caucasus | 28–45 ms | HTTP/2, TLS 1.3 | Operational |
| Central Asia | 60–95 ms | HTTP/2, TLS 1.3 | Operational |
| Eastern Europe | 22–40 ms | HTTP/2, TLS 1.3 | Operational |
Point a CNAME at your delivery hostname and requests start flowing through the edge. No SDK is required.
video.example.com. 300 IN CNAME msk9.cdn-video178.ru. $ curl -I https://video.example.com/live/master.m3u8 HTTP/2 200 content-type: application/vnd.apple.mpegurl x-cache: HIT x-pop: MSK9