Skip to content

Outage tracker / Nintendo

Is Nintendo down?

I'm having a problem

Operationalchecked 3 minutes ago

We reached Nintendo from all 10 regions we check.

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

Functional endpoints verified

Last outage: 59 min on Sep 27, 2026 (web surface, from US-East, US-Central and Canada).

Email me the next time we see Nintendo go down

Measured by our own probes from ten regions, not Nintendo's status page. One email when a measured outage opens and one when it closes, after you confirm the address. No account, no card.

our independent probeslive · checked Oct 5, 2026, 8:15 PM UTC
US-East332 msOperational
US-West270 msOperational
Europe324 msOperational
Asia-Pacific652 msOperational
US-Central121 msOperational
Canada303 msOperational
UK355 msOperational
Southeast Asia509 msOperational
Australia738 msOperational
South America508 msOperational
their status pagetheir claim, not our reading

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

Nintendo response time, by region

US-East
588msp95 · 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-06 UTC: p95 701ms2026-09-07 UTC: p95 570ms2026-09-08 UTC: p95 599ms2026-09-09 UTC: p95 709ms2026-09-10 UTC: p95 851ms2026-09-11 UTC: p95 784ms2026-09-12 UTC: p95 621ms2026-09-13 UTC: p95 713ms2026-09-14 UTC: p95 443ms2026-09-15 UTC: p95 538ms2026-09-16 UTC: p95 592ms2026-09-17 UTC: p95 675ms2026-09-18 UTC: p95 685ms2026-09-19 UTC: p95 582ms2026-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 588ms
Sep 6Sep 20Oct 5
US-West
797msp95 · 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-06 UTC: p95 635ms2026-09-07 UTC: p95 574ms2026-09-08 UTC: p95 488ms2026-09-09 UTC: p95 359ms2026-09-10 UTC: p95 343ms2026-09-11 UTC: p95 336ms2026-09-12 UTC: p95 370ms2026-09-13 UTC: p95 251ms2026-09-14 UTC: p95 242ms2026-09-15 UTC: p95 647ms2026-09-16 UTC: p95 719ms2026-09-17 UTC: p95 674ms2026-09-18 UTC: p95 823ms2026-09-19 UTC: p95 736ms2026-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 797ms
Sep 6Sep 20Oct 5
Europe
475msp95 · latest
1s500ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 363ms2026-09-07 UTC: p95 410ms2026-09-08 UTC: p95 751ms2026-09-09 UTC: p95 480ms2026-09-10 UTC: p95 599ms2026-09-11 UTC: p95 558ms2026-09-12 UTC: p95 546ms2026-09-13 UTC: p95 551ms2026-09-14 UTC: p95 442ms2026-09-15 UTC: p95 802ms2026-09-16 UTC: p95 682ms2026-09-17 UTC: p95 882ms2026-09-18 UTC: p95 821ms2026-09-19 UTC: p95 800ms2026-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 475ms
Sep 6Sep 20Oct 5
Asia-Pacific
1.0sp95 · 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-06 UTC: p95 1.2s2026-09-07 UTC: p95 662ms2026-09-08 UTC: p95 955ms2026-09-09 UTC: p95 835ms2026-09-10 UTC: p95 1.2s2026-09-11 UTC: p95 1.2s2026-09-12 UTC: p95 869ms2026-09-13 UTC: p95 1.0s2026-09-14 UTC: p95 1.2s2026-09-15 UTC: p95 892ms2026-09-16 UTC: p95 923ms2026-09-17 UTC: p95 979ms2026-09-18 UTC: p95 821ms2026-09-19 UTC: p95 778ms2026-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 1.0s
Sep 6Sep 20Oct 5
US-Central
510msp95 · 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-06 UTC: p95 677ms2026-09-07 UTC: p95 709ms2026-09-08 UTC: p95 704ms2026-09-09 UTC: p95 567ms2026-09-10 UTC: p95 574ms2026-09-11 UTC: p95 713ms2026-09-12 UTC: p95 492ms2026-09-13 UTC: p95 606ms2026-09-14 UTC: p95 681ms2026-09-15 UTC: p95 597ms2026-09-16 UTC: p95 636ms2026-09-17 UTC: p95 514ms2026-09-18 UTC: p95 469ms2026-09-19 UTC: p95 536ms2026-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 510ms
Sep 6Sep 20Oct 5
Canada
446msp95 · 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-06 UTC: p95 647ms2026-09-07 UTC: p95 547ms2026-09-08 UTC: p95 591ms2026-09-09 UTC: p95 498ms2026-09-10 UTC: p95 535ms2026-09-11 UTC: p95 504ms2026-09-12 UTC: p95 543ms2026-09-13 UTC: p95 510ms2026-09-14 UTC: p95 590ms2026-09-15 UTC: p95 667ms2026-09-16 UTC: p95 648ms2026-09-17 UTC: p95 813ms2026-09-18 UTC: p95 784ms2026-09-19 UTC: p95 803ms2026-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 446ms
Sep 6Sep 20Oct 5
UK
470msp95 · 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-06 UTC: p95 405ms2026-09-07 UTC: p95 291ms2026-09-08 UTC: p95 431ms2026-09-09 UTC: p95 401ms2026-09-10 UTC: p95 325ms2026-09-11 UTC: p95 352ms2026-09-12 UTC: p95 451ms2026-09-13 UTC: p95 493ms2026-09-14 UTC: p95 581ms2026-09-15 UTC: p95 624ms2026-09-16 UTC: p95 528ms2026-09-17 UTC: p95 613ms2026-09-18 UTC: p95 577ms2026-09-19 UTC: p95 592ms2026-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 470ms
Sep 6Sep 20Oct 5
Southeast Asia
1.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-06 UTC: p95 1.3s2026-09-07 UTC: p95 1.4s2026-09-08 UTC: p95 1.1s2026-09-09 UTC: p95 1.2s2026-09-10 UTC: p95 1.1s2026-09-11 UTC: p95 1.1s2026-09-12 UTC: p95 933ms2026-09-13 UTC: p95 1.0s2026-09-14 UTC: p95 930ms2026-09-15 UTC: p95 1.1s2026-09-16 UTC: p95 1.0s2026-09-17 UTC: p95 937ms2026-09-18 UTC: p95 1.0s2026-09-19 UTC: p95 1.0s2026-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.3s
Sep 6Sep 20Oct 5
Australia
1.2sp95 · 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-06 UTC: p95 2.0s2026-09-07 UTC: p95 1.1s2026-09-08 UTC: p95 1.3s2026-09-09 UTC: p95 1.3s2026-09-10 UTC: p95 1.3s2026-09-11 UTC: p95 1.2s2026-09-12 UTC: p95 744ms2026-09-13 UTC: p95 2.3s2026-09-14 UTC: p95 1.4s2026-09-15 UTC: p95 1.4s2026-09-16 UTC: p95 1.3s2026-09-17 UTC: p95 1.2s2026-09-18 UTC: p95 864ms2026-09-19 UTC: p95 1.2s2026-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.2s
Sep 6Sep 20Oct 5
South America
1.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-09-06 UTC: p95 2.4s2026-09-07 UTC: p95 1.5s2026-09-08 UTC: p95 1.9s2026-09-09 UTC: p95 2.4s2026-09-10 UTC: p95 2.2s2026-09-11 UTC: p95 2.2s2026-09-12 UTC: p95 2.0s2026-09-13 UTC: p95 1.4s2026-09-14 UTC: p95 1.5s2026-09-15 UTC: p95 1.7s2026-09-16 UTC: p95 1.8s2026-09-17 UTC: p95 2.0s2026-09-18 UTC: p95 1.7s2026-09-19 UTC: p95 1.4s2026-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.3s
Sep 6Sep 20Oct 5

Is it Nintendo, 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 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: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
  • APIprimaryUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
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: 332msstatus code: 200checked: Oct 5, 2026, 8:09 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
      Operationallatency: 270msstatus code: 200checked: Oct 5, 2026, 8:08 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
      Operationallatency: 121msstatus code: 200checked: Oct 5, 2026, 8:06 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
      Operationallatency: 303msstatus code: 200checked: Oct 5, 2026, 8:01 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
    Operationallatency: 508msstatus code: 200checked: Oct 5, 2026, 8:06 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
    OperationalEurope, UK
    • Europe
      Operationallatency: 324msstatus code: 200checked: Oct 5, 2026, 8:10 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
      Operationallatency: 355msstatus code: 200checked: Oct 5, 2026, 8:09 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
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 652msstatus code: 200checked: Oct 5, 2026, 8:15 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
      Operationallatency: 509msstatus code: 200checked: Oct 5, 2026, 8:02 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
      Operationallatency: 738msstatus code: 200checked: Oct 5, 2026, 8:00 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 outages

Outage, 59mmeasured by our probes · US-East and US-Central and Canada2026-09-27
Outage, 12mmeasured by our probes · Europe and US-West2026-08-31

measured 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 measurements and Nintendo's own claim at the time, side by side.

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

Put this badge in your README

Nintendo uptime measured by RealUptimeLive, from this page's own readings.
[![Nintendo uptime measured by RealUptime](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 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 Nintendo's SLA implies, from our measurement

Below your target

We measured 58 minutes of downtime for Nintendo over the last 30 days, which is 99.8642% uptime by our reading. A 99.9% target allows 43 minutes over that period.

That is 15 minutes more than the target allows. The figure above is the pro-rata share of one month's fee for the time we could not reach it. Your contract probably uses a tiered credit schedule instead, and we have not read it, so treat this as one common way to reason about a credit rather than the amount they owe.

This is computed from our own probe measurements, 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/
RealUptime is not affiliated with Nintendo; the name identifies what we measured, 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 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.