Connection pooler aws-0-us-east-2 unreachable Prisma - P1001 error
Hi! Having connection issues with our project that uses prisma to interface with the databse. We pay for the the pro plan and are new to supabase. The application on our local dev machines cannot connect or test the application it was completely functional and then suddenly P1001. Its been working for days no code changes on our side. Supabase has no IP Bans either visible in our Supabase Dashboard
Error: P1001 - Can't reach database server at aws-0-us-east-2.pooler.supabase.com:5432
Region: US East 2
What's weird:
- Port test succeeds (5432 is open)
- Project shows as active/not paused
- Was working fine, then suddenly stopped
- Both pooled AND direct connections fail
- No code changes on my end
Tried:
✅ Restarting API server
✅ Fresh connection strings
✅ Direct connection (non-pooled)
✅ URL encoding/decoding password
❌ Still can't connect
Is there an infrastructure issue with the us-east-2 pooler? Any known issues or workarounds?
3 Replies
Check your database settings at bottom of page and see if there are any IP blocks.
No outage on status page and you are only one here reporting anything
no ip blocks visible
I've reached out to Supabase official support its such a strange error works one day doesnt the work the next - we've tried all the different prisma connection string options, IPV4 IPV6 pg bouncer pooler non pooler. Hoping its an obvious miss on our side. No IP blocks, no firewalls
Same thing here today