Skip to content

Outage tracker / Nintendo

Is Nintendo down?

I'm having a problem

Checks passingchecked 1 minute ago

Our checks of Nintendo pass from all 10 regions we check.

As of Nov 7, 2026, 1:24 AM UTC, RealUptime's checks of Nintendo passed in all 10 regions that returned a reading.

Front-door and live API checks

Last time our checks failed from two or more distant regions: 12 min on Aug 31, 2026 (web surface, from Europe and US-West).

Email me when our checks of Nintendo fail from two or more distant regions

One email when our checks of Nintendo fail from two or more distant regions, and one when they pass, after you confirm the address. No account, no card.

This is our own reading from outside. It is not Nintendo's official status.

our check readinglive · checked Nov 7, 2026, 1:24 AM UTC
US-East1274 msChecks passing
US-West1365 msChecks passing
Europe1493 msChecks passing
Asia-Pacific1117 msChecks passing
US-Central691 msChecks passing
Canada1119 msChecks passing
UK352 msChecks passing
Southeast Asia1958 msChecks passing
Australia2147 msChecks passing
South America1820 msChecks passing
their status pagetheir claim, not our reading

Nintendo publishes no status feed we can read, so the only reading here is our check reading on the left.

Nintendo response time, by region

US-East
1.2sp95 · latest
5s2.5s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-09 UTC: p95 516ms2026-10-10 UTC: p95 546ms2026-10-11 UTC: p95 502ms2026-10-12 UTC: p95 474ms2026-10-13 UTC: p95 693ms2026-10-14 UTC: p95 616ms2026-10-15 UTC: p95 693ms2026-10-16 UTC: p95 683ms2026-10-17 UTC: p95 1.2s2026-10-18 UTC: p95 1.6s2026-10-19 UTC: p95 1.6s2026-10-20 UTC: p95 1.6s2026-10-21 UTC: p95 1.6s2026-10-22 UTC: p95 1.5s2026-10-23 UTC: p95 1.4s2026-10-24 UTC: p95 1.5s2026-10-25 UTC: p95 1.5s2026-10-26 UTC: p95 2.6s2026-10-27 UTC: p95 1.4s2026-10-28 UTC: p95 1.4s2026-10-29 UTC: p95 1.4s2026-10-30 UTC: p95 1.5s2026-10-31 UTC: p95 1.5s2026-11-01 UTC: p95 1.5s2026-11-02 UTC: p95 2.0s2026-11-03 UTC: p95 1.7s2026-11-04 UTC: p95 1.7s2026-11-05 UTC: p95 1.5s2026-11-06 UTC: p95 2.1s2026-11-07 UTC: p95 1.2s
Oct 9Oct 23Nov 7
US-West
1.7sp95 · 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-10-09 UTC: p95 544ms2026-10-10 UTC: p95 447ms2026-10-11 UTC: p95 524ms2026-10-12 UTC: p95 603ms2026-10-13 UTC: p95 610ms2026-10-14 UTC: p95 631ms2026-10-15 UTC: p95 620ms2026-10-16 UTC: p95 719ms2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.2s2026-10-19 UTC: p95 1.2s2026-10-20 UTC: p95 1.3s2026-10-21 UTC: p95 1.5s2026-10-22 UTC: p95 1.5s2026-10-23 UTC: p95 1.6s2026-10-24 UTC: p95 1.7s2026-10-25 UTC: p95 1.7s2026-10-26 UTC: p95 1.9s2026-10-27 UTC: p95 1.6s2026-10-28 UTC: p95 1.6s2026-10-29 UTC: p95 1.6s2026-10-30 UTC: p95 1.5s2026-10-31 UTC: p95 1.7s2026-11-01 UTC: p95 1.6s2026-11-02 UTC: p95 1.8s2026-11-03 UTC: p95 1.9s2026-11-04 UTC: p95 2.2s2026-11-05 UTC: p95 2.0s2026-11-06 UTC: p95 1.7s2026-11-07 UTC: p95 1.7s
Oct 9Oct 23Nov 7
Europe
1.7sp95 · latest
2.5s1.3s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-09 UTC: p95 419ms2026-10-10 UTC: p95 423ms2026-10-11 UTC: p95 377ms2026-10-12 UTC: p95 402ms2026-10-13 UTC: p95 342ms2026-10-14 UTC: p95 525ms2026-10-15 UTC: p95 414ms2026-10-16 UTC: p95 325ms2026-10-17 UTC: p95 874ms2026-10-18 UTC: p95 826ms2026-10-19 UTC: p95 1.1s2026-10-20 UTC: p95 766ms2026-10-21 UTC: p95 650ms2026-10-22 UTC: p95 646ms2026-10-23 UTC: p95 627ms2026-10-24 UTC: p95 614ms2026-10-25 UTC: p95 645ms2026-10-26 UTC: p95 774ms2026-10-27 UTC: p95 681ms2026-10-28 UTC: p95 659ms2026-10-29 UTC: p95 690ms2026-10-30 UTC: p95 842ms2026-10-31 UTC: p95 729ms2026-11-01 UTC: p95 922ms2026-11-02 UTC: p95 1.2s2026-11-03 UTC: p95 1.5s2026-11-04 UTC: p95 1.8s2026-11-05 UTC: p95 1.6s2026-11-06 UTC: p95 2.2s2026-11-07 UTC: p95 1.7s
Oct 9Oct 23Nov 7
Asia-Pacific
1.2sp95 · 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-10-09 UTC: p95 1.0s2026-10-10 UTC: p95 1.0s2026-10-11 UTC: p95 1.0s2026-10-12 UTC: p95 1.0s2026-10-13 UTC: p95 922ms2026-10-14 UTC: p95 1.0s2026-10-15 UTC: p95 1.1s2026-10-16 UTC: p95 1.1s2026-10-17 UTC: p95 2.1s2026-10-18 UTC: p95 2.2s2026-10-19 UTC: p95 2.1s2026-10-20 UTC: p95 2.2s2026-10-21 UTC: p95 2.1s2026-10-22 UTC: p95 2.4s2026-10-23 UTC: p95 2.8s2026-10-24 UTC: p95 2.5s2026-10-25 UTC: p95 2.1s2026-10-26 UTC: p95 2.9s2026-10-27 UTC: p95 2.5s2026-10-28 UTC: p95 2.2s2026-10-29 UTC: p95 2.3s2026-10-30 UTC: p95 2.3s2026-10-31 UTC: p95 2.0s2026-11-01 UTC: p95 2.2s2026-11-02 UTC: p95 2.3s2026-11-03 UTC: p95 2.4s2026-11-04 UTC: p95 2.6s2026-11-05 UTC: p95 2.5s2026-11-06 UTC: p95 2.7s2026-11-07 UTC: p95 1.2s
Oct 9Oct 23Nov 7
US-Central
542msp95 · 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-10-09 UTC: p95 503ms2026-10-10 UTC: p95 579ms2026-10-11 UTC: p95 678ms2026-10-12 UTC: p95 538ms2026-10-13 UTC: p95 458ms2026-10-14 UTC: p95 492ms2026-10-15 UTC: p95 641ms2026-10-16 UTC: p95 642ms2026-10-17 UTC: p95 1.2s2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 1.2s2026-10-20 UTC: p95 1.2s2026-10-21 UTC: p95 1.2s2026-10-22 UTC: p95 1.2s2026-10-23 UTC: p95 1.6s2026-10-24 UTC: p95 1.6s2026-10-25 UTC: p95 1.6s2026-10-26 UTC: p95 1.8s2026-10-27 UTC: p95 1.6s2026-10-28 UTC: p95 1.8s2026-10-29 UTC: p95 1.6s2026-10-30 UTC: p95 1.3s2026-10-31 UTC: p95 1.2s2026-11-01 UTC: p95 1.2s2026-11-02 UTC: p95 1.3s2026-11-03 UTC: p95 881ms2026-11-04 UTC: p95 931ms2026-11-05 UTC: p95 1.0s2026-11-06 UTC: p95 1.1s2026-11-07 UTC: p95 542ms
Oct 9Oct 23Nov 7
Canada
1.3sp95 · latest
2s1s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-09 UTC: p95 480ms2026-10-10 UTC: p95 575ms2026-10-11 UTC: p95 562ms2026-10-12 UTC: p95 674ms2026-10-13 UTC: p95 645ms2026-10-14 UTC: p95 592ms2026-10-15 UTC: p95 621ms2026-10-16 UTC: p95 600ms2026-10-17 UTC: p95 725ms2026-10-18 UTC: p95 861ms2026-10-19 UTC: p95 860ms2026-10-20 UTC: p95 862ms2026-10-21 UTC: p95 1.4s2026-10-22 UTC: p95 1.4s2026-10-23 UTC: p95 1.2s2026-10-24 UTC: p95 1.4s2026-10-25 UTC: p95 1.3s2026-10-26 UTC: p95 1.6s2026-10-27 UTC: p95 1.4s2026-10-28 UTC: p95 1.5s2026-10-29 UTC: p95 1.5s2026-10-30 UTC: p95 1.3s2026-10-31 UTC: p95 1.6s2026-11-01 UTC: p95 1.6s2026-11-02 UTC: p95 1.5s2026-11-03 UTC: p95 1.1s2026-11-04 UTC: p95 1.1s2026-11-05 UTC: p95 1.6s2026-11-06 UTC: p95 1.6s2026-11-07 UTC: p95 1.3s
Oct 9Oct 23Nov 7
UK
418msp95 · 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-10-09 UTC: p95 564ms2026-10-10 UTC: p95 441ms2026-10-11 UTC: p95 398ms2026-10-12 UTC: p95 466ms2026-10-13 UTC: p95 330ms2026-10-14 UTC: p95 365ms2026-10-15 UTC: p95 315ms2026-10-16 UTC: p95 484ms2026-10-17 UTC: p95 507ms2026-10-18 UTC: p95 701ms2026-10-19 UTC: p95 800ms2026-10-20 UTC: p95 789ms2026-10-21 UTC: p95 644ms2026-10-22 UTC: p95 881ms2026-10-23 UTC: p95 911ms2026-10-24 UTC: p95 818ms2026-10-25 UTC: p95 1.0s2026-10-26 UTC: p95 1.2s2026-10-27 UTC: p95 857ms2026-10-28 UTC: p95 1.1s2026-10-29 UTC: p95 870ms2026-10-30 UTC: p95 1.3s2026-10-31 UTC: p95 1.3s2026-11-01 UTC: p95 1.3s2026-11-02 UTC: p95 1.1s2026-11-03 UTC: p95 692ms2026-11-04 UTC: p95 827ms2026-11-05 UTC: p95 840ms2026-11-06 UTC: p95 744ms2026-11-07 UTC: p95 418ms
Oct 9Oct 23Nov 7
Southeast Asia
1.4sp95 · 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-10-09 UTC: p95 1.4s2026-10-10 UTC: p95 1.4s2026-10-11 UTC: p95 1.3s2026-10-12 UTC: p95 1.1s2026-10-13 UTC: p95 1.2s2026-10-14 UTC: p95 1.2s2026-10-15 UTC: p95 1.1s2026-10-16 UTC: p95 1.4s2026-10-17 UTC: p95 2.0s2026-10-18 UTC: p95 2.8s2026-10-19 UTC: p95 2.3s2026-10-20 UTC: p95 2.4s2026-10-21 UTC: p95 2.6s2026-10-22 UTC: p95 3.1s2026-10-23 UTC: p95 2.9s2026-10-24 UTC: p95 2.8s2026-10-25 UTC: p95 3.0s2026-10-26 UTC: p95 3.2s2026-10-27 UTC: p95 2.8s2026-10-28 UTC: p95 2.7s2026-10-29 UTC: p95 3.3s2026-10-30 UTC: p95 3.4s2026-10-31 UTC: p95 2.9s2026-11-01 UTC: p95 3.1s2026-11-02 UTC: p95 3.0s2026-11-03 UTC: p95 2.1s2026-11-04 UTC: p95 2.1s2026-11-05 UTC: p95 2.2s2026-11-06 UTC: p95 1.5s2026-11-07 UTC: p95 1.4s
Oct 9Oct 23Nov 7
Australia
2.3sp95 · 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-10-09 UTC: p95 1.0s2026-10-10 UTC: p95 972ms2026-10-11 UTC: p95 1.1s2026-10-12 UTC: p95 1.2s2026-10-13 UTC: p95 1.2s2026-10-14 UTC: p95 1.1s2026-10-15 UTC: p95 994ms2026-10-16 UTC: p95 1.1s2026-10-17 UTC: p95 2.4s2026-10-18 UTC: p95 2.3s2026-10-19 UTC: p95 2.5s2026-10-20 UTC: p95 2.5s2026-10-21 UTC: p95 2.3s2026-10-22 UTC: p95 2.3s2026-10-23 UTC: p95 2.3s2026-10-24 UTC: p95 2.3s2026-10-25 UTC: p95 2.3s2026-10-26 UTC: p95 2.4s2026-10-27 UTC: p95 2.2s2026-10-28 UTC: p95 2.3s2026-10-29 UTC: p95 2.3s2026-10-30 UTC: p95 2.6s2026-10-31 UTC: p95 2.3s2026-11-01 UTC: p95 2.5s2026-11-02 UTC: p95 2.4s2026-11-03 UTC: p95 1.7s2026-11-04 UTC: p95 2.1s2026-11-05 UTC: p95 2.1s2026-11-06 UTC: p95 2.3s2026-11-07 UTC: p95 2.3s
Oct 9Oct 23Nov 7
South America
2.3sp95 · latest
10s5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-10-09 UTC: p95 1.1s2026-10-10 UTC: p95 1.2s2026-10-11 UTC: p95 1.2s2026-10-12 UTC: p95 1.2s2026-10-13 UTC: p95 809ms2026-10-14 UTC: p95 1.1s2026-10-15 UTC: p95 1.1s2026-10-16 UTC: p95 1.3s2026-10-17 UTC: p95 2.6s2026-10-18 UTC: p95 2.8s2026-10-19 UTC: p95 2.6s2026-10-20 UTC: p95 2.6s2026-10-21 UTC: p95 2.7s2026-10-22 UTC: p95 2.7s2026-10-23 UTC: p95 9.2s2026-10-24 UTC: p95 3.4s2026-10-25 UTC: p95 3.4s2026-10-26 UTC: p95 3.5s2026-10-27 UTC: p95 2.9s2026-10-28 UTC: p95 2.8s2026-10-29 UTC: p95 3.0s2026-10-30 UTC: p95 2.6s2026-10-31 UTC: p95 2.6s2026-11-01 UTC: p95 2.7s2026-11-02 UTC: p95 2.9s2026-11-03 UTC: p95 1.9s2026-11-04 UTC: p95 2.6s2026-11-05 UTC: p95 2.3s2026-11-06 UTC: p95 2.5s2026-11-07 UTC: p95 2.3s
Oct 9Oct 23Nov 7

