Is Google Analytics Down?

No — Google Analytics is up

Reachable from all 8 checked regions

Average response time: 563ms

Last checked 3 hours ago · checks run every 6 hours

Official status page: https://ads.google.com/status/publisher/

Google Analytics uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

490ms

Avg response, 30 days

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

30-day history

58-day clean streak

Sep 14 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.

lax

213ms

DNS 0ms TCP 10ms TLS 14ms TTFB 213ms

lhr

496ms

DNS 0ms TCP 2ms TLS 6ms TTFB 494ms

nrt

789ms

DNS 0ms TCP 1ms TLS 6ms TTFB 789ms

ord

117ms

DNS 0ms TCP 1ms TLS 14ms TTFB 117ms

sin

1011ms

DNS 0ms TCP 2ms TLS 4ms TTFB 1006ms

sjc

486ms

DNS 0ms TCP 27ms TLS 39ms TTFB 483ms

syd

1278ms

DNS 0ms TCP 0ms TLS 109ms TTFB 1275ms

yyz

115ms

DNS 1ms TCP 1ms TLS 25ms TTFB 114ms

What Google Analytics does

Google Analytics measures traffic and conversions for websites and apps, and it is where most marketing teams check whether a campaign or a release did anything. It also feeds bid decisions in Google Ads and dashboards elsewhere. Because collection and reporting are separate systems, the site can be unreachable while your pages are still quietly sending data.

What an outage looks like

The Analytics interface fails to load or throws an error after sign-in. Realtime shows zero active users on a site that is plainly getting traffic. Reports load but come back empty, or figures for recent hours are missing and fill in later. Exports and scheduled emails arrive incomplete. Data collection usually keeps running through interface outages, so a gap often backfills.

What to do about it

Google reports Analytics on the Google Ads Status Dashboard at ads.google.com/status/publisher, alongside Google Ads, Ad Manager and Campaign Manager 360. Check there rather than the Workspace dashboard, which covers different products. If collection is unaffected, wait rather than re-tagging pages: changing tags during an incident risks double-counting once reporting recovers. Verify your tag is firing with browser developer tools.

Is it down for everyone, or just you?

If this page says Google Analytics 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 Analytics outage FAQ

Am I losing data during a Google Analytics outage?

Often not. Collection and reporting are separate systems, so tags on your site can keep delivering hits while the reporting interface is broken, and the numbers appear once processing catches up. Reporting delays of a few hours are common after an incident. A genuine collection outage does lose the hits sent during it, and those do not backfill later.

Does an Analytics outage affect Google Ads?

It can, because they sit on the same platform and the same status dashboard. Ads campaigns keep serving during Analytics incidents, but imported conversions and audiences that flow from Analytics into Ads can stall, which affects smart bidding decisions that depend on recent conversion data. Check whether Google Ads is listed separately on the dashboard before assuming one caused the other.

Realtime shows zero users. Is my tracking code broken?

Check the tag before assuming an outage. Open your site with browser developer tools and watch for the request to Google's collection endpoint: if it fires and returns a success code, your tag is fine and the problem is upstream. If nothing fires, the cause is on your side, usually a consent banner blocking the tag, a deploy that dropped it, or a container that failed to publish.

How long do Google Analytics incidents usually last?

Interface and reporting incidents are typically measured in hours, and the dashboard records start and resolution times for each one so you can see the pattern. Processing lag frequently outlives the incident itself, so reports can stay incomplete for a while after the status entry closes. Treat missing recent hours as unfinished rather than lost until a day or so has passed.

How we measure this

We request Google Analytics'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 Analytics 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 Analytics goes down

This page refreshes every 6 hours. 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