Prisma

Affected: Prisma Compute

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-15 19:34 UTC

   Description: We are investigating an increase in connections errors to Prisma Postgres. Affected users: All Regions Root cause: Currently unknown Workarounds: None identified

2. identified 2026-10-15 20:04 UTC

   The issue has been identified and we are rolling out a fix.

3. identified 2026-10-15 20:54 UTC

   A fix has been rolled out and errors are dropping.

4. monitoring 2026-10-15 21:32 UTC

   We are continuing to monitor. There has been no increase in errors.

5. resolved 2026-10-15 23:28 UTC

   We are continuing to observe healthy traffic to Prisma Postgres across all regions. This incident has been resolved.

Excerpts are shortened. Read the full incident on Prisma's status page.

Affected: Prisma Postgres

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-09-22 18:47 UTC

   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

2. monitoring 2026-09-22 18:51 UTC

   The issue has been resolved, we're continuing to monitor.

3. monitoring 2026-09-22 18:51 UTC

   We are continuing to monitor for any further issues.

4. resolved 2026-09-22 19:52 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Prisma's status page.

Affected: Prisma Accelerate

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-09-01 06:52 UTC

   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:...

2. monitoring 2026-09-01 08:15 UTC

   The capacity problems have subsided. We are monitoring the situation.

3. identified 2026-09-01 08:34 UTC

   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:...

4. monitoring 2026-09-01 08:59 UTC

   The capacity problems have subsided. We are monitoring the situation.

5. resolved 2026-09-01 09:16 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Prisma's status page.

Affected: Prisma Accelerate

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. monitoring 2026-08-03 10:01 UTC

   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...

2. resolved 2026-08-03 10:47 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Prisma's status page.

Affected: Prisma Accelerate

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Cloudflare.

1. investigating 2026-07-31 12:27 UTC

   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...

2. resolved 2026-07-31 13:27 UTC

   Responses from Cloudflare's API have returned to nominal behavior and Accelerate has recovered.

Excerpts are shortened. Read the full incident on Prisma's status page.

Affected: Prisma Accelerate

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-07-17 13:03 UTC

   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

2. investigating 2026-07-17 15:13 UTC

   We have applied mitigations to narrow the impact. We are continuing work toward a full mitigation.

3. monitoring 2026-07-17 16:16 UTC

   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.

4. resolved 2026-07-17 16:54 UTC

   We are continuing to observe successful traffic from Accelerate. This incident has been resolved.

Excerpts are shortened. Read the full incident on Prisma's status page.

Affected: Prisma Accelerate

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-07-08 11:24 UTC

   Accelerate is impacted by degraded service in AWS regions us-east-1 and us-west-1. We are investigating other possible causes.

2. resolved 2026-07-08 11:39 UTC

   Accelerate is operating within normal tolerances.

Excerpts are shortened. Read the full incident on Prisma's status page.

Affected: Prisma Console, Prisma MCP Server, Prisma Management API

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-18 17:53 UTC

   We are investigating errors provisioning new Prisma Postgres databases in some regions.

2. resolved 2026-06-18 20:22 UTC

   We've identified the issue and applied a mitigation.

Excerpts are shortened. Read the full incident on Prisma's status page.

Affected: Prisma Console, Prisma Accelerate

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Cloudflare.

1. monitoring 2026-04-14 12:44 UTC

   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:...

2. resolved 2026-04-15 04:53 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Prisma's status page.

Affected: Prisma Accelerate

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-04-08 09:40 UTC

   The issue has been identified and a fix is being implemented.

2. monitoring 2026-04-08 09:43 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-04-08 09:49 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Prisma's status page.

Affected: Prisma Postgres, Prisma Accelerate

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Cloudflare.

1. investigating 2026-04-01 22:15 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.

2. investigating 2026-04-01 23:36 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.

3. identified 2026-04-02 00:57 UTC

   We've isolated the root cause to an issue within Durable Objects. Cloudflare have an active status page. We're investigating mitigation options.

4. identified 2026-04-02 02:56 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...

5. monitoring 2026-04-02 05:43 UTC

   A fix has been implemented and we are monitoring the results.

6. resolved 2026-04-02 09:17 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Prisma's status page.

Affected: Prisma Postgres

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-27 15:19 UTC

   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

2. identified 2026-03-27 15:23 UTC

   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

