- Detected by Pingoru
- Sep 19, 2025, 08:15 AM UTC
- Resolved
- Sep 19, 2025, 11:05 AM UTC
- Duration
- 2h 49m
Affected: Prisma Accelerate
Timeline · 3 updates
-
identified Sep 19, 2025, 08:15 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
-
monitoring Sep 19, 2025, 08:52 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Sep 19, 2025, 11:05 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Sep 06, 2025, 11:50 AM UTC
- Resolved
- Sep 06, 2025, 11:51 AM UTC
- Duration
- 1m
Affected: Prisma AcceleratePrisma Postgres
Timeline · 2 updates
-
identified Sep 06, 2025, 11:50 AM UTC
Our upstream service provider is currently unable to provide enough capacity in eu-central-1.
-
resolved Sep 06, 2025, 11:51 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Sep 01, 2025, 06:13 PM UTC
- Resolved
- Sep 01, 2025, 07:07 PM UTC
- Duration
- 54m
Affected: Prisma Console
Timeline · 3 updates
-
identified Sep 01, 2025, 06:13 PM 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
-
monitoring Sep 01, 2025, 06:33 PM UTC
The incident has been resolved and we are monitoring the issue. We have not detected any data loss but investigation is ongoing.
-
resolved Sep 01, 2025, 07:07 PM UTC
Upstream analytics provider has identified and resolved the underlying issue. No further impact has been observed.
Read the full incident report →
- Detected by Pingoru
- Aug 28, 2025, 10:01 AM UTC
- Resolved
- Aug 28, 2025, 11:28 AM UTC
- Duration
- 1h 27m
Affected: Prisma AcceleratePrisma Console
Timeline · 5 updates
-
investigating Aug 28, 2025, 10:01 AM 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 expected
-
investigating Aug 28, 2025, 10:07 AM 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.
-
investigating Aug 28, 2025, 10:31 AM 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.
-
monitoring Aug 28, 2025, 10:37 AM 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.
-
resolved Aug 28, 2025, 11:28 AM 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.
Read the full incident report →
- Detected by Pingoru
- Aug 21, 2025, 06:13 PM UTC
- Resolved
- Aug 21, 2025, 07:58 PM UTC
- Duration
- 1h 45m
Affected: Prisma AcceleratePrisma Postgres
Timeline · 4 updates
-
identified Aug 21, 2025, 06:13 PM 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 Workarounds: Investigating
-
identified Aug 21, 2025, 06:43 PM UTC
The cause has been identified and a fix is being implemented by our upstream provider.
-
monitoring Aug 21, 2025, 07:35 PM UTC
Error rates have dropped and we have updated the status to monitoring while we await more feedback from our upstream provider.
-
resolved Aug 21, 2025, 07:58 PM UTC
The upstream provider has identified and fixed the issue. We have seen normal operations for the past 30 min. We'll continue monitoring.
Read the full incident report →
- Detected by Pingoru
- Aug 04, 2025, 10:47 AM UTC
- Resolved
- Aug 04, 2025, 06:43 PM UTC
- Duration
- 7h 55m
Affected: Prisma AcceleratePrisma ConsolePrisma Postgres
Timeline · 6 updates
-
investigating Aug 04, 2025, 10:47 AM UTC
Investigating increased error rates due to network degradation of a upstream provider
-
investigating Aug 04, 2025, 11:17 AM UTC
The upstream provider has identified the issue and are implementing a fix. We are monitoring the situation closely.
-
investigating Aug 04, 2025, 11:26 AM UTC
Upstream provider is continuing work on a fix. Impacted region appears to be restricted around the Frankfurt data centre.
-
investigating Aug 04, 2025, 12:11 PM UTC
Upstream provider has mitigated the current impact and continues to work on a fix.
-
monitoring Aug 04, 2025, 01:51 PM UTC
We continue to monitor the situation.
-
resolved Aug 04, 2025, 06:43 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 18, 2025, 06:36 PM UTC
- Resolved
- Jul 18, 2025, 11:24 PM UTC
- Duration
- 4h 47m
Affected: Prisma Postgres
Timeline · 4 updates
-
investigating Jul 18, 2025, 06:36 PM 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
-
monitoring Jul 18, 2025, 07:50 PM UTC
A fix has been implemented and we are monitoring the results.
-
monitoring Jul 18, 2025, 08:13 PM UTC
We are continuing to monitor for any further issues.
-
resolved Jul 18, 2025, 11:24 PM 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.
Read the full incident report →
- Detected by Pingoru
- Jul 18, 2025, 06:00 PM UTC
- Resolved
- Jul 18, 2025, 11:37 PM UTC
- Duration
- 5h 37m
Affected: Prisma AcceleratePrisma Postgres
Timeline · 6 updates
Read the full incident report →
- 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
-
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.
-
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.
-
resolved Jun 12, 2025, 09:49 PM UTC
All systems are back to normal operation.
Read the full incident report →
- 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
-
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.
-
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.
-
resolved Jun 05, 2025, 04:58 PM UTC
This incident has been resolved.
Read the full incident report →
- 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
-
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
-
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 →
- 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
-
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
-
monitoring Apr 03, 2025, 02:35 PM UTC
We are no longer observing elevated 500 responses and continuing to monitor.
-
resolved Apr 03, 2025, 02:45 PM UTC
We are continue to observe successful responses in all regions.
Read the full incident report →
- 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
-
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
-
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.
-
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 →
- 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
-
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.
-
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.
-
resolved Mar 10, 2025, 07:27 PM UTC
This incident has been resolved.
Read the full incident report →
- 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
-
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
-
investigating Mar 09, 2025, 12:20 PM UTC
We are continuing to investigate this issue.
-
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
-
resolved Mar 09, 2025, 05:09 PM UTC
This incident has been resolved.
Read the full incident report →
- 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
-
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
-
investigating Feb 12, 2025, 03:16 PM UTC
We are continuing to investigate this issue.
-
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.
-
monitoring Feb 12, 2025, 05:25 PM UTC
We are continuing to monitor for any further issues.
-
resolved Feb 12, 2025, 05:26 PM UTC
This incident has been resolved.
Read the full incident report →
- 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
-
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.
-
identified Jan 22, 2025, 12:56 AM UTC
We are continuing to work on a fix for this issue.
-
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.
-
resolved Jan 22, 2025, 01:03 AM UTC
This incident has been resolved.
Read the full incident report →
- 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
-
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
-
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.
-
resolved Jan 03, 2025, 03:25 PM UTC
This incident has been resolved.
Read the full incident report →
Critical December 5, 2024 - 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
-
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
-
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
-
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
-
resolved Dec 05, 2024, 06:37 PM UTC
This incident has been resolved.
Read the full incident report →
- 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
-
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
-
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.
-
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 →
- Detected by Pingoru
- Nov 28, 2024, 06:00 PM UTC
- Resolved
- Nov 28, 2024, 07:04 PM UTC
- Duration
- 1h 4m
Timeline · 1 update
-
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 →
