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 运行正常。 Netlify 构建并托管前端应用与静态站点。
根据 Netlify 公布的事件推算,属于估算,不是实测值。
最近一次事件:“Error accessing Netlify-hosted sites”,11 天前。
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 官方状态页显示:All Systems Operational。本页每次打开时会重新读取,最多每 5 分钟一次。
Netlify 最近一次报告的事件是“Error accessing Netlify-hosted sites”,发生在11 天前(2026-10-05 12:44 UTC)。最近一次完全中断始于59 天前。
Netlify 的状态页列出 39 个组件,包括 High-Performance Edge Network, Atlassian Bitbucket API, Standard Edge Network, Atlassian Bitbucket Webhooks, Atlassian Bitbucket SSH。每次页面刷新都会重新读取。
暂停依赖它的部署,等恢复后重试或补跑失败的任务,并看看镜像或缓存能否临时顶上。
构建管道出故障时就是这样:分发已部署站点的 Edge 网络和构建系统是不同组件,已发布的部署照常访问。
Netlify 在状态页上把 GitHub 和 Bitbucket webhook 列为依赖项。GitHub 那行降级时 push 不会触发构建,即使 Netlify 全绿——恢复后到后台手动重新触发。
如果上面显示运行正常但 Netlify 对你仍然不可用,问题多半在你这边:换个网络、清除缓存,或检查自己的网络连接。如果显示降级或故障,说明其他人也受到影响。
OpenUptime 每分钟检查一次你的网站,一旦无响应就通过 Slack、Telegram、邮件或 Webhook 告警。它是开源的,可以免费开始使用。