Some queries timing out
PostHog reports that some queries time out at a higher rate than usual. PostHog identified the probable cause and engineers prepare the fix to merge and deploy. The incident started 137 minutes ago and is not resolved.
State
Identified
Started
Ongoing for
4 h 34 min
Worst impact
Degraded
Timeline
4 updatesInvestigating
1 h 29 min 32%
Identified
3 h 5 min 68%
Updates
Times in UTCAs posted by PostHog
Engineers are working on preparing the fix to be merged and deployed.
Engineers have identified the probable cause, and are working on deploying a fix. We're still seeing a query timeouts at a bit more than the usual rate.
The rate of errors has fallen back into the normal range. Engineers are still investigating the cause.
We're seeing queries timing out at a higher rate than usual. Engineers are currently investigating.
PostHog in the last 90 days
Full historyIncidents in 90 days
30
Days with an incident
23
Median duration
1 h 14 min
This incident
3.7× the median
Other PostHog incidents
All incidentsPostHog·Realtime destinations: delivery issues
PostHog had delivery problems with the Destination Delivery (realtime) component. PostHog identified an internal issue and reports that the issue is resolved. The incident lasted 3 minutes.
PostHog·Some events missing GeoIP info
PostHog reported that some events did not get GeoIP info. PostHog later confirmed that the cause is fully resolved. The incident lasted 26 minutes.
PostHog·Event ingestion: processing delays
PostHog event ingestion had processing delays in the Event Ingestion Lag component. PostHog reports that the incident is resolved. The outage lasted about 43 minutes.
PostHog·Workflows Email Metric Ingestion Outage
PostHog reported an ingestion problem with email metrics such as open rates, click through, and bounces. The problem started on 3 November 2026 at 11:21 UTC and lasted 244 minutes. PostHog resolved the incident at 15:25 UTC.
PostHog·Agents: elevated GitHub error rates
We’ve deployed a mitigation for transient GitHub errors and haven’t observed further failures since.
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.live/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.live/feed.xml?providers=posthog/feed subscribe https://outages.live/feed.xml?providers=posthogFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane