Hosting / Frontend cloud / Netlify

Netlify

DEGRADED

Since Apr 2026 · 51 incidents · www.netlifystatus.com · checked just now

CompareStatus page
GradeBLast 90 days
BPRODASHIP

Overview

30d90d1y
Admitted uptimeTime not covered by a Sev 1 the provider posted itself. A best case.
100.000%Grade B
IncidentsEverything posted on the status page except scheduled maintenance.
170 Sev 1
Sev 1 downtimeTotal minutes of Sev 1 incidents, as posted.
0m
Median fixMedian time to resolve. Half of incidents were fixed faster.
34m
LongestLongest single incident, start to resolved.
3h 57m
Since lastTime since the last counted incident was resolved.
ongoing

By area

BProduction
12INCIDENTS
5h 24mAFFECTED
Your users are hit: apps, APIs, databases, inference
Worst, 90d
SEV 2Sep 21, 2026 · 1h 25mErrors accessing Netlify-hosted sites
SEV 2Aug 31, 2026 · 1h 20mIncreased Latency in IAD Region on Global Network
SEV 2Sep 16, 2026 · 51mElevated Image CDN Errors
Most hit
High-Performance Edge Network7
Standard Edge Network4
Edge Functions3
Netlify Image CDN2
Worse. 27 in the last 6 months, 6 in the 6 before.
AShipping
8INCIDENTS
12h 03mAFFECTED
You can't deploy, build or manage: CI, CLI, dashboard, auth, billing
Worst, 90d
SEV 2Oct 20, 2026 · 1h 09mAgent Runner failures
SEV 2Aug 3, 2026 · 25mElevated Build Errors
SEV 3Oct 22, 2026 · 3h 57mDelays in build logs appearing in the UI
Most hit
Build Pipeline4
High-Performance Edge Network2
Standard Edge Network2
Edge Function Logs1
Worse. 19 in the last 6 months, 1 in the 6 before.
CleanSev 3–4Sev 1–2No data

What it costs

One small production web app, per month512 MB app on all month, 1M requests, 100 GB out, commercial use, one seat. Cheapest plan that runs it.
Pro5 of 8 cheaper · Heroku: cheaper, better grade
~$20/mo
Pro plan (3,000 credits)$20

100 GB is 2,000 credits and 1M requests 200, so it outgrows Personal's 1,000 credits but fits Pro. Serverless, so memory isn't reserved. www.netlify.com · checked Oct 22, 2026 · Wrong price?

Trend, last 12 months

Worse. 44 in the last 6 months, 7 in the 6 before.

Severity mix

Sev 1 · Lights outProd site, API or database down, or data loss0
Sev 2 · BleedingProd degraded or partly down13
Sev 3 · Can't shipCan't deploy, build or manage it2
Sev 4 · PapercutDocs, status page, slow dashboard2

When it breaks

Start times, last 12 months, UTC.

What breaks

Standard Edge Network13 incidents
Build Pipeline12 incidents
High-Performance Edge Network12 incidents
Agent Runners8 incidents
Netlify Image CDN6 incidents
Edge Functions5 incidents

Communication

Updates eachStatus page updates per incident, on average.
2.9Last 12 months
Update gapMedian time between status page updates during an incident.
25mLast 12 months
PostmortemsSev 1–2 incidents with a published write-up.
0 of 34Sev 1–2

Incident history

Oct 22, 2026ongoingSEV 4
Delayed Edge Functions and Functions logsFunction and Edge Function logs from 13:58–15:35 UTC appeared late in the UI and log drains; requests were not affected.AI-graded · Edge Function Logs +1
Why this grade
  1. RULES · SEV 3
    Sev 3 because Edge Function Logs had degraded performance
  2. CLAUDE · SEV 4 · UNCLEAR · HIGH CONFIDENCE
    Function and Edge Function logs from 13:58–15:35 UTC appeared late in the UI and log drains; requests were not affected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
1 update
  1. 16:19 UTC · monitoring
    Edge Functions and Function logs from the period between 13:58–15:35 UTC may be delayed in appearing in the Netlify UI and in log drains. We are working to process the backlog; function and edge function requests are not affected.
