Netlify Outage History

51 incidents recorded over the last 365 days, 51 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Netlify status99.74% uptime history

Every Recorded Netlify Incident

Netlify incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Aug 18, 2026Elevated HTTP 500 errors serving sites and the Netlify UIOn 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…0 minResolved
Aug 3, 2026Elevated Build ErrorsThis incident has been resolved.24 minResolved
Jul 22, 2026Errors Uploading Attachments to Agent RunnersThis incident has been resolved.27 minResolved
Jul 1, 2026Increase in Edge Function ErrorsThis incident has been resolved.24 minResolved
Jun 14, 2026Connectivity issues affecting Bolt-powered sitesThis incident has been resolved.5h 49mResolved
Jun 13, 2026AI Gateway: Claude Fable 5 unavailableThis incident has been resolved.49h 18mResolved
Jun 9, 2026Elevated latency affecting image deliveryThis incident has been resolved.14 minResolved
Jun 4, 2026Elevated error rates for a subset of sites using Edge FunctionsThis incident has been resolved. Between approximately 17:00 and 20:30 UTC, a subset of sites using Edge Functions experienced elevated 504 error rates. We applied a mitigation and error rates have remained at normal…34 minResolved
Jun 2, 2026Blobs issues in Sydney regionBetween May 29th at 15:30 UTC till June 2 6:08 UTC, we experienced sporadic issues with Blobs in our Sydney region, affecting any Function using Blobs, including the ones that are generated by the framework runtimes…-5925 minResolved
May 27, 2026Failed & delayed builds due to Github incidentThis incident has been resolved, and builds have returned to functioning normally.2h 4mResolved
May 26, 2026Image Delivery IssuesThis incident has been resolved.30 minResolved
May 25, 2026Support Communication Delivery IssuesThis incident has been resolved.2h 0mResolved
May 23, 2026Elevated Build FailuresThis incident has been resolved.4h 47mResolved
May 19, 2026Elevated response times affecting origin servicesThis incident has been resolved. The issue that was causing elevated errors, increased latency, and intermittent site availability across Netlify services has been mitigated. All services, including site delivery and…1h 55mResolved
May 19, 2026Elevated Build and Functions Deployment ErrorsBetween 17:38 and 17:57 UTC, we experienced elevated error rates affecting the Build Pipeline. Some customers may have encountered failed deploys or HTTP 500/503 errors during deployment processing. The systems are…-134 minResolved
May 19, 2026Degraded performance with Create APIThis incident has been resolved.2h 22mResolved
May 19, 2026Degraded performance with Create APIThe incident with performance degradation for create.netlify.com has be resolved.25 minResolved
May 15, 2026Purges are Delayed on Primary Load BalancerThis incident has been resolved.2h 35mResolved
May 12, 2026Increased Latency in API & BuildsThis incident has been resolved.1h 7mResolved
May 11, 2026Build Issues due to Github OutageThis incident has been resolved.56 minResolved
May 11, 2026Latency in API & BuildsThis incident has been resolved.1h 51mResolved
May 10, 2026Degraded Service in IAD RegionOur network experienced degraded service in the IAD region between 12:53 UTC and 13:53 UTC. This issue is now resolved.0 minResolved
May 10, 2026Increase in DNS Resolution ErrorsThis incident has been resolved.48 minResolved
May 10, 2026Increase in Agent Runner ErrorsThis incident has been resolved.1h 6mResolved
May 9, 2026Issues Processing Account ChangesWe experienced issues processing account changes between 19:09 and 19:33 UTC. Users may have encountered issues when attempting to use Agent Runners, purchase credits, view credit usage, or complete account…0 minResolved
May 8, 2026Elevated Errors in IAD regionThis incident has been resolved.1h 6mResolved
May 6, 2026Elevated Errors and LatencyThis incident has been resolved.1h 19mResolved
May 5, 2026Agent Runner failures on new projectsThis incident has been resolved.2h 19mResolved
May 3, 2026Delayed Credit Usage UpdatesSome 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.-259 minResolved
Apr 26, 2026Increased errors on Image CDNWe experienced an elevated rate of errors on the Image CDN across Standard as well as High Performance Edge Networks. The errors started around 03:55 UTC. The recovery began around 04:55 UTC.-70 minResolved
Apr 24, 2026Increased Errors on Image CDNThis incident has been resolved.46 minResolved
Apr 23, 2026Elevated Rate of Build FailuresThis incident has been resolved.1h 0mResolved
Apr 13, 2026Scheduled Functions Auto-Triggering Not ExecutingThis incident has been resolved. A fix was deployed for the issue affecting Scheduled Functions auto-triggering, and scheduled invocations have recovered. During the incident, manual executions continued to work, but…37 minResolved
Apr 9, 2026Issues with credit purchases and auto top-upsbetween 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.-48 minResolved
Apr 6, 2026Agent Runners OutageBetween 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…-23 minResolved
Apr 2, 2026Increased errors on the CDNThis incident has been resolved.5h 32mResolved
Mar 30, 2026Environment Variables IssuesWe’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.0 minResolved
Mar 27, 2026Increased errors for Edge Functions on Standard Edge NetworkFrom 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…-45 minResolved
Mar 24, 2026Delayed Cache PurgesThis incident has been resolved.1h 2mResolved
Mar 20, 2026Increased errors and latency on the Standard Edge NetworkBetween 21:08 and 21:22 UTC, there was an increase in errors and latency on the Standard Edge Network.-40 minResolved
Mar 17, 2026Elevated Edge Function errors on Standard Edge NetworkThis incident has been resolved.36 minResolved
Mar 12, 2026Increased errors on High Performance Edge in Mumbai regionThis incident has been resolved.33 minResolved
Mar 11, 2026Service disruption for Netlify application, sites, builds & APIThis incident has been resolved.2h 49mResolved
Mar 10, 2026Increased errors for Edge Functions on Standard Edge NetworkFrom 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…-35 minResolved
Mar 4, 2026Increased edge function errors errors on Standard Edge NetworkBetween 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.0 minResolved
Mar 3, 2026Delayed Builds on Free AccountsThis incident has been resolved.34 minResolved
Feb 17, 2026Increased Latency on app.netlify.comWe experienced increased latency on app.netlify.com between 20:04 and 20:40 UTC. This incident is resolved.0 minResolved
Feb 11, 2026Service DisruptionBetween 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.28 minResolved
Feb 10, 2026Downtime for Live TunnelThis incident has been resolved.3 minResolved
Feb 9, 2026Increase in Deploy FailuresThis incident has been resolved.1h 15mResolved
Feb 9, 2026Increase in Deploy FailuresThis incident has been resolved.1h 11mResolved

How to Read This Netlify Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Netlify acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Netlify outage in this window ran 2d 1h, against a mean recovery of 2h 24m. If you depend on Netlify in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.