Netlify

Affected: Build Pipeline, Netlify Application UI

1. investigating 2026-10-21 11:46 UTC

   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.

2. investigating 2026-10-21 12:24 UTC

   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.

3. investigating 2026-10-21 14:20 UTC

   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.

4. investigating 2026-10-21 14:55 UTC

   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.

5. investigating 2026-10-21 15:33 UTC

   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...

6. investigating 2026-10-21 17:10 UTC

   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.

Excerpts are shortened. Read the full incident on Netlify's status page.

Affected: Agent Runners

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-20 07:47 UTC

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

2. monitoring 2026-10-20 08:04 UTC

   We are monitoring the incident.

3. resolved 2026-10-20 08:55 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Netlify's status page.

Affected: Build Pipeline

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-10-17 05:03 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.

2. monitoring 2026-10-17 05:30 UTC

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

3. resolved 2026-10-17 05:55 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Netlify's status page.

Affected: Edge Functions

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-10-08 14:34 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.

Excerpts are shortened. Read the full incident on Netlify's status page.

Affected: Agent Runners, AI Gateway

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-10-06 20:12 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.

Excerpts are shortened. Read the full incident on Netlify's status page.

Affected: High-Performance Edge Network

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-05 12:44 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.

2. investigating 2026-10-05 13:00 UTC

   We are continuing to investigate this issue.

3. identified 2026-10-05 13:17 UTC

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

4. monitoring 2026-10-05 13:24 UTC

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

5. resolved 2026-10-05 13:34 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.

Excerpts are shortened. Read the full incident on Netlify's status page.

Affected: High-Performance Edge Network

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-09-29 08:46 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.

Excerpts are shortened. Read the full incident on Netlify's status page.

Affected: High-Performance Edge Network, Standard Edge Network, Edge Functions

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-24 19:01 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.

2. monitoring 2026-09-24 19:10 UTC

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

3. resolved 2026-09-24 19:25 UTC

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

Excerpts are shortened. Read the full incident on Netlify's status page.

Affected: High-Performance Edge Network, Standard Edge Network, Build Pipeline

Failure mode: Network, DNS, routing or connectivity failure. Root cause: Network or DNS. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-09-23 23:26 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.

2. identified 2026-09-23 23:40 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.

3. monitoring 2026-09-23 23:50 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.

4. resolved 2026-09-24 00:00 UTC

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

Excerpts are shortened. Read the full incident on Netlify's status page.

Affected: High-Performance Edge Network, Standard Edge Network

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-21 15:12 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.

2. investigating 2026-09-21 15:30 UTC

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

3. identified 2026-09-21 15:45 UTC

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

4. monitoring 2026-09-21 15:52 UTC

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

5. resolved 2026-09-21 16:37 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Netlify's status page.

Affected: High-Performance Edge Network, Standard Edge Network, Netlify Image CDN

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-09-16 12:58 UTC

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

2. monitoring 2026-09-16 13:19 UTC

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

3. resolved 2026-09-16 13:48 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Netlify's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: Network or DNS. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-09-08 18:28 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.

Excerpts are shortened. Read the full incident on Netlify's status page.

Failure mode: Traffic surge or denial-of-service attack. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-09-04 10:30 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.

Excerpts are shortened. Read the full incident on Netlify's status page.

Affected: High-Performance Edge Network, Edge Functions, Netlify Image CDN

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-31 20:40 UTC

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

2. monitoring 2026-08-31 20:56 UTC

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

3. resolved 2026-08-31 22:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Netlify's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-08-18 20:00 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

Excerpts are shortened. Read the full incident on Netlify's status page.

Affected: Build Pipeline

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-03 09:31 UTC

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

2. investigating 2026-08-03 09:44 UTC

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

3. monitoring 2026-08-03 09:44 UTC

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

4. resolved 2026-08-03 09:55 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Netlify's status page.

Affected: Agent Runners

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2026-07-22 13:29 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.

2. resolved 2026-07-22 13:56 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Netlify's status page.

Affected: Edge Functions

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-07-01 17:53 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.

2. resolved 2026-07-01 18:18 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Netlify's status page.

Affected: Standard Edge Network, Build Pipeline

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-06-14 19:55 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.

2. identified 2026-06-14 20:23 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

3. resolved 2026-06-15 01:45 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Netlify's status page.

Affected: AI Gateway

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Anthropic (Claude).

1. monitoring 2026-06-13 08:25 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

2. resolved 2026-06-15 09:44 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Netlify's status page.

Affected: High-Performance Edge Network, Standard Edge Network, Netlify Image CDN

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-09 03:41 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...

2. monitoring 2026-06-09 03:49 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...

3. resolved 2026-06-09 03:55 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Netlify's status page.