Check your own site while you wait on Nintendo

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 Nintendo. It cannot diagnose Nintendo's own systems.

What we measured, function by function

Nintendo answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the api row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • APIprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
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 our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 1274msstatus code: 200checked: Nov 7, 2026, 1:24 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Nintendo normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 1365msstatus code: 200checked: Nov 7, 2026, 1:20 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Nintendo normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Checks passinglatency: 691msstatus code: 200checked: Nov 7, 2026, 1:10 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Nintendo normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Checks passinglatency: 1119msstatus code: 200checked: Nov 7, 2026, 1:11 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Nintendo normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Checks passinglatency: 1820msstatus code: 200checked: Nov 7, 2026, 1:11 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Nintendo normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 1493msstatus code: 200checked: Nov 7, 2026, 1:12 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Nintendo normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Checks passinglatency: 352msstatus code: 200checked: Nov 7, 2026, 1:05 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Nintendo normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 1117msstatus code: 200checked: Nov 7, 2026, 1:02 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Nintendo normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Checks passinglatency: 1958msstatus code: 200checked: Nov 7, 2026, 1:13 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Nintendo normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Checks passinglatency: 2147msstatus code: 200checked: Nov 7, 2026, 1:13 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Nintendo 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 Nintendo, 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 Nintendo yet, which is not evidence that nothing is wrong.

