Skip to content

Outage tracker / Nintendo / In the US

Is Nintendo down in the US?

Checks passingin the US, measured from Ashburn, San Jose, and Chicago

All 3 of our probes in the US, in Ashburn, San Jose, and Chicago, read checks passing when they last checked Nintendo at Nov 7, 2026, 11:27 AM UTC.

Over the last 24 hours we completed 325 checks from Ashburn, San Jose, and Chicago and 325 answered cleanly, 100.00% availability.

Of the 7 other regions we check Nintendo from, all 7 read checks passing right now.

Email me the next time we see Nintendo go down

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.

What our Ashburn, San Jose, and Chicago probes measured

AshburnChecks passing141 checks in 24h, 100.00%
San JoseChecks passing113 checks in 24h, 100.00%
ChicagoChecks passing71 checks in 24h, 100.00%

Last checked Nov 7, 2026, 11:27 AM UTC.

Nintendo from Ashburn, San Jose, and Chicago over the last 30 days

Over the last 30 days, Nintendo answered our Chicago probe in 804 ms on average, and 1 check in 20 took longer than 1,105 ms.

Over the last 30 days, Nintendo answered our San Jose probe in 909 ms on average, and 1 check in 20 took longer than 1,335 ms.

Over the last 30 days, Nintendo answered our Ashburn probe in 931 ms on average, and 1 check in 20 took longer than 1,342 ms.

Ranked by average response time across the 10 cities we check Nintendo from, Chicago 3rd, San Jose 5th, Ashburn 6th; Frankfurt was fastest at 498 ms and São Paulo slowest at 1,746 ms.

From Ashburn, San Jose, and Chicago we ran 10,387 checks of Nintendo in 30 days, and 10,384 answered cleanly: 99.97% availability.

2 of the 30 days had at least one failed check. The weakest was Nov 3 (UTC), at 99.36% across 316 checks.

In Ashburn local time (EST), Nintendo was slowest around 5 PM, at 1,351 ms on average over the last 14 days, and quickest around 11 AM, at 1,025 ms.

Day (UTC)ChecksAvailabilityAverage response
Sat, Nov 7153100.00%1,098 ms
Fri, Nov 6321100.00%1,102 ms
Thu, Nov 5318100.00%1,100 ms
Wed, Nov 4319100.00%975 ms
Tue, Nov 331699.36%1,124 ms
Mon, Nov 2339100.00%1,067 ms
Sun, Nov 1360100.00%1,148 ms
Sat, Oct 31359100.00%1,161 ms
Fri, Oct 30359100.00%1,087 ms
Thu, Oct 29360100.00%1,140 ms
Wed, Oct 28358100.00%1,157 ms
Tue, Oct 27359100.00%1,206 ms
Mon, Oct 26359100.00%1,379 ms
Sun, Oct 2535999.72%1,223 ms

Nintendo outages measured from the US

1 confirmed Nintendo outage reached our Ashburn, San Jose, and Chicago probes in the last 90 days, in the US's local time:

  • Aug 31, 2026, 10:18 AM PDT, from San Jose: 10 minutes

How the other regions read right now

Of the 7 other regions we check Nintendo from, all 7 read checks passing right now.

Probe cityRight nowLast 24h
FrankfurtChecks passing100.00% of 103 checks
TokyoChecks passing100.00% of 60 checks
TorontoChecks passing100.00% of 71 checks
LondonChecks passing100.00% of 71 checks
SingaporeChecks passing100.00% of 71 checks
SydneyChecks passing100.00% of 71 checks
São PauloChecks passing100.00% of 71 checks

Other countries we check Nintendo from

How we measured this

The US readings on this page come from RealUptime's own Ashburn, San Jose, and Chicago probes against Nintendo's public endpoints. They are not user reports, and they are not Nintendo's own status page.

See Nintendo's full check readings, the 90-day history by region, or the outage tracker methodology.

Check your own site from Ashburn

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

Run a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter