Prisma Data incident

Degraded performance in US East

Minor Resolved View vendor source →

Prisma Data experienced a minor incident on March 27, 2026 affecting Prisma Postgres, lasting 2h 6m. The incident has been resolved; the full update timeline is below.

Started
Mar 27, 2026, 03:19 PM UTC
Resolved
Mar 27, 2026, 05:25 PM UTC
Duration
2h 6m
Detected by Pingoru
Mar 27, 2026, 03:19 PM UTC

Affected components

Prisma Postgres

Update timeline

  1. investigating Mar 27, 2026, 03:19 PM 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 Mar 27, 2026, 03:23 PM 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 Mar 27, 2026, 03:34 PM UTC

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

  4. resolved Mar 27, 2026, 05:25 PM UTC

    This incident has been resolved.