Skip to main content
If you click on a link and make a purchase we may receive a small commission. Read our editorial policy.

Pokemon Go Down: June maintenance downtime and return time

Even evergreen, constant games need a little bit of TLC every now and then - which is why Pokemon Go is currently down.

The severs for Pokemon Go will be offline globally today, Monday June 1st 2020 - and it'll be down for quite a while. The game will be offline for seven hours total.

Due to the nature of the way Pokemon Go plays, during this downtime you won't be able to play Pokemon Go at all. That also means if you haven't completed daily tasks to do things like keep up your streaks or turn in field missions, you'll lose your chance if you haven't done so when the downtime begins.

It's long-overdue maintenance - this is the first full-game downtime for Pokemon Go since 2017. That might explain the length of this downtime, which is pretty extensive. If you're on the game when the downtime kicks in, you will be disconnected - you've been warned.

Pokemon Go Downtime: Maintenance schedule for June 2020

If you've come to this page just because you're screaming "Pokemon Go down?!" after trying to log in, have no fear. It's not broken. It's temporary, and has a defined end time (though don't be surprised if downtime overruns a bit - these things tend to). Here's what time the maintenance begins in each territory, plus when Pokemon Go will be back.

  • UK Time: 7pm (Jun 1st) until 2am (Jun 2nd)
  • Central Europe: 8pm (Jun 1st) until 3am (Jun 2nd)
  • Eastern US/NA: 2pm until 2pm (Jun 1st)
  • Western US/NA: 11am until 6pm (Jun 1st)
  • Australia: 4am until 11am (Jun 2nd)

Developer Niantic hasn't given any specific reason for why Pokemon Go is going down, but any game needs to have its servers given some love and attention every now and then in order to keep them ticking over - and if we're lucky, updates like this can also lead to new features. Niantic isn't being drawn, however, and is simply apologizing for any inconvenience.

Read this next