Prisma Data Outage History

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.

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.

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

We are seeing degraded performance in the CDG and FRA regions for PPG. We are investigating.

Prisma Postgres Direct TCP is experiencing degraded service in our US East (Newark) and EU Central (Frankfurt) regions. We have identified the cause and are investigating a fix.

Description: We've identified an issue where a small set of free tier users are depleting their usage quota faster than expected. We're currently investigating the issue and potential workarounds. Affected users: Small set of free tier users Root cause: Currently unknown Workarounds: None identified

An upstream infra provider is experiencing issues which is impacting our services. We are monitoring the situation.

Description: An upstream provider, Cloudflare, is experiencing an outage of critical services. The following services are impacted: Accelerate: Users are unable to connect to their database via Accelerate Console: Console is unavailable and returns a 500 error page. Prisma Postgres: Direct TCP is unaffected, users querying via Accelerate will be unable to to connection. Affected users: All users Root cause: Upstream infrastructure provider Workarounds: Please use direct TCP when connecting to your Prisma Postgres database.

We are currently investigating this issue.

Description: We are investigating the impact of a suspected disruption that affected the Prisma Postgres restore functionality in the Console.

Description: We are currently investigating Prisma Postgres connection issues in US East. Affected users: Users connecting from applications running in US East. Root cause: Currently unknown Workarounds: None identified

Description: We are investigating the impact of a suspected disruption that was automatically detected by our system. Affected users: Currently unknown Root cause: Currently unknown Workarounds: None identified

Description: We are investigating an issue affecting AP South East in starting new query engines. Active query engines remain operational. Affected users: AP South East Root cause: Currently unknown Workarounds: None identified

We're investigating an issue affecting the us-east-1 region. Accelerate experiences issues provisioning resources for new query engine instances. Affected users: Users provisioning new Accelerate query engines in the us-east-1 region. Existing query engines are working as expected

We identified that the Accelerate provisioning problems started to affect console.prisma.io and api.prisma.io. Customers are experiencing timeouts when loading console and when issuing requests to prismas management API.

We're seeing a drop in incoming request and suspect a network connectivity issue between our edge proxy and the query engines for us-east-1.

Investigating increased error rates due to network degradation of a upstream provider

The upstream provider has identified the issue and are implementing a fix. We are monitoring the situation closely.

Upstream provider is continuing work on a fix. Impacted region appears to be restricted around the Frankfurt data centre.

Upstream provider has mitigated the current impact and continues to work on a fix.

We are investigating the impact of an existing disruption that was automatically detected by our system. Affected users: Currently unknown Root cause: Currently unknown Workarounds: None identified