Loading status…
Prisma Data Platform status · Data & Backend · checked (2s ago)
Also searched as Prisma, Prisma Accelerate, Prisma Postgres.
No — Prisma Data Platform is not down. All Prisma Data Platform systems are reported operational.
According to Prisma Data Platform's official status page, Prisma Data Platform was reporting “All Systems Operational” when isuptime last checked at . Over the last 30 days, Prisma Data Platform's feed reported no outage in 100.00% of our checks.
Everything above is read from Prisma Data Platform's own status feed. This is what other visitors are saying in the last 24 hours — useful when the feed is green and you are still stuck, and never used to change the status above.
Nobody has reported Prisma Data Platform in the last 24 hours. Yours would be the first.
Reports are anonymous counts and are kept for 24 hours, then deleted. No account, no message, nothing stored about who reported. One report per service per hour, changeable until the hour is out.
This is the Prisma Data Platform — Accelerate's connection pooling and caching, Prisma Postgres and the associated console. The Prisma ORM itself is a library that runs in your own application and has no service behind it, so it cannot be down.
The status page covers the hosted platform only. This is the distinction that matters most on this page: if you use Prisma purely as an ORM talking straight to your own database, nothing here can affect you, and an incident on this page is irrelevant to your application. Only traffic routed through Accelerate or Prisma Postgres is exposed.
isuptime reads this feed on a schedule and reports what it says — how that works, in detail.
One bar per day. Each shows the share of that day's checks where Prisma Data Platform's own status feed reported no outage — degraded counts as no-outage. Days with no bar are days isuptime recorded no checks, not days Prisma Data Platform was down.
14 other services isuptime tracks were also reporting a problem as of the same check, 2s ago. They are checked on one schedule, so the timing is comparable — but overlapping in time does not mean they share a cause.
Each point is one check of Prisma Data Platform's status endpoint.
Prisma Data Platform has published 26 incidents in the last 12 months, the 20 most recent shown here. Only what Prisma Data Platform posted itself — not every problem users hit.
resolved · Sep 1, 06:52 AM (18d ago)
resolved · Aug 3, 10:01 AM (47d ago)
resolved · Jul 31, 12:27 PM (50d ago)
resolved · Jul 17, 01:03 PM (64d ago)
resolved · Jul 8, 11:24 AM (73d ago)
resolved · Jun 18, 05:53 PM (93d ago)
resolved · Apr 14, 12:44 PM (158d ago)
resolved · Apr 8, 09:40 AM (164d ago)
resolved · Apr 1, 10:15 PM (171d ago)
resolved · Mar 27, 03:19 PM (176d ago)
resolved · Mar 3, 09:04 AM (200d ago)
resolved · Feb 4, 06:25 PM (227d ago)
resolved · Jan 27, 06:56 PM (235d ago)
resolved · Jan 9, 01:43 PM (253d ago)
resolved · Dec 5, 09:03 AM (288d ago)
resolved · Dec 3, 09:49 PM (290d ago)
resolved · Nov 21, 12:22 PM (302d ago)
resolved · Nov 18, 12:06 PM (305d ago)
resolved · Nov 13, 10:09 AM (310d ago)
resolved · Oct 28, 04:55 PM (326d ago)
A Prisma error in your application is almost always your own database — connection limits, a migration that has not run, or a pool that is exhausted. `prisma generate` and `prisma migrate` failures are local tooling. If you do use Accelerate, note that its cache is regional and a cold region adds latency that is easily mistaken for degradation.
