Get email notifications whenever Prisma Data Platform creates, updates or resolves an incident.
Get incident updates and maintenance status messages in Slack.
Subscribe via Slack
By subscribing you agree to the Atlassian Cloud Terms of Service and acknowledge Atlassian's Privacy Policy.
Get webhook notifications whenever Prisma Data Platform creates an incident, updates an incident, resolves an incident or changes a component status.
All Systems Operational
Uptime over the past 90 days. View historical uptime.
Prisma Accelerate
Operational
90 days ago
99.89
% uptime
Today
Prisma Data Platform Console
Operational
90 days ago
99.95
% uptime
Today
Prisma Optimize
Operational
90 days ago
99.95
% uptime
Today
Prisma Postgres
Operational
90 days ago
99.87
% uptime
Today
Prisma Studio
Operational
90 days ago
99.95
% uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Related
No incidents or maintenance related to this downtime.
Past Incidents
Jul 19, 2025
No incidents reported today.
Jul 18, 2025
Resolved -
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.
Jul 18, 23:37 UTC
While systems are now operational and this incident has been resolved, we will continue to monitor things closely.
Jul 18, 23:37 UTC
Update -
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 instances.
We identified a bug in the cold instance path which prevented us from bringing Accelerate online for all users fast enough. While some users were able to get instances from the warm path as new instances were added to the pool, it wasn't fast enough to serve the backlog of users who were requesting new instances. Once we found and patched the bug Accelerate was able to serve all instance requests within minutes.
Because this only affected the creation of new instances, users with instances already running would have not experienced any issues.
Thank you for your patience. We're already working on collecting data and insights for our postmortem which always aim to make our products and services better.
Jul 18, 23:16 UTC
We identified a bug in the cold instance path which prevented us from bringing Accelerate online for all users fast enough. While some users were able to get instances from the warm path as new instances were added to the pool, it wasn't fast enough to serve the backlog of users who were requesting new instances. Once we found and patched the bug Accelerate was able to serve all instance requests within minutes.
Because this only affected the creation of new instances, users with instances already running would have not experienced any issues.
Thank you for your patience. We're already working on collecting data and insights for our postmortem which always aim to make our products and services better.
Jul 18, 23:16 UTC
Monitoring -
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 service.
Jul 18, 22:52 UTC
We're continuing to monitor closely and will provide another update with more details on what delayed bringing Accelerate back to service.
Jul 18, 22:52 UTC
Investigating -
We are currently investigating this issue.
Jul 18, 22:06 UTC
Jul 18, 22:06 UTC
Update -
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 starting up query engines
- The failover to S3 triggered but ORM, Accelerate, and Prisma Postgres were not able to download binaries
- We resolved the incident by overriding the failover and pointing to R2
We're investigating both the cause of the failover the issue related to downloading binaries from S3.
Jul 18, 20:43 UTC
- 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 starting up query engines
- The failover to S3 triggered but ORM, Accelerate, and Prisma Postgres were not able to download binaries
- We resolved the incident by overriding the failover and pointing to R2
We're investigating both the cause of the failover the issue related to downloading binaries from S3.
Jul 18, 20:43 UTC
Monitoring -
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 Accelerate and Prisma Postgres users, and a subset of Prisma ORM users
Root cause: Identified and fixed
Jul 18, 18:00 UTC
Affected users: All Accelerate and Prisma Postgres users, and a subset of Prisma ORM users
Root cause: Identified and fixed
Jul 18, 18:00 UTC
Resolved -
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.
Jul 18, 23:24 UTC
Jul 18, 23:24 UTC
Update -
We are continuing to monitor for any further issues.
Jul 18, 20:13 UTC
Jul 18, 20:13 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Jul 18, 19:50 UTC
Jul 18, 19:50 UTC
Investigating -
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
Jul 18, 18:36 UTC
Affected users: Currently unknown
Root cause: Currently unknown
Workarounds: None identified
Jul 18, 18:36 UTC
Completed -
The scheduled maintenance has been completed.
Jul 18, 10:11 UTC
Jul 18, 10:11 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 18, 09:00 UTC
Jul 18, 09:00 UTC
Scheduled -
Prisma Postgres is currently undergoing expected maintenance.
Impact: Active connections to Prisma Postgres databases may be temporarily disrupted.
Affected regions:
- US East (N.Virginia)
Jul 17, 16:07 UTC
Impact: Active connections to Prisma Postgres databases may be temporarily disrupted.
Affected regions:
- US East (N.Virginia)
Jul 17, 16:07 UTC
Jul 17, 2025
Completed -
The scheduled maintenance has been completed.
Jul 17, 16:05 UTC
Jul 17, 16:05 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 17, 14:00 UTC
Jul 17, 14:00 UTC
Scheduled -
Prisma Postgres is currently undergoing expected maintenance.
Impact: Active connections to Prisma Postgres databases may be temporarily disrupted.
Affected regions:
- US East (N.Virginia)
- US West (N. California)
- Europe (Paris)
- Europe (Frankfurt)
- Asia Pacific (Tokyo)
- Asia Pacific (Singapore)
Jul 17, 11:53 UTC
Impact: Active connections to Prisma Postgres databases may be temporarily disrupted.
Affected regions:
- US East (N.Virginia)
- US West (N. California)
- Europe (Paris)
- Europe (Frankfurt)
- Asia Pacific (Tokyo)
- Asia Pacific (Singapore)
Jul 17, 11:53 UTC
Jul 16, 2025
No incidents reported.
Jul 15, 2025
Completed -
The scheduled maintenance has been completed.
Jul 15, 11:14 UTC
Jul 15, 11:14 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 15, 10:00 UTC
Jul 15, 10:00 UTC
Scheduled -
Prisma Postgres is currently undergoing expected maintenance.
Impact: Active connections to Prisma Postgres databases may be temporarily disrupted.
Affected regions:
- US East (N.Virginia)
- US West (N. California)
- Europe (Paris)
- Europe (Frankfurt)
- Asia Pacific (Tokyo)
- Asia Pacific (Singapore)
Jul 15, 09:01 UTC
Impact: Active connections to Prisma Postgres databases may be temporarily disrupted.
Affected regions:
- US East (N.Virginia)
- US West (N. California)
- Europe (Paris)
- Europe (Frankfurt)
- Asia Pacific (Tokyo)
- Asia Pacific (Singapore)
Jul 15, 09:01 UTC
Jul 14, 2025
No incidents reported.
Jul 13, 2025
No incidents reported.
Jul 12, 2025
No incidents reported.
Jul 11, 2025
No incidents reported.
Jul 10, 2025
No incidents reported.
Jul 9, 2025
No incidents reported.
Jul 8, 2025
Completed -
The scheduled maintenance has been completed.
Jul 8, 10:10 UTC
Jul 8, 10:10 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 8, 09:00 UTC
Jul 8, 09:00 UTC
Scheduled -
We will be undergoing routine maintenance during this time.
Jul 8, 07:16 UTC
Jul 8, 07:16 UTC
Jul 7, 2025
No incidents reported.
Jul 6, 2025
No incidents reported.
Jul 5, 2025
No incidents reported.