Cannot connect to Neon Postgres from local dev (P1001 / EAI_AGAIN DNS error)
Node.jsHello Neon team,
I’m unable to connect to my Neon PostgreSQL database from my local development environment.
Details: Database: Neon Postgres Connection type: Pooler endpoint Errors encountered include Prisma P1001 (can’t reach database server) and getaddrinfo EAI_AGAIN on the Neon pooler hostname. Even running npx prisma db pull fails with the same error. This issue happens consistently on my current network. I have verified the connection string, SSL settings, and Prisma configuration. Restarting services and flushing DNS did not resolve the issue.
It appears to be a DNS or routing issue reaching the Neon pooler endpoint from my ISP or region.
Please advise whether this pooler endpoint is currently healthy, if there are recommended alternatives such as using a direct connection, changing region, or forcing IPv4, or if there are any known connectivity issues affecting this hostname.
Thanks.
I’m unable to connect to my Neon PostgreSQL database from my local development environment.
Details: Database: Neon Postgres Connection type: Pooler endpoint Errors encountered include Prisma P1001 (can’t reach database server) and getaddrinfo EAI_AGAIN on the Neon pooler hostname. Even running npx prisma db pull fails with the same error. This issue happens consistently on my current network. I have verified the connection string, SSL settings, and Prisma configuration. Restarting services and flushing DNS did not resolve the issue.
It appears to be a DNS or routing issue reaching the Neon pooler endpoint from my ISP or region.
Please advise whether this pooler endpoint is currently healthy, if there are recommended alternatives such as using a direct connection, changing region, or forcing IPv4, or if there are any known connectivity issues affecting this hostname.
Thanks.
