© 2026 Hedgehog Software, LLC

TwitterGitHubDiscord
More
CommunitiesDocsAboutTermsPrivacy
Search
Star
Setup for Free
SupabaseS
Supabase•6mo ago•
5 replies
FekAroundFerret

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?
Supabase banner
SupabaseJoin
Supabase gives you the tools, documentation, and community that makes managing databases, authentication, and backend infrastructure a lot less overwhelming.
45,816Members
Resources

Similar Threads

Was this page helpful?
Recent Announcements

Similar Threads

DNS Resolution Failure - Connection Pooler aws-0-us-east-1.pooler.supabase.com
SupabaseSSupabase / help-and-questions
3mo ago
is aws-1-us-east-2 pooler healthy?
SupabaseSSupabase / help-and-questions
4mo ago
aws-1-us-east-2 shared pooler timing out
SupabaseSSupabase / help-and-questions
4mo ago
Error: P1001: Can't reach database server at `aws-0-us-east-1.pooler.supabase.com:5432`
SupabaseSSupabase / help-and-questions
16mo ago