Looking for an update now? Check the current status, or follow Prisma for future changes.
89.5%of 57 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
September 2026
93.1%
29
2
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Jul 23Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
We are continuing to monitor. There has been no increase in errors.
identified
A fix has been rolled out and errors are dropping.
identified
The issue has been identified and we are rolling out a fix.
investigating
Description: We are investigating an increase in connections errors to Prisma Postgres.
Affected users: All Regions
Root cause: Currently unknown
Workarounds: None identified
September 2026
Degraded performance on Prisma Postgres for some users in US East.
We are continuing to monitor for any further issues.
monitoring
The issue has been resolved, we're continuing to monitor.
identified
Description: We've identified an issue causing disruption on some databases in US East.
Affected users: Some users in US East.
Root cause: Identified.
Workarounds: None
Accelerate is unable to provision new query engines in eu-west-3
The capacity problems have subsided. We are monitoring the situation.
identified
Description: We have identified an upstream infrastructure provider capacity issue affecting the eu-west-3 region. Accelerate is experiencing intermittent issues provisioning resources for new query engine instances in this region. No other regions are impacted.
Affected users: Users provisioning new Accelerate query engines in the eu-west-3 region.
Root cause: Upstream infrastructure provider capacity
Workarounds: None identified
monitoring
The capacity problems have subsided. We are monitoring the situation.
identified
Description: We have identified an upstream infrastructure provider capacity issue affecting the eu-west-3 region. Accelerate is experiencing intermittent issues provisioning resources for new query engine instances in this region. No other regions are impacted.
Affected users: Users provisioning new Accelerate query engines in the eu-west-3 region.
Root cause: Upstream infrastructure provider capacity
Workarounds: None identified
Legacy Incident Archive
8 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
August 2026
Accelerate is slow to provision new query engines in eu-west-3
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We have identified an upstream infrastructure provider issue affecting the eu-west-3 region. Accelerate is experiencing issues provisioning resources for new query engine instances.
Affected users: Users provisioning new Accelerate query engines in the eu-west-3 region.
Root cause: AWS EC2 instance capacity saturation
Workarounds: None identified
July 2026
Degraded service for Accelerate cold starts
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We are investigating an upstream service provider incident impacting Accelerate cold starts in all regions.
Impact: Allocations of new query engines may be delayed or fail.
Root cause: Accelerate is receiving degraded responses from Cloudflare's DNS API.
Workarounds: TCP connections for Prisma Postgres databases are unaffected.
Accelerate incident impacting the eu-central-1 region
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
We are no longer observing impact of this incident and traffic has returned to normal. We will continue to monitor until the upstream service provider closes their incident.
investigating
We have applied mitigations to narrow the impact. We are continuing work toward a full mitigation.
investigating
Description: We are investigating an upstream service provider incident impacting Accelerate service in the eu-central-1 region.
Affected users: allocations of new query engines in eu-central-1
Root cause: upstream service provider disruption
Workarounds: none
Degraded service for Accelerate in us-east-1 and us-west-1
minorSource not attested
Last archived state: resolved
View archived record details
investigating
Accelerate is impacted by degraded service in AWS regions us-east-1 and us-west-1. We are investigating other possible causes.
June 2026
Errors provisioning Prisma Postgres databases
majorSource not attested
Last archived state: resolved
View archived record details
investigating
We are investigating errors provisioning new Prisma Postgres databases in some regions.
April 2026
Degraded performance and accessibility for Prisma products
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Prisma Accelerate and the Prisma Console are experiencing degraded performance resulting from a Cloudflare outage. Customers may notice timeouts and connection failures.
We are monitoring the impact on our systems. More information may be available at Cloudflare's status pages:
- https://www.cloudflarestatus.com/incidents/lq1vw7z9xthq
- https://www.cloudflarestatus.com/incidents/213v4v7s7m97
Increase in Accelerate cold start time
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
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.
identified
We've isolated the root cause to an issue within Durable Objects. Cloudflare have an active status page.
We're investigating mitigation options.
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.
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.
March 2026
Degraded performance in US East
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been rolled out and US East is now operational. We're continuing to monitor.
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
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
