Delayed. Daily export tables are landing later than usual.
Started 13 Nov, 22:00 UTC
Updated 2 minutes ago
Today versus a usual day
Share of monitored properties whose daily table has landed, by hours after local midnight
The BigQuery location your GA4 export writes to. You chose it when you linked GA4 to BigQuery.
| Location | Status | Yesterday's table landed | Median delay, 7 days |
|---|---|---|---|
| USMulti-region, United States | Late | 38% | 41.2 h |
| EUMulti-region, European Union | Late | 44% | 39.8 h |
| europe-west2London | Late | 47% | 36.5 h |
| asia-northeast1Tokyo | On time | 98% | 8.9 h |
| australia-southeast1Sydney | On time | 97% | 9.4 h |
Past incidents
- Ongoing · Daily tables late in US, EU and europe-west2Started 13 Nov
- 6 to 8 Oct 2026 · Up to 30.4 h late · EUResolved
- 29 to 30 Aug 2026 · Up to 29.5 h late · EUResolved
- 7 to 9 Aug 2026 · Up to 32.1 h late · EUResolved
- 1 Jun 2026 · Table missing for 12 days, then reloaded · EUResolved
Looking for more advanced features?
Request access to our paid services
Get alerts in your own channels, pipeline refreshes synced with the export, dedicated support, and more...
Connect a GA4 property
Make this status page more accurate by sharing when your export lands. Setup takes about two minutes, and you can disconnect at any time. We only collect technical log data. The more, the merrier.
Choose how to connect
We create the log sink in your project for you. Fastest option, about one minute.
- Sign in and approve access to Cloud Logging.
- Pick the GA4 properties to connect, from any of your projects.
- We create one sink per project, then discard your access token.
You need the Logs Configuration Writer role on the projects you connect. Some organisations block third-party apps; if sign-in fails, set it up yourself instead.
Tell us what to monitor
Run this in Cloud Shell
Paste the writer identity
The command prints it as serviceAccount:service-…@gcp-sa-logging.iam.gserviceaccount.com. We use it to let your sink send entries to us, and nothing else.
Help us improve it
Found something wrong on this page? Missing a feature? Any questions? Write to us.
Frequently asked questions
Is this an official Google status page?
No. It is run by Superform Labs, the team behind GA4Dataform, and is not affiliated with Google. It measures the export from the outside, using the timings shared by connected properties.
How do you measure a delay?
For each connected property, we record when Google's daily load job for the events_YYYYMMDD table finishes, and compare it with midnight in the property's reporting timezone.
My export is late but the page says on time. Why?
The page reflects the properties connected to it. If most of them have received yesterday's table, the cause is more likely specific to your property or project, such as a billing issue, the daily export limit, or a removed permission on the dataset.
Do I need to connect a property to get alerts?
No. Alerts are free and only need an email address. Connecting a property makes the page more accurate for everyone.
Does connecting give you access to my data?
No. The log sink sends us only the audit entries the GA4 export writes when it loads or replaces tables: table names, timestamps and data location. We cannot read your datasets, your queries or any other logs.
How do I disconnect?
Delete the log sink in your project, for example with: gcloud logging sinks delete ga4-delay-monitor --project=YOUR_PROJECT. Nothing else is installed.
Does connecting cost anything?
The service is free. [To confirm before launch: whether log routing adds any cost on the contributor's side.]
Which exports are covered?
The daily export (events_YYYYMMDD tables). Intraday streaming and the GA4 360 Fresh Daily export are not measured yet.
Why group by data location?
The export writes to the BigQuery location chosen when GA4 was linked to BigQuery, so you can compare your property with others that share its location.