Prisma Outage History
54 incidents recorded over the last 365 days, 30 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Prisma Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Aug 11, 2026 | Prisma Compute/Postgres MaintenanceScheduled maintenance is currently in progress. We will provide updates as necessary. | 30 min | Scheduled |
| Aug 3, 2026 | Accelerate is slow to provision new query engines in eu-west-3This incident has been resolved. | 46 min | Resolved |
| Jul 31, 2026 | Degraded service for Accelerate cold startsResponses from Cloudflare's API have returned to nominal behavior and Accelerate has recovered. | 59 min | Resolved |
| Jul 30, 2026 | Prisma Compute/Postgres MaintenanceThe scheduled maintenance has been completed. | 15 min | Scheduled |
| Jul 28, 2026 | Prisma Compute/Postgres MaintenanceThe scheduled maintenance has been completed. | 30 min | Scheduled |
| Jul 21, 2026 | Prisma Compute/Postgres Maintenance: eu-central-1The scheduled maintenance has been completed. | 30 min | Scheduled |
| Jul 17, 2026 | Accelerate incident impacting the eu-central-1 regionWe are continuing to observe successful traffic from Accelerate. This incident has been resolved. | 3h 51m | Resolved |
| Jul 8, 2026 | Degraded service for Accelerate in us-east-1 and us-west-1Accelerate is operating within normal tolerances. | 14 min | Resolved |
| Jun 18, 2026 | Errors provisioning Prisma Postgres databasesWe've identified the issue and applied a mitigation. | 2h 29m | Resolved |
| May 6, 2026 | Prisma Postgres MaintenanceThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Apr 28, 2026 | Prisma Postgres MaintenanceThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Apr 15, 2026 | Prisma Postgres MaintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Apr 14, 2026 | Degraded performance and accessibility for Prisma productsThis incident has been resolved. | 16h 8m | Resolved |
| Apr 10, 2026 | Prisma Postgres MaintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Apr 8, 2026 | Accelerate Degradation due to partial deployment failureThis incident has been resolved. | 8 min | Resolved |
| Apr 7, 2026 | Prisma Postgres MaintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Apr 2, 2026 | Prisma Postgres MaintenanceThe scheduled maintenance has been completed. | 3h 0m | Scheduled |
| Apr 1, 2026 | Increase in Accelerate cold start timeThe incident has been resolved. | 11h 1m | Resolved |
| Apr 1, 2026 | Prisma Postgres MaintenanceThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Mar 27, 2026 | Degraded performance in US EastThis incident has been resolved. | 2h 6m | Resolved |
| Mar 17, 2026 | Prisma Postgres MaintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Mar 4, 2026 | Prisma Postgres MaintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Mar 3, 2026 | Degraded Performance in CDG and FRA regionsThe upstream issue has been resolved. The impact to users was minimal. | 22 min | Resolved |
| Feb 24, 2026 | Prisma Postgres MaintenanceThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Feb 18, 2026 | Prisma Postgres MaintenanceThe scheduled maintenance has been completed. | 15 min | Scheduled |
| Feb 17, 2026 | Prisma Postgres MaintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Feb 12, 2026 | Prisma Postgres MaintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Feb 10, 2026 | Prisma Postgres MaintenanceThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Feb 4, 2026 | Accelerate degraded operationThis incident has been resolved. | 33 min | Resolved |
| Feb 4, 2026 | Prisma Postgres MaintenanceThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Jan 29, 2026 | Prisma Postgres MaintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Jan 27, 2026 | Prisma Postgres Direct TCP: Degraded service in us-east-1 and eu-central-1This incident has been resolved. | 2h 4m | Resolved |
| Jan 20, 2026 | Prisma Postgres MaintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Jan 13, 2026 | Prisma Postgres MaintenanceThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Jan 9, 2026 | Usage quota issue on free tierThis incident has been resolved. | 10h 46m | Resolved |
| Jan 9, 2026 | Prisma Postgres MaintenanceThe scheduled maintenance has been completed. | 30 min | Scheduled |
| Jan 8, 2026 | Prisma Postgres MaintenanceThe scheduled maintenance has been completed. | 5h 0m | Scheduled |
| Dec 5, 2025 | Prisma Console is experiencing a partial outageThis incident has been resolved. | 25 min | Resolved |
| Dec 3, 2025 | Accelerate degraded performanceThis incident has been resolved. | 46 min | Resolved |
| Nov 21, 2025 | Singapore Network Connectivity IssuesThe issue has been resolved by our upstream provider. | 2h 37m | Resolved |
| Nov 18, 2025 | Accelerate degraded operationWe're continuing to observe healthy traffic through Prisma Accelerate. This incident has resolved. | 7h 5m | Resolved |
| Nov 13, 2025 | Intermittent connection failures from Accelerate to Prisma Postgres databases in US EastThis incident has been resolved. | 6h 52m | Resolved |
| Oct 28, 2025 | Accelerate degraded performanceWe're continuing to observe nominal traffic through Prisma Accelerate. This incident has been resolved. | 2h 29m | Resolved |
| Oct 22, 2025 | Accelerate degraded operationThis incident has been resolved. | 19 min | Resolved |
| Oct 20, 2025 | Accelerate degraded operation in us-east-1 regionWe're continuing to see healthy operation of services in us-east-1 region. This incident has been resolved. | 5h 54m | Resolved |
| Oct 11, 2025 | Prisma Postgres Database Restore DisruptionThis incident has been resolved, and the Prisma Postgres restore functionality is now working correctly. | 48 min | Resolved |
| Oct 8, 2025 | Prisma Postgres connection issues in US East regionWe 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… | 1h 48m | Resolved |
| Oct 2, 2025 | Suspected Accelerate Disruption - InvestigatingThis incident has been resolved. | 48 min | Resolved |
| Sep 24, 2025 | Issue Starting New Query Engines in AP South EastThis incident has been resolved. The incident lasted 20 minutes and had minor impact on users in AP South East when creating new query engines. | 3h 7m | Resolved |
| Sep 19, 2025 | Accelerate is unable to provision new query engines in eu-central-1This incident has been resolved. | 2h 49m | Resolved |
| Sep 17, 2025 | Accelerate is unable to provision new query engines in eu-central-1Description: 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… | -16 min | Resolved |
| Sep 6, 2025 | eu-central-1 is unable to provision new query engines for PPG / AccelerateThis incident has been resolved. | 1 min | Resolved |
| Sep 1, 2025 | Delays in usage dataUpstream analytics provider has identified and resolved the underlying issue. No further impact has been observed. | 54 min | Resolved |
| Aug 28, 2025 | Accelerate is unable to provision new query engines in us-east-1The 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. | 1h 27m | Resolved |
How to Read This Prisma Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Prisma acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Prisma outage in this window ran 16h 8m, against a mean recovery of 2h 19m. If you depend on Prisma in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.