Skip to content

Outage tracker / Netlify

Is Netlify down?

I'm having a problem

Operationalchecked 2 minutes ago

We reached Netlify from all 10 regions we check.

As of Oct 5, 2026, 8:15 PM UTC, Netlify answered RealUptime's probes in all 10 regions that returned a reading.

Functional endpoints verified

Last outage: 10 min on Sep 21, 2026 (web surface, from US-East).

our independent probeslive · checked Oct 5, 2026, 8:15 PM UTC
US-East311 msOperational
US-West327 msOperational
Europe509 msOperational
Asia-Pacific970 msOperational
US-Central623 msOperational
Canada142 msOperational
UK573 msOperational
Southeast Asia1280 msOperational
Australia1066 msOperational
South America755 msOperational
their status pagetheir claim, not our reading

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

from Netlify's own status page, checked Oct 5, 2026, 7:58 PM 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
646msp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 433ms2026-09-07 UTC: p95 658ms2026-09-08 UTC: p95 596ms2026-09-09 UTC: p95 1.5s2026-09-10 UTC: p95 648ms2026-09-11 UTC: p95 827ms2026-09-12 UTC: p95 652ms2026-09-13 UTC: p95 651ms2026-09-14 UTC: p95 883ms2026-09-15 UTC: p95 821ms2026-09-16 UTC: p95 987ms2026-09-17 UTC: p95 1.2s2026-09-18 UTC: p95 859ms2026-09-19 UTC: p95 651ms2026-09-20 UTC: p95 628ms2026-09-21 UTC: p95 1.1s2026-09-22 UTC: p95 521ms2026-09-23 UTC: p95 966ms2026-09-24 UTC: p95 1.1s2026-09-25 UTC: p95 746ms2026-09-26 UTC: p95 658ms2026-09-27 UTC: p95 661ms2026-09-28 UTC: p95 819ms2026-09-29 UTC: p95 768ms2026-09-30 UTC: p95 733ms2026-10-01 UTC: p95 783ms2026-10-02 UTC: p95 767ms2026-10-03 UTC: p95 704ms2026-10-04 UTC: p95 643ms2026-10-05 UTC: p95 646ms
Sep 6Sep 20Oct 5
US-West
680msp95 · latest
2.5s1.3s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 762ms2026-09-07 UTC: p95 728ms2026-09-08 UTC: p95 815ms2026-09-09 UTC: p95 2.0s2026-09-10 UTC: p95 681ms2026-09-11 UTC: p95 847ms2026-09-12 UTC: p95 540ms2026-09-13 UTC: p95 735ms2026-09-14 UTC: p95 1.2s2026-09-15 UTC: p95 1.3s2026-09-16 UTC: p95 900ms2026-09-17 UTC: p95 1.0s2026-09-18 UTC: p95 727ms2026-09-19 UTC: p95 723ms2026-09-20 UTC: p95 823ms2026-09-21 UTC: p95 2.2s2026-09-22 UTC: p95 654ms2026-09-23 UTC: p95 736ms2026-09-24 UTC: p95 667ms2026-09-25 UTC: p95 697ms2026-09-26 UTC: p95 667ms2026-09-27 UTC: p95 986ms2026-09-28 UTC: p95 777ms2026-09-29 UTC: p95 671ms2026-09-30 UTC: p95 680ms2026-10-01 UTC: p95 863ms2026-10-02 UTC: p95 600ms2026-10-03 UTC: p95 730ms2026-10-04 UTC: p95 743ms2026-10-05 UTC: p95 680ms
Sep 6Sep 20Oct 5
Europe
759msp95 · 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-09-06 UTC: p95 652ms2026-09-07 UTC: p95 664ms2026-09-08 UTC: p95 1.0s2026-09-09 UTC: p95 1.4s2026-09-10 UTC: p95 1.6s2026-09-11 UTC: p95 1.3s2026-09-12 UTC: p95 870ms2026-09-13 UTC: p95 730ms2026-09-14 UTC: p95 1.3s2026-09-15 UTC: p95 1.1s2026-09-16 UTC: p95 949ms2026-09-17 UTC: p95 989ms2026-09-18 UTC: p95 962ms2026-09-19 UTC: p95 846ms2026-09-20 UTC: p95 874ms2026-09-21 UTC: p95 1.9s2026-09-22 UTC: p95 816ms2026-09-23 UTC: p95 896ms2026-09-24 UTC: p95 1.0s2026-09-25 UTC: p95 821ms2026-09-26 UTC: p95 837ms2026-09-27 UTC: p95 655ms2026-09-28 UTC: p95 774ms2026-09-29 UTC: p95 884ms2026-09-30 UTC: p95 929ms2026-10-01 UTC: p95 864ms2026-10-02 UTC: p95 829ms2026-10-03 UTC: p95 782ms2026-10-04 UTC: p95 754ms2026-10-05 UTC: p95 759ms
Sep 6Sep 20Oct 5
Asia-Pacific
1.4sp95 · latest
5s2.5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.4s2026-09-07 UTC: p95 1.6s2026-09-08 UTC: p95 1.6s2026-09-09 UTC: p95 2.5s2026-09-10 UTC: p95 1.6s2026-09-11 UTC: p95 2.2s2026-09-12 UTC: p95 1.4s2026-09-13 UTC: p95 1.3s2026-09-14 UTC: p95 1.8s2026-09-15 UTC: p95 1.7s2026-09-16 UTC: p95 1.8s2026-09-17 UTC: p95 1.8s2026-09-18 UTC: p95 1.6s2026-09-19 UTC: p95 1.5s2026-09-20 UTC: p95 1.4s2026-09-21 UTC: p95 2.1s2026-09-22 UTC: p95 1.6s2026-09-23 UTC: p95 1.7s2026-09-24 UTC: p95 1.6s2026-09-25 UTC: p95 1.4s2026-09-26 UTC: p95 1.5s2026-09-27 UTC: p95 1.4s2026-09-28 UTC: p95 1.3s2026-09-29 UTC: p95 1.5s2026-09-30 UTC: p95 1.5s2026-10-01 UTC: p95 1.4s2026-10-02 UTC: p95 1.4s2026-10-03 UTC: p95 1.4s2026-10-04 UTC: p95 1.3s2026-10-05 UTC: p95 1.4s
Sep 6Sep 20Oct 5
US-Central
645msp95 · latest
2s1s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 500ms2026-09-07 UTC: p95 649ms2026-09-08 UTC: p95 1.1s2026-09-09 UTC: p95 1.1s2026-09-10 UTC: p95 969ms2026-09-11 UTC: p95 1.1s2026-09-12 UTC: p95 612ms2026-09-13 UTC: p95 583ms2026-09-14 UTC: p95 639ms2026-09-15 UTC: p95 894ms2026-09-16 UTC: p95 988ms2026-09-17 UTC: p95 721ms2026-09-18 UTC: p95 756ms2026-09-19 UTC: p95 595ms2026-09-20 UTC: p95 545ms2026-09-21 UTC: p95 1.6s2026-09-22 UTC: p95 684ms2026-09-23 UTC: p95 537ms2026-09-24 UTC: p95 987ms2026-09-25 UTC: p95 704ms2026-09-26 UTC: p95 806ms2026-09-27 UTC: p95 496ms2026-09-28 UTC: p95 456ms2026-09-29 UTC: p95 413ms2026-09-30 UTC: p95 378ms2026-10-01 UTC: p95 689ms2026-10-02 UTC: p95 617ms2026-10-03 UTC: p95 749ms2026-10-04 UTC: p95 676ms2026-10-05 UTC: p95 645ms
Sep 6Sep 20Oct 5
Canada
595msp95 · latest
2.5s1.3s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 565ms2026-09-07 UTC: p95 529ms2026-09-08 UTC: p95 584ms2026-09-09 UTC: p95 2.0s2026-09-10 UTC: p95 1.3s2026-09-11 UTC: p95 674ms2026-09-12 UTC: p95 481ms2026-09-13 UTC: p95 623ms2026-09-14 UTC: p95 1.2s2026-09-15 UTC: p95 712ms2026-09-16 UTC: p95 1.1s2026-09-17 UTC: p95 982ms2026-09-18 UTC: p95 816ms2026-09-19 UTC: p95 818ms2026-09-20 UTC: p95 854ms2026-09-21 UTC: p95 1.8s2026-09-22 UTC: p95 571ms2026-09-23 UTC: p95 767ms2026-09-24 UTC: p95 1.2s2026-09-25 UTC: p95 650ms2026-09-26 UTC: p95 641ms2026-09-27 UTC: p95 461ms2026-09-28 UTC: p95 438ms2026-09-29 UTC: p95 456ms2026-09-30 UTC: p95 671ms2026-10-01 UTC: p95 728ms2026-10-02 UTC: p95 728ms2026-10-03 UTC: p95 797ms2026-10-04 UTC: p95 726ms2026-10-05 UTC: p95 595ms
Sep 6Sep 20Oct 5
UK
726msp95 · latest
2s1s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 639ms2026-09-07 UTC: p95 608ms2026-09-08 UTC: p95 1.2s2026-09-09 UTC: p95 1.6s2026-09-10 UTC: p95 604ms2026-09-11 UTC: p95 611ms2026-09-12 UTC: p95 619ms2026-09-13 UTC: p95 608ms2026-09-14 UTC: p95 1.1s2026-09-15 UTC: p95 877ms2026-09-16 UTC: p95 966ms2026-09-17 UTC: p95 1.7s2026-09-18 UTC: p95 770ms2026-09-19 UTC: p95 756ms2026-09-20 UTC: p95 766ms2026-09-21 UTC: p95 1.4s2026-09-22 UTC: p95 756ms2026-09-23 UTC: p95 670ms2026-09-24 UTC: p95 652ms2026-09-25 UTC: p95 902ms2026-09-26 UTC: p95 1.0s2026-09-27 UTC: p95 623ms2026-09-28 UTC: p95 634ms2026-09-29 UTC: p95 639ms2026-09-30 UTC: p95 676ms2026-10-01 UTC: p95 748ms2026-10-02 UTC: p95 670ms2026-10-03 UTC: p95 671ms2026-10-04 UTC: p95 710ms2026-10-05 UTC: p95 726ms
Sep 6Sep 20Oct 5
Southeast Asia
1.7sp95 · latest
5s2.5s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.9s2026-09-07 UTC: p95 2.0s2026-09-08 UTC: p95 2.9s2026-09-09 UTC: p95 3.2s2026-09-10 UTC: p95 2.7s2026-09-11 UTC: p95 2.6s2026-09-12 UTC: p95 2.0s2026-09-13 UTC: p95 1.9s2026-09-14 UTC: p95 2.1s2026-09-15 UTC: p95 1.9s2026-09-16 UTC: p95 2.1s2026-09-17 UTC: p95 2.2s2026-09-18 UTC: p95 2.6s2026-09-19 UTC: p95 2.1s2026-09-20 UTC: p95 2.2s2026-09-21 UTC: p95 4.4s2026-09-22 UTC: p95 2.7s2026-09-23 UTC: p95 3.4s2026-09-24 UTC: p95 3.3s2026-09-25 UTC: p95 3.1s2026-09-26 UTC: p95 3.5s2026-09-27 UTC: p95 2.9s2026-09-28 UTC: p95 2.9s2026-09-29 UTC: p95 2.4s2026-09-30 UTC: p95 1.9s2026-10-01 UTC: p95 1.8s2026-10-02 UTC: p95 1.9s2026-10-03 UTC: p95 2.0s2026-10-04 UTC: p95 1.8s2026-10-05 UTC: p95 1.7s
Sep 6Sep 20Oct 5
Australia
1.5sp95 · latest
5s2.5s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 2.2s2026-09-07 UTC: p95 1.8s2026-09-08 UTC: p95 2.1s2026-09-09 UTC: p95 3.3s2026-09-10 UTC: p95 1.7s2026-09-11 UTC: p95 1.6s2026-09-12 UTC: p95 1.6s2026-09-13 UTC: p95 1.4s2026-09-14 UTC: p95 1.4s2026-09-15 UTC: p95 1.8s2026-09-16 UTC: p95 1.8s2026-09-17 UTC: p95 1.9s2026-09-18 UTC: p95 1.8s2026-09-19 UTC: p95 1.8s2026-09-20 UTC: p95 1.9s2026-09-21 UTC: p95 2.0s2026-09-22 UTC: p95 1.5s2026-09-23 UTC: p95 1.6s2026-09-24 UTC: p95 1.4s2026-09-25 UTC: p95 1.7s2026-09-26 UTC: p95 2.2s2026-09-27 UTC: p95 2.2s2026-09-28 UTC: p95 2.1s2026-09-29 UTC: p95 2.5s2026-09-30 UTC: p95 2.2s2026-10-01 UTC: p95 2.1s2026-10-02 UTC: p95 2.3s2026-10-03 UTC: p95 2.2s2026-10-04 UTC: p95 1.8s2026-10-05 UTC: p95 1.5s
Sep 6Sep 20Oct 5
South America
1.3sp95 · latest
5s2.5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.4s2026-09-07 UTC: p95 1.5s2026-09-08 UTC: p95 2.1s2026-09-09 UTC: p95 1.7s2026-09-10 UTC: p95 2.3s2026-09-11 UTC: p95 1.4s2026-09-12 UTC: p95 1.2s2026-09-13 UTC: p95 1.2s2026-09-14 UTC: p95 1.2s2026-09-15 UTC: p95 1.1s2026-09-16 UTC: p95 1.8s2026-09-17 UTC: p95 2.7s2026-09-18 UTC: p95 1.9s2026-09-19 UTC: p95 1.9s2026-09-20 UTC: p95 1.8s2026-09-21 UTC: p95 1.7s2026-09-22 UTC: p95 1.5s2026-09-23 UTC: p95 1.2s2026-09-24 UTC: p95 1.4s2026-09-25 UTC: p95 1.7s2026-09-26 UTC: p95 1.7s2026-09-27 UTC: p95 1.2s2026-09-28 UTC: p95 1.3s2026-09-29 UTC: p95 1.8s2026-09-30 UTC: p95 1.3s2026-10-01 UTC: p95 1.4s2026-10-02 UTC: p95 1.3s2026-10-03 UTC: p95 1.5s2026-10-04 UTC: p95 1.6s2026-10-05 UTC: p95 1.3s
Sep 6Sep 20Oct 5

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.

