iszdown
Menu
Service status & outage reports

Is Netlify down?

Check Netlify availability, incident history, downtime reports, and website performance.

https://www.netlify.com/ ↗
Provider reports service problems

The official provider feed identifies an active incident or affected component.

0 recorded outage reports · rolling 24 hours

Estimated activity checked · Text version ↗

My watchlist

Estimated down reports for Netlify

Last 24 hours

Current estimates unavailable. The last successful observation is more than two hours old or has insufficient samples. Older estimates are excluded from this chart. Official status and website checks below update independently.

Not enough activity data is available for this service yet.

Last successful 24-hour estimate: 2026-10-21 04:57:01 UTC.

Last collection attempt: 2026-10-21 04:57:01 UTC · Collected successfully.

No user-submitted outage reports in the last 24 hours.

Netlify outage history

2025–2026

Daily history over the past 12 months. Select a day for its evidence.

NovDecJanFebMarAprMayJunJulAugSepOct
GoodDown / service issuesNot enough data

Select a square for daily details. Scroll sideways to explore earlier months.

How to read this calendar

Dates use New York time (America/New_York). Green means no issues observed with sufficient monitoring coverage; it does not guarantee uninterrupted uptime. Pink includes official incidents, repeated website failures, or corroborated user reports. Gray days are unknown. Activity estimates alone do not turn a day pink. Today’s result can change.

Netlify website uptime and response time

Website responded successfully HTTP 200. Last checked 2026-10-22 00:09:51 UTC.

Checked address: https://www.netlify.com/

DNS lookup: 3 ms · TCP connection: 2 ms · TLS handshake: 2 ms. Certificate expires 2027-02-05; trusted connection: yes.

100%
Successful website checks (24h)
136 successful / 136 measurable checks

28 ms
Median response time

48 ms
95th percentile response time

Successful website response times, 0 to 366 milliseconds366 ms0 ms2026-10-21T12:36:33.000Z: 17 ms2026-10-21T12:41:43.000Z: 24 ms2026-10-21T12:46:51.000Z: 36 ms2026-10-21T12:52:01.000Z: 39 ms2026-10-21T12:57:09.000Z: 32 ms2026-10-21T13:02:16.000Z: 24 ms2026-10-21T13:07:25.000Z: 20 ms2026-10-21T13:12:35.000Z: 37 ms2026-10-21T13:17:45.000Z: 19 ms2026-10-21T13:22:55.000Z: 19 ms2026-10-21T13:28:01.000Z: 366 ms2026-10-21T13:33:07.000Z: 43 ms2026-10-21T13:38:13.000Z: 21 ms2026-10-21T13:43:21.000Z: 39 ms2026-10-21T13:48:30.000Z: 40 ms2026-10-21T13:53:39.000Z: 17 ms2026-10-21T13:58:49.000Z: 19 ms2026-10-21T14:03:57.000Z: 51 ms2026-10-21T14:09:05.000Z: 17 ms2026-10-21T14:14:14.000Z: 39 ms2026-10-21T14:19:21.000Z: 18 ms2026-10-21T14:24:31.000Z: 33 ms2026-10-21T14:29:41.000Z: 23 ms2026-10-21T14:34:51.000Z: 40 ms2026-10-21T14:39:58.000Z: 23 ms2026-10-21T14:45:05.000Z: 18 ms2026-10-21T14:50:11.000Z: 37 ms2026-10-21T14:55:15.000Z: 33 ms2026-10-21T15:00:21.000Z: 18 ms2026-10-21T15:05:27.000Z: 17 ms2026-10-21T15:10:33.000Z: 20 ms2026-10-21T15:15:39.000Z: 19 ms2026-10-21T15:20:47.000Z: 17 ms2026-10-21T15:25:53.000Z: 35 ms2026-10-21T15:31:03.000Z: 22 ms2026-10-21T15:36:07.000Z: 35 ms2026-10-21T15:41:13.000Z: 32 ms2026-10-21T15:46:21.000Z: 48 ms2026-10-21T15:51:31.000Z: 41 ms2026-10-21T15:56:39.000Z: 45 ms2026-10-21T16:01:48.000Z: 19 ms2026-10-21T16:06:57.000Z: 17 ms2026-10-21T16:12:07.000Z: 18 ms2026-10-21T16:17:17.000Z: 38 ms2026-10-21T16:22:25.000Z: 15 ms2026-10-21T16:27:35.000Z: 16 ms2026-10-21T16:32:39.000Z: 20 ms2026-10-21T16:37:45.000Z: 19 ms2026-10-21T16:42:49.000Z: 34 ms2026-10-21T16:47:55.000Z: 20 ms2026-10-21T16:53:03.000Z: 43 ms2026-10-21T16:58:13.000Z: 32 ms2026-10-21T17:03:23.000Z: 17 ms2026-10-21T17:08:32.000Z: 114 ms2026-10-21T17:13:41.000Z: 17 ms2026-10-21T17:18:51.000Z: 20 ms2026-10-21T17:24:01.000Z: 32 ms2026-10-21T17:29:09.000Z: 39 ms2026-10-21T17:34:17.000Z: 41 ms2026-10-21T17:39:27.000Z: 40 ms2026-10-21T17:44:33.000Z: 23 ms2026-10-21T17:49:37.000Z: 26 ms2026-10-21T17:54:43.000Z: 38 ms2026-10-21T17:59:50.000Z: 40 ms2026-10-21T18:04:58.000Z: 37 ms2026-10-21T18:10:07.000Z: 20 ms2026-10-21T18:15:17.000Z: 22 ms2026-10-21T18:20:26.000Z: 21 ms2026-10-21T18:25:31.000Z: 20 ms2026-10-21T18:30:39.000Z: 67 ms2026-10-21T18:35:49.000Z: 21 ms2026-10-21T18:40:59.000Z: 17 ms2026-10-21T18:46:09.000Z: 40 ms2026-10-21T18:51:17.000Z: 29 ms2026-10-21T18:56:27.000Z: 41 ms2026-10-21T19:01:35.000Z: 28 ms2026-10-21T19:06:43.000Z: 30 ms2026-10-21T19:11:51.000Z: 46 ms2026-10-21T19:17:01.000Z: 22 ms2026-10-21T19:22:11.000Z: 42 ms2026-10-21T19:27:19.000Z: 33 ms2026-10-21T19:32:28.000Z: 45 ms2026-10-21T19:37:37.000Z: 18 ms2026-10-21T19:42:47.000Z: 41 ms2026-10-21T19:47:55.000Z: 22 ms2026-10-21T19:53:03.000Z: 27 ms2026-10-21T19:58:13.000Z: 19 ms2026-10-21T20:03:21.000Z: 34 ms2026-10-21T20:08:30.000Z: 48 ms2026-10-21T20:13:39.000Z: 31 ms2026-10-21T20:18:48.000Z: 25 ms2026-10-21T20:23:57.000Z: 29 ms2026-10-21T20:29:05.000Z: 22 ms2026-10-21T20:34:15.000Z: 18 ms2026-10-21T20:39:23.000Z: 28 ms2026-10-21T20:44:31.000Z: 38 ms2026-10-21T20:49:41.000Z: 25 ms2026-10-21T20:54:50.000Z: 36 ms2026-10-21T20:59:58.000Z: 18 ms2026-10-21T21:05:07.000Z: 20 ms2026-10-21T21:10:13.000Z: 17 ms2026-10-21T21:15:21.000Z: 20 ms2026-10-21T21:20:31.000Z: 41 ms2026-10-21T21:25:39.000Z: 23 ms2026-10-21T21:30:49.000Z: 20 ms2026-10-21T21:35:57.000Z: 47 ms2026-10-21T21:41:02.000Z: 42 ms2026-10-21T21:46:07.000Z: 41 ms2026-10-21T21:51:11.000Z: 37 ms2026-10-21T21:56:17.000Z: 26 ms2026-10-21T22:01:21.000Z: 50 ms2026-10-21T22:06:27.000Z: 23 ms2026-10-21T22:11:31.000Z: 20 ms2026-10-21T22:16:37.000Z: 19 ms2026-10-21T22:21:42.000Z: 17 ms2026-10-21T22:26:49.000Z: 18 ms2026-10-21T22:31:58.000Z: 20 ms2026-10-21T22:37:05.000Z: 27 ms2026-10-21T22:42:15.000Z: 51 ms2026-10-21T22:47:25.000Z: 33 ms2026-10-21T22:52:35.000Z: 30 ms2026-10-21T22:57:45.000Z: 40 ms2026-10-21T23:02:55.000Z: 22 ms2026-10-21T23:08:03.000Z: 22 ms2026-10-21T23:13:13.000Z: 36 ms2026-10-21T23:18:23.000Z: 37 ms2026-10-21T23:23:30.000Z: 22 ms2026-10-21T23:28:39.000Z: 36 ms2026-10-21T23:33:49.000Z: 39 ms2026-10-21T23:38:59.000Z: 41 ms2026-10-21T23:44:07.000Z: 21 ms2026-10-21T23:49:17.000Z: 31 ms2026-10-21T23:54:27.000Z: 36 ms2026-10-21T23:59:35.000Z: 39 ms2026-10-22T00:04:43.000Z: 21 ms2026-10-22T00:09:51.000Z: 29 ms

