- 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-09-10 10:54 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
- resolved
Status: Resolved This incident has been resolved. Any warehouse sources that failed to sync will catch up on their next scheduled run. A manual sync can be triggered to refresh data for affected sources 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-17f5af5de4
Is this PostHog maintenance still going on?
No, it ended 2026-09-10 10:54 UTC.
How long did it last?
0m, from 2026-09-10 10:54 UTC to 2026-09-10 10:54 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.