Cloud US Ingestion System Maintenance
Maintenance has started
The latest update from PostHog.
State
Resolved
Started
Lasted
1 h 56 min
Worst impact
Maintenance
Timeline
2 updatesMaintenance in progress
1 h 56 min 100%
Updates
Times in UTCAs posted by PostHog
Maintenance has started
Affected components
1PostHog in the last 90 days
Full historyIncidents in 90 days
28
Days with an incident
21
Median duration
1 h 10 min
This incident
Not comparable
Other PostHog incidents
All incidentsPostHog·Stripe data syncs failing for some customers
Some Stripe data warehouse syncs failed for PostHog customers in the Data Warehouse Source Ingestion component. PostHog identified the cause, deployed a fix, and monitored recovery. The incident is resolved and lasted about 4 hours and 31 minutes.
PostHog·Some queries timing out
PostHog reported that some queries timed out at a higher rate than usual. PostHog identified a probable cause and deployed a fix. PostHog says the incident is resolved and the error rate returned to normal by 06:00 UTC on 10 November 2026.
PostHog·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.
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