0 failed checks; 0 restricted checks. Restricted checks are excluded from the success rate. Lines connect recorded samples across gaps; availability between checks is unknown. Response time measures receipt of HTTP headers, not full page load. Checks run from one US monitoring server and do not verify sign-in, API, or app features. These sampled results are separate from down reports and estimated activity.

Evidence behind the status

Provider reports service problems. The official provider feed identifies an active incident or affected component.

Website checks and estimated activity have independent update times. Refer to each section for its latest observation.

These measurements describe different things. A reachable homepage can coexist with login or API failures. Missing evidence stays unknown.

Official component status

Netlify official status · fetched 2026-10-22 00:09:10 UTC

41 mapped components · 2 reporting problems
ComponentProvider status
High-Performance Edge Networkoperational
Atlassian Bitbucket APIoperational
Standard Edge Networkoperational
Atlassian Bitbucket Webhooksoperational
Atlassian Bitbucket SSHoperational
Origin Serversoperational
Build Pipelinedegraded performance
npm, Inc. Registry Readsoperational
GitHub API Requestsoperational
Netlify Application UIdegraded performance
APIoperational
GitHub Webhooksoperational
Hosted DNSoperational
GitHub Git Operationsoperational
Prerenderingoperational
NS1 APIoperational
Identityoperational
NS1 Management Portaloperational
Netlify Functionsoperational
Name.comoperational
Analyticsoperational
Log Drainsoperational
Collaborative Deploy Previewsoperational
Git Gatewayoperational
Edge Functionsoperational
Netlify Image CDNoperational
Netlify Blobsoperational
Netlify Observabilityoperational
Netlify Connectoperational
Netlify Create APIoperational
Visual Editoroperational
Netlify Formsoperational
Netlify Support Forumsoperational
Netlify Helpdeskoperational
Domain Purchasingoperational
Third-Party Servicesoperational
Billingoperational
Agent Runnersoperational
AI Gatewayoperational
Live Tunneloperational
Netlify Databaseoperational

Official incident timeline

Delays in build logs appearing in the UI · identified · 2026-10-21T19:42:07.650Z

Product match: components.

Read the provider’s incident report

  1. · identified

    We continue to work with our upstream service provider on the delays in build logs appearing in the Netlify UI.

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

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

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

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

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

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

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

Agent Runner failures · resolved · 2026-10-20T08:56:00.313Z

Product match: components.

Read the provider’s incident report

  1. · resolved

    This incident has been resolved.

  2. · monitoring

    We are monitoring the incident.

  3. · investigating

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

Elevated Build Errors · resolved · 2026-10-17T05:55:39.161Z

Product match: components.

Read the provider’s incident report

  1. · resolved

    This incident has been resolved.

  2. · monitoring

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

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

Elevated Edge Function Errors · resolved · 2026-10-08T14:34:05.706Z

Product match: components.

Read the provider’s incident report

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

Elevated error rates for AI Gateway · resolved · 2026-10-06T20:12:41.945Z

Product match: components.

Read the provider’s incident report

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

Error accessing Netlify-hosted sites · resolved · 2026-10-05T13:34:48.805Z

Product match: components.

Read the provider’s incident report

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

  2. · monitoring

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

  3. · identified

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

  4. · investigating

    We are continuing to investigate this issue.

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

Error accessing Netlify-hosted sites · resolved · 2026-09-29T09:00:14.403Z

Product match: components.

Read the provider’s incident report

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

Error accessing Netlify-hosted sites · resolved · 2026-09-24T19:25:40.645Z

Product match: components.

Read the provider’s incident report

  1. · resolved

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

  2. · monitoring

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

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

Recovery tracker

The provider still reports an active problem.

5 consecutive successful checks within the last 30 minutes. These checks measure the public website; they cannot establish recovery of every feature.

Slowdown detection

