- Detected by Pingoru
- Oct 17, 2026, 05:03 AM UTC
- Resolved
- Oct 17, 2026, 05:55 AM UTC
- Duration
- 51m
Affected: Build Pipeline
Timeline · 3 updates
-
identified Oct 17, 2026, 05:03 AM UTC
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.
-
monitoring Oct 17, 2026, 05:30 AM UTC
We've released a fix to resolve the errors for builds using the CSP extension, and we are monitoring the results.
-
resolved Oct 17, 2026, 05:55 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Oct 08, 2026, 02:34 PM UTC
- Resolved
- Oct 08, 2026, 02:34 PM UTC
- Duration
- —
Affected: Edge Functions
Timeline · 1 update
-
resolved Oct 08, 2026, 02:34 PM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Oct 06, 2026, 08:12 PM UTC
- Resolved
- Oct 06, 2026, 08:12 PM UTC
- Duration
- —
Affected: Agent RunnersAI Gateway
Timeline · 1 update
-
resolved Oct 06, 2026, 08:12 PM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Oct 05, 2026, 12:44 PM UTC
- Resolved
- Oct 05, 2026, 01:34 PM UTC
- Duration
- 50m
Affected: High-Performance Edge Network
Timeline · 5 updates
-
investigating Oct 05, 2026, 12:44 PM UTC
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.
-
investigating Oct 05, 2026, 01:00 PM UTC
We are continuing to investigate this issue.
-
identified Oct 05, 2026, 01:17 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Oct 05, 2026, 01:24 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Oct 05, 2026, 01:34 PM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Sep 23, 2026, 11:26 PM UTC
- Resolved
- Sep 24, 2026, 12:00 AM UTC
- Duration
- 34m
Affected: High-Performance Edge NetworkStandard Edge NetworkBuild Pipeline
Timeline · 4 updates
-
identified Sep 23, 2026, 11:26 PM UTC
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.
-
identified Sep 23, 2026, 11:40 PM UTC
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.
-
monitoring Sep 23, 2026, 11:50 PM UTC
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.
-
resolved Sep 24, 2026, 12:00 AM UTC
The issue causing elevated CDN errors has been resolved. DNS resolution has recovered, and affected services are operating normally.
Read the full incident report →
- Detected by Pingoru
- Sep 21, 2026, 03:12 PM UTC
- Resolved
- Sep 21, 2026, 04:37 PM UTC
- Duration
- 1h 24m
Affected: High-Performance Edge NetworkStandard Edge Network
Timeline · 5 updates
-
investigating Sep 21, 2026, 03:12 PM UTC
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.
-
investigating Sep 21, 2026, 03:30 PM UTC
We are continuing to investigate this issue. Customers may also experience issues accessing the Netlify application and its features.
-
identified Sep 21, 2026, 03:45 PM UTC
We have identified the issue and are working to restore normal service. We will provide another update as more information becomes available.
-
monitoring Sep 21, 2026, 03:52 PM UTC
A fix has been implemented and we are monitoring the results. We will provide another update as we continue to monitor recovery.
-
resolved Sep 21, 2026, 04:37 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Sep 16, 2026, 12:58 PM UTC
- Resolved
- Sep 16, 2026, 01:48 PM UTC
- Duration
- 50m
Affected: High-Performance Edge NetworkStandard Edge NetworkNetlify Image CDN
Timeline · 3 updates
-
investigating Sep 16, 2026, 12:58 PM UTC
We are experiencing elevated errors within our Image CDN service starting at 12:37 UTC. We are currently investigating this issue.
-
monitoring Sep 16, 2026, 01:19 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Sep 16, 2026, 01:48 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Sep 08, 2026, 06:28 PM UTC
- Resolved
- Sep 08, 2026, 06:28 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Sep 08, 2026, 06:32 PM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Sep 04, 2026, 10:30 AM UTC
- Resolved
- Sep 04, 2026, 10:30 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Sep 04, 2026, 10:57 AM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Aug 31, 2026, 08:40 PM UTC
- Resolved
- Aug 31, 2026, 10:00 PM UTC
- Duration
- 1h 20m
Affected: High-Performance Edge NetworkEdge FunctionsNetlify Image CDN
Timeline · 3 updates
-
investigating Aug 31, 2026, 08:40 PM UTC
We're experiencing increased latency on a subset of CDN nodes in the IAD region. We are currently investigating this issue.
-
monitoring Aug 31, 2026, 08:56 PM UTC
Request latency across the IAD region has returned to normal levels, and we are continuing to monitor the situation.
-
resolved Aug 31, 2026, 10:00 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 18, 2026, 08:00 PM UTC
- Resolved
- Aug 18, 2026, 08:00 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Aug 18, 2026, 08:21 PM UTC
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
Read the full incident report →
- Detected by Pingoru
- Jul 22, 2026, 01:29 PM UTC
- Resolved
- Jul 22, 2026, 01:56 PM UTC
- Duration
- 27m
Affected: Agent Runners
Timeline · 2 updates
-
monitoring Jul 22, 2026, 01:29 PM UTC
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.
-
resolved Jul 22, 2026, 01:56 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 01, 2026, 05:53 PM UTC
- Resolved
- Jul 01, 2026, 06:18 PM UTC
- Duration
- 24m
Affected: Edge Functions
Timeline · 2 updates
-
monitoring Jul 01, 2026, 05:53 PM UTC
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.
-
resolved Jul 01, 2026, 06:18 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 14, 2026, 07:55 PM UTC
- Resolved
- Jun 15, 2026, 01:45 AM UTC
- Duration
- 5h 49m
Affected: Standard Edge NetworkBuild Pipeline
Timeline · 3 updates
-
identified Jun 14, 2026, 07:55 PM UTC
We are currently investigating a connectivity issue affecting customers using Bolt. Some customers may be experiencing errors or degraded performance when attempting to use Bolt at this time.
-
identified Jun 14, 2026, 08:23 PM UTC
While recovery is in progress, enabling and disabling sites may take longer than usual. Customers using Bolt may continue to experience delays or intermittent errors when accessing, creating, or updating Bolt-powered sites
-
resolved Jun 15, 2026, 01:45 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 13, 2026, 08:25 AM UTC
- Resolved
- Jun 15, 2026, 09:44 AM UTC
- Duration
- 2d 1h
Affected: AI Gateway
Timeline · 2 updates
-
monitoring Jun 13, 2026, 08:25 AM UTC
We are aware that requests to claude-fable-5 through Netlify AI Gateway are failing. Anthropic has suspended access to Claude Fable 5, and the model is currently unavailable. https://www.anthropic.com/news/fable-mythos-access
-
resolved Jun 15, 2026, 09:44 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 09, 2026, 03:41 AM UTC
- Resolved
- Jun 09, 2026, 03:55 AM UTC
- Duration
- 14m
Affected: High-Performance Edge NetworkStandard Edge NetworkNetlify Image CDN
Timeline · 3 updates
-
investigating Jun 09, 2026, 03:41 AM UTC
We are investigating elevated latency affecting image delivery for some Netlify-hosted sites Some customers may experience slower image load times or intermittent errors when loading images. Our engineering team is actively working to mitigate the issue, and we will provide another update as soon as we have more information.Impact start time: 03:19 AM UTC
-
monitoring Jun 09, 2026, 03:49 AM UTC
We are seeing recovery from the elevated latency affecting image delivery for some Netlify-hosted sites across our network. Error rates have decreased and image delivery performance has improved. Our engineering team is continuing to monitor the service to confirm stability. We will provide another update once the issue is fully resolved.
-
resolved Jun 09, 2026, 03:55 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 04, 2026, 08:24 PM UTC
- Resolved
- Jun 04, 2026, 08:59 PM UTC
- Duration
- 34m
Affected: Edge Functions
Timeline · 4 updates
-
investigating Jun 04, 2026, 08:24 PM UTC
Our team is investigating an increase in observed error rates affecting a subset of sites that use Edge Functions. Affected sites may see elevated 504 responses or slow page loads beginning at approximately 17:00 UTC. We are actively working to identify the cause and will provide updates here.
-
identified Jun 04, 2026, 08:34 PM UTC
We have identified an issue with a subset of our Edge Functions infrastructure causing elevated 504 errors for some sites beginning at approximately 17:00 UTC. We are applying mitigations and error rates are improving. Customers do not need to take any action. We will continue to provide updates here.
-
monitoring Jun 04, 2026, 08:42 PM UTC
We have applied a mitigation and error rates for affected sites have returned to normal levels as of approximately 20:30 UTC. We are continuing to monitor the situation and will provide a final update once we have confirmed full recovery
-
resolved Jun 04, 2026, 08:59 PM UTC
This 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 levels since. We apologize for the impact to your sites and visitors.
Read the full incident report →
- Detected by Pingoru
- May 29, 2026, 03:30 PM UTC
- Resolved
- May 29, 2026, 03:30 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Jun 02, 2026, 06:15 PM UTC
Between 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. Our team has deployed a fix and the errors have subsided.
Read the full incident report →
- Detected by Pingoru
- May 27, 2026, 12:13 PM UTC
- Resolved
- May 27, 2026, 02:17 PM UTC
- Duration
- 2h 4m
Affected: Build Pipeline
Timeline · 3 updates
-
investigating May 27, 2026, 12:13 PM UTC
We are currently experiencing delays in our build pipeline due to a current incident at Github.
-
identified May 27, 2026, 12:58 PM UTC
In addition to delayed builds, we are also experiencing build failures due to the current incident at Github.
-
resolved May 27, 2026, 02:17 PM UTC
This incident has been resolved, and builds have returned to functioning normally.
Read the full incident report →
- Detected by Pingoru
- May 26, 2026, 01:14 PM UTC
- Resolved
- May 26, 2026, 01:44 PM UTC
- Duration
- 30m
Affected: Netlify Image CDN
Timeline · 3 updates
-
investigating May 26, 2026, 01:14 PM UTC
We are continuing to investigate issues affecting image delivery. Some customers may continue to see slow or failed image requests. We are working to identify the cause and will share more information when available.
-
monitoring May 26, 2026, 01:23 PM UTC
We have implemented a fix and are monitoring results. Some customers may have experienced slow or failed image requests. We will continue to monitor image delivery and provide an update once the issue is fully resolved.
-
resolved May 26, 2026, 01:44 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 25, 2026, 03:31 PM UTC
- Resolved
- May 25, 2026, 05:32 PM UTC
- Duration
- 2h
Affected: Netlify Helpdesk
Timeline · 3 updates
-
identified May 25, 2026, 03:31 PM UTC
We are currently investigating an issue affecting outbound email delivery for some Netlify services, including support-related communications. Our team is working with our email provider to restore service as quickly as possible
-
monitoring May 25, 2026, 03:53 PM UTC
outbound email delivery has been restored and emails are now processing successfully. Some delays may continue while queued messages are delivered. We are continuing to monitor the recovery closely
-
resolved May 25, 2026, 05:32 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 23, 2026, 02:52 PM UTC
- Resolved
- May 23, 2026, 07:40 PM UTC
- Duration
- 4h 47m
Affected: Build PipelineCollaborative Deploy Previews
Timeline · 2 updates
-
investigating May 23, 2026, 02:52 PM UTC
We are currently experiencing an increased level of build failures related to downstream issues with GitHub beginning at 06:00 UTC. Any impacted users can attempt to retry their deploys as a workaround while we continue to investigate this issue.
-
resolved May 23, 2026, 07:40 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 19, 2026, 09:08 PM UTC
- Resolved
- May 19, 2026, 11:04 PM UTC
- Duration
- 1h 55m
Affected: Build PipelineNetlify Application UINetlify Functions
Timeline · 6 updates
-
investigating May 19, 2026, 09:08 PM UTC
We are investigating elevated latency and errors affecting origin services. This is currently impacting request performance and may result in degraded experience or failures for some users.
-
investigating May 19, 2026, 09:33 PM UTC
We are continuing to investigate an ongoing incident causing elevated latency, errors, and intermittent failures across multiple Netlify services. In addition to earlier impact, we are now observing issues with the build pipeline where new builds are not starting for some customers. This may result in delayed or failed deploys, in addition to degraded site performance and intermittent timeouts.
-
investigating May 19, 2026, 09:45 PM UTC
We are continuing to investigate this issue.
-
investigating May 19, 2026, 09:52 PM UTC
We are continuing to investigate an ongoing incident causing elevated latency, errors, and intermittent failures across multiple Netlify services. Impact remains broad and includes intermittent site availability issues where some customer sites may be unavailable or returning errors, as well as disruptions to the build pipeline where builds may fail to start or be delayed
-
monitoring May 19, 2026, 10:14 PM UTC
We have implemented mitigation steps for the issue that was causing elevated errors, increased latency, and intermittent site availability issues across Netlify services. Service health has significantly improved, and core functionality such as site loading and build processing is operating normally for most customers. However, we are continuing to monitor closely to ensure full stability and to catch any residual impact
-
resolved May 19, 2026, 11:04 PM UTC
This 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 the build pipeline, are now operating normally. We monitored system stability following recovery and are no longer observing elevated error rates or degraded performance
Read the full incident report →
- Detected by Pingoru
- May 19, 2026, 06:18 PM UTC
- Resolved
- May 19, 2026, 08:41 PM UTC
- Duration
- 2h 22m
Affected: Netlify Create API
Timeline · 3 updates
-
investigating May 19, 2026, 06:18 PM UTC
Investigating: We’re seeing degraded performance with create.netlify.com. Some customers are seeing issues with latency or 500 errors while accessing the create.netlify.com
-
monitoring May 19, 2026, 08:23 PM UTC
We have resolved the issue causing elevated error rates in the Create API. Systems are now recovering, and we are monitoring closely.
-
resolved May 19, 2026, 08:41 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 19, 2026, 05:30 PM UTC
- Resolved
- May 19, 2026, 05:30 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved May 19, 2026, 07:44 PM UTC
Between 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 recovering and we're continuing to investigate the root cause
Read the full incident report →
