Resolved after 11 hours 1 minute, affecting Prisma Accelerate and Prisma Postgres, on April 1, 2026.
A fix has been implemented and we are monitoring the results.
Affected components
Update timeline
- investigating Apr 01, 2026, 10:15 PM UTC
Description: We are investigating an issue where Accelerate cold starts have increased. Affected users: US East Root cause: Currently unknown Workarounds: For Prisma Postgres users we recommend Direct TCP with connection pooling enabled.
- investigating Apr 01, 2026, 11:36 PM UTC
We are continuing to investigate the issue. Affected users: US East, AP Northeast, AP Southeast, US West, EU Central Root cause: Currently unknown Workarounds: For Prisma Postgres users we recommend Direct TCP with connection pooling enabled.
- identified Apr 02, 2026, 12:57 AM UTC
We've isolated the root cause to an issue within Durable Objects. Cloudflare have an active status page. We're investigating mitigation options.
- identified Apr 02, 2026, 02:56 AM UTC
We are awaiting an update from Cloudflare. As the incident persists, we recommend not deploying new versions of your schema until the incident is resolved to avoid requesting a new Query Engine and encountering a cold start. Workarounds: For Prisma Postgres users we still recommend Direct TCP with connection pooling enabled.
- monitoring Apr 02, 2026, 05:43 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Apr 02, 2026, 09:17 AM UTC
The incident has been resolved.
Your product runs on more than Prisma Data
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services