DNS Resolution Failure - Connection Pooler aws-0-us-east-1.pooler.supabase.com
I'm experiencing a critical DNS resolution issue preventing my self-hosted n8n workflows from connecting to the Supabase database through the connection pooler.
ISSUE DETAILS:
- Error: getaddrinfo EAI_AGAIN aws-0-us-east-1.pooler.supabase.com
- Pooler Host: aws-0-us-east-1.pooler.supabase.com
- Error Type: DNS resolution failure (EAI_AGAIN)
- Started: November 11, 2025, ~09:18 AM (UTC-3)
- Impact: All database queries from n8n are failing
TECHNICAL CONTEXT:
- n8n Version: 1.110.1 (Self Hosted)
- Node: Postgres v2.5 (n8n-nodes-base.postgres)
- Operation: SELECT queries
WHAT I'VE VERIFIED:
✓ My server has internet connectivity
✓ Other external services are accessible
✓ Issue is specific to the Supabase pooler hostname
✓ Connection credentials are correct
WHAT I NEED:
1. Confirmation if there are DNS issues with the pooler endpoint
2. Any ongoing incidents in us-east-1 region
3. Recommended workaround or alternative connection method
This is affecting production workflows. Any urgent guidance would be appreciated.
ISSUE DETAILS:
- Error: getaddrinfo EAI_AGAIN aws-0-us-east-1.pooler.supabase.com
- Pooler Host: aws-0-us-east-1.pooler.supabase.com
- Error Type: DNS resolution failure (EAI_AGAIN)
- Started: November 11, 2025, ~09:18 AM (UTC-3)
- Impact: All database queries from n8n are failing
TECHNICAL CONTEXT:
- n8n Version: 1.110.1 (Self Hosted)
- Node: Postgres v2.5 (n8n-nodes-base.postgres)
- Operation: SELECT queries
WHAT I'VE VERIFIED:
✓ My server has internet connectivity
✓ Other external services are accessible
✓ Issue is specific to the Supabase pooler hostname
✓ Connection credentials are correct
WHAT I NEED:
1. Confirmation if there are DNS issues with the pooler endpoint
2. Any ongoing incidents in us-east-1 region
3. Recommended workaround or alternative connection method
This is affecting production workflows. Any urgent guidance would be appreciated.
