Prisma Postgres suspended before reaching 100k limit

Help
1

Current versus Expected behavior

My Prisma Postgres database on Vercel got suspended, even though the usage shows only around 47.1k operations — well below the 100k free plan limit.

I expected the database to remain active until it reached the 100k operation limit, but it was suspended early.
Now I can’t access my important data stored there.

I just need temporary reactivation so I can take a backup, or a data dump/export of the database.

Code, configuration, and steps that reproduce this issue

No code issue — this is a platform-level problem.

  • Prisma database hosted via Vercel Storage → Prisma Postgres.
  • Plan: Free (100k operations/month)
  • Actual usage shown: ~47.1k
  • Status: Suspended
  • Unable to connect via Prisma Client or Studio.

Steps:

  1. Created Prisma Postgres on Oct 9
  2. Used normally with Next.js app
  3. Suddenly marked as “Suspended” even though usage below limit.

Project information (URL, framework, environment, project settings)

  • Project name: tawakkul-agro
  • Account: Baitul Hikmah (Hobby plan)
  • Framework: Next.js + Prisma
  • Database: Prisma Postgres (Free tier)
  • Environment: Vercel hosted

Request

Please help me reactivate my suspended database temporarily
or provide a data export/dump file so I can recover my data safely.

Thank you :folded_hands:

4

The marketplace integrations such as Prisma Postgres are hosted by third parties – in this case, Prisma is the one in charge of your database.

I believe “suspended” in this context refers to the database being paused due to inactivity, and you may just need to revive it on the Prisma dashboard.

You can get there by going from Vercel to Storage → Prisma Postgres → Open in Prisma which will open the vendor’s dashboard

image
image870×316 4.72 KB