Elevated Edge Function Errors
Between 13:16 and 13:24 UTC some requests to sites that use Edge Functions experienced increased latency and an elevated rate of 502 errors. This incident has been resolved.
Netlify is up and running. Netlify builds and hosts front-end apps and static sites.
Worked out from the incidents Netlify reported, so it is an estimate and not a measurement.
Last incident: “Error accessing Netlify-hosted sites”, 11 days ago.
Between 13:16 and 13:24 UTC some requests to sites that use Edge Functions experienced increased latency and an elevated rate of 502 errors. This incident has been resolved.
Between 19:05 and 19:18 UTC, some requests to the AI Gateway returned errors. We've since increased the capacity of the affected service, and error rates returned to normal levels at 19:18 UTC. We apologize for the disruption.
This incident has been resolved. Sites on our High-Performance Edge Network have returned to normal operation. The incident began at 12:19 UTC and service was restored at 13:14 UTC.
This incident has been resolved. Sites on the High-Performance Edge have returned to normal operation, and we are no longer seeing elevated error rates.
This incident has been resolved. Service has returned to normal operation, and we are no longer seeing elevated error rates.
Netlify’s official status page says: All Systems Operational. This page checks it again when you load it, at most every 5 minutes.
The most recent incident Netlify reported was “Error accessing Netlify-hosted sites”, 11 days ago (2026-10-05 12:44 UTC). Its last full outage started 59 days ago.
Netlify reports 39 components on its status page, including High-Performance Edge Network, Atlassian Bitbucket API, Standard Edge Network, Atlassian Bitbucket Webhooks, Atlassian Bitbucket SSH. Each is checked again whenever this page refreshes.
Pause deploys that depend on it, queue or retry failed jobs once it recovers, and check whether a mirror or cache can cover the gap.
Expected during a build-pipeline incident: the edge network serving deployed sites is a different component from the build system, so published deploys keep being served.
Netlify tracks GitHub and Bitbucket webhooks as dependencies on its status page. If the GitHub row is degraded, pushes won't start builds even when Netlify itself is green — retrigger from the dashboard once it recovers.
If the status above is operational but Netlify still fails for you, the cause is probably on your side: try another network, clear the cache, or check your own connection. If it shows a degradation or an outage, others are affected too.
OpenUptime checks your site every minute and sends an alert to Slack, Telegram, email or a webhook the moment it stops responding. It is open source and free to start.