- Level
- confirmed
- Worst impact
- Partial outage
- Regions
- us
- Down Index
- 28of 100
What to do
Check whether you use PostHog in us. 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-11-03 15:25 UTC and 2026-11-03 15:25 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 Between 10:58-11:36 GMT we had an incident that dropped email engagement events for emails sent from within workflows and broadcasts affecting downstream triggered automations for a handful of customers. At no point were emails lost. Additionally during this time period email metrics are showing inflated numbers. All affected customers will be contacted by us about their affected workflows and impact.
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-b5e038c0cb
Is PostHog still down?
No, this incident was resolved 2026-11-03 15:25 UTC. For PostHog's live state, see https://down.guide/posthog.
How long did it last?
0m, from 2026-11-03 15:25 UTC to 2026-11-03 15:25 UTC, by the times PostHog posted.
What was affected?
PostHog named in us.
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.