problems

[UT20232025]

My Prisma Postgres database (project "Genwelth AI", region Frankfurt) returns "Failed to connect to upstream database" on every connection for several hours. It's under all free-tier limits (0.9 MiB / 512 MiB storage, 84.7K / 200K operations), the project shows Live, and status.prisma.io is green. The same connection string worked earlier today — the instance failed mid-operation. Please restart / investigate the instance.

[jhmartins1]

Since the same connection string was working earlier and the database became unreachable mid-operation while the project still reports as Live, this sounds more like an instance/infrastructure issue than a Prisma Client configuration problem.

A few things I'd check first to rule out a client-side issue:

1. Try connecting directly using the same connection string with psql or another PostgreSQL client. If that also returns an upstream connection error, it would confirm that the problem isn't specific to Prisma Client.

2. Create/regenerate a connection string from the Prisma Console and test it separately, just to rule out a credential/connection-string issue.

3. If both the old and newly generated connection strings fail while the project remains Live, I'd contact Prisma support and include the project/region and approximate time when the failure started. Since this appears to be isolated to the database instance, a public status page can still remain green if the broader service is operational.

Given that it failed mid-operation without a configuration change, I wouldn't start changing the schema, migrations, or Prisma Client setup yet.

If you can share the exact error returned by psql (with credentials removed), that could help determine whether this is definitely an upstream instance issue or something at the connection layer.

[nios-x]

Thanks for the detailed suggestions. I’ll try connecting directly using psql with the same connection string and also test a newly generated connection string from the Prisma Console.

Since the database became unreachable in the middle of an operation without any configuration changes, I’ll avoid changing the Prisma Client, schema, or migrations for now. If both connection strings fail, I’ll share the exact psql error along with the project/region and approximate failure time so we can determine whether this is an infrastructure/instance issue.