Skip to content

Outage tracker / Netlify

Is Netlify down?

I'm having a problem

Operationalchecked 3 minutes ago

We reached Netlify from all 4 regions we check.

Functional endpoints verified

No outage recorded in the 12 days we have measured Netlify (since Aug 20, 2026).

our independent probeslive · checked Sep 1, 2026, 4:07 AM UTC
US-East327 msOperational
US-West364 msOperational
Europe461 msOperational
Asia-Pacific1286 msOperational
their status pagetheir claim, not our reading

Netlify reports: All systems operational (“All Systems Operational”)

from Netlify's own status page, checked Sep 1, 2026, 3:55 AM UTC
Our probes and Netlify's own status page agree: both show Netlify as reachable right now.

Netlify's own component breakdown, as they publish it

  • Atlassian Bitbucket APIOperational
  • High-Performance Edge NetworkOperational
  • Atlassian Bitbucket WebhooksOperational
  • Standard Edge NetworkOperational
  • Atlassian Bitbucket SSHOperational
  • Origin ServersOperational
  • Build PipelineOperational
  • npm, Inc. Registry ReadsOperational
  • GitHub API RequestsOperational
  • Netlify Application UIOperational
  • APIOperational
  • GitHub WebhooksOperational
  • GitHub Git OperationsOperational
  • Hosted DNSOperational
  • NS1 APIOperational
  • PrerenderingOperational
  • IdentityOperational
  • NS1 Management PortalOperational
  • Name.comOperational
  • Netlify FunctionsOperational
  • 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
  • BillingOperational
  • Agent RunnersOperational
  • AI GatewayOperational
  • Live TunnelOperational

These are Netlify's components, named and scored by Netlify. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is Netlify's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

Netlify response time, by region

US-East
452msp95 · latest
1s500ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-20 UTC: p95 581ms2026-08-21 UTC: p95 580ms2026-08-22 UTC: p95 480ms2026-08-23 UTC: p95 538ms2026-08-24 UTC: p95 628ms2026-08-25 UTC: p95 747ms2026-08-26 UTC: p95 807ms2026-08-27 UTC: p95 571ms2026-08-28 UTC: p95 743ms2026-08-29 UTC: p95 898ms2026-08-30 UTC: p95 969ms2026-08-31 UTC: p95 928ms2026-09-01 UTC: p95 452ms
Aug 3Aug 17Sep 1
US-West
616msp95 · latest
1s500ms0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-20 UTC: p95 541ms2026-08-21 UTC: p95 680ms2026-08-22 UTC: p95 556ms2026-08-23 UTC: p95 613ms2026-08-24 UTC: p95 735ms2026-08-25 UTC: p95 694ms2026-08-26 UTC: p95 512ms2026-08-27 UTC: p95 727ms2026-08-28 UTC: p95 829ms2026-08-29 UTC: p95 813ms2026-08-30 UTC: p95 504ms2026-08-31 UTC: p95 767ms2026-09-01 UTC: p95 616ms
Aug 3Aug 17Sep 1
Europe
751msp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-20 UTC: p95 588ms2026-08-21 UTC: p95 861ms2026-08-22 UTC: p95 647ms2026-08-23 UTC: p95 714ms2026-08-24 UTC: p95 807ms2026-08-25 UTC: p95 829ms2026-08-26 UTC: p95 668ms2026-08-27 UTC: p95 695ms2026-08-28 UTC: p95 761ms2026-08-29 UTC: p95 667ms2026-08-30 UTC: p95 754ms2026-08-31 UTC: p95 1.3s2026-09-01 UTC: p95 751ms
Aug 3Aug 17Sep 1
Asia-Pacific
1.4sp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-20 UTC: p95 1.4s2026-08-21 UTC: p95 1.4s2026-08-22 UTC: p95 1.4s2026-08-23 UTC: p95 1.5s2026-08-24 UTC: p95 1.3s2026-08-25 UTC: p95 1.5s2026-08-26 UTC: p95 1.5s2026-08-27 UTC: p95 1.5s2026-08-28 UTC: p95 1.3s2026-08-29 UTC: p95 1.4s2026-08-30 UTC: p95 1.4s2026-08-31 UTC: p95 1.6s2026-09-01 UTC: p95 1.4s
Aug 3Aug 17Sep 1