3. monitoring 2026-03-27 15:34 UTC

   A fix has been rolled out and US East is now operational. We're continuing to monitor.

4. resolved 2026-03-27 17:25 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Prisma's status page.

Affected: Prisma Postgres

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-03-03 09:04 UTC

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

2. identified 2026-03-03 09:18 UTC

   We have identified an issue with an upstream provider in the Paris region and are implementing mitigations.

3. resolved 2026-03-03 09:27 UTC

   The upstream issue has been resolved. The impact to users was minimal.

Excerpts are shortened. Read the full incident on Prisma's status page.

Affected: Prisma Accelerate

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-02-04 18:25 UTC

   Accelerate customers may experience errors when new query engine instances are provisioned caused by active upstream service provider incident. We're working to monitor the situation and apply mitigations.

2. monitoring 2026-02-04 18:47 UTC

   Mitigations have been applied and we are observing healthy traffic through Accelerate. We are continuing to monitor.

3. resolved 2026-02-04 18:59 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Prisma's status page.

Affected: Prisma Postgres

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-01-27 18:56 UTC

   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.

2. monitoring 2026-01-27 20:50 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-01-27 21:01 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Prisma's status page.

Affected: Prisma Postgres, Prisma Console, Prisma Accelerate

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-01-09 13:43 UTC

   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...

2. monitoring 2026-01-09 13:48 UTC

   The issue has been resolved and we're actively monitoring the situation.

3. monitoring 2026-01-09 16:18 UTC

   We have confirmed this issue is related to an upstream provider and we are continuing to monitor the situation. During this time, usage data may also appear higher for some time ranges in the Prisma Console.

4. resolved 2026-01-10 00:30 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Prisma's status page.

Affected: Prisma Postgres, Prisma Console, Prisma Accelerate

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Cloudflare.

1. investigating 2025-12-05 09:03 UTC

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

2. investigating 2025-12-05 09:12 UTC

   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...

3. monitoring 2025-12-05 09:15 UTC

   A fix has been deployed by Cloudflare and our all services appear to have come back online. We're continuing to monitor.

4. monitoring 2025-12-05 09:17 UTC

   We are continuing to monitor for any further issues.

5. resolved 2025-12-05 09:28 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Prisma's status page.

Affected: Prisma Accelerate

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-12-03 21:49 UTC

   Accelerate is experiencing issues while provisioning resources for new query engine instances. The issue has been identified and a fix is being implemented.

2. monitoring 2025-12-03 22:21 UTC

   Accelerate has begun to recover. We are continuing to monitor the fix.

3. resolved 2025-12-03 22:36 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Prisma's status page.

Affected: Prisma Postgres

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2025-11-21 12:22 UTC

   Description: We are monitoring ongoing network connectivity issues from an upstream provider causing some requests to Prisma Postgres to fail. Affected users: Asia Root cause: Upstream infrastructure provider Workarounds: None identified

2. monitoring 2025-11-21 12:40 UTC

   We are continuing to monitor for any further issues.

3. resolved 2025-11-21 14:59 UTC

   The issue has been resolved by our upstream provider.

Excerpts are shortened. Read the full incident on Prisma's status page.

Affected: Prisma Accelerate

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2025-11-18 12:06 UTC

   We identified an upstream infrastructure provider issue. Accelerate is experiencing issues while provisioning resources for new query engine instances. The ORM engine binary downloads are also currently impacted. We're working on mitigating and monitoring the situation and...

2. identified 2025-11-18 13:07 UTC

   Latest update from our infrastructure provider is that the they are continuing to investigate the issue. Prisma Postgres direct TCP remains unaffected.

3. identified 2025-11-18 13:13 UTC

   The issue has been identified and a fix is being implemented by our upstream provider. Prisma Postgres direct TCP remains unaffected.

4. monitoring 2025-11-18 15:01 UTC

   The issue has been resolved and we're actively monitoring. Prisma Postgres direct TCP remains unaffected.

5. resolved 2025-11-18 19:12 UTC

   We're continuing to observe healthy traffic through Prisma Accelerate. This incident has resolved.

Excerpts are shortened. Read the full incident on Prisma's status page.

Affected: Prisma Postgres, Prisma Accelerate

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-11-13 10:09 UTC

   We are currently investigating this issue.

2. identified 2025-11-13 14:02 UTC

   We have identified degraded network connectivity between two upstream providers. We have reached out to the providers for a resolution.