Source
Oct 22, 20263h 57mSEV 3
Delays in build logs appearing in the UIBuild logs in the Netlify UI were delayed for roughly 27 hours after an upstream provider's issue backed up log ingestion. The upstream provider applied a fix on October 22 at 3:30 UTC, and Netlify then processed the backlog, finishing at 09:35 UTC before resolving the incident at 10:12 UTC. Real-time logs worked during backlog processing, but historical logs were intermittently missing.AI-graded · Build Pipeline +1
Why this grade
  1. RULES · SEV 3
    Sev 3 because Build Pipeline had degraded performance
  2. CLAUDE · SEV 3 · GLOBAL · HIGH CONFIDENCE
    Build logs appeared in the Netlify UI with hours of delay for about 27 hours; builds themselves and live sites were not described as affected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
14 updates
  1. 11:46 UTC · investigating
    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. 12:24 UTC · investigating
    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. 14:20 UTC · investigating
    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. 14:55 UTC · investigating
    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. 15:33 UTC · investigating
    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 information becomes available.
  6. 17:10 UTC · investigating
    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.
  7. 18:31 UTC · identified
    We've identified the cause of the delays in build logs appearing in the Netlify UI as an issue with an upstream service provider, who is working on a fix
  8. 19:42 UTC · identified
    We continue to work with our upstream service provider on the delays in build logs appearing in the Netlify UI.
  9. 05:42 UTC · monitoring
    The upstream provider applied a fix at 3:30 UTC and we are monitoring system health. We are able to ingest build logs at full throughput but we have hours of backlog that we need to process.
  10. 06:15 UTC · monitoring
    We are still monitoring the build log ingestion backlog. We will post our next update at 7:30 UTC, or sooner if anything changes.
  11. 07:41 UTC · monitoring
    Build log processing continues at full throttle and we estimate backlog to be cleared by 9:00 UTC. We’ll post next update at 8:45 UTC.
  12. 08:59 UTC · monitoring
    As of 08:45 UTC, we are still processing the backlog of build logs at full throttle. Some partitions have completed backlog processing, but others still have backlog pending. As a result of this partial processing, customers may experience intermittent availability until the full backlog is processed. Some build logs may be available, and others not. Real-time build logs should be working as expected. The new ETA for backlog processing is 10:00 UTC. We will provide our next update at 10:00 UTC.
  13. 09:35 UTC · monitoring
    We have completed processing the Build Logs backlog. All customers should now have a consistent experience when viewing both historical and new Build Logs in the UI. We believe customer impact has ended. We will continue to closely monitor the situation for any signs of recurrence.
  14. 10:12 UTC · resolved
    The issue causing delays in build logs appearing in the Netlify UI has been resolved.
Source
Oct 20, 20261h 09mSEV 2
Agent Runner failuresNetlify Agent Runner failures rose for about 70 minutes; the text does not say how many runs or customers were hit.AI-graded · Agent Runners
Why this grade
  1. RULES · SEV 1
    Sev 1 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · UNCLEAR · MEDIUM CONFIDENCE
    Netlify Agent Runner failures rose for about 70 minutes; the text does not say how many runs or customers were hit.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
3 updates
  1. 07:47 UTC · investigating
    We are investigating increased Agent Runner failures. We will share updates as we learn more.
  2. 08:04 UTC · monitoring
    We are monitoring the incident.
  3. 08:55 UTC · resolved
    This incident has been resolved.
Source
Oct 17, 202652mSEV 3
Elevated Build ErrorsBuilds using the CSP extension saw increased errors for about 50 minutes; other builds were not described as affected.AI-graded · some customers · Build Pipeline
Why this grade
  1. RULES · SEV 3
    Sev 3 because Build Pipeline had degraded performance
  2. CLAUDE · SEV 3 · SUBSET · MEDIUM CONFIDENCE
    Builds using the CSP extension saw increased errors for about 50 minutes; other builds were not described as affected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
3 updates
  1. 05:03 UTC · identified
    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. 05:30 UTC · monitoring
    We've released a fix to resolve the errors for builds using the CSP extension, and we are monitoring the results.
  3. 05:55 UTC · resolved
    This incident has been resolved.
Source
Oct 8, 20260mSEV 2
Elevated Edge Function ErrorsSome requests to Edge Functions sites saw higher latency and 502 errors for about eight minutes; scope was not stated.AI-graded · Edge Functions
Why this grade
  1. RULES · SEV 2
    Sev 2 because Edge Functions had degraded performance
  2. CLAUDE · SEV 2 · UNCLEAR · MEDIUM CONFIDENCE
    Some requests to Edge Functions sites saw higher latency and 502 errors for about eight minutes; scope was not stated.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
1 update
  1. 14:34 UTC · resolved
    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.
Source
Oct 6, 20260mSEV 2
Elevated error rates for AI GatewaySome AI Gateway requests returned errors for about 13 minutes until capacity was increased; the scope across customers is not stated.AI-graded · Agent Runners +1
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · UNCLEAR · MEDIUM CONFIDENCE
    Some AI Gateway requests returned errors for about 13 minutes until capacity was increased; the scope across customers is not stated.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
1 update
  1. 20:12 UTC · resolved
    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.
Source
Oct 5, 202650mSEV 2
Error accessing Netlify-hosted sitesNetlify reported errors accessing sites on its High-Performance Edge Network. The issue was identified, a fix was implemented, and sites returned to normal operation after about 50 minutes. The update text gives conflicting start and restore times (12:19 and 13:14 UTC in the closing note versus 12:44 and 13:34 in the timeline), and the scope is not stated.AI-graded · High-Performance Edge Network
Why this grade
  1. RULES · SEV 2
    Sev 2 because High-Performance Edge Network had degraded performance
  2. CLAUDE · SEV 2 · UNCLEAR · MEDIUM CONFIDENCE
    Errors accessing sites on Netlify's Edge Network for about 50 minutes; the text does not say how many sites or regions were hit.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
5 updates
  1. 12:44 UTC · investigating
    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. 13:00 UTC · investigating
    We are continuing to investigate this issue.
  3. 13:17 UTC · identified
    The issue has been identified and a fix is being implemented.
  4. 13:24 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  5. 13:34 UTC · resolved
    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.
Source
Sep 29, 20260mSEV 4
Error accessing Netlify-hosted sitesNetlify-hosted sites on the High-Performance Edge saw elevated errors; the update gives no duration, scope, or cause.AI-graded · High-Performance Edge Network
Why this grade
  1. RULES · SEV 2
    Sev 2 because High-Performance Edge Network had degraded performance
  2. CLAUDE · SEV 4 · UNCLEAR · LOW CONFIDENCE
    Netlify-hosted sites on the High-Performance Edge saw elevated errors; the update gives no duration, scope, or cause.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
1 update
  1. 08:46 UTC · resolved
    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.
Source
Sep 24, 202624mSEV 2
Error accessing Netlify-hosted sitesErrors accessing Netlify-hosted sites via the edge network and functions for about 25 minutes; widespread but scope not stated.AI-graded · High-Performance Edge Network +2
Why this grade
  1. RULES · SEV 1
    Sev 1 because High-Performance Edge Network had a partial outage
  2. CLAUDE · SEV 2 · UNCLEAR · MEDIUM CONFIDENCE
    Errors accessing Netlify-hosted sites via the edge network and functions for about 25 minutes; widespread but scope not stated.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
3 updates
  1. 19:01 UTC · investigating
    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. 19:10 UTC · monitoring
    We are seeing signs of recovery, and service has returned to normal operation.
  3. 19:25 UTC · resolved
    This incident has been resolved. Service has returned to normal operation, and we are no longer seeing elevated error rates.
Source
Sep 23, 202634mSEV 2
Elevated CDN ErrorsNetlify's edge network had a DNS resolution problem that stopped it reaching some origin servers, so requests to affected sites could fail. Netlify applied mitigations and later reported DNS recovered and services operating normally, about 34 minutes after start. Build Pipeline was listed as affected but the text does not describe its impact.AI-graded · High-Performance Edge Network +2
Why this grade
  1. RULES · SEV 2
    Sev 2 because High-Performance Edge Network had degraded performance
  2. CLAUDE · SEV 2 · UNCLEAR · MEDIUM CONFIDENCE
    Edge network DNS resolution issue made some requests to customer sites fail for about 34 minutes; scope across regions not stated.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
4 updates
  1. 23:26 UTC · identified
    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. 23:40 UTC · identified
    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. 23:50 UTC · monitoring
    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. 00:00 UTC · resolved
    The issue causing elevated CDN errors has been resolved. DNS resolution has recovered, and affected services are operating normally.
Source
Sep 21, 20261h 25mSEV 2
Errors accessing Netlify-hosted sitesNetlify reported errors accessing hosted sites via its edge networks from about 15:12 to 16:37 UTC on 21 September 2026. Customers may also have had trouble using the Netlify application. A fix was implemented around 15:52 UTC and monitored until resolution. The provider did not describe the cause or the breadth of impact.AI-graded · High-Performance Edge Network +1
Why this grade
  1. RULES · SEV 1
    Sev 1 because High-Performance Edge Network had a partial outage
  2. CLAUDE · SEV 2 · UNCLEAR · MEDIUM CONFIDENCE
    Errors accessing Netlify-hosted sites through the edge network for about 80 minutes; extent across customers not stated.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
5 updates
  1. 15:12 UTC · investigating
    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. 15:30 UTC · investigating
    We are continuing to investigate this issue. Customers may also experience issues accessing the Netlify application and its features.
  3. 15:45 UTC · identified
    We have identified the issue and are working to restore normal service. We will provide another update as more information becomes available.
  4. 15:52 UTC · monitoring
    A fix has been implemented and we are monitoring the results. We will provide another update as we continue to monitor recovery.
  5. 16:37 UTC · resolved
    This incident has been resolved.
Source
Sep 16, 202651mSEV 2
Elevated Image CDN ErrorsNetlify Image CDN returned elevated errors for about 70 minutes; scope across customers and regions was not stated.AI-graded · High-Performance Edge Network +2
Why this grade
  1. RULES · SEV 2
    Sev 2 because High-Performance Edge Network had degraded performance
  2. CLAUDE · SEV 2 · UNCLEAR · MEDIUM CONFIDENCE
    Netlify Image CDN returned elevated errors for about 70 minutes; scope across customers and regions was not stated.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
3 updates
  1. 12:58 UTC · investigating
    We are experiencing elevated errors within our Image CDN service starting at 12:37 UTC. We are currently investigating this issue.
  2. 13:19 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  3. 13:48 UTC · resolved
    This incident has been resolved.
Source
Sep 8, 20260mSEV 2
Elevated Errors and Latency in IAD RegionSev 2 from the incident title (no components listed)
1 update
  1. 18:28 UTC · resolved
    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.
Source
Sep 4, 20260mSEV 2
Increased errors on High Performance Edge Network - FRA RegionSev 2 from the incident title (no components listed)
1 update
  1. 10:30 UTC · resolved
    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.
Source
Aug 31, 20261h 20mSEV 2
Increased Latency in IAD Region on Global NetworkIncreased CDN and edge latency in the IAD region for about 16 minutes; requests were slower but not failing.AI-graded · regional · High-Performance Edge Network +2
Why this grade
  1. RULES · SEV 2
    Sev 2 because High-Performance Edge Network had degraded performance
  2. CLAUDE · SEV 2 · REGIONAL · MEDIUM CONFIDENCE
    Increased CDN and edge latency in the IAD region for about 16 minutes; requests were slower but not failing.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
3 updates
  1. 20:40 UTC · investigating
    We're experiencing increased latency on a subset of CDN nodes in the IAD region. We are currently investigating this issue.
  2. 20:56 UTC · monitoring
    Request latency across the IAD region has returned to normal levels, and we are continuing to monitor the situation.
  3. 22:00 UTC · resolved
    This incident has been resolved.
Source
Aug 18, 20260mSEV 2
Elevated HTTP 500 errors serving sites and the Netlify UISome visitors to Netlify-hosted sites and some dashboard users got error pages for about six minutes; scope not stated.AI-graded
Why this grade
  1. RULES · SEV 1
    Sev 1 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · UNCLEAR · MEDIUM CONFIDENCE
    Some visitors to Netlify-hosted sites and some dashboard users got error pages for about six minutes; scope not stated.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
1 update
  1. 20:00 UTC · resolved
    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
Source
Aug 3, 202625mSEV 2
Elevated Build ErrorsNetlify builds showed elevated error rates starting around 08:58 UTC on 3 August 2026. Failed builds decreased from 09:32 UTC after a fix was implemented, and the incident was resolved about 09:56 UTC. The provider did not describe the cause or the share of builds affected.AI-graded · Build Pipeline
Why this grade
  1. RULES · SEV 3
    Sev 3 because Build Pipeline had a partial outage
  2. CLAUDE · SEV 2 · UNCLEAR · MEDIUM CONFIDENCE
    Netlify builds failed at elevated rates for about an hour; the text does not say how many customers were hit.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
4 updates
  1. 09:31 UTC · investigating
    We're currently investigating elevated build errors starting at 8:58 UTC.
  2. 09:44 UTC · investigating
    Since 9:32 UTC we're seeing a decrease in failed builds. The team will continue to monitor.
  3. 09:44 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  4. 09:55 UTC · resolved
    This incident has been resolved.
Source
Jul 22, 202628mSEV 4
Errors Uploading Attachments to Agent RunnersSome users hit errors uploading attachments to Agent Runners for about 27 minutes; the rest of Netlify was unaffected.AI-graded · some customers · Agent Runners
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 4 · SUBSET · MEDIUM CONFIDENCE
    Some users hit errors uploading attachments to Agent Runners for about 27 minutes; the rest of Netlify was unaffected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
2 updates
  1. 13:29 UTC · monitoring
    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. 13:56 UTC · resolved
    This incident has been resolved.
Source
Jul 1, 202625mSEV 2
Increase in Edge Function ErrorsEdge Function errors tied to module loading rose for about 25 minutes; the provider did not say how many requests or customers were hit.AI-graded · Edge Functions
Why this grade
  1. RULES · SEV 2
    Sev 2 because Edge Functions had degraded performance
  2. CLAUDE · SEV 2 · UNCLEAR · LOW CONFIDENCE
    Edge Function errors tied to module loading rose for about 25 minutes; the provider did not say how many requests or customers were hit.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
2 updates
  1. 17:53 UTC · monitoring
    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. 18:18 UTC · resolved
    This incident has been resolved.
Source
Jun 14, 20265h 49mSEV 2
Connectivity issues affecting Bolt-powered sitesBolt-powered sites saw errors and delays for about six hours; enabling and disabling sites was slow, and builds were affected.AI-graded · some customers · Standard Edge Network +1
Why this grade
  1. RULES · SEV 2
    Sev 2 because Standard Edge Network had degraded performance
  2. CLAUDE · SEV 2 · SUBSET · MEDIUM CONFIDENCE
    Bolt-powered sites saw errors and delays for about six hours; enabling and disabling sites was slow, and builds were affected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
3 updates
  1. 19:55 UTC · identified
    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. 20:23 UTC · identified
    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. 01:45 UTC · resolved
    This incident has been resolved.
Source
Jun 13, 20262d 1hSEV 2
AI Gateway: Claude Fable 5 unavailableRequests to one model, claude-fable-5, failed through Netlify AI Gateway for about two days because Anthropic suspended that model.AI-graded · some customers · AI Gateway
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · SUBSET · MEDIUM CONFIDENCE
    Requests to one model, claude-fable-5, failed through Netlify AI Gateway for about two days because Anthropic suspended that model.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
2 updates
  1. 08:25 UTC · monitoring
    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. 09:44 UTC · resolved
    This incident has been resolved.
Source
Jun 9, 202615mSEV 2
Elevated latency affecting image deliveryImage delivery through Netlify's edge network and Image CDN ran slowly with intermittent load errors for some sites, starting around 03:19 UTC on June 9, 2026. Error rates dropped after mitigation and the incident was resolved about 15 minutes later. The provider did not give a root cause in these updates.AI-graded · some customers · High-Performance Edge Network +2
Why this grade
  1. RULES · SEV 2
    Sev 2 because High-Performance Edge Network had degraded performance
  2. CLAUDE · SEV 2 · SUBSET · MEDIUM CONFIDENCE
    Image delivery for some Netlify-hosted sites saw elevated latency and intermittent errors for about 35 minutes before recovering.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
3 updates
  1. 03:41 UTC · investigating
    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
  2. 03:49 UTC · monitoring
    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.
  3. 03:55 UTC · resolved
    This incident has been resolved.
Source
Jun 4, 202635mSEV 1
Elevated error rates for a subset of sites using Edge FunctionsSev 1 because Edge Functions had a partial outageEdge Functions
4 updates
  1. 20:24 UTC · investigating
    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.
  2. 20:34 UTC · identified
    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.
  3. 20:42 UTC · monitoring
    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. 20:59 UTC · resolved
    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.
Source
Jun 2, 20260mSEV 2
Blobs issues in Sydney regionSev 2 from the incident title (no components listed)
1 update
  1. 15:30 UTC · resolved
    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.
Source
May 27, 20262h 04mSEV 3
Failed & delayed builds due to Github incidentSev 3 because Build Pipeline had a partial outageBuild Pipeline
3 updates
  1. 12:13 UTC · investigating
    We are currently experiencing delays in our build pipeline due to a current incident at Github.
  2. 12:58 UTC · identified
    In addition to delayed builds, we are also experiencing build failures due to the current incident at Github.
  3. 14:17 UTC · resolved
    This incident has been resolved, and builds have returned to functioning normally.
Source
May 26, 202630mSEV 2
Image Delivery IssuesSev 2 because Netlify Image CDN had degraded performanceNetlify Image CDN
3 updates
  1. 13:14 UTC · investigating
    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. 13:23 UTC · monitoring
    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. 13:44 UTC · resolved
    This incident has been resolved.
Source
May 25, 20262h 01mSEV 4
Support Communication Delivery IssuesSev 4 from the incident title (no components listed)Netlify Helpdesk
3 updates
  1. 15:31 UTC · identified
    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. 15:53 UTC · monitoring
    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. 17:32 UTC · resolved
    This incident has been resolved.
Source
May 23, 20264h 47mSEV 3
Elevated Build FailuresSev 3 because Build Pipeline had degraded performanceBuild Pipeline +1
2 updates
  1. 14:52 UTC · investigating
    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. 19:40 UTC · resolved
    This incident has been resolved.
Source
May 19, 20261h 56mSEV 1
Elevated response times affecting origin servicesSev 1 because Netlify Functions had a major outageBuild Pipeline +2
6 updates
  1. 21:08 UTC · investigating
    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. 21:33 UTC · investigating
    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.
  3. 21:45 UTC · investigating
    We are continuing to investigate this issue.
  4. 21:52 UTC · investigating
    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
  5. 22:14 UTC · monitoring
    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
  6. 23:04 UTC · resolved
    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
Source
May 19, 20260mSEV 3
Elevated Build and Functions Deployment ErrorsSev 3 from the incident title (no components listed)
1 update
  1. 17:30 UTC · resolved
    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
Source
May 19, 20262h 22mSEV 3
Degraded performance with Create APISev 3 because Netlify Create API had degraded performanceNetlify Create API
3 updates
  1. 18:18 UTC · investigating
    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. 20:23 UTC · monitoring
    We have resolved the issue causing elevated error rates in the Create API. Systems are now recovering, and we are monitoring closely.
  3. 20:41 UTC · resolved
    This incident has been resolved.
