Google Analytics Is Down? Current Problems, Outages and Solutions

Google Analytics outages reported in the last 24 hours

Report a problem with Google Analytics

Today, , outages were reported:

0

Yesterday, , outages were reported:

0

In the chart you can see the reported outages and errors of the app and the web version of Google Analytics. If Google Analytics is not working for you, or you’re experiencing errors that make the service essentially unusable, or you’re sure the measurement is flawed, use the button above the chart to let others know they’re not alone.

Then, if you have a specific problem, let them know in the comments at the bottom of the page. Other users who may have also encountered the problem and know what’s behind it can help.

Reporting services that aren’t working also helps other users who know that the fault isn’t with their device, so they don’t have to try to fix it by turning off other apps or changing various settings.

Quick availability check of analytics.google.com

Check the status of Google Analytics

Here you can check the availability of “https://analytics.google.com/”, the web version of Google Analytics.

The check will be successful if we can connect to the website that loads within a few seconds after clicking the button. If the site returns an error or the connection takes too long, the check will fail.

Please note that we only check the functioning and loading of the website itself, not the mobile apps or any other functionality. Nor do we check for faulty metering or any other features.

So if you encounter any error on an otherwise functional site, please let us know about it using the button at the top of this page, and you can describe the error in more detail in the comments below.

This is a better way to keep track of other users’ reported outages and errors, as well as responses in the comments, which are more likely to show that the errors happened somewhere on the Google Analytics side, and thus the error is not on your device.

What can go wrong with Google Analytics

Google Analytics is the most powerful analytics service in the world, allowing you to find out basically everything there is to know about traffic and interaction with your website or app. Unlike most of its competitors, it’s completely free with everything it offers.

That’s also why it’s the most widely used analytics tool of its kind in the world, and it’s a cut above any competition.

But that doesn’t mean that Google Analytics doesn’t stop working now and then too. A mistake can happen on the side of Google, which manages the application, but also in a wrong setting on our side.

Before you start fixing anything, we recommend using the page with a list of known outages or completely broken Google Ads services (under which Analytics falls). If you see that Google Analytics is orange or red, it means that the service is limited or completely unavailable, and that Google is aware of this outage. At this point, there’s not much we can do to fix it, and we just need to wait.

Download links for Google Analytics for phones and tablets

The web version is the strongest, offering all the features and services. The mobile app mainly offers quick overviews of the essentials, but this can be useful for quickly checking if your site or app is running as it should.

So if you want to take advantage of all the features, the browser is better. If you want quick overviews on your phone and tablet as well, you can use the Android or iOS apps:

How to fix potential problems with Google Analytics

Every now and then, a bug in the app (often accompanied by a mismeasurement in Google AdSense, for example) will occur, but sometimes a problem on our end is to blame for Google Analytics not working. Let’s take a look at common problems on the website owner’s side and how to solve them.

Check if Google Analytics is really not measuring

If you’re seeing significantly fewer users than you’d expect, or even none at all, it’s possible Analytics has stopped working. But it’s always a good idea to check this fact. This also applies to a brand new Analytics deployment on a website.

Try visiting your website in an anonymous web browser window. If you don’t see your visit in a real-time report within a few seconds to tens of seconds, there’s a problem in Analytics.

If, on the other hand, you see yourself even when you click through the site, then maybe the measurement is working correctly, but the problem lies in the fact that there simply aren’t people on your page.

Here, then, it depends on how you expect them to have arrived at your site, but you will rather need to fix your ads or social networks, for example. If your traffic is coming from search engines (i.e. you’re mainly dealing with SEO), perhaps the search engines have made an algorithm change that has had a very negative effect on your site’s positions.

In this case, Google Analytics is not to blame, but simply the fact that there is no traffic to the site.

Check the correctness of the code deployment

If the code is deployed correctly on the site, the traffic (including your test traffic) will appear immediately in the Real Time section. So you can check for correct functionality at basically any time, even within seconds of deploying the code.

It is the incorrect code deployment that is responsible for a lot of errors and non-functional services. We recommend copying the code directly from Google Analytics and deploying it exactly as is (you can safely delete the first line" ", which is just an unnecessary comment, but anything from the initial <script> tag to the end of the code must remain the same. Overwriting anything may mean the service stops working.

If you use any other service, plugin or add-on to deploy Google Analytics code, make sure everything is ok with that service as well and the code deploys correctly. Ideally, then, you should be able to deploy the code without using other third-party services, where you are essentially adding another place where things can go wrong.

The code should be deployed between the <head> tags on the site, but the main point is that the scripts load quickly. Theoretically, you can deploy the code all the way to the footer of the site, and everything will work. So if you don’t know how to deploy code to the header, you can deploy it in the middle of the article or anywhere you know how. For testing purposes, this is perfectly sufficient, and then you simply move the code to where it should be.

Also, sometimes the format of the deployed code may change slightly. If you’re not sure, just re-deploy the code by copying it from Google Analytics.

Check for applications that shrink or otherwise modify JavaScript

There are a number of techniques used to speed up websites. One of these is shrinking JavaScript files, for example by removing unnecessary lines and spaces. When we deploy Analytics on the web, we are adding JavaScript, so this is very relevant to our situation.

Different programs can automatically shrink these files for us, which usually helps, but there is also the possibility of a bug where Analytics stops working because of some optimization.

Other programs may download the files needed for measurement locally to the server, i.e. they are not downloaded from Google. Again, this can be beneficial in terms of performance, but there may be an error in our local file or it just isn’t up to date.

For example, Universal Analytics (which is now being superseded by Google Analytics version 4, GA4 for short) could also be set up via various add-on codes to anonymize visitor IP addresses. For example, GA4 does this in the basic settings and there is no need to do anything else. However, if you are using Universal Analytics, something can go wrong here as well by setting it up incorrectly.

Others may use what is known as cookieless mode, where no cookies from the measurement are stored in the user’s browser.

In short, disable any programs that can interfere with Google Analytics codes in any way, download them locally, shrink them, or anything else.

These programs and features can be useful, but they can also be the cause of measurement not working as it should.

Check filters or other settings

You can set up basically anything in Analytics and filter visitors by almost anything you can think of. However, this also means that a poorly set filter can almost completely disable the service.

Especially if you’re in the process of setting up some filters and something stops working, the easiest way is to revert everything back to its original state.

This generally applies to any setting you have changed that may have affected the measurement.

Clear the site cache

If you are using a page cache site (i.e., readers are presented with preloaded versions of pages, which is faster than having to generate each page over and over for each visitor), clear that cache.

Various updates to anything could mean code changes that have not yet been reflected on the site for visitors.

So the easiest way to do this is to clear the cache, which will create new up-to-date versions of the site. It’s not certain that this helps anything, but clearing the cache usually takes a few seconds, and it doesn’t hurt anything.

Has the Universal Analytics version stopped working?

Universal Analytics, as we mentioned, is being replaced by GA4.

1. on July 2023, Universal Analytics , the older but still very popular version of GA, will stop working and we will need to permanently switch to GA4.

Web Facebook @GoogleAnalytics X/Twitter @googleanalytics LinkedIn @google YouTube Wikipedia

Google Analytics on Twitter

Here you can see Google Analytics support on the official Twitter profile. The profile is not particularly up to date, but major outages will be listed here:

This page serves only as a way to easily share information about outegas of services. It is up to the operators of these services to resolve reported outages.

Affiliate Disclaimer: There may be affiliate links on this page. If you click on them and purchase the service, we may receive a small commission at no cost to you.