Recent probe events

Checks failing, 12mour checks · Europe and US-West2026-08-31

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

We have been measuring Nintendo since August 22, 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 Nintendo covering any window you pick, with our check readings and Nintendo's own claim at the time, side by side.

Full check history for Nintendo: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.

Put this badge in your README

Nintendo uptime by RealUptime's checksLive, from this page's own readings.
[![Nintendo uptime by RealUptime's checks](https://realuptime.io/outages/nintendo/badge.svg?days=30)](https://realuptime.io/outages/nintendo)
<a href="https://realuptime.io/outages/nintendo"><img src="https://realuptime.io/outages/nintendo/badge.svg?days=30" alt="Nintendo uptime by RealUptime's checks" height="20"></a>

Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.

To cite this page: RealUptime, "Is Nintendo down?", https://realuptime.io/outages/nintendo. The readings change with every check, so give the date you read them.

How our checks compare with Nintendo's stated SLA

At or above your target

Our checks of Nintendo failed for none over the last 30 days, which is 100% uptime by our checks. A 99.9% target allows 43 minutes over that period.

Our checks show no gap in this period. That does not rule out one you saw.

These figures come from our own checks of one public endpoint per service. They are not the service's real uptime. This is computed from our own checks, not from Nintendo'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: live API
https://api-lp1.znc.srv.nintendo.net/v3/Account/Login
secondary
https://www.nintendo.com/

What our check can and cannot see

A pass means a public route of the service's API answered our request normally. We do not check what it returned, so it does not show that the data is right, that sign-in works or that the rest of the product works.

Host checked: api-lp1.znc.srv.nintendo.net

RealUptime is not affiliated with Nintendo; the name identifies what we checked, and nothing here speaks for Nintendo's own team. We send a single web request to Nintendo from 10 regions on our own schedule and time the response. We do not see inside Nintendo's systems, do not use an account or real transaction, and are not the same signal Nintendo's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Nintendo is a real functional API call (marked “functional” above), not just a landing page, so a passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.