- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 40of 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 26m it lasted.
Anything that failed between 2026-11-06 19:51 UTC and 2026-11-06 20:17 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 2
- resolved
Status: Monitoring Due to a race condition during a deployment, some events did not get geoIP info, for about 15 minutes. The problem has been resolved, we're monitoring and we're investigating backfill possibilities.
provider
- resolved
Status: Resolved We've confirmed the cause of the issue is now fully resolved. We'll be backfilling the missed GeoIP data within the next couple of days.
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-cf521c503c
Is PostHog still down?
No, this incident was resolved 2026-11-06 20:17 UTC. For PostHog's live state, see https://down.guide/posthog.
How long did it last?
26m, from 2026-11-06 19:51 UTC to 2026-11-06 20:17 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.