System Status

This incident has been resolved.

Projects running Postgres version 14 in us-east-1 and ap-northeast-2 may experience query slowness. We've identified the cause and are working on a fix.

This incident has been resolved.

We are investigating reports of increased Edge Function latency and elevated rates of HTTP 503 responses, beginning at approximately 06:00 UTC. Our team is working to identify the cause and will provide further updates as they become available.

We observed latency issues over the weekend resulting in 504 errors primarily impacting customers on the Free tier. The incident has been resolved.

Between 05:50–06:05 UTC some customer using connection pooler in us-east-1 may have experienced brief dropped connections or connection disruptions. This issue was caused by an unexpected restart of connection pooler instances in the affected cluster. We apologize for any disruption caused.

Lifecycle operations have been re-enabled for 100% of users and error rates have returned to normal.

We are seeing increased error rates in actions across all project lifecycle actions - Creations, Deletions, Restores, Configuration and Compute size upgrades. We are currently looking into the cause. Out of an abundance of caution, we would suggest against taking any of these actions until this incident is resolved. We will provide additional updates as we have more information

Customers should now be able to connect to branch environments via MCP normally.

We have pushed a fix to address the root cause and are monitoring the situation. If you continue to see an error, you can re-authenticate with the MCP server and also confirm that you have access to the preview branch.

UPDATE: We are currently pushing a fix to address the root cause. We'll provide another update once the fix has been fully deployed.