PostHog Status

Resolved: Event and property definitions backfill has been completed, and new definitions are being generated in real time. System stability is being actively monitored.

Monitoring: The issue has been identified and resolved, new event and property definitions are now being created properly. We're re-processing historical data to ensure all definitions are available for use.

Investigating: The database failover was completed successfully, however it did not appear to be the root cause and new event names are still delayed. We are still investigating this

Identified: We have identified the root cause as a database issue, we will shortly be performing a database failover which may result in some ingestion delays. There will not be any data loss

Investigating: New event names (ie posthog.capture('new event name')) are not being created or are severely delayed in being created. That means that you can't select them in the interface

Resolved: Event and property definitions backfill has been completed, and new definitions are being generated in real time. System stability is being actively monitored.

Monitoring: The issue has been identified and resolved, new event and property definitions are now being created properly. We're re-processing historical data to ensure all definitions are available for use.

Investigating: The database failover was completed successfully, however it did not appear to be the root cause and new event names are still delayed. We are still investigating this

Identified: We have identified the root cause as a database issue, we will shortly be performing a database failover which may result in some ingestion delays. There will not be any data loss

Investigating: New event names (ie posthog.capture('new event name')) are not being created or are severely delayed in being created. That means that you can't select them in the interface

Resolved: Event and property definitions backfill has been completed, and new definitions are being generated in real time. System stability is being actively monitored.

Monitoring: The issue has been identified and resolved, new event and property definitions are now being created properly. We're re-processing historical data to ensure all definitions are available for use.

Investigating: The database failover was completed successfully, however it did not appear to be the root cause and new event names are still delayed. We are still investigating this

Identified: We have identified the root cause as a database issue, we will shortly be performing a database failover which may result in some ingestion delays. There will not be any data loss

Investigating: New event names (ie posthog.capture('new event name')) are not being created or are severely delayed in being created. That means that you can't select them in the interface

Resolved: Two missing indexes were created, which resolved the query time out that was the root cause of the deletion failure. Delete API requests should now be functioning as normal.

Identified: We're seeing that person deletes via the API are returning an elevated number of 504's/time outs in the EU region. This appears to be due to degraded query performance in our database, along the path required to delete person profiles. We're working to resolve this now.