Prisma Outage History
Uptime record, past incidents, and downtime history for Prisma.
Checking current status...
90-Day Trend
Monthly Uptime
| Month | Uptime | Days Tracked | Days with Issues |
|---|---|---|---|
| April 2026 | 70% | 10 | 3 |
| March 2026 | 87.1% | 31 | 4 |
| February 2026 | 81.8% | 22 | 4 |
Uptime is calculated from daily worst-status snapshots. A day with any non-operational status counts as a day with issues.
Daily Status (Last 63 Days)
Feb 7
Today
Operational
Degraded
Partial Outage
Major Outage
Maintenance
No Data
Incident History
April 2026
Increase in Accelerate cold start time
Started: Apr 1, 10:15 PM
monitoring
A fix has been implemented and we are monitoring the results.
Apr 2, 5:43 AM
identified
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.
Apr 2, 2:56 AM
identified
We've isolated the root cause to an issue within Durable Objects. Cloudflare have an active status page.
We're investigating mitigation options.
Apr 2, 12:57 AM
investigating
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.
Apr 1, 11:36 PM
investigating
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.
Apr 1, 10:15 PM
March 2026
Degraded performance in US East
Started: Mar 27, 3:19 PM
monitoring
A fix has been rolled out and US East is now operational. We're continuing to monitor.
Mar 27, 3:34 PM
identified
Description: We have identified an issue degraded performance in the US East region and are working to implement a fix.
Affected users: US East
Root cause: The cause has already been identified and we're implementing a fix.
Workarounds: None identified
Mar 27, 3:23 PM
investigating
Description: We have identified an issue degraded performance in the US East region and are working to implement a fix.
Affected users: US East
Root cause: Currently unknown
Workarounds: None identified
Mar 27, 3:19 PM