PostHog US Outage History

PostHog experienced processing delays in their event ingestion pipeline for 40 minutes, causing events to take longer than usual to appear in the product. While no data was lost, users were unable to see events in PostHog apps and queries until the processing delays were resolved. The incident was identified and investigated, with the pipeline returning to normal operation after the 40-minute duration.

PostHog experienced issues with cohort calculations that caused feature flags dependent on those cohorts to incorrectly evaluate as false. The problem affected feature flag functionality for users relying on cohort-based targeting. The issue was resolved after 1.3 hours when a fix was implemented to restore correct feature flag evaluations.

A bad deploy of PostHog's internal API blocked session replay playback functionality for 2.6 hours. The issue was identified and resolved through a rollback, with no data loss occurring. Session replay playback was restored and the service returned to normal operation.

PostHog experienced elevated API error rates affecting the MCP server for 14 minutes on March 16, 2026. The incident was classified as minor and the team investigated the issue. No resolution details were provided in the available updates.

PostHog experienced analytics query timeouts and failures that affected dashboards, insights, and other query-driven views, making them slow or unavailable. Data ingestion was also impacted, causing delays in query results. The incident lasted 2.2 hours before being resolved.

PostHog experienced a delay in delivery for realtime destinations, causing recent events to be sent late to destination providers. The service resolved the backlog over approximately one hour, with no data loss occurring during the incident.

PostHog experienced an issue where session replays were missing for some customers over a 19.6-hour period. The company released a fix for the underlying problem while investigating the full scope of the impact. The incident was classified as minor severity.

PostHog's managed reverse proxies became stuck in 'loading' or 'issuing' states due to a Cloudflare configuration issue on PostHog's infrastructure. The incident affected users' ability to properly provision and use managed proxies for their PostHog implementations. Engineers resolved the Cloudflare configuration problem after 2.4 hours and continued monitoring the service.

PostHog experienced a partial outage for 37 minutes caused by a degraded database that prevented users from fetching insights and accessing certain pages or actions. The primary issue was resolved, with only a backlog of events remaining to be processed.

PostHog experienced event ingestion processing delays for 7.6 hours due to increased latency in the ingestion event queue, causing degraded throughput and accumulating lag of 30-40 minutes. The issue was resolved by upgrading the underlying compute infrastructure for the queueing system to handle increased event throughput. No data was lost during the incident, and the system recovered with full catch-up expected within 3-4 hours after throughput was restored.