Delays in build logs appearing in the UI
The issue causing delays in build logs appearing in the Netlify UI has been resolved.
The latest update from Netlify.
State
Resolved
Started
10 d ago
2026-10-22 06:15 UTC
Lasted
3 h 57 min
until 2026-10-22 10:12 UTC
Worst impact
Degraded
Timeline
14 updatesMonitoring
3 h 57 min 100%
Updates
Times in UTCAs posted by Netlify
The issue causing delays in build logs appearing in the Netlify UI has been resolved.
We have completed processing the Build Logs backlog. All customers should now have a consistent experience when viewing both historical and new Build Logs in the UI. We believe customer impact has ended. We will continue to closely monitor the situation for any signs of recurrence.
As of 08:45 UTC, we are still processing the backlog of build logs at full throttle. Some partitions have completed backlog processing, but others still have backlog pending. As a result of this partial processing, customers may experience intermittent availability until the full backlog is processed. Some build logs may be available, and others not. Real-time build logs should be working as expected. The new ETA for backlog processing is 10:00 UTC. We will provide our next update at 10:00 UTC.
Build log processing continues at full throttle and we estimate backlog to be cleared by 9:00 UTC. We’ll post next update at 8:45 UTC.
We are still monitoring the build log ingestion backlog. We will post our next update at 7:30 UTC, or sooner if anything changes.
The upstream provider applied a fix at 3:30 UTC and we are monitoring system health. We are able to ingest build logs at full throughput but we have hours of backlog that we need to process.
We continue to work with our upstream service provider on the delays in build logs appearing in the Netlify UI.
We've identified the cause of the delays in build logs appearing in the Netlify UI as an issue with an upstream service provider, who is working on a fix
We continue to experience delays in build logs appearing in the Netlify UI. We remain in contact with our upstream service provider as the investigation continues. We will provide further updates as more information becomes available.
We have identified an ongoing issue with an upstream service provider that may be contributing to delays in build logs appearing in the Netlify UI. We are in contact with the provider and are continuing to monitor the situation. We will provide further updates as more information becomes available.
We are continuing to investigate the delays affecting build log availability in the Netlify UI. We will share further updates as more information becomes available.
We are continuing to investigate delays in build logs appearing in the Netlify UI. We are still actively investigating and will provide further updates as information becomes available.
We are continuing to investigate delays in build logs appearing in the Netlify UI. Our team is working to identify the cause and will provide further updates as information becomes available.
We are investigating an issue causing delays in build logs appearing in the Netlify UI. Our team is actively investigating and will provide updates as we learn more.
Affected components
2Netlify in the last 90 days
Full historyIncidents in 90 days
17
Days with an incident
15
Median duration
51 min
This incident
4.7× the median
Other Netlify incidents
All incidentsNetlify·Elevated Build Errors and Agent Runner failures
The issue affecting builds and agent runs has been resolved.
Netlify·Delays in build logs appearing in the UI
This incident has been resolved.
Netlify·Delayed Edge Functions and Functions logs
This incident has been resolved.
Netlify·Agent Runner failures
This incident has been resolved.
Netlify·Elevated Build Errors
This incident has been resolved.
Follow Netlify
Your coding agent knows when Netlify is down, and tells you when a failure is theirs, not yours. You can also get Netlify incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "netlify" and tell me if Netlify has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=netlify/feed subscribe https://outages.cc/feed.xml?providers=netlifyFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane