Google Play outages and problems
In the past 24 hours, 57 user reports came in for Google Play. Counting only the 15-minute windows with a spike big enough to count as an outage, that comes to 100.00% uptime for the day.
The busiest 15-minute window had 4 reports, about 6 hours ago. That stays below our outage threshold, so it doesn't count as downtime.
What people can report about Google Play
What went wrong
What people said was wrong in recent problem reports for Google Play worldwide.
Share of 31 recent reports that said what was wrong, from every country listed below.
Google Play reports around the world
In the last 24 hours, 235 problem reports about Google Play came in from 28 countries. Right now reports are at the usual level in every country.
- Outage now
- Problems now
- Normal
| Country | Now | Last hour | 24 hours |
|---|---|---|---|
| The US numbers above | Normal | 5 | 59 |
| Poland | Normal | 4 | 91 |
| Bangladesh | Normal | 2 | 14 |
| Sweden | Normal | 2 | 2 |
| South Africa | Normal | 1 | 3 |
| Brazil | Normal | 0 | 13 |
| Japan | Normal | 0 | 8 |
| The UK | Normal | 0 | 5 |
| Germany | Normal | 0 | 4 |
| Canada | Normal | 0 | 3 |
| Mexico | Normal | 0 | 3 |
| The Philippines | Normal | 0 | 3 |
Each country's status compares its reports with the usual level there. 60 more countries had 27 reports in the last 24 hours. Map outlines: Natural Earth.
Google Play problem spikes, last 30 days
Since 6 October, Google Play had 1 outage spike and 1 period of elevated reports. The longest lasted 51 min, on 28 October.
- Sat 3 Oct: no data
- Sun 4 Oct: no data
- Mon 5 Oct: no data
- Tue 6 Oct: 1 report
- Wed 7 Oct: 0 reports
- Thu 8 Oct: 0 reports
- Fri 9 Oct: 9 reports
- Sat 10 Oct: 0 reports
- Sun 11 Oct: 1 report
- Mon 12 Oct: 2 reports
- Tue 13 Oct: 1 report
- Wed 14 Oct: 0 reports
- Thu 15 Oct: 0 reports
- Fri 16 Oct: 1 report
- Sat 17 Oct: 0 reports
- Sun 18 Oct: 0 reports
- Mon 19 Oct: 2 reports
- Tue 20 Oct: 1 report
- Wed 21 Oct: no data
- Thu 22 Oct: 0 reports
- Fri 23 Oct: 0 reports
- Sat 24 Oct: 0 reports
- Sun 25 Oct: 0 reports
- Mon 26 Oct: 0 reports
- Tue 27 Oct: 2 reports
- Wed 28 Oct: 13 reports (outage spike that day)
- Thu 29 Oct: 52 reports
- Fri 30 Oct: 58 reports
- Sat 31 Oct: 57 reports
- Sun 1 Nov: no data
-
Outage
Wed 28 Oct, 10:26–11:17Lasted 51 min49peak reports
-
Elevated reports
Wed 28 Oct, 08:11–08:31Lasted 21 min10peak reports
By country
Each square is one day in the countries with the most reports: red when reports stayed at outage level for half an hour or more, amber when they stayed above the usual level for an hour or more, grey otherwise.
- Poland316
- The US142
- Brazil38
- Japan21
- Bangladesh15
- Pakistan13
- Canada12
- The UK11
Country history starts on 29 October 2026. Days run from midnight to midnight, Central European time.
A spike is a sharp rise in problem reports from users, kept exactly as this page showed it at the time. This history starts on 6 October 2026. Monthly reports for all services
How to fix Google Play not working
Google Play is up on our end, so if it won't work for you, the problem is most likely on your side. Work through these in order:
Your browser tries to reach play.google.com over your own connection, right now. Nothing is sent to us or stored.
Test Play Store connection
Open a web page or another app that needs data. If nothing loads, switch between Wi-Fi and mobile data, then turn airplane mode on and off to force a fresh connection; if other apps load, the problem is likely with the Play Store app rather than your network.
Fix Play Store clock settings
Open Settings, open System, then Date & time, and turn on Set time automatically and Set time zone automatically. On Samsung phones, look under General management instead of System. Wrong clock settings can stop the Play Store from making secure connections.
Clear Play Store cache
Use Settings to open Apps, open Google Play Store, then Storage & cache, and tap Clear cache; if your phone shows See all apps, use that list to find the store first. Reopen the app and try the download again, because a damaged cache can leave the store stuck on loading.
Clear Play Store storage
The same Apps screen leads to Google Play Store, so open it, go to Storage & cache, and tap Clear storage; if your phone shows See all apps, use that list to find the store first. Reopen the app and sign in if asked, since this resets local data but leaves installed apps alone.
Common Google Play error messages
What each message means and what to try. The wording can differ a little between app versions.
-
Error retrieving information from server. [DF-DFERH-01]
- Means
- The app could not load account or store data from Google's servers.
- Fix
- Check your internet connection, then clear the app's cache and reopen it. If the message returns, remove your Google account from the device and add it again.
-
Your device isn't compatible with this version.
- Means
- The app requires hardware or software your device does not have.
- Fix
- Check the app's listed Android version and device requirements. If your device falls short, install it on a supported device or look for a compatible alternative.
-
This item isn't available in your country.
- Means
- The app or content is restricted to certain countries.
- Fix
- There is no setting in the app that changes this. Use an account from a supported country, or pick something else.
While Google Play is down: what to use instead
- Google Play website If the app will not open, use the Google Play website in a browser to browse apps and manage your account.
- Google Play Games on PC If a game is available there, install and play it on a Windows PC while your phone has trouble.
- Amazon Appstore Check for the app there if you have an Android device that supports the store.
- App Store On an iPhone or iPad, look for the same app in Apple’s App Store.
Fix Google Play on Windows, Mac, Android and iPhone
Google Play on Windows
- Fix
- Clear your web browser's cache and cookies, or restart the Google Play Games app if you are using the PC beta client. Ensure your Windows firewall is not blocking Google Play network traffic.
- Check
- Try loading the Google Play website in an incognito browser window to see if it loads. You can also check if the Google Play Games client displays connection errors.
ping play.google.comTest whether Google Play's servers replynslookup play.google.comCheck that Google Play's DNS resolvestracert play.google.comTrace where the connection dropsipconfig /flushdnsClear the DNS cache, then reloadGoogle Play on Mac
- Fix
- Clear your Safari or Chrome browser cache and cookies to resolve web access issues with Google Play. Ensure your Mac's system date and time are correct to prevent SSL connection errors.
- Check
- Attempt to load the Google Play store website in a different web browser on your Mac. Check if other Google services are functioning, which can indicate a wider Google outage.
ping -c 4 play.google.comTest whether Google Play's servers replynslookup play.google.comCheck that Google Play's DNS resolvestraceroute play.google.comTrace where the connection dropssudo dscacheutil -flushcache; sudo killall -HUP mDNSResponderFlush the macOS DNS cache, then reloadGoogle Play on Android
- Fix
- Go to Settings > Apps > Google Play Store and select Clear Cache and Clear Data. Restart your Android device and verify that your Google account is properly synced.
- Check
- Open the Google Play Store app to see if it loads the home screen or shows a connection error. Try downloading a free app to verify if the Google Play servers are responding.
Google Play on iPhone and iPad
- Fix
- If using Google Play apps like Google Play Books, force close the app and restart your iPhone or iPad. For web access, clear your mobile browser's history and website data.
- Check
- Try signing into the Google Play website via Safari or Chrome on your iOS device. Check if your Google Play companion apps can refresh and sync your library.
Problems at the same time as Google Play
Since 6 October, all 2 of Google Play's spikes in problem reports overlapped a spike at another service.
When several services get problem reports at once, something they share, such as a cloud host or a network, can be the real cause. Matching times alone do not prove it.
Most often at the same time
- ESPN Fantasy Football2 times
- Spectrum2 times
- Telkom2 times
- Discord2 times
- NBN (National Broadband Network)2 times
- Telstra2 times
How many of Google Play's spikes overlapped one of theirs.
During the latest spike
Google Play: Wed 28 Oct, 10:26 to 11:17
- ESPN Fantasy Football, outage,27 Oct 19:50 to 30 Oct 05:40
- Spectrum, outage,06:55 to 12:19
- Sunrise, outage,08:33 to 11:34
- TalkTalk, outage,08:44 to 21:15
- Telkom, outage,09:13 to 10:33, 10:55 to 11:36
- NBN (National Broadband Network), outage,09:35 to 11:11
- NHS England, outage,09:35 to 10:43
- Nationwide, outage,09:35 to 12:30
34 more services. Red dot: outage. Amber dot: elevated reports.
A spike is a sharp rise in problem reports from users, as the live pages showed it. Times are Central European time.
When people report Google Play problems
The busiest hour for reports about Google Play is 04:00 to 05:00 Central European time, and the busiest day is Friday.
By hour of the day
- 00:00 to 01:00: 0.37 reports on an average day
- 01:00 to 02:00: 0.17 reports on an average day
- 02:00 to 03:00: 0.31 reports on an average day
- 03:00 to 04:00: 0.42 reports on an average day
- 04:00 to 05:00: 0.66 reports on an average day
- 05:00 to 06:00: 0.34 reports on an average day
- 06:00 to 07:00: 0.24 reports on an average day
- 07:00 to 08:00: 0.08 reports on an average day
- 08:00 to 09:00: 0.15 reports on an average day
- 09:00 to 10:00: 0.41 reports on an average day
- 10:00 to 11:00: 0.24 reports on an average day
- 11:00 to 12:00: 0.17 reports on an average day
- 12:00 to 13:00: 0.31 reports on an average day
- 13:00 to 14:00: 0.39 reports on an average day
- 14:00 to 15:00: 0.26 reports on an average day
- 15:00 to 16:00: 0.13 reports on an average day
- 16:00 to 17:00: 0.49 reports on an average day
- 17:00 to 18:00: 0.31 reports on an average day
- 18:00 to 19:00: 0.49 reports on an average day
- 19:00 to 20:00: 0.52 reports on an average day
- 20:00 to 21:00: 0.44 reports on an average day
- 21:00 to 22:00: 0.58 reports on an average day
- 22:00 to 23:00: 0.36 reports on an average day
- 23:00 to 00:00: 0.31 reports on an average day
By day of the week
- Monday: 1.2 reports on an average Monday
- Tuesday: 1.3 reports on an average Tuesday
- Wednesday: 4.4 reports on an average Wednesday
- Thursday: 17 reports on an average Thursday
- Friday: 17 reports on an average Friday
- Saturday: 14 reports on an average Saturday
- Sunday: 0.33 reports on an average Sunday
Each bar is the average number of user reports in that hour, or on that day of the week, from 24 days of reports since 5 October 2026. The busiest bar is highlighted. Spikes in reports are left out, so one outage does not set the pattern.
What happens when Google Play goes down
Google Play is the Google store at play.google.com for Android apps and games, used mostly in the US, and Android owners and people buying those apps rely on it. An outage interrupts installs, updates, purchases, and access to owned content.
An outage usually hits downloads and updates first, so a tap on Install can sit on Pending or fail with a server error, and update checks may return the same message. Purchases and subscriptions often hang at the payment sheet, while your library or installed-app list may stop refreshing even when the store home page still loads. Partial failures are common. One country or one payment method can fail while other parts of the store keep working, and the report level at the top shows whether user problem reports are above their usual level, counted in 15-minute windows over the last 24 hours; those reports go to a public outage-reporting service, and this site does not probe or monitor the service, nor does it collect reports itself; for Google's own health notes, check the official status page, and for account or payment help, use the help centre.
Google Play IP address, servers and network
- IPv4 addresses
- 142.251.150.7
Show all 8
- 142.251.151.7
- 142.251.152.7
- 142.251.153.7
- 142.251.154.7
- 142.251.155.7
- 142.251.156.7
- 142.251.157.7
- IPv6 addresses
- 2001:4860:4826:700::
Show all 8
- 2001:4860:4827:700::
- 2001:4860:4828:700::
- 2001:4860:4829:700::
- 2001:4860:482a:700::
- 2001:4860:482b:700::
- 2001:4860:482c:700::
- 2001:4860:482d:700::
- Network
- AS15169 · Google LLC, registered in the United States
- Served through
- DNS hosted by
- its own name servers (nip.io)
- HTTPS certificate
- Issued by Google Trust Services, valid until 30 Dec 2026 (59 days)
- HTTP/3
- Supported
- Our check
- Answered in 525 ms
Checked from our server in Frankfurt, Germany, 24 h ago, for play.google.com. A service behind a CDN answers from many data centres, usually the one nearest to you, so these addresses are where its traffic enters, not where its own servers stand. Visitors elsewhere may see different addresses.
Checked from 11 places around the world
All 11 locations got an answer from play.google.com. Fastest from Singapore (26 ms), slowest from Madrid (144 ms). Every location connected through Google LLC (AS15169), using 7 different addresses.
| Location | Result | Time | Address reached |
|---|---|---|---|
| FrankfurtGermany | Up · HTTP 302 | 37 ms | 142.251.151.7 |
| ViennaAustria | Up · HTTP 302 | 92 ms | 142.251.153.7 |
| MilanItaly | Up · HTTP 302 | 93 ms | 142.251.151.7 |
| ParisFrance | Up · HTTP 302 | 56 ms | 142.251.157.7 |
| AmsterdamNetherlands | Up · HTTP 302 | 96 ms | 142.251.152.7 |
| MadridSpain | Up · HTTP 302 | 144 ms | 142.251.155.7 |
| WarsawPoland | Up · HTTP 302 | 125 ms | 142.251.150.7 |
| Los AngelesUSA | Up · HTTP 302 | 46 ms | 142.251.151.7 |
| São PauloBrazil | Up · HTTP 302 | 134 ms | 142.251.157.7 |
| SingaporeSingapore | Up · HTTP 302 | 26 ms | 142.251.152.7 |
| TokyoJapan | Up · HTTP 302 | 62 ms | 142.251.154.7 |
Checked with check-host.net from its servers in these cities 24 h ago, for play.google.com. Time is how long each server took to load the page.
Google Play FAQ
Is Google Play down right now?
Why does the Play Store show 'Your device isn't compatible with this version'?
Why did my Play Store purchase fail with a payment error?
Why does Google Play keep stopping on my phone?
Can I install an app that Google Play says is unavailable in my country?
Service updates from @GooglePlay
No posts about problems from @GooglePlay in the last 14 days. The latest is from .
How we track Google Play
The status on this page comes from user-submitted problem reports for Google Play, counted in 15-minute windows over the last 24 hours. Each window is compared with the normal level for Google Play, so a few complaints on a quiet day don't trigger anything, but a sudden jump well above normal does.
When reports climb well above normal, the status here changes to partial outage or major outage and the chart moves with it. This is separate from Google Play's official status page: user reports tend to show a problem early, while the official page confirms the cause. If the two disagree, check both.