Insights alerts are not being triggered
The fix has been fully deployed, and alerts on insights are back to normal.
The latest update from PostHog.
State
Resolved
Started
53 d ago
2026-09-09 12:32 UTC
Lasted
10 h 35 min
until 2026-09-09 23:06 UTC
Worst impact
Degraded
Timeline
5 updatesInvestigating
39 min 6%
Identified
2 h 11 min 21%
Monitoring
7 h 46 min 73%
Updates
Times in UTCAs posted by PostHog
The fix has been fully deployed, and alerts on insights are back to normal.
All but a handful of alerts are caught up. We're working to get those alerts processed now and continuing to monitor. For almost all customers there should be no impact at this time.
The fix to unblock the backlog is now deployed and in-progress. We're continuing to monitor the issue.
We’ve identified that the EU insight alert scheduler is getting overloaded by an unbounded batch of due alerts, which can cause scheduler runs to time out and prevent new alert checks from being scheduled. We have a mitigation ready in PR #97378 . This is intended to let the EU cluster drain the backlog gradually once deployed.
Alerts on insights are not being sent, the team is investigating
Affected components
1PostHog in the last 90 days
Full historyIncidents in 90 days
28
Days with an incident
22
Median duration
1 h 14 min
This incident
8.5× the median
Other PostHog incidents
All incidentsPostHog·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.
PostHog·Warehouse sources delayed imports
Warehouse sources backlog has been processed
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