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.
171 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 1Aug 18, 2026 · 0mElevated HTTP 500 errors serving sites and the Netlify UI
SEV 2Sep 21, 2026 · 1h 25mErrors accessing Netlify-hosted sites
SEV 2Aug 31, 2026 · 1h 20mIncreased Latency in IAD Region on Global Network
Most hit
High-Performance Edge Network7
Standard Edge Network4
Edge Functions3
Netlify Image CDN2
Worse. 28 in the last 6 months, 6 in the 6 before.
AShipping
7INCIDENTS
11h 23mAFFECTED
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. 17 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 loss1
Sev 2 · BleedingProd degraded or partly down13
Sev 3 · Can't shipCan't deploy, build or manage it2
Sev 4 · PapercutDocs, status page, slow dashboard1

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 36Sev 1–2

Incident history

Show all 51
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 ErrorsSev 2 because Edge Functions had degraded performanceEdge Functions
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 GatewaySev 2 from the incident title (no components listed)Agent Runners +1
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 2
Error accessing Netlify-hosted sitesSev 2 because High-Performance Edge Network had degraded performanceHigh-Performance Edge Network
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 1
Elevated HTTP 500 errors serving sites and the Netlify UISev 1 from the incident title (no components listed)
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 2
Errors Uploading Attachments to Agent RunnersSev 2 from the incident title (no components listed)Agent Runners
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 ErrorsSev 2 because Edge Functions had degraded performanceEdge Functions
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 sitesSev 2 because Standard Edge Network had degraded performanceStandard Edge Network +1
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

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% up25 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)