惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

D
DataBreaches.Net
F
Fortinet All Blogs
D
Docker
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
WordPress大学
WordPress大学
罗磊的独立博客
Y
Y Combinator Blog
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
J
Java Code Geeks
T
The Blog of Author Tim Ferriss
U
Unit 42
N
Netflix TechBlog - Medium
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
V
V2EX
云风的 BLOG
云风的 BLOG
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
T
Tailwind CSS Blog
Hugging Face - Blog
Hugging Face - Blog
Stack Overflow Blog
Stack Overflow Blog
爱范儿
爱范儿
酷 壳 – CoolShell
酷 壳 – CoolShell
P
Proofpoint News Feed
G
Google Developers Blog
H
Help Net Security

Netlify Status - Incident History

Elevated Errors and Latency in IAD Region Increased errors on High Performance Edge Network - FRA Region Increased Latency in IAD Region on Global Network Elevated HTTP 500 errors serving sites and the Netlify UI Elevated Build Errors Errors Uploading Attachments to Agent Runners Increase in Edge Function Errors Connectivity issues affecting Bolt-powered sites AI Gateway: Claude Fable 5 unavailable Elevated latency affecting image delivery Elevated error rates for a subset of sites using Edge Functions Blobs issues in Sydney region Failed & delayed builds due to Github incident Image Delivery Issues Support Communication Delivery Issues Elevated Build Failures Elevated response times affecting origin services Degraded performance with Create API Elevated Build and Functions Deployment Errors Degraded performance with Create API Purges are Delayed on Primary Load Balancer Increased Latency in API & Builds Latency in API & Builds Build Issues due to Github Outage Increase in DNS Resolution Errors Increase in Agent Runner Errors Issues Processing Account Changes Elevated Errors in IAD region Elevated Errors and Latency Agent Runner failures on new projects
Degraded Service in IAD Region
2026-05-11 · via Netlify Status - Incident History

Resolved

Our network experienced degraded service in the IAD region between 12:53 UTC and 13:53 UTC. This issue is now resolved.

Posted May 10, 2026 - 16:33 UTC

This incident affected: Standard Edge Network.