- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 18of 100
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.Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.
Anything that failed between 2026-09-08 12:19 UTC and 2026-09-08 12:19 UTC may need a replay.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 The issue was fixed and everything is back to normal. The impacted customers will be informed. Affected components Destination Delivery (realtime) (Operational) Destination Delivery (realtime) (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-44822a8896
Is PostHog still down?
No, this incident was resolved 2026-09-08 12:19 UTC. For PostHog's live state, see https://down.guide/posthog.
How long did it last?
0m, from 2026-09-08 12:19 UTC to 2026-09-08 12: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.