PostHog incident

Realtime destinations: delivery issues

Resolved after 2 hours 40 minutes, affecting US Cloud 🇺🇸 (Destination Delivery (realtime)) and EU Cloud 🇪🇺 (Destination Delivery (realtime)), on September 8, 2026.

resolved Sep 08, 2026, 12:19 PM UTC

The issue was fixed and everything is back to normal. The impacted customers will be informed.

Started
Sep 08, 2026, 09:39 AM UTC
Resolved
Sep 08, 2026, 12:19 PM UTC
Duration
2h 40m
Detected by Pingoru
Sep 08, 2026, 09:39 AM UTC

Affected components

US Cloud 🇺🇸 (Destination Delivery (realtime))EU Cloud 🇪🇺 (Destination Delivery (realtime))

Update timeline

  1. identified Sep 08, 2026, 09:39 AM UTC

    A breaking change in our HogVM caused some destinations to fail. We currently identified the issue and preparing a fix to mitigate the issue.

  2. monitoring Sep 08, 2026, 10:37 AM UTC

    We've identified the root cause: a recent change to Hog function validation was stricter than intended and caused some valid destinations and transformations to fail. When this happens, matching events aren't forwarded to the destination and those deliveries can't be replayed - the events themselves remain safely in PostHog, but the forwarding for the affected window is lost. Only a very small number of customers were affected. We've pulled the complete lists of impacted teams and functions in EU and US to start outbound communication. A fix has been merged that restores the previous behaviour and stops new failures once deployed. We're also scoping a longer-term mechanism to make this class of failure recoverable in the future.

  3. resolved Sep 08, 2026, 12:19 PM UTC

    The issue was fixed and everything is back to normal. The impacted customers will be informed.

Your product runs on more than PostHog

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →