Is Google Play Down?

No — Google Play is up

Google Play's status page: Not available · we could not read it
FlareWarden checks: Website reachable · 8 of 8 regions · 588 ms

Right now

We could not read Google Play's status page, so the verdict rests on our checks. Check it yourself How we decide

FlareWarden checks

play.google.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable

Regions up: 8 of 8
Response: 588 ms
Checked: 1 hour ago

By region

Chicago reachable, 729 ms
Johannesburg reachable, 1269 ms
London reachable, 410 ms
Los Angeles reachable, 402 ms
San Jose reachable, 227 ms
Singapore reachable, 349 ms
Sydney reachable, 958 ms
Tokyo reachable, 363 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Chicago	187 ms	19 ms	22 ms	314 ms
Johannesburg	206 ms	1 ms	170 ms	614 ms
London	62 ms	3 ms	9 ms	152 ms
Los Angeles	23 ms	11 ms	14 ms	131 ms
San Jose	54 ms	2 ms	20 ms	116 ms
Singapore	8 ms	2 ms	4 ms	39 ms
Sydney	244 ms	2 ms	114 ms	515 ms
Tokyo	7 ms	1 ms	7 ms	86 ms

We check that play.google.com loads, not every feature behind it. Test it yourself

History

Google Play website availability

Measured by FlareWarden · play.google.com

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 597ms

Last 30 days

55-day clean streak

Oct 7 Today

No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of play.google.com from multiple regions every 6 hours. Google Play's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 55 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

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 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

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. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
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. Our checks only change their 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, and the verdict is the worse of what it reports and what our checks see: a major outage of Google Play itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. A reading counts for 45 minutes; we read the feed again within minutes of any change to its incidents. The availability figures above are our measurement alone.

Get alerted when Google Play goes down

We check Google Play every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required