Elevated API Errors

We've reverted a change that moved our infrastructure from pgbouncer to rds-proxy until we can root cause what exactly happened after a burst of traffic saturated rds-proxy. All systems are back to normal operating conditions. Enjoy your Friday and enjoy your weekend!

We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.

We're experiencing an elevated level of API errors and have identified the issue as a connections count issue to our postgres instance. We are working to mitigate. The application (us.posthog.com) is back online and we are processing events. However, we still are experiencing issues with feature flag endpoints and are working to bring those back online.