3. monitoring 2025-11-13 15:39 UTC

   Network connectivity between the upstream providers appears to be improving. We are continuing to monitor the issue.

4. monitoring 2025-11-13 16:11 UTC

   Network connectivity appears to have returned to nominal performance. We are continuing to monitor.

5. resolved 2025-11-13 17:01 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Prisma's status page.

Affected: Prisma Accelerate

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-10-28 16:55 UTC

   Accelerate is experiencing issues while provisioning resources for new query engine instances. We are investigating the source of the issue.

2. investigating 2025-10-28 17:44 UTC

   We have identified an incident with an upstream provider. We will continue to monitor the situation and will provide feedback as soon as it becomes available.

3. identified 2025-10-28 18:44 UTC

   We're continuing to monitor the situation.

4. monitoring 2025-10-28 18:56 UTC

   Upstream provider have identified the issue and implemented mitigations. Services are currently operational as a result. We're continuing to monitor the situation.

5. resolved 2025-10-28 19:24 UTC

   We're continuing to observe nominal traffic through Prisma Accelerate. This incident has been resolved.

Excerpts are shortened. Read the full incident on Prisma's status page.

Affected: Prisma Accelerate

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-10-22 13:35 UTC

   Accelerate is experiencing issues while provisioning resources for new query engine instances. The issue has been identified and a fix is being implemented.

2. monitoring 2025-10-22 13:37 UTC

   Accelerate has begun to recover. We are continuing to monitor the fix.

3. resolved 2025-10-22 13:55 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Prisma's status page.

Affected: Prisma Accelerate

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. identified 2025-10-20 15:19 UTC

   Description: We identified an upstream infrastructure provider issue affecting the us-east-1 region. Accelerate is experiencing issues while provisioning resources for new query engine instances. We're working on mitigating and monitoring the situation and gathering more...

2. monitoring 2025-10-20 20:20 UTC

   The upstream infrastructure provider has mitigated the issue and we're observing recovery. We'll keep monitoring the services status.

3. resolved 2025-10-20 21:13 UTC

   We're continuing to see healthy operation of services in us-east-1 region. This incident has been resolved.

Excerpts are shortened. Read the full incident on Prisma's status page.

Affected: Prisma Postgres

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-10-11 08:12 UTC

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

2. identified 2025-10-11 08:24 UTC

   We identified the issue and we are actively working on a fix. We verified the issue does not affect user's data.

3. monitoring 2025-10-11 08:47 UTC

   A fix has been implemented and we're monitoring the results

4. resolved 2025-10-11 09:01 UTC

   This incident has been resolved, and the Prisma Postgres restore functionality is now working correctly.

Excerpts are shortened. Read the full incident on Prisma's status page.

Affected: Prisma Postgres

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-10-08 14:18 UTC

   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

2. monitoring 2025-10-08 14:34 UTC

   Description: We've identified an issue in the proxies running on US East hosts and have applied a mitigation. Affected users: Users connecting from applications running in US East. Root cause: disruption to proxy services in US East region Workarounds: None identified

3. resolved 2025-10-08 16:07 UTC

   We identified and resolved an issue that caused new TCP connections from the US East region to fail, while existing connections continued to function normally. As a result, only a subset of users in the region were affected. The root cause has been identified, and a mitigation...

Excerpts are shortened. Read the full incident on Prisma's status page.

Affected: Prisma Accelerate

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-10-02 15:49 UTC

   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

2. monitoring 2025-10-02 16:11 UTC

   Description: Query engines are now being started as expected and traffic has returned to normal. We're continuing to investigate the issue and monitor traffic across Accelerate. Affected users: All Root cause: Currently unknown Workarounds: None identified

3. resolved 2025-10-02 16:37 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Prisma's status page.

Affected: Prisma Postgres, Prisma Accelerate

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-09-24 07:34 UTC

   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

2. monitoring 2025-09-24 07:38 UTC

   Errors creating query engines have come down; queries continue to execute as expected. We are keeping the status page open while we investigate the root cause and monitor the issue.

3. resolved 2025-09-24 10:41 UTC

   This incident has been resolved. The incident lasted 20 minutes and had minor impact on users in AP South East when creating new query engines.

Excerpts are shortened. Read the full incident on Prisma's status page.

