This incident has been fully resolved. We sincerely apologise for the inconvenience caused by this internal routing issue.
We have identified affected users and our teams will be getting in touch to let you know how we will be rectifying the issue whilst this small number of database clusters were unavailable. There is no need to contact our Support team in advance.
If you are experiencing any further issues, please do contact our Support Team who are ready to assist you.
Posted May 25, 2026 - 16:56 UTC
Monitoring
A fix has been implemented and we are monitoring the results.
Posted May 25, 2026 - 16:30 UTC
Update
Our engineering team are currently testing a resolution to this issue. We expect the issue to be resolved very shortly.
Posted May 25, 2026 - 15:29 UTC
Update
We are continuing to work on a fix for this issue.
Posted May 25, 2026 - 14:50 UTC
Identified
We've identified an issue with Serverless Postgres hostnames in the Singapore region and are working on a fix with our upstream provider.
Posted May 24, 2026 - 20:56 UTC
Investigating
We are currently investigating this issue.
Posted May 24, 2026 - 17:44 UTC
This incident affected: Serverless Postgres (Serverless Postgres - Asia Pacific (Singapore)).