Prisma connection fails :/
Today I encountered this issue, but the system has been working fine for the past few days:
0|aia-core-backend | 2025-11-03T16:31:03: prisma:error
0|aia-core-backend | 2025-11-03T16:31:03: Invalid
prisma.branch.findMany() invocation:
0|aia-core-backend | 2025-11-03T16:31:03:
0|aia-core-backend | 2025-11-03T16:31:03:
0|aia-core-backend | 2025-11-03T16:31:03: Can't reach database server at db.prisma.io:5432
0|aia-core-backend | 2025-11-03T16:31:03:
0|aia-core-backend | 2025-11-03T16:31:03: Please make sure your database server is running at db.prisma.io:5432.4 Replies
You decided to hold for human wisdom. We'll chime in soon! Meanwhile,
#ask-ai is there if you need a quick second opinion.I've been having that error on production today, it last for really little (seconds), then goes back up.
Seems that the problem is on Prisma's side.
Sure, look—sometimes this happens: I have 15 pool connections open out of 40 max, and the exact same query on the same connection fails and then works fine afterward :/
I'm thinking about moving to another DB provider. In the last month, Prisma has been failing too much :/
Hey!
Did you face these issues when using the direct connection string (starting with postgres://) or with the accelerate connection string (starting with prisma+postgres://)?