CDN incidents are easy to misread because a public symptom can originate in the CDN, an origin, DNS, a certificate authority, a cloud dependency, or the customer’s own configuration. Use primary sources to establish what is known before assigning cause.
This page is a monitoring method and source directory. It is not a live incident feed.
Start with the incident class Signal Check first Confirm with Broad availability drop Provider status page Provider incident history and your regional probes New CVE or exploited flaw Vendor advisory and CISA KEV Product/version scope and remediation text Elevated 5xx responses CDN and origin logs The 5xx ownership and diagnosis guide Certificate failures CDN certificate state and CA status TLS handshake logs and affected hostnames Cache or purge anomaly Cache-status headers and purge operation IDs The purge verification checklist Suspected attack WAF, bot, and DDoS event logs Provider advisory, indicators, and application logs Primary status sources Akamai service status AWS Health Dashboard Cloudflare status Fastly status Google Cloud service health Microsoft Azure status Subscribe to the provider’s official email, RSS, Atom, webhook, or API option where one exists. A third-party aggregator is useful for discovery, but it should not be the sole evidence for impact, cause, or resolution.
...