Netlify Outage History

Between 12:00 UTC and 12:28 UTC our Origin showed query contention that caused higher latencies and elevated error rates impacting different components like Origin Servers, Build Pipleine, API and UI utilization.

We are continuing to monitor for any further issues.

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

We are currently investigating this issue.

The purchasing of extra credits for credit-based plans is available again. The incident is resolved.

Purchasing of extra credits is currently unavailable. Auto-recharge is still available at this time.

This incident has been resolved.

We are continuing to monitor our mitigations and for any further issues.

We are continuing to monitor the recovery results across the network.

We are continuing to see recovery across the network

We have applied a mitigation and are seeing recovery.

We are continuing to investigate this issue

As of 12:04 UTC, we are experiencing issues and latency serving traffic from the High Powered Edge Network.

Service has been restored.

We are continuing to investigate this issue.

Starting from 11:14:20 UTC, we are experiencing an increased number of errors serving traffic from the Standard Edge. HP Edge is not affected.

Some sites on the Standard Edge Network experienced intermittent availability issues. Our team identified and mitigated the cause, and services have since recovered.

Our team is actively working to mitigate the impact for sites on the Standard Edge Network. Services are recovering, and we're monitoring stability. This started at 2:17PM UTC. We will provide more updates shortly

The build issues have been resolved.

From 10:06 to 10:25 am UTC, builds experienced a high rate of errors. We have mitigated the issue and put a fix in place, and will continue to monitor the result.

This incident has been resolved.

From 6pm UTC October 20 until 7am UTC October 21, Agent Runners Service has been experiencing failures. We have determined the source of the issue, put a fix in place, and will continue to monitor its effectiveness.

The issues impacting our services have been fully resolved. All systems are now operating normally. We appreciate your patience during this incident.

We're seeing each of the impacted Netlify services returning to a stable condition, and we're continuing to monitor for any further issues.

Our teams are closely monitoring the issue and collaborating with AWS to restore normal service as quickly as possible. Impact continues across several services, including Functions, Email, CDN (Intermittent connectivity issues and timeouts in some regions), ImageCDN, Agent Runners, and some Builds

We have identified and resolved the primary issue affecting our services. The problem was related to upstream infrastructure issues that impacted how traffic was being routed to our systems. We have made configuration changes to route around the affected infrastructure

Impact continues across several services, including Functions, Email, CDN ( Intermittent connectivity issues and timeouts) , ImageCDN, Agent Runners, and delays in processing some Builds

We continue to experience CDN-related issues in the IAD (US-East-1) regions. This may cause slow load times or intermittent errors for users served from these locations. Our team is working with upstream providers to mitigate the impact and restore full performance. We’ll share another update as soon as we see meaningful recovery.

The upstream provider didn’t fully recover from the outage, and despite our services stay operational, our team continues to monitor the situation to ensure stability.

Starting 11:50 UTC the upstream provider is showing consistent recovery and not throttling our function creation anymore. Netlify Build error rates have been reduced to normal values. Our team is continuing to monitor the situation to ensure stability.

We are continuing to investigate increased Netlify Build error rates that contain functions that are deployed to us-east-1 region. For more urgent resolution, we suggest moving functions to a different region, see https://docs.netlify.com/build/functions/optional-configuration/?data-tab=TypeScript#region.

We are continuing to mitigate these service issues.

We’re seeing recovery across several services after an AWS outage affected our systems. AWS has posted details here: https://health.aws.amazon.com/health/status. Services are improving, and we’ll keep you updated as we confirm full restoration.

As of 6:56 am UTC, we have been experiencing issues related to an outage at AWS in US-East-1. Affected services include UI actions, outgoing emails from Netlify, builds, functions, as well as 500 errors during site loading.

This incident has been resolved.

Sites still pointing to the legacy edge network (Equinix) with the IP 147.75.40.150 will be offline until the DNS is updated to the current IP address. Please follow this guide: https://www.netlify.com/changelog/equinix-ip-address-expiring-for-4-year-old-sites/. DNS propagation can take up to 24–48 hours, depending on TTL.

This incident has been resolved.

We have identified the cause, implemented a fix, and are now monitoring results.

We see an increase in errors serving content on HP Edge across several regions starting at 12:15 UTC.

Between 11:35–11:37 UTC, some customers experienced elevated 500 errors, 503s, and increased latency across multiple sites. Services automatically recovered within 2 minutes.

This incident has been resolved.

A fix has been implemented and we are monitoring for any issues.

We are experience build failures this morning as of 7:05am UTC due to missing npm package versions. We have identified the source of the issue and are implementing a fix.

This incident has been resolved.

We're observing that build processing times have returned to normal. We're continuing to monitor the system closely to ensure stability.

We are currently investigating an issue causing delays in builds during the build processing

This incident has been resolved.

A fix has been implemented and we’re are monitoring the results. Please re-deploy any sites that may have been affected.

Starting at 16:04 UTC August 18 we’ve see an increase in Functions errors affecting a subset of our Next.js customers. We've narrowed down the root cause and applying a fix.

Some users experienced regional DNS resolution issues due to a third-party network provider outside our control. Throughout the incident, our servers remained fully operational and continued serving web traffic without interruption. We have not received any new reports and believe the issue has been resolved. Based on this and the external nature of the root cause, we are now closing this incident. If you continue to experience DNS-related problems, we recommend updating your DNS settings to use a public DNS service such as: 8.8.8.8 8.8.4.4 Thank you for your understanding

We are currently monitoring the situation.

After further investigation, we have identified that the issue appears to stem from a regional network provider. Our servers are operating normally and continuing to serve web traffic without interruption. This issue is related to DNS resolution and is outside of our direct control. We have escalated the matter with our upstream providers and are monitoring the situation closely. As a workaround, we recommend updating client DNS settings to use a public DNS service such as: - 8.8.8.8 - 8.8.4.4 This may help mitigate the issue for affected users. We will continue to monitor the situation and provide updates as information becomes available.

We've seen recent reports of DNS errors for users in Latin America. We are currently investigating this issue.