Is it Netlify, or is it you?

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Netlify -- it cannot diagnose Netlify's own systems.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What we measured, and what people reported

  • US-East
    Operationallatency: 327msstatus code: 401checked: Sep 1, 2026, 3:59 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Netlify normally. We do not have enough reports from US-East to say anything about what people there are seeing.
  • US-West
    Operationallatency: 364msstatus code: 401checked: Sep 1, 2026, 4:05 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Netlify normally. We do not have enough reports from US-West to say anything about what people there are seeing.
  • Europe
    Operationallatency: 461msstatus code: 401checked: Sep 1, 2026, 4:07 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Netlify normally. We do not have enough reports from Europe to say anything about what people there are seeing.
  • Asia-Pacific
    Operationallatency: 1286msstatus code: 401checked: Sep 1, 2026, 4:01 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Netlify normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
  • US-Central
    Not monitored from this regionNetlify is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Canada
    Not monitored from this regionNetlify is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • UK
    Not monitored from this regionNetlify is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Southeast Asia
    Not monitored from this regionNetlify is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Australia
    Not monitored from this regionNetlify is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • South America
    Not monitored from this regionNetlify is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Netlify, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Netlify yet, which is not evidence that nothing is wrong.

Recent outages

Increased Latency in IAD Region on Global Network, 1h 20mdeclared on their status page2026-08-31
Elevated HTTP 500 errors serving sites and the Netlify UI, 1mdeclared on their status page2026-08-18
Elevated Build Errors, 25mdeclared on their status page2026-08-03
Errors Uploading Attachments to Agent Runners, 28mdeclared on their status page2026-07-22
Increase in Edge Function Errors, 25mdeclared on their status page2026-07-01
Connectivity issues affecting Bolt-powered sites, 5h 49mdeclared on their status page2026-06-14
AI Gateway: Claude Fable 5 unavailable, 49h 19mdeclared on their status page2026-06-13
Elevated latency affecting image delivery, 15mdeclared on their status page2026-06-09

measured entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Netlify since August 20, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Netlify covering any window you pick, with our measurements and Netlify's own claim at the time, side by side.

Full availability history for Netlify: 90-day availability by region, month-by-month uptime, and every incident on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Tell me when this goes down

Get told when we measure this

We will tell you when our probes stop reaching Netlify, and again when they can reach it again. That is our own measurement from ten regions, not Netlify's status page. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when a measured outage opens, one when it closes, and a one-click unsubscribe in every one. We do not send anything else to this address.

Put this badge in your README

Netlify uptime measured by RealUptimeLive, from this page's own readings.
[![Netlify uptime measured by RealUptime](https://realuptime.io/outages/netlify/badge.svg?days=30)](https://realuptime.io/outages/netlify)
<a href="https://realuptime.io/outages/netlify"><img src="https://realuptime.io/outages/netlify/badge.svg?days=30" alt="Netlify uptime measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What Netlify's SLA implies, from our measurement

At or above your target

We measured none of downtime for Netlify over the 292h 9m since we started watching it on 2026-08-20, which is 100% uptime by our reading. A 99.9% target allows 17 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, not from Netlify's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primaryfunctional
https://api.netlify.com/api/v1/user
secondary
https://www.netlifystatus.com/
RealUptime is not affiliated with Netlify; the name identifies what we measured, and nothing here speaks for Netlify's own team. We send a single web request to Netlify from 4 regions on our own schedule and time the response. We do not see inside Netlify's systems, do not use an account or real transaction, and are not the same signal Netlify's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Netlify is a real functional API call (marked “functional” above), not just a landing page, so a clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Netlify operates in a limited set of regions, so we only check it from where it is actually available; we do not probe from a region we know it does not serve. We started monitoring this service on August 20, 2026 (12 of 14 days so far, 12292 of 500 checks). We show a full track record once we have enough continuous history. Check back soon, or monitor your own site continuously with RealUptime. Read the full methodology.