Prisma Data Outage History

Prisma Data is up right now

Prisma Data had 42 outages in the last 2 years totaling 33h 47m of downtime — averaging 1.7 incidents per month.

There were 42 Prisma Data outages since July 8, 2024 totaling 33h 47m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://www.prisma-status.com

Major June 12, 2025

Intermittent availability issues for Prisma Postgres, Prisma Accelerate, and Prisma Console

Detected by Pingoru
Jun 12, 2025, 06:52 PM UTC
Resolved
Jun 12, 2025, 09:49 PM UTC
Duration
2h 57m
Affected: Prisma AcceleratePrisma ConsolePrisma OptimizePrisma PostgresPrisma Studio
Timeline · 3 updates
  1. investigating Jun 12, 2025, 06:52 PM 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 Jun 12, 2025, 08:49 PM 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 Jun 12, 2025, 09:49 PM UTC

    All systems are back to normal operation.

Read the full incident report →

Minor June 5, 2025

Connectivity issues for a subset of databases in the Asia Pacific (Tokyo) region.

Detected by Pingoru
Jun 05, 2025, 04:17 PM UTC
Resolved
Jun 05, 2025, 04:58 PM UTC
Duration
40m
Affected: Prisma Postgres
Timeline · 3 updates
  1. investigating Jun 05, 2025, 04:17 PM 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 Jun 05, 2025, 04:32 PM 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 Jun 05, 2025, 04:58 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 21, 2025

Accelerate is unable to provision new query engines in EU Central (1)

Detected by Pingoru
May 21, 2025, 09:29 AM UTC
Resolved
May 21, 2025, 09:47 AM UTC
Duration
18m
Affected: Prisma Accelerate
Timeline · 2 updates
  1. identified May 21, 2025, 09:29 AM 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 region. Root cause: Upstream infrastructure provider Workarounds: None identified

  2. resolved May 21, 2025, 09:47 AM UTC

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

Read the full incident report →

Minor April 3, 2025

Accelerate elevated 500 responses in eu-west-3

Detected by Pingoru
Apr 03, 2025, 02:14 PM UTC
Resolved
Apr 03, 2025, 02:45 PM UTC
Duration
31m
Affected: Prisma AcceleratePrisma ConsolePrisma OptimizePrisma Postgres
Timeline · 3 updates
  1. identified Apr 03, 2025, 02:14 PM 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 identified

  2. monitoring Apr 03, 2025, 02:35 PM UTC

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

  3. resolved Apr 03, 2025, 02:45 PM UTC

    We are continue to observe successful responses in all regions.

Read the full incident report →

Major March 14, 2025

Accelerate intermittent errors provisioning new query engines

Detected by Pingoru
Mar 14, 2025, 10:26 PM UTC
Resolved
Mar 14, 2025, 10:52 PM UTC
Duration
26m
Affected: Prisma Accelerate
Timeline · 3 updates
  1. investigating Mar 14, 2025, 10:26 PM 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: Intermittently all users Root cause: Upstream provider Workarounds: None identified

  2. identified Mar 14, 2025, 10:38 PM UTC

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

  3. resolved Mar 14, 2025, 10:52 PM UTC

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

Read the full incident report →

Minor March 10, 2025

Accelerate: Increased Error Rate

Detected by Pingoru
Mar 10, 2025, 08:12 AM UTC
Resolved
Mar 10, 2025, 07:27 PM UTC
Duration
11h 14m
Affected: Prisma AcceleratePrisma ConsolePrisma Postgres
Timeline · 3 updates
  1. identified Mar 10, 2025, 08:12 AM 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 currently investigating a workaround.

  2. monitoring Mar 10, 2025, 01:17 PM 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 Accelerate requests. Workarounds: We have implemented and deployed mitigations for each of the issues found.

  3. resolved Mar 10, 2025, 07:27 PM UTC

    This incident has been resolved.

Read the full incident report →

Major March 9, 2025

Platform Console is unavailable

Detected by Pingoru
Mar 09, 2025, 12:09 PM UTC
Resolved
Mar 09, 2025, 05:09 PM UTC
Duration
5h
Affected: Prisma Console
Timeline · 4 updates
  1. investigating Mar 09, 2025, 12:09 PM 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 Mar 09, 2025, 12:20 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Mar 09, 2025, 01:36 PM 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 Mar 09, 2025, 05:09 PM UTC

    This incident has been resolved.

Read the full incident report →

Major February 12, 2025

Accelerate elevated 500 responses

Detected by Pingoru
Feb 12, 2025, 02:19 PM UTC
Resolved
Feb 12, 2025, 05:26 PM UTC
Duration
3h 6m
Affected: Prisma AcceleratePrisma Studio
Timeline · 5 updates
  1. investigating Feb 12, 2025, 02:19 PM 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 Feb 12, 2025, 03:16 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Feb 12, 2025, 03:26 PM 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 Feb 12, 2025, 05:25 PM UTC

    We are continuing to monitor for any further issues.

  5. resolved Feb 12, 2025, 05:26 PM UTC

    This incident has been resolved.

Read the full incident report →

Major January 22, 2025

Accelerate issue provisioning new query engines in us-east-1

Detected by Pingoru
Jan 22, 2025, 12:50 AM UTC
Resolved
Jan 22, 2025, 01:03 AM UTC
Duration
13m
Affected: Prisma Accelerate
Timeline · 4 updates
  1. identified Jan 22, 2025, 12:50 AM 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 Jan 22, 2025, 12:56 AM UTC

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

  3. monitoring Jan 22, 2025, 12:56 AM 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 Jan 22, 2025, 01:03 AM UTC

    This incident has been resolved.

