PostHog Status

Resolved: We've deployed a fix. We apologize for any inconvenience.

Identified: We're experiencing elevated cases of users being asked for their 2FA, we've identified the issue and are deploying a fix.

Resolved: All systems have returned to being full operational

Monitoring: We are continuing to monitor for any further issues.

Monitoring: We applied some fixes to our clickhouse infrastructure that was the root cause for this issue. The web app has recovered and is stable for a while now. We're monitoring!

Apologies for this interruption!

Identified: The posthog web interface is currently down. We've identified the root cause as a performance issue in one of our database systems. We're deploying a fix now. No data has been lost.

Resolved: All systems recovered and appear stable

Monitoring: Upstream vendor has provided a fix, and all systems are recovering.

Identified: we're working on a fix and will send an update asap

Investigating: We've identified the root cause as an upstream vendor incident. We're currently monitoring and investigating possible alternative actions. We see a delay of realtime destination delivery.

Investigating: We're in communication with the upstream provider, and preparing failover actions. Realtime destinations are also impacted by this outage - delivery of realtime event data is delayed, but no data is lost.

Investigating: We've identified the root cause as an upstream vendor incident. We're currently monitoring and investigating possible alternative actions

Investigating: We're experiencing an elevated level of session recording capture errors, which will lead to sessions not being captured. We're currently investigating the source of this issue. This is currently only impacting the US cloud

Resolved: We've confirmed that the fix resolved the issue.

Monitoring: We've identified the issue and have deployed a fix.

Investigating: We've rolled out a system improvement that broke authentication for the Google Cloud Storage and Google Pub/Sub destination. We are working to resolve the issue.

Resolved: All systems recovered and appear stable

Monitoring: Upstream vendor has provided a fix, and all systems are recovering.

Identified: we're working on a fix and will send an update asap

Investigating: We've identified the root cause as an upstream vendor incident. We're currently monitoring and investigating possible alternative actions. We see a delay of realtime destination delivery.

Investigating: We're in communication with the upstream provider, and preparing failover actions. Realtime destinations are also impacted by this outage - delivery of realtime event data is delayed, but no data is lost.

Investigating: We've identified the root cause as an upstream vendor incident. We're currently monitoring and investigating possible alternative actions

Investigating: We're experiencing an elevated level of session recording capture errors, which will lead to sessions not being captured. We're currently investigating the source of this issue. This is currently only impacting the US cloud

Resolved: We've deployed a fix. We apologize for any inconvenience.

Identified: We're experiencing elevated cases of users being asked for their 2FA, we've identified the issue and are deploying a fix.

Resolved: We've confirmed that the fix resolved the issue.

Monitoring: We've identified the issue and have deployed a fix.

Investigating: We've rolled out a system improvement that broke authentication for the Google Cloud Storage and Google Pub/Sub destination. We are working to resolve the issue.