Affected: Edge Functions

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-04 20:24 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...

2. identified 2026-06-04 20:34 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...

3. monitoring 2026-06-04 20:42 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

4. resolved 2026-06-04 20:59 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...

Excerpts are shortened. Read the full incident on Netlify's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-05-29 15:30 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.

Excerpts are shortened. Read the full incident on Netlify's status page.

Affected: Build Pipeline

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-05-27 12:13 UTC

   We are currently experiencing delays in our build pipeline due to a current incident at Github.

2. identified 2026-05-27 12:58 UTC

   In addition to delayed builds, we are also experiencing build failures due to the current incident at Github.

3. resolved 2026-05-27 14:17 UTC

   This incident has been resolved, and builds have returned to functioning normally.

Excerpts are shortened. Read the full incident on Netlify's status page.

Affected: Netlify Image CDN

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-26 13:14 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.

2. monitoring 2026-05-26 13:23 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.

3. resolved 2026-05-26 13:44 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Netlify's status page.

Affected: Netlify Helpdesk

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-05-25 15:31 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

2. monitoring 2026-05-25 15:53 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

3. resolved 2026-05-25 17:32 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Netlify's status page.

Affected: Build Pipeline, Collaborative Deploy Previews

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

1. investigating 2026-05-23 14:52 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.

2. resolved 2026-05-23 19:40 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Netlify's status page.

Affected: Build Pipeline, Netlify Application UI, Netlify Functions

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-19 21:08 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.

2. investigating 2026-05-19 21:33 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...

3. investigating 2026-05-19 21:45 UTC

   We are continuing to investigate this issue.

4. investigating 2026-05-19 21:52 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...

5. monitoring 2026-05-19 22:14 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...

6. resolved 2026-05-19 23:04 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...

Excerpts are shortened. Read the full incident on Netlify's status page.

Affected: Netlify Create API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-19 18:18 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

2. monitoring 2026-05-19 20:23 UTC

   We have resolved the issue causing elevated error rates in the Create API. Systems are now recovering, and we are monitoring closely.

3. resolved 2026-05-19 20:41 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Netlify's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-05-19 17:30 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

Excerpts are shortened. Read the full incident on Netlify's status page.

Affected: Netlify Create API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-19 14:26 UTC

   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.

2. identified 2026-05-19 14:31 UTC

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

3. monitoring 2026-05-19 14:37 UTC

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

4. resolved 2026-05-19 14:52 UTC

   The incident with performance degradation for create.netlify.com has be resolved.

Excerpts are shortened. Read the full incident on Netlify's status page.

Affected: Standard Edge Network

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-05-15 16:23 UTC

   We are currently experiencing a delay in cache purges, and some sites on our Standard Edge Network may be serving stale content. The issue has been identified and a fix is being implemented.

2. monitoring 2026-05-15 17:44 UTC

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

3. resolved 2026-05-15 18:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Netlify's status page.

Affected: Build Pipeline, API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-12 14:30 UTC

   We are currently investigating increased latency affecting our API and build systems. Some users may experience slower-than-normal response times for API requests and builds while we work to identify the source of the issue.

2. monitoring 2026-05-12 15:20 UTC

   We have implemented a fix and are monitoring system performance to ensure services continue to recover as expected.

3. resolved 2026-05-12 15:38 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Netlify's status page.

Affected: Build Pipeline

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-05-11 14:31 UTC

   We are experiencing issues with our build pipeline due to degraded performance in Github

2. identified 2026-05-11 14:35 UTC

   The issue has been identified and posted on Github's status page.

3. monitoring 2026-05-11 14:47 UTC

   We are monitoring improvements.

4. monitoring 2026-05-11 15:20 UTC

   We are continuing to monitor for any further issues.

5. resolved 2026-05-11 15:27 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Netlify's status page.

Affected: Build Pipeline, API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-11 13:36 UTC

   We are currently experiencing increased latency in our API and builds. We are investigating the source.

2. monitoring 2026-05-11 13:47 UTC

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

3. identified 2026-05-11 14:10 UTC

   We have identified other causes of this latency, and are continuing to work on resolutions.

4. monitoring 2026-05-11 14:47 UTC

   We are monitoring the results of our fix.

5. monitoring 2026-05-11 15:19 UTC

   We are continuing to monitor for any further issues.

6. resolved 2026-05-11 15:27 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Netlify's status page.

Affected: Standard Edge Network

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-05-10 16:33 UTC

   Our network experienced degraded service in the IAD region between 12:53 UTC and 13:53 UTC. This issue is now resolved.

Excerpts are shortened. Read the full incident on Netlify's status page.

Affected: Standard Edge Network, Hosted DNS

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-05-10 08:07 UTC

   We're experiencing an increase in DNS resolution errors impacting domains on our Standard Edge Network. A fix has been deployed, and we're monitoring the results.

2. monitoring 2026-05-10 08:32 UTC

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

3. monitoring 2026-05-10 08:55 UTC

   We are continuing to monitor for any further issues.

4. resolved 2026-05-10 08:56 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Netlify's status page.

Affected: Agent Runners

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-10 07:15 UTC

   We are seeing an increase in Agent Runner failures for both initial and follow-up prompts. We are currently investigating this issue.

2. resolved 2026-05-10 08:21 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Netlify's status page.

Affected: Domain Purchasing, Billing, Agent Runners

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-05-09 00:58 UTC

   We 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 transactions. This issue is now resolved.

Excerpts are shortened. Read the full incident on Netlify's status page.

Affected: High-Performance Edge Network, Standard Edge Network

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-05-08 02:53 UTC

   We're seeing an increased level of errors in the IAD region starting around 02:10 UTC for both our Standard and HP Edge Networks due to an upstream issue at AWS: https://health.aws.amazon.com/health/status.

2. resolved 2026-05-08 04:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Netlify's status page.

Affected: High-Performance Edge Network, Standard Edge Network, Netlify Image CDN, Agent Runners

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-06 15:29 UTC

   We're experiencing elevated errors and latency starting at 15:00 UTC. We are currently investigating this issue.

2. monitoring 2026-05-06 15:39 UTC

   We've implemented a fix and have begun to see improvement starting at 15:15 UTC. We're continuing to monitor the results.

3. resolved 2026-05-06 16:49 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Netlify's status page.

Affected: Agent Runners

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-05 20:53 UTC

   We are investigating increased Agent Runner failures affecting builds for some newly created projects. We will share updates as we learn more.

2. monitoring 2026-05-05 21:58 UTC

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

3. resolved 2026-05-05 23:12 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Netlify's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-05-03 00:00 UTC

   Some 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.

Excerpts are shortened. Read the full incident on Netlify's status page.

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-04-26 03:55 UTC

   We 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.

Excerpts are shortened. Read the full incident on Netlify's status page.

Affected: High-Performance Edge Network, Standard Edge Network, Netlify Image CDN

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-24 14:10 UTC

   We are currently experiencing an elevated error rate for Image CDN requests, starting at 13:35 UTC. We are investigating this issue.

2. monitoring 2026-04-24 14:44 UTC

   We've confirmed that Image CDN errors have decreased, and we are continuing to monitor this issue.

3. resolved 2026-04-24 14:57 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Netlify's status page.

Affected: Build Pipeline, Collaborative Deploy Previews, Agent Runners

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

1. investigating 2026-04-23 16:23 UTC

   We're experiencing an increased rate of build failures beginning around 16:00 UTC, caused by a GitHub issue: https://www.githubstatus.com/incidents/myrbk7jvvs6p. We're currently investigating this issue.

2. monitoring 2026-04-23 17:13 UTC

   We've confirmed a decrease in the rate of build failures, which coincides with GitHub's restoration of impacted services. We are continuing to monitor this issue.

3. resolved 2026-04-23 17:23 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Netlify's status page.

Affected: Netlify Functions

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-13 00:39 UTC

   Investigating an issue affecting Scheduled Functions auto-triggering. Manual “Run now” executions are succeeding, but some scheduled functions are not automatically invoking at their expected times.Beginning around April 12, 2026 at 1:00 AM UTC and are actively investigating.

2. monitoring 2026-04-13 01:04 UTC

   We implemented a fix for the issue affecting Scheduled Functions auto-triggering and are seeing signs of recovery. Manual executions were unaffected during the incident, and scheduled invocations now appear to be resuming. We are continuing to monitor closely

3. resolved 2026-04-13 01:16 UTC

   This 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 some scheduled runs did not trigger automatically as expected.

Excerpts are shortened. Read the full incident on Netlify's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-04-09 18:00 UTC

   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.

Excerpts are shortened. Read the full incident on Netlify's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2026-04-06 09:30 UTC

   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.

Excerpts are shortened. Read the full incident on Netlify's status page.

Affected: High-Performance Edge Network, Standard Edge Network

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-04-02 12:26 UTC

   We're currently experiencing some errors on the Standard Edge Network. High Performance Edge Network should be unaffected.

2. investigating 2026-04-02 14:19 UTC

   We're also experiencing errors on the High Performance Edge Network. We're investigating the issue.

3. investigating 2026-04-02 14:19 UTC

   We are continuing to investigate this issue.

4. monitoring 2026-04-02 15:34 UTC

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

5. resolved 2026-04-02 17:59 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Netlify's status page.