Get an email when we see Netlify go down, and when it is back

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.

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

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 311msstatus code: 401checked: Oct 5, 2026, 8:14 PM 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: 327msstatus code: 401checked: Oct 5, 2026, 8:14 PM 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.
    • US-Central
      Operationallatency: 623msstatus code: 401checked: Oct 5, 2026, 8:04 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Netlify normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Operationallatency: 142msstatus code: 401checked: Oct 5, 2026, 8:04 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Netlify normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Operationallatency: 755msstatus code: 401checked: Oct 5, 2026, 8:04 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Netlify normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    OperationalEurope, UK
    • Europe
      Operationallatency: 509msstatus code: 401checked: Oct 5, 2026, 8:14 PM 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.
    • UK
      Operationallatency: 573msstatus code: 401checked: Oct 5, 2026, 8:04 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Netlify normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 970msstatus code: 401checked: Oct 5, 2026, 8:15 PM 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.
    • Southeast Asia
      Operationallatency: 1280msstatus code: 401checked: Oct 5, 2026, 8:04 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Netlify normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Operationallatency: 1066msstatus code: 401checked: Oct 5, 2026, 8:04 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Netlify normally. We do not have enough reports from Australia to say anything about what people there are seeing.

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

Error accessing Netlify-hosted sites, 50mdeclared on their status page2026-10-05
Error accessing Netlify-hosted sites, 1mdeclared on their status page2026-09-29
Error accessing Netlify-hosted sites, 24mdeclared on their status page2026-09-24
Elevated CDN Errors, 34mdeclared on their status page2026-09-23
Errors accessing Netlify-hosted sites, 1h 25mdeclared on their status page2026-09-21
Partial outage, under our ~10m probe resolutionmeasured by our probes · US-East2026-09-21
Elevated Image CDN Errors, 51mdeclared on their status page2026-09-16
Elevated Errors and Latency in IAD Region, 1mdeclared on their status page2026-09-08

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

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 last 30 days, which is 100% uptime by our reading. A 99.9% target allows 43 minutes over that period.

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

Separately, we measured 9 minutes where only one of our regions was affected. It is excluded above because most SLAs would not credit it, and it is the kind of outage a single-vantage monitor never sees at all.

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 10 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. Read the full methodology.