Read the full incident report →

Major January 3, 2025

Accelerate partial disruption affecting new query engine starts

Detected by Pingoru
Jan 03, 2025, 02:56 PM UTC
Resolved
Jan 03, 2025, 03:25 PM UTC
Duration
29m
Affected: Prisma Accelerate
Timeline · 3 updates
  1. identified Jan 03, 2025, 02:56 PM 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 identified

  2. monitoring Jan 03, 2025, 03:08 PM 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 Jan 03, 2025, 03:25 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical December 5, 2024

Accelerate disruption affecting new query engine starts

Detected by Pingoru
Dec 05, 2024, 06:05 PM UTC
Resolved
Dec 05, 2024, 06:37 PM UTC
Duration
32m
Affected: Prisma Accelerate
Timeline · 4 updates
  1. investigating Dec 05, 2024, 06:05 PM 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 Dec 05, 2024, 06:14 PM 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 operate. Root cause: service provider Workarounds: None identified

  3. monitoring Dec 05, 2024, 06:19 PM 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 engines will continue to operate. Root cause: service provider Workarounds: None identified

  4. resolved Dec 05, 2024, 06:37 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice November 29, 2024

Optimize unavailable due to schema migration

Detected by Pingoru
Nov 29, 2024, 08:22 PM UTC
Resolved
Nov 28, 2024, 06:00 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Nov 29, 2024, 08:22 PM 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. Workarounds: None

Read the full incident report →

Major November 29, 2024

Accelerate partial disruption in us-east-1

Detected by Pingoru
Nov 29, 2024, 07:32 PM UTC
Resolved
Nov 29, 2024, 08:48 PM UTC
Duration
1h 16m
Affected: Prisma Accelerate
Timeline · 3 updates
  1. investigating Nov 29, 2024, 07:32 PM 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 Nov 29, 2024, 07:52 PM 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 Nov 29, 2024, 08:48 PM UTC

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

Read the full incident report →

Major October 2, 2024

Accelerate issue provisioning new query engines in eu-central-1

Detected by Pingoru
Oct 02, 2024, 01:16 PM UTC
Resolved
Oct 02, 2024, 04:51 PM UTC
Duration
3h 34m
Affected: Prisma Accelerate
Timeline · 4 updates
  1. investigating Oct 02, 2024, 01:16 PM UTC

    Description: We are currently investigating a potential impact on Accelerate identified in our service monitoring. Affected users: Currently unknown Root cause: Currently unknown Workarounds: None identified

  2. identified Oct 02, 2024, 01:25 PM 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 region. Root cause: Upstream infrastructure provider Workarounds: None identified

  3. monitoring Oct 02, 2024, 01:31 PM UTC

    Description: The upstream infrastructure provide issue has resolved and Accelerate is provisioning new query engines successfully. We are continuing to monitor for any further impact. Affected users: Users provisioning new Accelerate query engines in the eu-central-1 region. Root cause: Upstream infrastructure provider Workarounds: None identified

  4. resolved Oct 02, 2024, 04:51 PM UTC

    This incident has been resolved.

Read the full incident report →

Major July 26, 2024

Accelerate partially unavailable in some regions

Detected by Pingoru
Jul 26, 2024, 10:11 PM UTC
Resolved
Jul 26, 2024, 08:00 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Jul 26, 2024, 10:11 PM UTC

    Description: Between 19:50 and 20:22 UTC some users requesting new query engines took a significantly longer period of time. Majority of users remained unaffected because this incident did not affect existing query engines. Affected users: Some users in US East, SA East, AP North East Root cause: Network issue experienced by one of our Cloud providers.

Read the full incident report →

Notice July 17, 2024

Delay In Usage Data Appearing In Console

Detected by Pingoru
Jul 17, 2024, 04:49 PM UTC
Resolved
Jul 17, 2024, 07:42 PM UTC
Duration
2h 52m
Affected: Prisma Console
Timeline · 3 updates
  1. investigating Jul 17, 2024, 04:49 PM UTC

    Description: We are investigating an incident impacting usage reporting in the Console. Affected users: All Root cause: Upstream analytics provider Workarounds: None identified

  2. monitoring Jul 17, 2024, 05:02 PM UTC

    The incident has been resolved and we are monitoring the issue. We are aware that there is a 57 minute gap in usage data which we're investigating how to recover.

  3. resolved Jul 17, 2024, 07:42 PM UTC

    The remaining data from the affected time range has been recovered and no further impact has been observed.

Read the full incident report →

Major July 8, 2024

Increased 500s from Accelerate

Detected by Pingoru
Jul 08, 2024, 03:07 PM UTC
Resolved
Jul 08, 2024, 03:40 PM UTC
Duration
32m
Affected: Prisma Accelerate
Timeline · 4 updates
  1. investigating Jul 08, 2024, 03:07 PM UTC

    We are currently investigating an increase in 500 responses from Accelerate.

  2. identified Jul 08, 2024, 03:18 PM UTC

    Description: We are investigating an increase in 500 responses from Accelerate caused by an incident with one of our hosting providers. Affected users: Those allocating new query engines due to new Prisma schemas, Prisma versions, or returning from idle activity Root cause: Upstream hosting provider incident affecting DNS propagation Workarounds: None

  3. monitoring Jul 08, 2024, 03:22 PM UTC

    We're observing that Accelerate traffic has recovered. We are continuing to monitor the upstream incident for additional impact.

  4. resolved Jul 08, 2024, 03:40 PM UTC

    We're continuing to observe successful traffic through Accelerate and the upstream incident has been resolved by the hosting provider.

Read the full incident report →