The day the numbers went to zero, no dashboard said so
On 1 September 2026, Google Analytics 4 standard reports showed almost nothing for a great many properties. The first thing anyone tries is to find a status page. Analytics does not have one of its own — its official status lives inside the Google Ads dashboard, and we downloaded that dashboard's machine-readable history to see what it actually records.
What happened. For most of 1 September 2026, Google Analytics 4 standard reports showed zero or near-zero traffic while realtime kept working — a processing problem, not a traffic problem. It was reported by the trade press on 2 September. The obvious next move, checking an official status page, is where this gets interesting.
Why this is not for everyone. If your reporting already crosses two independent counters, you spotted the gap in an hour and moved on. This page is for the businesses that read one dashboard on a Monday morning and decide the month from it. There are a lot of them, and nothing about that is stupid — it is what the tools invite you to do.
What you get. Where Google actually publishes Analytics status, what its published incident history contains when you download it rather than look at it, how the four dashboards a European business depends on compare, and the documented number of hours each report is allowed to be behind before anything is wrong at all.
- Google Analytics has no status page of its own: the official one is the Google Ads Status Dashboard.
- That dashboard's published history holds 35 incidents since 24 October 2025. None of them is Analytics.
- Ten of its 16 listed products have no incident at all in the published window.
- Before you panic: GA4 documents that «data processing can take 24-48 hours».
Where Google publishes the status of Google Analytics
Google Analytics has no status page under its own name; the status source Google documents for it is the Google Ads Status Dashboard at ads.google.com/status/publisher, which lists Analytics as one of sixteen products alongside AdSense, AdMob and Ad Manager.
This is not a guess. The Analytics Help article titled «Analytics service status» sends you there in one line: the Ads Status Dashboard «displays the performance status of some Google products, including Analytics», and the sentence applies to «both standard and 360 versions». There is no second address. On 3 September 2026 we checked the obvious candidates: status.analytics.google.com does not resolve, analytics.google.com/status/ returns 404, and status.google.com does not resolve either. Google runs separate dashboards for Workspace and for Search — Analytics rides on the advertising one.
Read the destination page and the seam shows. Its own description says: «This page provides status information on the services that are part of Google Ads.» Google Analytics is not part of Google Ads. Neither is AdSense, and neither is Ad Manager. Sixteen products sit on a dashboard whose masthead describes a smaller set than the one it carries, and the help article explaining the dashboard is filed under Google Ad Manager Help, not under Analytics.
A status page is the one place where the vendor and the customer agree about reality. When it is hard to find, the conversation that follows an incident is not «here is what happened» but «are you seeing this too?» — which is how a three-hour reporting bug becomes a week of doubt about the numbers in a marketing report.
What happened on 1 September 2026
Search Engine Roundtable published it on 2 September 2026 at 6:13 am: «September 1, 2026 data is showing zero traffic to websites; I believe this is across every Google Analytics install.» The article's read is that this was a reporting fault rather than lost visits — «It is a Google bug, nothing for you to do on your end» — and that realtime reports kept showing activity while standard reports did not. Search Engine Land and Search Engine Watch covered the same day.
One detail is worth keeping rather than smoothing over, because it is the sort of thing that decides whether you trust a story. The same article quotes the analytics practitioner Dana DiTomaso saying it «looks like Google Analytics is having an issue with processing yesterday's (August 31st) data», while the headline and the body refer to 1 September. Those are two different dates. Both readings are compatible with a processing queue that stalls and takes the following day's reports down with it, but we cannot tell you which day's rows were affected in your property, and neither can the report.
What we can tell you is what the official status surface said. We opened the Google Ads Status Dashboard on 3 September 2026: «No incidents», last updated 7:20 AM UTC, with the eight dated columns running from 27 August to 3 September — a window that contains 1 September in full.
What the published history contains when you download it
The dashboard does something better than most: it publishes its data. At the bottom of the page there are two links, incidents.json and products.json, and both return plain JSON to a plain request. We downloaded them on 3 September 2026, which turns a page you squint at into a table you can count.
products.json returns 16 products. incidents.json returns 35 incidents, the earliest beginning 24 October 2025 at 17:44 UTC and the latest on 1 September 2026 at 14:28 UTC — 313 days of history as of the day we read it, which matches the history page's own heading, «Incidents reported in the last 365 days». Two of the 35 touch more than one product, so there are 37 product-incident pairs to distribute.
All 35 incidents belong to six products, and Analytics is not one of them
Incidents per product in the Google Ads Status Dashboard's own history file, downloaded on 3 September 2026. The window runs from 24 October 2025 to 1 September 2026.
Source: incidents.json and products.json from the Google Ads Status Dashboard, downloaded 3 September 2026 · cittago.com
| incidents | |
|---|---|
| Google Ad Manager | 24 |
| AdMob | 8 |
| Ad Manager DAI | 2 |
| AdSense | 1 |
| Exchange Platforms | 1 |
| Ad Manager Data Transfer | 1 |
| Google Ads | 0 |
| Google Analytics | 0 |
Ten of the sixteen listed products carry no incident at all in the published window: Ads Data Hub, Campaign Manager 360 and its API, Display & Video 360, Google Ads, the Google Ads API, Google Analytics, Platform Home, Platform Reporting and Search Ads 360. Everything that got posted belongs to the publisher side of the house — Ad Manager 24 times, AdMob 8, Ad Manager DAI twice, and AdSense, Exchange Platforms and Ad Manager Data Transfer once each.
The severities in the file are worth a line of their own, because they show the bar is not set at catastrophe: 27 of the 35 are recorded as service disruptions, 7 as service information, and exactly one as a full service outage. The help article defines a disruption as «major features in the product are unavailable or affected by a known issue» — which is a fair description of standard reports showing zero. Durations run from 30 minutes to 18 days and 14 hours, with a median of 17 hours; the longest was an Ad Manager incident that opened on 25 March 2026 and closed on 13 April.
The dashboard posts about three incidents a month, and August 2026 was its busiest
Incidents by the month they began, from the same history file. October 2025 and September 2026 are partial months at the edges of the window and are left out.
Source: incidents.json and products.json from the Google Ads Status Dashboard, downloaded 3 September 2026 · cittago.com
| incidents | |
|---|---|
| Nov | 4 |
| Dec | 2 |
| Jan | 5 |
| Feb | 2 |
| Mar | 4 |
| Apr | 5 |
| May | 2 |
| Jun | 2 |
| Jul | 1 |
| Aug | 6 |
Here is the sentence we cannot write, and the reason we cannot. We cannot tell you that Google Analytics has never had an incident posted, because the file is a rolling window: 35 entries reaching back 313 days, with no way to know from the outside whether older entries were removed or whether there simply were none. What the file supports is narrower and still useful — in the history this dashboard publishes today, the product a business checks when its reports go blank has never been the subject of an entry.
Four dashboards, four different promises
A European business running search, social and a website depends on four of these pages, and they are not built to the same standard. We opened all four on 3 September 2026 and counted the named rows on each, because the number of rows is the cheapest honest measure of how specific a status page is willing to be.
Microsoft names 33 parts of its advertising platform; Google Search names four
The number of separately named components on each public status page, counted on 3 September 2026. More rows is not automatically better, but it is a promise about where the vendor is willing to be specific.
Source: the four status pages and the three data-freshness help pages, all read on 3 September 2026 · cittago.com
| named components | |
|---|---|
| Google Search | 4 |
| Google Ads | 16 |
| Meta | 17 |
| Microsoft Ads | 33 |
Google Search keeps the shortest list: Crawling, Indexing, Ranking, Serving. Its history file holds ten entries between 26 August 2025 and 18 August 2026, and eight of them are not faults at all — they are ranking and Discover updates, announced through the same channel. That is a deliberate choice and a useful one, but it means the page answers «is Google changing something?» more often than «is Google broken?»
Meta publishes seventeen rows in four groups: seven under Ads, three under Business Tools, five under Developer Platform and two under Transparency Tools, each with its own page and its own history feed. All seventeen read «No known issues» at 7:22 AM UTC on 3 September 2026. What is not there is worth naming: none of the seventeen rows is the pixel, Events Manager or the Conversions API. Ads delivery has a row; the thing that counts what the ads did does not.
Microsoft Advertising is the most granular of the four, and by a distance. Its platform health page names 33 components across four areas — six applications, nine platform services, seven APIs and eleven network and ad-format rows. Two of those rows are «Reporting Data» and «UET», Microsoft's tag: the measurement layer has its own status line, which is exactly the row that was missing everywhere else on 1 September.
| Page | Named rows | History published | Covers measurement? |
|---|---|---|---|
| Google Ads Status Dashboard | 16 | JSON, 35 incidents since 24 Oct 2025 | Analytics is listed; no entry in the history |
| Google Search Status Dashboard | 4 | JSON, 10 entries since 26 Aug 2025 | No — crawling, indexing, ranking, serving |
| metastatus.com | 17 | Per-product history and RSS | No row for the pixel, Events Manager or Conversions API |
| Microsoft Advertising platform health | 33 | Blog-style, per area | Yes — «Reporting Data» and «UET» are rows |
We also looked for the rule that decides when an incident is posted, because that would explain a great deal, and we did not find it. Not on the dashboard, not in the Ad Manager help article the dashboard links to, and not in the Analytics help article that names the dashboard. All three explain what the icons mean; none states the threshold at which a problem becomes an entry. We read them in English on 3 September 2026, and we would update this page happily if someone shows us the page we missed.
Late or missing? The documented answer, in hours
Before anyone opens a status page there is a cheaper question to settle, and most of the panic lives here: is the number missing, or is it merely later than you expected? Each of the three Google tools documents this, and the figures are further apart than most people assume.
Google Analytics 4 publishes a data-freshness table. Realtime is «typically a few minutes». Intraday on a standard property is 2 to 6 hours. Daily reporting is 12 hours on a standard property. And the sentence to keep is the plainest one on the page: «Data processing can take 24-48 hours. During that time, data in your reports may change.» Not «may be missing» — may change. A number you screenshot on Tuesday morning is allowed to be a different number on Wednesday, by design, and nothing is wrong.
Google Ads is faster and says so precisely: clicks, impressions and cost are «subject to a 1-hour data freshness Service Level Objective (SLO), which means they're refreshed hourly». Conversions are slower and depend on how they arrive. Google Ads conversion tracking on a Last Click model is documented at 3 hours, other attribution models at 15 hours; goals and transactions imported from Analytics take 12 hours on Last Click and 24 hours on other models.
Search Console is the slowest of the three, and the one people forget: «Normally, however, collected data should be available in 2-3 days.» For a site newly added to Search Console, the same page says it «can take up to a week to generate data». Three days is not a bug. It is the documented behaviour of the report that many businesses check daily.
Three days for Search Console, one hour for Google Ads clicks
The maximum documented delay for each metric, from the three vendors' own data-freshness pages, read on 3 September 2026. Hours, not estimates.
Source: the four status pages and the three data-freshness help pages, all read on 3 September 2026 · cittago.com
| hours | |
|---|---|
| Search Console · Performance | 72 h |
| GA4 · full processing | 48 h |
| Ads · GA conversions, other models | 24 h |
| Ads · conversions, other models | 15 h |
| Ads · GA conversions, Last Click | 12 h |
| GA4 · daily reports | 12 h |
| GA4 · intraday, standard property | 6 h |
| Ads · conversions, Last Click | 3 h |
| Ads · clicks, impressions, cost | 1 h |
What you need to answer this yourself
- The right status URL, saved. For Analytics and Google Ads it is
ads.google.com/status/publisher. For Search,status.search.google.com. For Meta,metastatus.com. For Microsoft Advertising,status.ads.microsoft.com. None of the four is where a reasonable person would first look. - A second counter that does not share a failure. Server logs, the hosting panel, the ad platform's own click column, a CRM. When two independent counters disagree, the disagreement itself is information; when you own one, you are guessing.
- The freshness numbers above, written down once. They are the difference between «the data is gone» and «it is Wednesday morning».
- The RSS or atom feed. All four pages publish one. A feed reader is a better monitor than a habit of remembering to check.
- A screenshot with a timestamp. If you report a problem, the timestamp is what makes your report usable — and if the data quietly backfills, it is what tells you it did.
What these numbers do NOT say
- They do not say Google Analytics is unreliable. Counting incidents on a status page measures what a vendor publishes, not what a vendor experiences. Those are different quantities and only one of them is visible from outside.
- They do not say the 1 September data was lost. Reporting faults are usually backfilled, and the reports we read describe a processing problem rather than dropped collection. We did not verify the backfill on any property and are not claiming it.
- They do not say Analytics has never had an incident posted. The file we downloaded is a rolling window of 35 entries reaching back 313 days.
- They do not compare vendors on reliability. Thirty-three rows on one page and four on another is a difference in disclosure design, not a scoreboard.
- They do not apply to Google Analytics 360, Google Cloud or Workspace, each of which has its own arrangements that we did not read for this article.
How to check, in order
- Compare the report to its own documented delay. If the missing rows are inside the 24-48 hour processing window GA4 documents, wait before doing anything else.
- Open realtime. If realtime shows visitors while standard reports show nothing, collection is working and processing is not — which is the shape of a vendor-side problem, not a broken tag.
- Check the second counter. Server logs or the hosting panel, and the ad platform's click column. Two sources that disagree with the third one identify the third one.
- Open the right status page — for Analytics, the Google Ads one — and note the timestamp it shows, not just the colour of the icon.
- Write down what you saw, with the hour. A dated note is worth more than a memory when the same question comes back in three weeks.
- Then, and only then, touch the tag. The most expensive version of this day is the one where someone reinstalls a working measurement tag during a vendor incident and spends the next fortnight comparing two setups.
That order is the whole method, and the reason we go through it before touching anything is that measurement work has a nasty asymmetry: waiting an hour costs an hour, while a panicked change to a working setup costs a month of comparability. It is also why, when we plan digital marketing for a business, the reporting stack gets at least two independent counters before the first campaign runs — not for elegance, but because one of them will be silent on a day when a decision is due.
Who does not need any of this
If your decisions are monthly and your invoices come from the ad platforms, a day of missing analytics rows changes nothing you do; read the freshness table once and go back to work. If you already reconcile two sources at the end of each month, you found the gap without us. And if your reporting runs on server-side collection with your own store of raw events, this article describes a problem you designed out years ago.
The businesses this is written for are the ones where a single dashboard is the whole measurement system, which is most small companies and a fair number of large ones. The fix is not a bigger stack. It is knowing which page to open, and how long to wait before opening it.
Glossary
| Term | What it means |
|---|---|
| Status dashboard | A vendor's public page recording outages and disruptions. For Google Analytics, the documented one is the Google Ads Status Dashboard. |
| Service disruption | Google's middle severity: «major features in the product are unavailable or affected by a known issue». 27 of the 35 published incidents carry it. |
| Service outage | Google's top severity: «the product is inaccessible to all users». One of the 35. |
| Data freshness | How long a vendor allows itself before a number appears or stops changing. GA4 documents 24-48 hours for full processing. |
| Intraday | Partial data for the current day, before daily processing runs. On a standard GA4 property, 2 to 6 hours behind. |
| Backfill | Rows arriving after the fact and filling a gap that was previously empty. Common after reporting faults, and the reason a screenshot with an hour on it is useful. |
Three thresholds, to see how much this concerns you
- One tool, decisions once a month. Save the four URLs and the freshness numbers. That is the whole job; a missing day will have refilled before it matters.
- One tool, decisions every week. Add a second counter this quarter — server logs are free and already running. A weekly decision made on a silent Monday is a decision made on nothing.
- Automated bidding fed by imported conversions. Here a gap is not a reporting inconvenience: it is an input. The documented import delays of 12 and 24 hours are the reason a same-day reaction to a soft day is almost always premature.
All of this was read on 3 September 2026, on pages that change without notice. We will come back to it in 3-6 months 😉
Questions nobody has actually asked us
This one is new enough that nobody has written in yet, so these are the questions we asked while reading the four dashboards.
Does Google Analytics have a status page?
Not under its own name. The Analytics Help article «Analytics service status» points to the Google Ads Status Dashboard at ads.google.com/status/publisher, which «displays the performance status of some Google products, including Analytics», for both standard and 360 versions. On 3 September 2026, status.analytics.google.com did not resolve and analytics.google.com/status/ returned 404.
Why is Analytics on the Google Ads dashboard?
Google does not explain it on any of the three pages we read. The dashboard describes itself as covering «the services that are part of Google Ads», yet it also carries AdSense, AdMob, Ad Manager and Analytics, and the help article documenting it lives in Google Ad Manager Help. The practical consequence is that the page is hard to find from inside Analytics.
Did the dashboard report the 1 September 2026 Analytics problem?
No entry for it exists in the history file. We downloaded incidents.json on 3 September 2026: 35 incidents since 24 October 2025, none of them for Google Analytics. The three incidents whose windows include 1 September belong to Ad Manager, Ad Manager DAI and AdMob.
What happened to Google Analytics on 1 September 2026?
Standard reports showed zero or near-zero traffic on very many properties while realtime kept working, which points to a processing fault rather than lost collection. Search Engine Roundtable reported it on 2 September 2026: «September 1, 2026 data is showing zero traffic to websites; I believe this is across every Google Analytics install.»
How long can data legitimately take to appear in GA4?
Google's own freshness page: realtime «typically a few minutes», intraday 2 to 6 hours on a standard property, 12 hours for daily reporting, and «data processing can take 24-48 hours. During that time, data in your reports may change.» A gap inside that window is documented behaviour, not a fault.
And in Google Ads and Search Console?
Google Ads documents a 1-hour freshness objective for clicks, impressions and cost; conversions take 3 hours on Last Click and 15 hours on other models, and conversions imported from Analytics take 12 and 24 hours respectively. Search Console says «collected data should be available in 2-3 days», and up to a week for a newly added site.
Does Meta publish a status page for its pixel?
metastatus.com lists 17 named products in four groups, and none of them is the pixel, Events Manager or the Conversions API. Ads Manager, Marketing API and Messaging Ads each have a row; the measurement layer does not. All 17 read «No known issues» when we checked at 7:22 AM UTC on 3 September 2026.
Which advertising platform is most specific about status?
Microsoft Advertising, by the count of named rows: 33 components across applications, platform, APIs and network formats, including «Reporting Data» and «UET». That is a measure of disclosure, not of reliability — a page with more rows tells you more when something breaks, and nothing at all about how often it breaks.
What should I do first when a report shows zero?
Check the report against its own documented delay, then open realtime. If realtime shows visitors and standard reports do not, collection is fine and processing is not. Only after that is it worth opening a status page, and only after that is it worth touching the tag — reinstalling a working tag during a vendor incident costs weeks of comparability.
Is a single analytics tool enough for a small business?
For monthly decisions, usually yes, as long as you know the freshness numbers. For weekly decisions, a second counter that fails independently — server logs, the hosting panel, the ad platform's own click column — is the cheapest insurance there is, because it is already running and costs nothing to start reading.
Last updated: 3 September 2026. The incident counts come from incidents.json and products.json on the Google Ads Status Dashboard, downloaded on 3 September 2026; the file held 35 incidents beginning between 24 October 2025 and 1 September 2026, which is a rolling window and not the full life of the dashboard. The component counts for Google Search, Meta and Microsoft Advertising were taken from the rendered pages the same morning, in English. The freshness figures come from the GA4, Google Ads and Search Console help pages, also read on 3 September 2026. The 1 September incident itself is reported by the trade press; we found no incident entry for it and no official statement. We update this page when a status page changes what it covers or when a freshness figure moves.
Sources: Google Ads Status Dashboard · Ads Status Dashboard incident history (JSON) · Analytics Help, Analytics service status · Ad Manager Help, Monitor product status · [GA4] Data freshness · Google Ads, About data freshness · About Search Console data · Google Search Status Dashboard · Meta business products status · Microsoft Advertising platform health · Search Engine Roundtable, 2 September 2026
