Netlify

Apr 9, 18:00 UTC Resolved - between 17:40 UTC and 18:10 UTC, some customers may have experienced failures when purchasing credits or updating auto top-ups. This issue has been resolved.

Apr 6, 09:30 UTC Resolved - Between 08:50 UTC and 09:41 UTC, Agent Runner experienced an outage caused by an issue with a third-party dependency. Customers may have experienced failures or degraded performance when running agents during this period. The issue has been resolved.

Apr 2, 17:59 UTC Resolved - This incident has been resolved. Apr 2, 15:34 UTC Monitoring - A fix has been implemented and we are monitoring the results. Apr 2, 14:19 UTC Update - We are continuing to investigate this issue. Apr 2, 14:19 UTC Update - We're also experiencing errors on the High Performance Edge Network. We're investigating the issue. Apr 2, 12:26 UTC Investigating - We're currently experiencing some errors on the Standard Edge Network. High Performance Edge Network should be u...

Mar 30, 21:09 UTC Resolved - We’ve deployed a fix for the environment variables issue affecting some sites, and this all sites have received this fix as of 4:45pm UTC 3-31. Mar 30, 19:38 UTC Monitoring - We’ve identified the root cause of the environment variables issue affecting some sites and have deployed a fix. The fix is now live, and impacted sites should have automatically received it. Customers do not need to take any further action. We’ll keep monitoring our channels for any additional ...

Mar 27, 16:30 UTC Resolved - From 16:30 UTC, we observed increased errors for Edge Function invocations on the Standard Edge Network. This includes framework generated Edge Functions like Next.js Middleware. The issue has been resolved as of 16:52 UTC.

Mar 24, 01:32 UTC Resolved - This incident has been resolved. Mar 24, 00:30 UTC Monitoring - We experienced an increased number of delayed cache purges on both the Standard and HP Edge Networks between 22:30 and 0:10 UTC. We have deployed a fix and are currently monitoring the results.

Mar 20, 21:08 UTC Resolved - Between 21:08 and 21:22 UTC, there was an increase in errors and latency on the Standard Edge Network.

Mar 17, 14:44 UTC Resolved - This incident has been resolved. Mar 17, 14:10 UTC Update - We are continuing to monitor for any further issues. Mar 17, 14:10 UTC Monitoring - A fix has been implemented and we will continue to monitor the results. Mar 17, 14:07 UTC Investigating - We are currently experiencing elevated rates of Edge Function errors on the Standard Edge Network since 13:38-14:07 UTC. We are investigating the cause.

Mar 12, 04:17 UTC Resolved - This incident has been resolved. Mar 12, 03:43 UTC Investigating - We're investigating an increase in errors on the High Performance Edge Network in Mumbai (BOM) region since 3 AM UTC.

Mar 11, 11:33 UTC Resolved - This incident has been resolved. Mar 11, 11:19 UTC Update - We are continuing to monitor for any further issues. Mar 11, 10:57 UTC Monitoring - The cause of the issue was identified, and we are monitoring the fix that was applied. Mar 11, 10:33 UTC Update - We are continuing to investigate this issue. Mar 11, 10:08 UTC Update - We are continuing to investigate this issue Mar 11, 09:38 UTC Investigating - We continue to investigate this rise in latencies creating high...

Mar 10, 16:43 UTC Resolved - From 16:43 UTC to 16:58 UTC, we served HTTP 500 for paths invoking Edge Functions (including framework-generated ones like Next.js Middleware/Proxy). This affected the Free/Starter as well as some part of the Pro tier users on the Standard Edge Network. The issue has since been resolved.

Mar 4, 10:26 UTC Resolved - Between February 25 until March 4, we saw an increased number of edge function errors related to requests with larger payloads on some sites on the standard network. This has been resolved.

Mar 3, 01:25 UTC Resolved - This incident has been resolved. Mar 3, 01:14 UTC Monitoring - A fix has been implemented, and we are monitoring the results. Mar 3, 00:51 UTC Investigating - Beginning at 23:58 UTC, we began seeing an increased rate of delayed builds for plans on the Free tier. We are currently investigating this issue.

Feb 17, 20:49 UTC Resolved - We experienced increased latency on app.netlify.com between 20:04 and 20:40 UTC. This incident is resolved.

Feb 11, 12:44 UTC Resolved - 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. Feb 11, 12:36 UTC Update - We are continuing to monitor for any further issues. Feb 11, 12:30 UTC Monitoring - A fix has been implemented and we are monitoring the results. Feb 11, 12:15 UTC Investigating - We are currently investigating this issue.

Feb 10, 12:56 UTC Resolved - This incident has been resolved. Feb 10, 12:52 UTC Investigating - We're currently investigating an issue with Live Tunnel.

Feb 9, 20:18 UTC Resolved - This incident has been resolved. Feb 9, 19:20 UTC Monitoring - We are seeing some improvement, and we're continuing to monitor this issue. Feb 9, 19:02 UTC Investigating - We're currently experiencing an elevated rate of deploy failures. We are investigating this issue.

Feb 9, 17:58 UTC Resolved - This incident has been resolved. Feb 9, 17:42 UTC Monitoring - We are continuing to monitor this issue. Feb 9, 16:53 UTC Update - We are continuing to investigate this issue. Feb 9, 16:46 UTC Investigating - We're currently experiencing an increase in deploy failures due to an issue affecting an upstream provider.

Feb 6, 04:40 UTC Resolved - We've resolved the issue that was causing 404 errors when accessing app.netlify.com The Netlify App is now fully operational. All services are functioning normally Feb 6, 03:51 UTC Investigating - We're currently investigating an issue where users may see a 404 error when accessing the Netlify App at app.netlify.com Our team is actively working to identify the root cause and restore access as quickly as possible