Workflows Email Metric Ingestion Outage
PostHog has an ingestion problem with email metrics, such as open rates, click through, and bounces, for workflow and broadcast emails. PostHog rolled out a fix and now monitors the system. PostHog is still checking the impact and will tell affected customers.
State
Monitoring
Started
Ongoing for
2 h 43 min
Worst impact
Degraded
Timeline
4 updatesIdentified
24 min 14%
Monitoring
2 h 20 min 86%
Updates
Times in UTCAs posted by PostHog
Between 10:58-11:36 GMT we had an incident that dropped email engagement events for emails sent within workflows or broadcasts in the given time window. The emails were sent but without engagement events, even if turned on for the project. During this time period email metrics were recorded with inflated numbers. We are working on assessing customer impact and will contact and inform the affected customers.
We identified the customers that have been affected by the incident and of which their workflow email sending workflow steps show as failed and stopped the workflow run. The emails for the failed steps went out, but the workflow aborted at that point. We are working on resuming the failed workflows and will inform the affected customers.
Due to a rollout issue we experienced a temporary ingestion problem with email metrics like open rates, click through, bounces etc. We identified the issue and already rolled out a fix stopping the bleeding. We are now investigating the impact and will inform impacted customers with the impact that they experience if we cannot recover the lost metrics.
Due to a rollout issue we are currently experiencing some ingestion problem with email metrics like open rates, click through, bounces etc. We identified the issue and already rolled out a fix which stops the bleeding. We will inform the impacted customers with the impact that they experience if we cannot recover the lost metrics.
PostHog in the last 90 days
Full historyIncidents in 90 days
28
Days with an incident
22
Median duration
1 h 15 min
This incident
2.2× 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.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