Source
May 19, 202625mSEV 3
Degraded performance with Create APISev 3 because Netlify Create API had degraded performanceNetlify Create API
4 updates
  1. 14:26 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. 14:31 UTC · identified
    The issue has been identified and a fix is being implemented.
  3. 14:37 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  4. 14:52 UTC · resolved
    The incident with performance degradation for create.netlify.com has be resolved.
Source
May 15, 20262h 36mSEV 2
Purges are Delayed on Primary Load BalancerSev 2 because Standard Edge Network had degraded performanceStandard Edge Network
3 updates
  1. 16:23 UTC · identified
    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. 17:44 UTC · monitoring
    A fix has been implemented, and we are monitoring the results.
  3. 18:58 UTC · resolved
    This incident has been resolved.
Source
May 12, 20261h 08mSEV 3
Increased Latency in API & BuildsSev 3 because Build Pipeline had degraded performanceBuild Pipeline +1
3 updates
  1. 14:30 UTC · investigating
    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. 15:20 UTC · monitoring
    We have implemented a fix and are monitoring system performance to ensure services continue to recover as expected.
  3. 15:38 UTC · resolved
    This incident has been resolved.
Source
May 11, 202656mSEV 3
Build Issues due to Github OutageSev 3 because Build Pipeline had degraded performanceBuild Pipeline
5 updates
  1. 14:31 UTC · investigating
    We are experiencing issues with our build pipeline due to degraded performance in Github
  2. 14:35 UTC · identified
    The issue has been identified and posted on Github's status page.
  3. 14:47 UTC · monitoring
    We are monitoring improvements.
  4. 15:20 UTC · monitoring
    We are continuing to monitor for any further issues.
  5. 15:27 UTC · resolved
    This incident has been resolved.
Source
May 11, 20261h 51mSEV 3
Latency in API & BuildsSev 3 because Build Pipeline had a partial outageBuild Pipeline +1
6 updates
  1. 13:36 UTC · investigating
    We are currently experiencing increased latency in our API and builds. We are investigating the source.
  2. 13:47 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  3. 14:10 UTC · identified
    We have identified other causes of this latency, and are continuing to work on resolutions.
  4. 14:47 UTC · monitoring
    We are monitoring the results of our fix.
  5. 15:19 UTC · monitoring
    We are continuing to monitor for any further issues.
  6. 15:27 UTC · resolved
    This incident has been resolved.
Source
May 10, 20260mSEV 2
Degraded Service in IAD RegionSev 2 because Standard Edge Network had degraded performanceStandard Edge Network
1 update
  1. 16:33 UTC · resolved
    Our network experienced degraded service in the IAD region between 12:53 UTC and 13:53 UTC. This issue is now resolved.
Source
May 10, 202649mSEV 2
Increase in DNS Resolution ErrorsSev 2 because Standard Edge Network had degraded performanceStandard Edge Network +1
4 updates
  1. 08:07 UTC · identified
    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. 08:32 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  3. 08:55 UTC · monitoring
    We are continuing to monitor for any further issues.
  4. 08:56 UTC · resolved
    This incident has been resolved.
Source
May 10, 20261h 06mSEV 2
Increase in Agent Runner ErrorsSev 2 from the incident title (no components listed)Agent Runners
2 updates
  1. 07:15 UTC · investigating
    We are seeing an increase in Agent Runner failures for both initial and follow-up prompts. We are currently investigating this issue.
  2. 08:21 UTC · resolved
    This incident has been resolved.
Source
May 9, 20260mSEV 4
Issues Processing Account ChangesSev 4 because Billing had degraded performanceDomain Purchasing +2
1 update
  1. 00:58 UTC · resolved
    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.
Source
May 8, 20261h 07mSEV 2
Elevated Errors in IAD regionSev 2 because High-Performance Edge Network had degraded performanceHigh-Performance Edge Network +1
2 updates
  1. 02:53 UTC · investigating
    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. 04:00 UTC · resolved
    This incident has been resolved.
