Skip to main content
PostHog

Google Ads Data Warehouse source - some schemas are failing to sync

Maintenance Lasted 0m · started · PostHog's page

Level
confirmed
Worst impact
Maintenance

What to do

  • Check whether your product depends on PostHog. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Check that everything you run on PostHog came back after the window closed 2026-10-09 08:19 UTC.

  • Subscribe to PostHog's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=posthog works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from PostHog 1

  1. resolved

    Status: Resolved We've released a fix for this - affected Google Ads tables will catch up automatically at their next scheduled sync, or you can trigger a refresh manually to update the tables sooner. Affected components Data Warehouse Source Ingestion (Operational) Data Warehouse Source Ingestion (Operational)

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-cb90c2c1fb

Is this PostHog maintenance still going on?

No, it ended 2026-10-09 08:19 UTC.

How long did it last?

0m, from 2026-10-09 08:19 UTC to 2026-10-09 08:19 UTC, by the times PostHog posted.

What caused it?

PostHog hasn't published a root cause. If it does, it shows here.

Where does this come from?

PostHog's official status page, https://www.posthogstatus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.