Affected: Prisma Accelerate

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2025-09-19 08:15 UTC

   Description: We identified an upstream infrastructure provider issue affecting the eu-central-1 region. Accelerate experienced issues provisioning resources for new query engine instances. Affected users: Users provisioning new Accelerate query engines in the eu-central-1...

2. monitoring 2025-09-19 08:52 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2025-09-19 11:05 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Prisma's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2025-09-17 14:00 UTC

   Description: We identified an upstream infrastructure provider issue affecting the eu-central-1 region. Accelerate experienced issues provisioning resources for new query engine instances. Affected users: Users provisioning new Accelerate query engines in the eu-central-1...

Excerpts are shortened. Read the full incident on Prisma's status page.

Affected: Prisma Postgres, Prisma Accelerate

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2025-09-06 11:50 UTC

   Our upstream service provider is currently unable to provide enough capacity in eu-central-1.

2. resolved 2025-09-06 11:51 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Prisma's status page.

Affected: Prisma Console

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2025-09-01 18:13 UTC

   We are investigating delays in usage data being reported from some services and impacting the ability to review usage data in Console. Root cause: Upstream analytics provider Workarounds: None identified

2. monitoring 2025-09-01 18:33 UTC

   The incident has been resolved and we are monitoring the issue. We have not detected any data loss but investigation is ongoing.

3. resolved 2025-09-01 19:07 UTC

   Upstream analytics provider has identified and resolved the underlying issue. No further impact has been observed.

Excerpts are shortened. Read the full incident on Prisma's status page.

Affected: Prisma Console, Prisma Accelerate

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2025-08-28 10:01 UTC

   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...

2. investigating 2025-08-28 10:07 UTC

   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.

3. investigating 2025-08-28 10:31 UTC

   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.

4. monitoring 2025-08-28 10:37 UTC

   Our upstream provider seems to have fixed the network connectivity issues, and we see incoming request return to normal levels. We'll keep monitoring the situation.

5. resolved 2025-08-28 11:28 UTC

   The network errors have stopped and request levels are back to normal. Query engines are being successfully provisioned in us-east-1 again and console.prisma.io and api.prisma.io are fully operational again.

Excerpts are shortened. Read the full incident on Prisma's status page.

Affected: Prisma Postgres, Prisma Accelerate

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2025-08-21 18:13 UTC

   Description: Users of Accelerate and PPg may be experiencing network issues. This is related to an upstream provider experiencing an ongoing network incident. We're investigating potential workaround to the issue. Affected users: US East Root cause: Upstream provider...

2. identified 2025-08-21 18:43 UTC

   The cause has been identified and a fix is being implemented by our upstream provider.

3. monitoring 2025-08-21 19:35 UTC

   Error rates have dropped and we have updated the status to monitoring while we await more feedback from our upstream provider.

4. resolved 2025-08-21 19:58 UTC

   The upstream provider has identified and fixed the issue. We have seen normal operations for the past 30 min. We'll continue monitoring.

Excerpts are shortened. Read the full incident on Prisma's status page.

Affected: Prisma Postgres, Prisma Console, Prisma Accelerate

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-08-04 10:47 UTC

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

2. investigating 2025-08-04 11:17 UTC

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

3. investigating 2025-08-04 11:26 UTC

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

4. investigating 2025-08-04 12:11 UTC

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

5. monitoring 2025-08-04 13:51 UTC

   We continue to monitor the situation.

6. resolved 2025-08-04 18:43 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Prisma's status page.

Affected: Prisma Postgres

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-07-18 18:36 UTC

   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

2. monitoring 2025-07-18 19:50 UTC

   A fix has been implemented and we are monitoring the results.

3. monitoring 2025-07-18 20:13 UTC

   We are continuing to monitor for any further issues.

4. resolved 2025-07-18 23:24 UTC

   This was an issue affecting only a small handful of databases. It has been fully resolved and is unrelated to the Accelerate issue that occurred at the same time.

Excerpts are shortened. Read the full incident on Prisma's status page.

Affected: Prisma Postgres, Prisma Accelerate

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2025-07-18 18:00 UTC

   Description: We have identified and mitigated an issue with Accelerate, also affecting Prisma Postgres, where Prisma ORM binaries are unable to be downloaded. The root cause has been found and fixed and we are monitoring Accelerate and Prisma Postgres. Affected users: All...

