PostHog US Outage History

PostHog US experienced a service incident where email delivery failed across all third-party email providers, causing delays in authentication, transactional, and promotional emails reaching customers. The issue lasted 1.2 hours before email delivery was restored to normal operation. The team continued monitoring to ensure stable service recovery.

PostHog's MCP (Model Context Protocol) service experienced connection failures that prevented coding agents and IDEs (including Cursor, Claude, VS Code) from connecting properly. The incident lasted 18 minutes before the team identified the cause and resolved it by rolling back to a stable release. The team is now working to fix the problematic update to prevent future occurrences.

PostHog US experienced analytics query timeouts and failures that affected dashboards, insights, and other query-driven views, making them slow or unavailable. The incident lasted 1.8 hours before a fix was deployed and error rates returned to normal levels.

PostHog US experienced failures with Experiments queries for 21 minutes. The engineering team investigated and resolved the issue. The incident was classified as minor, indicating limited impact on the service's overall functionality.

PostHog US experienced a 25-minute incident where the error tracking ingestion pipeline was lagging due to resolution failures and database connection timeouts. The Error Tracking Ingestion component was affected, causing delays in processing error data. The team investigated the root cause of the database connectivity and resolution issues.

PostHog US experienced analytics query timeouts and failures for 22 minutes, affecting dashboards, insights, and other query-driven views in the app and REST API endpoints. Users encountered slow or unavailable analytics functionality during this period. The incident was identified and resolved as a minor service disruption.

PostHog US Cloud experienced a 2.6-hour incident where logs became unqueryable, affecting the Logs Ingestion component. The service was restored with log queries functioning normally and ingestion catching up on the backlog, with no data loss occurring during the outage.

PostHog US experienced processing delays in their logs ingestion pipeline for 44 minutes, causing logs to take longer than usual to appear in the product. While no data was lost, logs were temporarily unavailable in PostHog apps and queries until the processing delays were resolved. The incident was classified as minor and affected the Logs Ingestion component.

PostHog US experienced an issue where LLM analytics traces older than approximately 17 hours failed to load in the dashboard, displaying "trace not found" errors instead. The problem affected the main application and prevented users from accessing historical LLM trace data. The issue was resolved after 33 minutes with a fix implemented and monitoring in place.

PostHog US experienced processing delays in their logs ingestion pipeline for 16 minutes, causing logs to take longer than usual to appear in the product. While no data was lost, logs were temporarily unavailable in PostHog apps and queries until the processing delays were resolved. The incident was classified as minor and affected the Logs Ingestion component.