Production database stuck after AWS us-east-1 outage - Need help
roject ID: cffllblnrjbjaltgtoqfRegion: us-east-1 (Free tier)
Problem:
My production database got stuck during yesterday's AWS outage and hasn't recovered even though the outage is resolved. All connection attempts fail with:
FATAL: Unable to check out process from the pool due to timeout
What I've tried:
-
Restarted pooler multiple times (15→20→15)
- Added ?pgbouncer=true to connection string
- Redeployed application
- Waited 12+ hours
- Submitted support ticket (SU-282150) - no response yet
-
Nothing clears the stuck connections
My dev database in us-east-2 works fine - same code, different region. Proves this is infrastructure, not code.
What I need:
Free tier doesn't have "Restart Database" button. My production site has been down for 12+ hours.
Is there any way to:
1. Manually kill stuck connections?
2. Force a database restart on Free tier?
3. Get faster support response?
Should I just upgrade to Pro temporarily to get the restart button?
Any help would be greatly appreciated!
Problem:
My production database got stuck during yesterday's AWS outage and hasn't recovered even though the outage is resolved. All connection attempts fail with:
FATAL: Unable to check out process from the pool due to timeout
What I've tried:
-
Restarted pooler multiple times (15→20→15)-
Added ?pgbouncer=true to connection string-
Redeployed application-
Waited 12+ hours-
Submitted support ticket (SU-282150) - no response yet-
Nothing clears the stuck connectionsMy dev database in us-east-2 works fine - same code, different region. Proves this is infrastructure, not code.
What I need:
Free tier doesn't have "Restart Database" button. My production site has been down for 12+ hours.
Is there any way to:
1. Manually kill stuck connections?
2. Force a database restart on Free tier?
3. Get faster support response?
Should I just upgrade to Pro temporarily to get the restart button?
Any help would be greatly appreciated!