No sustained slowdown has been established against the earlier baseline.

Recent median: 31 ms · Earlier median: 27 ms. Flags require at least 3 recent and 5 earlier checks, more than twice the baseline, and at least 500 ms extra latency. Slowness alone does not identify server load as the cause.

Emerging down-report signals

  • is netlify down

Query “netlify” · observed 2026-10-22 00:09:50 UTC · 0 newly observed problem phrases.

Query “is netlify” · observed 2026-10-22 00:09:50 UTC · 0 newly observed problem phrases.

Emerging problem patterns can persist after an incident and do not measure report counts or prove an outage.

Is it down in your region?

Run one public website check from a community probe. Results describe that probe, not every user in a country.

Results are reused for 15 minutes. Shared free allowance: up to 60 tests per hour. A successful website check does not verify authenticated app or API functions.

Infrastructure incident context

Check whether broader platform incidents coincide with the problem you are seeing. These providers are context, not verified dependencies of Netlify.

GitHub official status · 2026-10-22 00:13:12 UTC

No active incidents recorded.

Cloudflare official status · 2026-10-22 00:13:12 UTC

About Netlify status on Iszdown

Check Netlify availability, incident history, downtime reports, and website performance.

This page combines the available Netlify report activity, official product status, public website measurements, and daily history. Each measurement has its own observation time. A search spike alone does not confirm downtime, and a reachable website does not establish that sign-in or every product feature works.

41 product-matched official components are listed above. Latest public website measurement: 2026-10-22T00:09:51.000Z.

Visit the official Netlify website · Official provider status · How it works

What to check when Netlify is not working

These are troubleshooting suggestions, not a list of currently reported problems.

Netlify will not open

Compare your usual browser or app with a private browser window, then try another network if available. Save unsent work first. A difference between networks can help separate a local connection problem from a wider disruption.

Netlify is slow or only one feature fails

Record the affected action, exact error, and time. Compare the website response measurements with any official component incidents; loading a homepage does not test every feature.

Website troubleshooting guide · Sign-in problems · API errors and timeouts

Include the time, affected feature, and error message when contacting official support. Keep passwords, payment information, session cookies, and access tokens private.

Recent Netlify outage history

Latest available product-matched official incidents in the calendar’s archive. Times below use UTC. Duration is the provider’s recorded incident window, not a measurement of impact on every user.

IncidentStarted (UTC)Recorded durationLast collected status
Delays in build logs appearing in the UINo resolution recordedidentified
Agent Runner failures69 minresolved
Elevated Build Errors52 minresolved
Error accessing Netlify-hosted sites50 minresolved
Error accessing Netlify-hosted sites24 minresolved
Elevated CDN Errors34 minresolved
Errors accessing Netlify-hosted sites85 minresolved
Elevated Image CDN Errors51 minresolved

Frequently asked questions about Netlify

Is Netlify down right now?

Provider reports service problems. The official provider feed identifies an active incident or affected component. This page was assembled at 2026-10-22T00:14:14.000Z.

How many Netlify outage reports are there today?

The displayed rolling 24-hour window contains 0 recorded reports, from 2026-10-21T00:10:00.000Z to 2026-10-22T00:10:00.000Z. This is not a calendar-day total or a count of affected people. Estimated activity is shown separately as an estimate.

Why does Netlify show operational when it is not working for me?

An official operational status can coexist with a local network issue, account problem, or feature-specific incident. Compare the mapped components, recent incident updates, and regional diagnostic on this page. Automated website checks test public access, not your signed-in session or every Netlify feature.

When was Netlify status last updated?

The latest status observation was 2026-10-22T00:09:10.000Z. Only matched product components and incidents are shown. The assessment is recent.

Has Netlify had outages before?

The daily calendar links available incident evidence and retains daily monitoring summaries. Pink marks service issues, green requires sufficient observations with no issues observed, and gray means insufficient coverage. The collected history is incomplete and is not a lifetime outage count or a guarantee of uninterrupted uptime.

How do I follow Netlify or report a problem?

Use “Watch this service” to save Netlify in this browser’s watchlist, then return to compare its status with other saved services. Optional browser notifications can flag status changes while the watchlist page stays open and visible; background alerts are not sent. Use the problem-report button for an outage report; contact the provider through its official website for account, billing, or private support issues. Iszdown is independent and cannot resolve provider support tickets.

Related services to Netlify

Check a related product separately; its status can differ from Netlify.

Netlify