Skip to content

Outage tracker / Nintendo

Is Nintendo down?

I'm having a problem

Partially degradedchecked 2 minutes ago

Nintendo is answering our probes, but its web surface is running at least 0.3x its 7-day median from Europe, South America, UK, Asia-Pacific, Southeast Asia and Australia. Everything else we check answered at its usual speed.

As of Oct 19, 2026, 8:52 PM 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 Oct 19, 2026, 8:52 PM UTC
US-East1695 msChecks passing
US-West830 msChecks passing
Europe628 msPartially degraded
Asia-Pacific1622 msPartially degraded
US-Central951 msChecks passing
Canada726 msChecks passing
UK520 msPartially degraded
Southeast Asia2011 msPartially degraded
Australia1922 msPartially degraded
South America1558 msPartially degraded
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.6sp95 · latest
10s5s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 759ms2026-09-21 UTC: p95 504ms2026-09-22 UTC: p95 530ms2026-09-23 UTC: p95 891ms2026-09-24 UTC: p95 959ms2026-09-25 UTC: p95 808ms2026-09-26 UTC: p95 848ms2026-09-27 UTC: p95 461ms2026-09-28 UTC: p95 510ms2026-09-29 UTC: p95 5.2s2026-09-30 UTC: p95 6.6s2026-10-01 UTC: p95 575ms2026-10-02 UTC: p95 457ms2026-10-03 UTC: p95 571ms2026-10-04 UTC: p95 617ms2026-10-05 UTC: p95 580ms2026-10-06 UTC: p95 580ms2026-10-07 UTC: p95 636ms2026-10-08 UTC: p95 607ms2026-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.6s
Sep 20Oct 4Oct 19
US-West
1.2sp95 · latest
10s5s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 817ms2026-09-21 UTC: p95 794ms2026-09-22 UTC: p95 915ms2026-09-23 UTC: p95 738ms2026-09-24 UTC: p95 524ms2026-09-25 UTC: p95 1.0s2026-09-26 UTC: p95 821ms2026-09-27 UTC: p95 571ms2026-09-28 UTC: p95 869ms2026-09-29 UTC: p95 7.7s2026-09-30 UTC: p95 8.1s2026-10-01 UTC: p95 556ms2026-10-02 UTC: p95 514ms2026-10-03 UTC: p95 573ms2026-10-04 UTC: p95 704ms2026-10-05 UTC: p95 746ms2026-10-06 UTC: p95 667ms2026-10-07 UTC: p95 670ms2026-10-08 UTC: p95 692ms2026-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.2s
Sep 20Oct 4Oct 19
Europe
1.1sp95 · 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-20 UTC: p95 812ms2026-09-21 UTC: p95 886ms2026-09-22 UTC: p95 907ms2026-09-23 UTC: p95 739ms2026-09-24 UTC: p95 756ms2026-09-25 UTC: p95 751ms2026-09-26 UTC: p95 834ms2026-09-27 UTC: p95 527ms2026-09-28 UTC: p95 576ms2026-09-29 UTC: p95 787ms2026-09-30 UTC: p95 646ms2026-10-01 UTC: p95 484ms2026-10-02 UTC: p95 553ms2026-10-03 UTC: p95 533ms2026-10-04 UTC: p95 453ms2026-10-05 UTC: p95 491ms2026-10-06 UTC: p95 523ms2026-10-07 UTC: p95 467ms2026-10-08 UTC: p95 437ms2026-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.1s
Sep 20Oct 4Oct 19
Asia-Pacific
2.1sp95 · latest
10s5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 870ms2026-09-21 UTC: p95 1.1s2026-09-22 UTC: p95 936ms2026-09-23 UTC: p95 1.1s2026-09-24 UTC: p95 1.0s2026-09-25 UTC: p95 762ms2026-09-26 UTC: p95 911ms2026-09-27 UTC: p95 1.1s2026-09-28 UTC: p95 846ms2026-09-29 UTC: p95 7.7s2026-09-30 UTC: p95 8.6s2026-10-01 UTC: p95 790ms2026-10-02 UTC: p95 908ms2026-10-03 UTC: p95 878ms2026-10-04 UTC: p95 968ms2026-10-05 UTC: p95 990ms2026-10-06 UTC: p95 969ms2026-10-07 UTC: p95 1.1s2026-10-08 UTC: p95 875ms2026-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.1s
Sep 20Oct 4Oct 19
US-Central
1.1sp95 · latest
10s5s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 442ms2026-09-21 UTC: p95 465ms2026-09-22 UTC: p95 896ms2026-09-23 UTC: p95 964ms2026-09-24 UTC: p95 965ms2026-09-25 UTC: p95 680ms2026-09-26 UTC: p95 934ms2026-09-27 UTC: p95 543ms2026-09-28 UTC: p95 678ms2026-09-29 UTC: p95 5.4s2026-09-30 UTC: p95 6.4s2026-10-01 UTC: p95 472ms2026-10-02 UTC: p95 399ms2026-10-03 UTC: p95 377ms2026-10-04 UTC: p95 497ms2026-10-05 UTC: p95 493ms2026-10-06 UTC: p95 435ms2026-10-07 UTC: p95 411ms2026-10-08 UTC: p95 608ms2026-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.1s
Sep 20Oct 4Oct 19
Canada
856msp95 · latest
10s5s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 720ms2026-09-21 UTC: p95 740ms2026-09-22 UTC: p95 665ms2026-09-23 UTC: p95 676ms2026-09-24 UTC: p95 554ms2026-09-25 UTC: p95 572ms2026-09-26 UTC: p95 942ms2026-09-27 UTC: p95 863ms2026-09-28 UTC: p95 1.2s2026-09-29 UTC: p95 5.3s2026-09-30 UTC: p95 7.1s2026-10-01 UTC: p95 851ms2026-10-02 UTC: p95 1.1s2026-10-03 UTC: p95 880ms2026-10-04 UTC: p95 634ms2026-10-05 UTC: p95 488ms2026-10-06 UTC: p95 487ms2026-10-07 UTC: p95 491ms2026-10-08 UTC: p95 555ms2026-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 856ms
Sep 20Oct 4Oct 19
UK
802msp95 · latest
10s5s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 565ms2026-09-21 UTC: p95 709ms2026-09-22 UTC: p95 765ms2026-09-23 UTC: p95 497ms2026-09-24 UTC: p95 900ms2026-09-25 UTC: p95 378ms2026-09-26 UTC: p95 613ms2026-09-27 UTC: p95 707ms2026-09-28 UTC: p95 628ms2026-09-29 UTC: p95 7.6s2026-09-30 UTC: p95 8.4s2026-10-01 UTC: p95 536ms2026-10-02 UTC: p95 450ms2026-10-03 UTC: p95 590ms2026-10-04 UTC: p95 502ms2026-10-05 UTC: p95 465ms2026-10-06 UTC: p95 510ms2026-10-07 UTC: p95 392ms2026-10-08 UTC: p95 610ms2026-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 802ms
Sep 20Oct 4Oct 19
Southeast Asia
2.3sp95 · latest
10s5s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 1.1s2026-09-21 UTC: p95 1.4s2026-09-22 UTC: p95 1.5s2026-09-23 UTC: p95 2.0s2026-09-24 UTC: p95 2.1s2026-09-25 UTC: p95 1.6s2026-09-26 UTC: p95 1.7s2026-09-27 UTC: p95 1.7s2026-09-28 UTC: p95 1.9s2026-09-29 UTC: p95 1.8s2026-09-30 UTC: p95 7.8s2026-10-01 UTC: p95 1.4s2026-10-02 UTC: p95 1.3s2026-10-03 UTC: p95 1.2s2026-10-04 UTC: p95 888ms2026-10-05 UTC: p95 1.4s2026-10-06 UTC: p95 1.3s2026-10-07 UTC: p95 1.3s2026-10-08 UTC: p95 1.2s2026-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.3s
Sep 20Oct 4Oct 19
Australia
2.5sp95 · latest
2.5s1.3s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 1.2s2026-09-21 UTC: p95 1.1s2026-09-22 UTC: p95 1.1s2026-09-23 UTC: p95 834ms2026-09-24 UTC: p95 881ms2026-09-25 UTC: p95 635ms2026-09-26 UTC: p95 1.2s2026-09-27 UTC: p95 1.0s2026-09-28 UTC: p95 984ms2026-09-29 UTC: p95 943ms2026-09-30 UTC: p95 2.3s2026-10-01 UTC: p95 1.1s2026-10-02 UTC: p95 1.2s2026-10-03 UTC: p95 1.2s2026-10-04 UTC: p95 1.2s2026-10-05 UTC: p95 1.2s2026-10-06 UTC: p95 1.2s2026-10-07 UTC: p95 1.3s2026-10-08 UTC: p95 1.2s2026-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.5s
Sep 20Oct 4Oct 19
South America
2.5sp95 · 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-09-20 UTC: p95 1.8s2026-09-21 UTC: p95 1.6s2026-09-22 UTC: p95 1.5s2026-09-23 UTC: p95 1.8s2026-09-24 UTC: p95 1.7s2026-09-25 UTC: p95 1.5s2026-09-26 UTC: p95 1.8s2026-09-27 UTC: p95 1.9s2026-09-28 UTC: p95 2.0s2026-09-29 UTC: p95 2.1s2026-09-30 UTC: p95 6.6s2026-10-01 UTC: p95 1.3s2026-10-02 UTC: p95 1.2s2026-10-03 UTC: p95 1.4s2026-10-04 UTC: p95 1.4s2026-10-05 UTC: p95 1.3s2026-10-06 UTC: p95 1.1s2026-10-07 UTC: p95 977ms2026-10-08 UTC: p95 1.2s2026-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.5s
Sep 20Oct 4Oct 19

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: Degraded Answering, but 1x slower than its 7-day median.Asia-Pacific: Degraded Answering, but 0.4x slower than its 7-day median.US-Central: Checks passingCanada: Checks passingUK: Degraded Answering, but 1.5x slower than its 7-day median.Southeast Asia: Degraded Answering, but 0.3x slower than its 7-day median.Australia: Degraded Answering, but 1.2x slower than its 7-day median.South America: Degraded Answering, but 0.4x slower than its 7-day median.
  • 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: 1695msstatus code: 200checked: Oct 19, 2026, 8:52 PM 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: 830msstatus code: 200checked: Oct 19, 2026, 8:52 PM 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: 951msstatus code: 200checked: Oct 19, 2026, 8:37 PM 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: 726msstatus code: 200checked: Oct 19, 2026, 8:42 PM 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
    Partially degradedlatency: 1558msstatus code: 200checked: Oct 19, 2026, 8:37 PM 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
    Partially degradedEurope, UK
    • Europe
      Partially degradedlatency: 628msstatus code: 200checked: Oct 19, 2026, 8:49 PM 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
      Partially degradedlatency: 520msstatus code: 200checked: Oct 19, 2026, 8:38 PM 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
    Partially degradedAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Partially degradedlatency: 1622msstatus code: 200checked: Oct 19, 2026, 8:52 PM 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
      Partially degradedlatency: 2011msstatus code: 200checked: Oct 19, 2026, 8:40 PM 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
      Partially degradedlatency: 1922msstatus code: 200checked: Oct 19, 2026, 8:44 PM 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>

The badge shows the share of our checks that passed over the last 30 days. 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 and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

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.

Checking a site of your own? The free website down checker sends it one request and reports the answer, and the SLA calculator shows how much downtime an uptime figure allows.

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.