Database connection errors for `ap-southeast-2`

[haydn]

Bug report

• [x] I confirm this is a bug with Supabase, not with my own application.
• [x] I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug

Since maintenance (which I believe was an upgrade to Supavisor 2.0) was done on Supabase's ap-southeast-2 region on January 28 (https://status.supabase.com/incidents/cbzhwr1wjr5b), we have been getting {:shutdown, :db_termination} errors.

I known the upgrade for other regions had to be rolled-back (https://status.supabase.com/incidents/zk493yyz17hy), but it's unclear to me what the status of ap-southeast-2 is. Was it one of the 9 that got upgraded early? Was it rolled-back as part of the incident response?

To Reproduce

I have not been able to reliably reproduce this issue, but it's constantly occurring for our users.

Expected behavior

No errors.

Screenshots

Graph of {:shutdown, :db_termination} errors in our logs (times are using Australia/Sydney time zone):

Graph of 504 responses from our application (times are using Australia/Sydney time zone):

Recent pooler logs in Supabase dashboard:

System information

N/A

Additional context

• #567

I will also log a support request via the Supabase dashboard and link to this issue.