2. monitoring 2025-07-18 20:43 UTC

   As we continue to monitor we have an update on the root cause and resolution of this incident: - When a new version of the ORM is published it uploads a binary to R2 and a failover to copy to S3 - ORM users, including Accelerate and Prisma Postgres, require these binaries when...

3. investigating 2025-07-18 22:06 UTC

   We are currently investigating this issue.

4. monitoring 2025-07-18 22:52 UTC

   The issue has officially been resolved. After identifying and resolving the root cause we experienced issues while restoring Accelerate to service. We're continuing to monitor closely and will provide another update with more details on what delayed bringing Accelerate back to...

5. monitoring 2025-07-18 23:16 UTC

   After resolving the original Prisma ORM binaries download issue we observed many users attempting to create query engines at the same time. Accelerate keeps a pool of warm instances to serve these requests quickly and when that warm pool is depleted we fallback on creating cold...

6. resolved 2025-07-18 23:37 UTC

   The number of active instances and HTTP traffic has returned to typical levels, warm pools are healthy and serving new instance requests, and errors are down. While systems are now operational and this incident has been resolved, we will continue to monitor things closely.

Excerpts are shortened. Read the full incident on Prisma's status page.

Affected: Prisma Postgres, Prisma Console, Prisma Studio, Prisma Accelerate, Prisma Optimize

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-06-12 18:52 UTC

   We are currently investigating the impact of an incident with an upstream service provider. Prisma Postgres, Prisma Accelerate, and the Prisma Console may experience service degradation during this time.

2. identified 2025-06-12 20:49 UTC

   The upstream service provider implemented a fix for the underlying issue, and we see quick recovery to normal operation across all services.

3. resolved 2025-06-12 21:49 UTC

   All systems are back to normal operation.

Excerpts are shortened. Read the full incident on Prisma's status page.

Affected: Prisma Postgres

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-06-05 16:17 UTC

   We noticed that a small set of databases that haven't been active for over 24 hours experience connectivity issues when new connections attempts are made.

2. monitoring 2025-06-05 16:32 UTC

   We identified the issue and rolled out a fix. All databases in the Asia Pacific (Tokyo) region should behave normal again. We continue to monitor the situation.

3. resolved 2025-06-05 16:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Prisma's status page.

Affected: Prisma Accelerate

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2025-05-21 09:29 UTC

   Description: We identified an upstream infrastructure provider issue affecting the eu-central-1 region. Accelerate experienced issues provisioning resources for new query engine instances. Affected users: Users provisioning new Accelerate query engines in the eu-central-1...

2. resolved 2025-05-21 09:47 UTC

   The upstream infrastructure provider issue has resolved and Accelerate is provisioning new query engines successfully.

Excerpts are shortened. Read the full incident on Prisma's status page.

Affected: Prisma Postgres, Prisma Console, Prisma Accelerate, Prisma Optimize

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2025-04-03 14:14 UTC

   Description: Accelerate is observing elevated 500 responses in eu-west-3 caused by an upstream provider service degradation. We are continuing to monitor the impact. Affected users: Accelerate usage in eu-west-3 Root cause: infrastructure provider degradation Workarounds: None...

2. monitoring 2025-04-03 14:35 UTC

   We are no longer observing elevated 500 responses and continuing to monitor.

3. resolved 2025-04-03 14:45 UTC

   We are continue to observe successful responses in all regions.

Excerpts are shortened. Read the full incident on Prisma's status page.

Affected: Prisma Accelerate

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-03-14 22:26 UTC

   Description: We are investigating intermittent failures occurring in the query engine provisioning flow of Accelerate. This may impact the ability to start new query engines during Accelerate autoscaling and other events that trigger new query engine allocation. Affected users:...

2. identified 2025-03-14 22:38 UTC

   We've identified an upstream provider service disruption. We're continuing to monitor the upstream provider incident and apply mitigations.

3. resolved 2025-03-14 22:52 UTC

   We're observing that the upstream provider incident has resolved and query engine allocations are succeeding.

Excerpts are shortened. Read the full incident on Prisma's status page.

Affected: Prisma Postgres, Prisma Console, Prisma Accelerate

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2025-03-10 08:12 UTC

   Description: We are investigating an increase in errors on accelerate. Affected users: Some users in the US region. Root cause: Our upstream cloud provider is experiencing latency on their storage service which is used to download Prisma ORM binaries. Workarounds: We're...

