Netlify outage history

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.

A fix has been implemented and we are monitoring the results.

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.

As of 20:50 UTC, build logs are visible in the UI as expected. We are continuing to monitor while our upstream service provider investigates the underlying cause.

Edge Functions and Function logs from the period between 13:58–15:35 UTC may be delayed in appearing in the Netlify UI and in log drains. We are working to process the backlog; function and edge function requests are not affected.

This incident has been resolved.

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.

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 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 the delays affecting build log availability in the Netlify UI. We will share 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 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'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 work with our upstream service provider on the delays in build logs appearing in the Netlify UI.

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 are still monitoring the build log ingestion backlog. We will post our next update at 7:30 UTC, or sooner if anything changes.

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.

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.

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.

The issue causing delays in build logs appearing in the Netlify UI has been resolved.

We are investigating increased Agent Runner failures. We will share updates as we learn more.

We are monitoring the incident.

This incident has been resolved.

We have identified an issue with a third-party service used by our build system. Builds started on or after 21:10 UTC that use the CSP extension may experience increased errors.

We've released a fix to resolve the errors for builds using the CSP extension, and we are monitoring the results.

This incident has been resolved.

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.

We are investigating reports of errors affecting access to sites on our High-Performance Edge Network. Our engineering team is actively investigating the issue. We will provide additional updates as more information becomes available.

We are continuing to investigate this issue.

The issue has been identified and a fix is being implemented.

A fix has been implemented and we are monitoring the results.

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.

We are investigating reports of errors affecting access to Netlify-hosted sites. Our engineering team is actively investigating the issue. We will provide additional updates as more information becomes available.

We are seeing signs of recovery, and service has returned to normal operation.

This incident has been resolved. Service has returned to normal operation, and we are no longer seeing elevated error rates.

We have identified a DNS resolution issue affecting our edge network’s ability to reach some origin servers. Requests to affected sites may fail. Our team is working to restore service.

We have identified the cause of the elevated CDN errors and are applying mitigations across affected systems. Recovery is underway, though some requests may continue to fail during this process.

We have applied a fix for the issue causing elevated CDN errors. Services are recovering, and we are monitoring the platform to confirm full recovery.

The issue causing elevated CDN errors has been resolved. DNS resolution has recovered, and affected services are operating normally.

We are investigating reports of errors affecting access to Netlify-hosted sites. Our engineering team is actively investigating the issue. We will provide additional updates as more information becomes available.

We are continuing to investigate this issue. Customers may also experience issues accessing the Netlify application and its features.

We have identified the issue and are working to restore normal service. We will provide another update as more information becomes available.

A fix has been implemented and we are monitoring the results. We will provide another update as we continue to monitor recovery.

This incident has been resolved.

We are experiencing elevated errors within our Image CDN service starting at 12:37 UTC. We are currently investigating this issue.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

We experienced increased errors and latency in the IAD region on our regular network between 15:50 and 17:45 UTC. This issue has been resolved.

Between 10:32 UTC and 10:36 UTC, we observed an increase in errors affecting traffic on the High Performance Edge Network in the FRA region due to an unexpected increase in traffic. Error rates have since returned to normal.

We're experiencing increased latency on a subset of CDN nodes in the IAD region. We are currently investigating this issue.

Request latency across the IAD region has returned to normal levels, and we are continuing to monitor the situation.

This incident has been resolved.

On August 18 between 20:02 and 20:08 UTC, some visitors to Netlify-hosted sites and people using the Netlify dashboard received error pages instead of the content they requested. Normal service was restored at 20:08 UTC. We apologize for the disruption

We're currently investigating elevated build errors starting at 8:58 UTC.

Since 9:32 UTC we're seeing a decrease in failed builds. The team will continue to monitor.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

We are currently investigating an issue where some users are encountering errors when uploading attachments to Agent Runners. We have implemented a fix and are monitoring the results.

This incident has been resolved.

We're currently monitoring an increase in Edge Function errors related to module loading. These errors would primarily surface during builds, but remote module loading can also impact runtime. We will post updates as more information becomes available.

This incident has been resolved.