Before 1/14, my fly app was able to reliably reach my Supabase instance at aws-0-us-east-1.pooler.supabase.com:6543
But starting 1/15, I start seeing elevated Prisma connection error like
“Can’t reach database server at aws-0-us-east-1.pooler.supabase.com:6543
” especially for the first request after having no request for a while.
I’m able to reach the Supabase using the same connection configuration from my laptop. So I suspect the issue come from Fly io networking. If I reload the page, the connection will usually go through though.
I also tried switching my database to AWS RDS with public access. My laptop can reliably connect to AWS RDS, while my fly machine would give connection errors like Can't reach database server at
xxxxxxxx-xxxxxxxx.us-east-1.rds.amazonaws.com:5432`.
Is there networking issue going on at iad region that prevents fly machine from reaching aws domain?