Suddenly unable to connect to my external database in SEA region, switching region fixes.

Hi! Just wanted to chime in that I had users report that my website was down. After checking my logs in Fly, I see:

2022-03-31T22:10:08Z app[1a9d49d3] sea [info]Starting init (commit: 6f9865f)...
2022-03-31T22:10:08Z app[1a9d49d3] sea [info]Preparing to run: ` npm run start` as root
2022-03-31T22:10:08Z app[1a9d49d3] sea [info]2022/03/31 22:10:08 listening on [fdaa:0:3778:a7b:2d30:1a9d:49d3:2]:22 (DNS: [fdaa::3]:53)
2022-03-31T22:10:09Z app[1a9d49d3] sea [info]> releasehub-server@0.0.0 start /workspace
2022-03-31T22:10:09Z app[1a9d49d3] sea [info]> node dist/api/app.js
2022-03-31T22:10:17Z app[1a9d49d3] sea [info](node:539) UnhandledPromiseRejectionWarning: Error: Can't reach database server at ``:`25060`
2022-03-31T22:10:17Z app[1a9d49d3] sea [info]Please make sure your database server is running at ``:`25060`.

Unable to connect to my database…Which is weird because this had been working completely fine and I had not deployed any changes for a weeks.

I moved my instance to ORD:

jordan@Jordans-iMac encore % fly regions set ord -a encore-graphql
**Region Pool:**
**Backup Region:**

And now my app is running fine. Did something happen in the SEA region disallowing connections all of a sudden?


We’re looking into it: Status - Connectivity failures in the Seattle region

Indeed we’re seeing these issues in Seattle and are looking into it.

woo! thank you both @michael @joshua haha