Netlify and Cloudflare Service Disruptions Impact Enterprise Builds
What happened
Netlify experienced multiple service disruptions in May 2024, including build failures linked to a GitHub outage on May 11 and separate API latency issues affecting enterprise deployments. The GitHub-related incident lasted approximately one hour, from 14:35 to 15:27 UTC, blocking automated builds across the platform. Simultaneously, Cloudflare reported issues with challenge page functionality in China, preventing users from accessing protected sites for over six hours from 05:33 to 12:08 UTC. These incidents followed earlier Netlify disruptions in March, including a platform-wide outage affecting all services and delayed builds specifically impacting free tier accounts.
Business impact
Background
Modern enterprise web operations increasingly depend on integrated CI/CD pipelines where GitHub triggers automatic Netlify builds for production deployments. The March incidents at Netlify, combined with May's repeated disruptions, signal potential reliability concerns for teams using the platform for mission-critical deployments. Cloudflare's China-specific issues reflect the complex regulatory and technical challenges of maintaining global CDN services.
What this means for your team
What to watch
Monitor Netlify's infrastructure updates and any changes to their GitHub integration architecture following these repeated build system failures. Track whether similar CDN providers report China-specific access issues, which could indicate broader regional connectivity problems.
Sources
-
Browser Run API availability issues
Cloudflare Status
-
Errors with Email Sending via the Worker Binding
Cloudflare Status
-
Latency in API & Builds
Netlify Status
-
Service disruption for Netlify application, sites, builds & API
Netlify Status
-
Network Performance Issues
Cloudflare Status
-
Issues passing Challenge Pages in China
Cloudflare Status