Some hog destinations and workflow steps were incorrectly rejected by a CDP safety guard

Resolved

Started

Lasted 3h 30m

View official incident ↗

Updates

  1. Resolved

    The rollback has completed and the affected hog destinations and workflow steps have returned to normal operation. No further impact. A follow-up fix to the safety guard is in progress and will be re-deployed only after additional validation against production traffic patterns.

  2. Identified

    A CDP safety guard deployed earlier today is incorrectly rejecting some hog destinations and workflow steps that call PostHog's own API endpoints. Affected destinations are seeing "Refusing to fetch a posthog.com endpoint…" errors and failing to forward events to their downstream targets. Some workflow runs are also halting at the affected step. Event ingestion, dashboards, queries, and the rest of PostHog are unaffected. The issue is limited to hog destinations and workflow steps that fetch back into PostHog APIs from within the same project. Rollback is in progress.