Edge Node — Russia / Central

MSK-01 Node Status

All Systems Operational
99.97%
Uptime — Last 90 Days
Avg Latency
12ms
Requests / sec
45.2K
Cache Hit Ratio
94.8%
Bandwidth
2.4Gbps
Uptime — Last 30 Days
Operational
Degraded
30 days ago Today

Points of Presence

St. Petersburg Moscow Kazan Yekaterinburg Novosibirsk Rostov-on-Don
Moscow (MSK-01) 1ms
St. Petersburg (SPB-01) 6ms
Kazan (KZN-01) 11ms
Rostov-on-Don (ROV-01) 16ms
Yekaterinburg (EKB-01) 22ms
Novosibirsk (NVS-01) 38ms

Service Status

Service Description Status Uptime
HTTP Cache Edge caching and content delivery Operational 99.99%
HTTPS Termination TLS/SSL certificate management Operational 99.99%
DNS Resolution Anycast DNS with GeoDNS routing Operational 100.0%
Origin Shield Origin protection and load balancing Operational 99.98%
DDoS Protection L3/L4/L7 traffic filtering Operational 100.0%
Edge Compute Serverless functions at the edge Operational 99.95%

Recent Incidents

Mar 14
Elevated latency on Origin Shield
Brief increase in p99 latency due to upstream provider maintenance. No user-facing impact detected. Issue resolved automatically after provider completed maintenance window.
Resolved
Mar 3
DNS propagation delay
GeoDNS configuration update caused temporary resolution delays for approximately 0.3% of requests in the Central region. Rollback applied within 4 minutes.
Resolved

Documentation

Getting Started
Quick start guide for integrating with InfraCDN edge nodes. Setup, configuration, and first request.
Cache Configuration
TTL policies, cache keys, purge API, and cache tag invalidation rules for edge nodes.
TLS & Security
Certificate management, HTTPS enforcement, HSTS headers, and origin shield configuration.
Analytics & Logs
Real-time analytics, access logs, error rate monitoring, and custom log drains.

API Reference

Base URL https://api.infra-cdn-01-msk.org/v1
GET /status Current node status and health check
GET /metrics Real-time performance metrics
GET /nodes List all PoP nodes and their status
POST /cache/purge Purge cached content by URL or tag
GET /incidents Incident history and current alerts
All endpoints require authentication via X-API-Key header. Request access through the dashboard.