Pokémon GO suffered a widespread outage on Friday, August 14, leaving tens of thousands of players unable to launch the game, sign in or use location-based features normally.

Downdetector reports passed 20,000 at around 3:27 p.m. PT, climbed above 40,000 by about 3:53 p.m. and exceeded 53,000 by approximately 4:13 p.m. PT. The rapid increase pointed to a broad service disruption rather than an isolated problem with a particular phone or internet connection.

Players reported several symptoms, including the game failing to launch, login problems, “Network Error (2)” and GPS-related errors. The timing added urgency because Pokémon GO’s Nickit Community Day is scheduled for Sunday, August 16.

What happened during the Pokémon GO outage?

The outage developed quickly on Friday afternoon. More than 20,000 problems had been reported to Downdetector by 3:27 p.m. PT, before reports more than doubled and eventually passed 53,000.

One snapshot of outage data showed approximately 62% of complaints involving game-launch problems, around 23% related to login and roughly 13% categorized as server issues.

Downdetector numbers are not an exact count of everyone affected. They represent reports submitted by users and other signals, meaning many players experiencing problems may never appear in the total. The unusually rapid increase is more useful for showing the scale and timing of a disruption.

Why are players seeing Network Error 2 and GPS errors?

Network Error 2 can appear when Pokémon GO cannot communicate properly with the online services it needs. Although an individual network error can sometimes involve Wi-Fi, mobile data or a player’s device, thousands of similar complaints arriving together suggest a wider service problem.

Players should therefore avoid immediately resetting passwords, reinstalling the game or making major account changes when outage reports are surging.

GPS errors require slightly different troubleshooting because Pokémon GO depends heavily on real-world location. Phone permissions, weak GPS reception or device settings can cause location failures. However, when GPS complaints appear alongside widespread launch and login failures, checking the game’s broader status should come first.

Similar authentication problems have affected other online games, where authentication and online-play services stopped working despite players having functioning internet connections.

Scopely acknowledged the disruption

Early reports said there had been no official acknowledgement of the outage, but that changed as the incident developed. Scopely Explore Support subsequently said it was investigating an issue affecting Pokémon GO gameplay and was working to resolve it.

That update is important because it confirmed the problem was being investigated at the service level. Players checking older reports should remember that outage stories can become outdated quickly as companies acknowledge problems and services begin recovering.

Is Pokémon GO still down today?

The major spike in reports occurred on August 14. Service conditions can change rapidly during an outage and recovery may not happen simultaneously for every player or region.

If Pokémon GO still refuses to load, players should first check whether other apps work, try Wi-Fi and mobile data, restart the game and confirm they have the latest version installed. Location permissions should also be checked when GPS errors persist.

If thousands of fresh outage reports are appearing at the same time, repeatedly reinstalling the application is unlikely to fix a service-side problem.

Why Nickit Community Day makes the timing important

Pokémon GO’s official Nickit Community Day announcement schedules the event for Sunday, August 16, from 2:00 p.m. to 5:00 p.m. local time.

Nickit is scheduled to appear more frequently in the wild, while players will have opportunities to encounter Shiny Nickit. Event bonuses include 3× catch Stardust, 2× catch Candy and an increased chance for Trainers level 31 and above to receive Candy XL.

Players who evolve Nickit during the event or within the specified period afterward can obtain a Thievul that knows the Charged Attack Icy Wind.

Because Community Day activities operate within limited local-time windows, stable server access matters more than on an ordinary day. Players should not assume, however, that Friday’s outage will result in compensation, an event extension or replacement bonuses unless Pokémon GO announces them officially.

Was AWS responsible for the outage?

There is currently no verified information in the provided reporting establishing Amazon Web Services as the cause of Friday’s disruption.

An October 2025 AWS failure previously affected multiple major games and online platforms, demonstrating how cloud infrastructure problems can spread across seemingly unrelated services. Readers can see the broader impact in our coverage of an AWS outage that disrupted multiple online services.

That previous incident does not prove AWS was responsible for this Pokémon GO outage. Without an official technical explanation, attributing the August 14 disruption to AWS, GPS infrastructure or another specific system would be speculation.

What should Pokémon GO players do now?

Players experiencing problems should check official Pokémon GO updates alongside current outage-report trends before changing their account or device settings. If other internet services work and large numbers of players are reporting the same error, waiting for service recovery may be more useful than reinstalling the game.

Players preparing for Nickit Community Day should open Pokémon GO before their local 2:00 p.m. start time and confirm that login, GPS and map functions are operating normally.

The key figure from Friday is not simply “53,000 players.” Downdetector does not measure every affected account. What matters is that reports rose from more than 20,000 to above 53,000 in less than an hour, providing a strong indication of the scale of the disruption.