Source
May 6, 20261h 20mSEV 2
Elevated Errors and LatencySev 2 because High-Performance Edge Network had degraded performanceHigh-Performance Edge Network +3
3 updates
  1. 15:29 UTC · investigating
    We're experiencing elevated errors and latency starting at 15:00 UTC. We are currently investigating this issue.
  2. 15:39 UTC · monitoring
    We've implemented a fix and have begun to see improvement starting at 15:15 UTC. We're continuing to monitor the results.
  3. 16:49 UTC · resolved
    This incident has been resolved.
Source
May 5, 20262h 19mSEV 1
Agent Runner failures on new projectsSev 1 from the incident title (no components listed)Agent Runners
3 updates
  1. 20:53 UTC · investigating
    We are investigating increased Agent Runner failures affecting builds for some newly created projects. We will share updates as we learn more.
  2. 21:58 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  3. 23:12 UTC · resolved
    This incident has been resolved.
Source
May 3, 20260mSEV 4
Delayed Credit Usage UpdatesSev 4 from the incident title (no components listed)
1 update
  1. 00:00 UTC · resolved
    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.
Source
Apr 26, 20260mSEV 2
Increased errors on Image CDNSev 2 from the incident title (no components listed)
1 update
  1. 03:55 UTC · resolved
    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.
Source
Apr 24, 202647mSEV 2
Increased Errors on Image CDNSev 2 because High-Performance Edge Network had degraded performanceHigh-Performance Edge Network +2
3 updates
  1. 14:10 UTC · investigating
    We are currently experiencing an elevated error rate for Image CDN requests, starting at 13:35 UTC. We are investigating this issue.
  2. 14:44 UTC · monitoring
    We've confirmed that Image CDN errors have decreased, and we are continuing to monitor this issue.
  3. 14:57 UTC · resolved
    This incident has been resolved.
Source
Apr 23, 20261h 00mSEV 3
Elevated Rate of Build FailuresSev 3 because Build Pipeline had degraded performanceBuild Pipeline +2
3 updates
  1. 16:23 UTC · investigating
    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. 17:13 UTC · monitoring
    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. 17:23 UTC · resolved
    This incident has been resolved.
Source
Apr 13, 202638mSEV 1
Scheduled Functions Auto-Triggering Not ExecutingSev 1 because Netlify Functions had a partial outageNetlify Functions
3 updates
  1. 00:39 UTC · investigating
    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. 01:04 UTC · monitoring
    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. 01:16 UTC · resolved
    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.
Source
Apr 9, 20260mSEV 2
Issues with credit purchases and auto top-upsSev 2 from the incident title (no components listed)
1 update
  1. 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.
Source
Apr 6, 20260mSEV 2
Agent Runners OutageSev 2 from the incident title (no components listed)
1 update
  1. 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.
Source
Apr 2, 20265h 33mSEV 2
Increased errors on the CDNSev 2 because High-Performance Edge Network had degraded performanceHigh-Performance Edge Network +1
5 updates
  1. 12:26 UTC · investigating
    We're currently experiencing some errors on the Standard Edge Network. High Performance Edge Network should be unaffected.
  2. 14:19 UTC · investigating
    We're also experiencing errors on the High Performance Edge Network. We're investigating the issue.
  3. 14:19 UTC · investigating
    We are continuing to investigate this issue.
  4. 15:34 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  5. 17:59 UTC · resolved
    This incident has been resolved.
Source

Peers, 90 days

Compare
HerokuGrade A+100.00% up0 incidentsMTTR –$7/moNetlifyGrade B100.00% up17 incidentsMTTR 34m~$20/moRenderGrade C100.00% up13 incidentsMTTR 1h 35m$21.25/moVercelGrade C100.00% up23 incidentsMTTR 47m~$20/moDigitalOceanGrade F100.00% up18 incidentsMTTR 4h 02m$6/moFly.ioGrade F99.38% up26 incidentsMTTR 44m$5.69/moCloudflareGrade F100.00% up54 incidentsMTTR 1h 13m~$5/moRailwayGrade F98.31% up27 incidentsMTTR 55m~$12/mo

README badge

Netlify's live grade, for your README.

Netlify grade badge
[![netlify on downagain.dev](https://downagain.dev/badge/netlify.svg)](https://downagain.dev/p/netlify)