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

推荐订阅源

S
SegmentFault 最新的问题
Google DeepMind News
Google DeepMind News
G
Google Developers Blog
Martin Fowler
Martin Fowler
MongoDB | Blog
MongoDB | Blog
月光博客
月光博客
Jina AI
Jina AI
宝玉的分享
宝玉的分享
人人都是产品经理
人人都是产品经理
D
DataBreaches.Net
V
V2EX
WordPress大学
WordPress大学
T
The Blog of Author Tim Ferriss
Last Week in AI
Last Week in AI
B
Blog
博客园 - 叶小钗
小众软件
小众软件
Stack Overflow Blog
Stack Overflow Blog
P
Proofpoint News Feed
A
About on SuperTechFans
J
Java Code Geeks
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
Y
Y Combinator Blog
Microsoft Security Blog
Microsoft Security Blog

Netlify Status - Incident History

Elevated Image CDN Errors 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 Degraded Service in IAD Region Increase in DNS Resolution Errors Increase in Agent Runner Errors Issues Processing Account Changes Elevated Errors in IAD region
Delayed Credit Usage Updates
2026-05-03 · via Netlify Status - Incident History

Resolved

Some customers may have seen delayed credit usage updates and related notifications between 00:14–01:37 UTC on May 3. The issue has been resolved, and usage information is now up to date.

Posted May 03, 2026 - 00:00 UTC