Event ingestion: processing delays
PostHog event ingestion had processing delays that affected the Event Ingestion Lag component. PostHog reports that the incident is resolved. The outage lasted 43 minutes.
State
Resolved
Started
Lasted
43 min
Worst impact
Degraded
Timeline
3 updatesIdentified
14 min 32%
Monitoring
29 min 68%
Updates
Times in UTCAs posted by PostHog
All events processing and delays are back to normal levels.
The impacted node was identified and all service running again as normal. Lag is coming down and we're monitoring for now.
We’ve identified processing delays in the event ingestion pipeline. Events may take longer than usual to appear in the product. Data is not lost but may not show in PostHog apps and queries until the processing delay is resolved.
Affected components
1PostHog in the last 90 days
Full historyIncidents in 90 days
29
Days with an incident
22
Median duration
1 h 15 min
This incident
42% shorter than the median
Other PostHog incidents
All incidentsPostHog·Workflows Email Metric Ingestion Outage
PostHog reports that email engagement events for workflow and broadcast emails were dropped between 10:58 and 11:36 GMT. Email metrics showed inflated numbers in that window. The incident is resolved and lasted about 4 hours. PostHog will contact affected customers.
PostHog·Agents: elevated GitHub error rates
We’ve deployed a mitigation for transient GitHub errors and haven’t observed further failures since.
PostHog·Application: partial outage
All services have returned to normal.
PostHog·PostHog AI connections
This issue has been resolved. PostHog AI and other services are back to normal. Apologies for the interruption.
PostHog·Google Ads Data Warehouse source - some schemas are failing to sync
We've released a fix for this - affected Google Ads tables will catch up automatically at their next scheduled sync, or you can trigger a refresh manually to update the tables sooner.
Follow PostHog
Your coding agent knows when PostHog is down, and tells you when a failure is theirs, not yours. You can also get PostHog incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "posthog" and tell me if PostHog has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=posthog/feed subscribe https://outages.cc/feed.xml?providers=posthogFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane