Skip to main content
Google Play logo

Is Google Play Down?

No — Google Play is up

Reachable from all 8 checked regions

Average response time: 501ms

Last checked · checks run every 6 hours

Official status page: https://status.play.google.com

Google Play uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
516ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 9 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

9-day clean streak
Aug 22: no data
Aug 23: no data
Aug 24: no data
Aug 25: no data
Aug 26: no data
Aug 27: no data
Aug 28: no data
Aug 29: no data
Aug 30: no data
Aug 31: no data
Sep 1: no data
Sep 2: no data
Sep 3: no data
Sep 4: no data
Sep 5: no data
Sep 6: no data
Sep 7: no data
Sep 8: no data
Sep 9: no data
Sep 10: no data
Sep 11: no data
Sep 12: 100.00% uptime, 16 checks
Sep 13: 100.00% uptime, 24 checks
Sep 14: 100.00% uptime, 32 checks
Sep 15: 100.00% uptime, 32 checks
Sep 16: 100.00% uptime, 31 checks
Sep 17: 100.00% uptime, 31 checks
Sep 18: 100.00% uptime, 32 checks
Sep 19: 100.00% uptime, 32 checks
Sep 20: 100.00% uptime, 16 checks
Aug 22 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams
575ms
DNS 26ms TCP 1ms TLS 6ms TTFB 86ms
arn
688ms
DNS 23ms TCP 1ms TLS 13ms TTFB 88ms
bom
735ms
DNS 86ms TCP 2ms TLS 7ms TTFB 205ms
cdg
455ms
DNS 17ms TCP 1ms TLS 17ms TTFB 84ms
dfw
265ms
DNS 13ms TCP 2ms TLS 6ms TTFB 79ms
ewr
266ms
DNS 68ms TCP 6ms TLS 15ms TTFB 142ms
syd
718ms
DNS 159ms TCP 1ms TLS 111ms TTFB 408ms
yyz
312ms
DNS 39ms TCP 1ms TLS 32ms TTFB 142ms

What Google Play does

Google Play is the app store and digital storefront on Android devices, handling app discovery, installs and updates, in-app purchases and subscription billing. Almost every Android app depends on it for distribution and for payments. Google publishes a status dashboard for Play, but it is marked beta and covers developer-facing products rather than the consumer store.

What an outage looks like

Apps fail to install or update, with downloads stalling instead of returning an error. In-app purchases are declined or take payment without granting the item, and subscriptions fail to renew. Developers see the Publishing API reject uploads, and Play Integrity API verdicts stop returning, which locks users out of apps that gate access on an integrity check.

What to do about it

Read status.play.google.com, but read it for what it covers: the dashboard is in beta and reports Play Billing Purchases, the Developer Subscriptions and In-App Purchases API, Play Integrity, Subscriptions Renewal and Management, Voided Purchases and the Publishing API. It does not track the consumer store, so an app that will not install can fail while the page shows no incidents.

Is it down for everyone, or just you?

If this page says Google Play is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 18 cities across three regions to find out where it breaks.

Test it yourself

Related services

Firebase
Firebase
Google Workspace
Google Workspace
P
PlayStation Network
R
Roblox

Google Play outage FAQ

The Google Play dashboard says no incidents, so why will my app not install?
Because the dashboard does not measure the part of Play you are using. Google's status page is marked beta and covers developer products: Play Billing Purchases, the Developer Subscriptions and In-App Purchases API, Play Integrity, Subscriptions Renewal and Management, Voided Purchases and the Publishing API. App discovery, installs and updates on the consumer store are not among its rows, so a store-side problem can leave every listed component green.
Is Google Play down for everyone or just me?
Check scope before assuming either. A problem confined to one device or one account often clears on its own and points at local state rather than at Google. If several devices on different networks and different accounts fail the same way, the cause is more likely upstream. The uptime history on this page shows what our probes measured from multiple regions, which is a different signal from a single device's experience.
Will a Play outage affect apps I have already installed?
Mostly no, with one exception worth knowing. Installed apps run from your device and do not call Play to launch. The exception is anything that checks Play at runtime: apps using in-app purchases or subscriptions may fail at the payment step, and apps that gate access on the Play Integrity API can refuse to start when integrity verdicts stop returning. Everything else generally keeps working.
Does a Play outage stop my purchase or subscription from going through?
It can, and the two failure shapes differ. Play Billing Purchases and Subscriptions Renewal and Management are separate components on Google's dashboard, so a new purchase can fail while existing subscriptions renew normally, or the reverse. If a payment was taken but the item never arrived, avoid buying again: a duplicate charge is harder to unpick than a delayed entitlement, and Google reports Voided Purchases as its own component.
Does a Google Play outage mean other Google services are down?
Not necessarily. Play runs on Google's infrastructure alongside Gmail, Drive and Google Cloud, but it is operated and reported separately, so a Play problem does not imply a wider Google outage and a Workspace incident does not imply Play is affected. Treat each as its own dependency. If several Google properties fail at once the shared layer is more likely, but that is an observation to make rather than assume.

How we measure this

  • We request Google Play's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Google Play publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Google Play goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 18 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required