MyCDN

Content Delivery Network — Edge Node Active

Operational — All systems normal
# MyCDN Edge Server server { listen 443 ssl http2; server_name a-masterkov.ru; location / { proxy_pass https://ger01.a-masterkov.ru; proxy_cache MYCDN_CACHE; proxy_cache_valid 200 7d; add_header X-CDN-Node "edge-ams-01"; } }
Node ID
edge-ams-01
Region
EU-West (Amsterdam)
Cache Hit Ratio
94.7%
Uptime
99.99%
📦 Access CDN 📊 Status

Planned Maintenance

Scheduled maintenance in progress

Maintenance Mode — ETA: 45 minutes
# Maintenance Window start_time: 2024-01-15 02:00 UTC end_time: 2024-01-15 03:00 UTC reason: "Edge cache upgrade to v2.5" affected_nodes: - edge-ams-01 - edge-fra-02 - edge-lon-03 status: "In progress — 65% complete"
Scheduled
2024-01-15 02:00 UTC
Estimated Completion
2024-01-15 03:00 UTC
Affected Services
CDN Edge Cache
Origin Status
Online
📅 View Maintenance Schedule
404

Resource Not Found

The requested file was not found on this CDN node

Error — Cache Miss & Origin 404
# Request Details method: GET path: /assets/js/main.min.js node: edge-ams-01 origin: origin.example.com cache_status: MISS origin_status: 404 Not Found # Suggestions possible_cause: "File deleted or renamed" ttl_after_purge: 0s (purged immediately)
🏠 Back to CDN Root 📁 Browse Available Files

Internal Server Error

Unexpected error on edge node

Error 500 — Node Failure
# Error Report error_code: 500 node: edge-fra-02 timestamp: 2024-01-15 14:32:07 UTC exception: "ConnectionTimeoutError" origin_status: "unreachable (timeout 30s)" failover: "Attempting failover to edge-lon-03..." # Auto-Recovery retry_count: 3/3 (exhausted) next_action: "Escalating to on-call engineer"
Node Status
Degraded
Failover Node
edge-lon-03
Incident ID
INC-2024-0142
Priority
P2 — High
🔄 Retry Request 📋 View Incident