Netlify

Netlify’s unified platform for build pipelines, edge CDNs, and serverless functions presents a unique challenge in incident reporting. Each layer can fail independently, leaving a team with a green build but a degraded CDN, or functional functions but a broken pipeline. The status page at https://www.netlifystatus.com/ disambiguates these split-brain scenarios, providing granular insight into what’s truly affecting your deployments.

Incidents are logged by component, ‘Builds’, ‘CDN’, and ‘Functions’ each with their own timeline. A delay in one doesn’t necessarily mean the others are impacted. For instance, a regional CDN degradation might not affect builds or functions running elsewhere. Netlify’s status feed at https://www.netlifystatus.com/history.atom is the go-to surface for teams relying on its unified platform to understand what’s truly affecting their users.