2. monitoring 2025-03-10 13:17 UTC

   Description: We're seeing performance improve across all US users and are continuing to monitor the situation. Affected users: Some users in the US region. Root cause: We identified an underlying cloud provider as the root cause which affects multiple aspects of serving...

3. resolved 2025-03-10 19:27 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Prisma's status page.

Affected: Prisma Console

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-03-09 12:09 UTC

   Description: 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

2. investigating 2025-03-09 12:20 UTC

   We are continuing to investigate this issue.

3. monitoring 2025-03-09 13:36 UTC

   Description: Console is operational and we're monitoring it closely as we investigate the root cause. Affected users: All console users. Root cause: Currently unknown Workarounds: N/A

4. resolved 2025-03-09 17:09 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Prisma's status page.

Affected: Prisma Studio, Prisma Accelerate

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-02-12 14:19 UTC

   Description: We are investigating an increase in 500 responses from Accelerate for some environments. Affected users: Currently unknown Root cause: Currently unknown Workarounds: None identified

2. investigating 2025-02-12 15:16 UTC

   We are continuing to investigate this issue.

3. monitoring 2025-02-12 15:26 UTC

   We're experiencing issues with an upstream cloud service provider which we're actively investigating. We'll be monitoring the affected components while we find the root cause.

4. monitoring 2025-02-12 17:25 UTC

   We are continuing to monitor for any further issues.

5. resolved 2025-02-12 17:26 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Prisma's status page.

Affected: Prisma Accelerate

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. identified 2025-01-22 00:50 UTC

   We identified an upstream infrastructure provider issue affecting the us-east-1 region. Accelerate experiences issues provisioning resources for new query engine instances.

2. identified 2025-01-22 00:56 UTC

   We are continuing to work on a fix for this issue.

3. monitoring 2025-01-22 00:56 UTC

   The upstream infrastructure provide issue has resolved and Accelerate is provisioning new query engines successfully. We are continuing to monitor for any further impact.

4. resolved 2025-01-22 01:03 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Prisma's status page.

Affected: Prisma Accelerate

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2025-01-03 14:56 UTC

   Description: We have identified an issue affecting allocation of new query engines caused by an incident with an upstream service provider. Affected users: users allocating new query engines due to normal activity Root cause: upstream service provider incident Workarounds: none...

2. monitoring 2025-01-03 15:08 UTC

   The upstream service provider incident has been resolved and we are no longer observing errors impacting Accelerate. We will continue to monitor for any further impact.

3. resolved 2025-01-03 15:25 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Prisma's status page.

Affected: Prisma Accelerate

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2024-12-05 18:05 UTC

   Description: We are investigating an Accelerate disruption affecting the ability to start new query engines. Affected users: Currently unknown Root cause: Currently unknown Workarounds: None identified

2. identified 2024-12-05 18:14 UTC

   Description: We've identified an issue creating DNS entries with one of our service providers. The provider has now posted an active incident and is investigating. Affected users: Accelerate users provisioning new query engine instances. Existing query engines will continue to...

3. monitoring 2024-12-05 18:19 UTC

   Description: The incident has been resolved with the service provider and we are seeing Accelerate traffic return to normal operation. We are continuing to monitor for any further impact. Affected users: Accelerate users provisioning new query engine instances. Existing query...

4. resolved 2024-12-05 18:37 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Prisma's status page.

Affected: Prisma Accelerate

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2024-11-29 19:32 UTC

   Description: We are investigating an Accelerate disruption in the us-east-1 region affecting the ability to start new query engines. Affected users: Accelerate users operating in the us-east-1 region Root cause: Currently unknown Workarounds: None

2. monitoring 2024-11-29 19:52 UTC

   We've identified an issue in the cleanup flow for inactive query engines that led to resource capacity pressure. We've implemented a fix and confirmed that new query engines are being provisioned successfully.

3. resolved 2024-11-29 20:48 UTC

   We're continuing to observe successful provisioning and cleanup of query engine instances in all regions. This incident is resolved.

Excerpts are shortened. Read the full incident on Prisma's status page.

Failure mode: A schema or data migration caused the failure. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2024-11-28 18:00 UTC

   RESOLVED A production data migration caused Optimize to remain in maintenance mode for 64 minutes. Affected Users: All users were unable to access Optimize during the incident. Root cause: An issue with an upstream provider caused the schema migration process to stall....

Excerpts are shortened. Read the full incident on Prisma's status page.