Is Prisma Data down?

Last checked 10m ago
Current status
Prisma Data is up

No incidents right now.

Official status page: https://www.prisma-status.com · Polled every 5 minutes · 7 components tracked

Prisma Data is operational right now. Last checked 10m ago; the most recent incident resolved 38d ago.

Real-time Prisma Data status, recent outages, and incident history — pulled directly from Prisma Data's official status page at https://www.prisma-status.com every 5 minutes. Pingoru tracks 7 Prisma Data services and has captured 6 incidents in the last 90 days (98.41% uptime). Get email, Slack, Discord, or webhook alerts the moment Prisma Data reports a new incident — free for 5 monitors, no credit card.

Users who monitor Prisma Data also follow these Database services: Snowflake Supabase Stitch Data ClickHouse Iron.io Aiven SolarWinds Observability Neo4j Aura Upstash Pinecone View all 6,000+ providers
Prisma Data uptime 98.41% uptime · past 90 days
Mon Wed Fri
MarAprMayJun
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 16h 8m
    Started Apr 14, 2026, 12:44 PM UTC · Resolved Apr 15, 2026, 04:53 AM UTC
    Prisma AcceleratePrisma Console
    Timeline · 2 updates
    • monitoring · Apr 14, 2026, 12:44 PM UTC

      Prisma Accelerate and the Prisma Console are experiencing degraded performance resulting from a Cloudflare outage. Customers may notice timeouts and connection failures. We are monitoring the impact on our systems. More information may be available at Cloudflare's status pages: - https://www.cloudflarestatus.com/incidents/lq1vw7z9xthq - https://www.cloudflarestatus.com/incidents/213v4v7s7m97

    • resolved · Apr 15, 2026, 04:53 AM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  2. Resolved 8m
    Started Apr 08, 2026, 09:40 AM UTC · Resolved Apr 08, 2026, 09:49 AM UTC
    Prisma Accelerate
    Timeline · 3 updates
    • identified · Apr 08, 2026, 09:40 AM UTC

      The issue has been identified and a fix is being implemented.

    • monitoring · Apr 08, 2026, 09:43 AM UTC

      A fix has been implemented and we are monitoring the results.

    • resolved · Apr 08, 2026, 09:49 AM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  3. Resolved 11h 1m
    Started Apr 01, 2026, 10:15 PM UTC · Resolved Apr 02, 2026, 09:17 AM UTC
    Prisma AcceleratePrisma Postgres
    Timeline · 6 updates
    • investigating · Apr 01, 2026, 10:15 PM UTC

      Description: We are investigating an issue where Accelerate cold starts have increased. Affected users: US East Root cause: Currently unknown Workarounds: For Prisma Postgres users we recommend Direct TCP with connection pooling enabled.

    • investigating · Apr 01, 2026, 11:36 PM UTC

      We are continuing to investigate the issue. Affected users: US East, AP Northeast, AP Southeast, US West, EU Central Root cause: Currently unknown Workarounds: For Prisma Postgres users we recommend Direct TCP with connection pooling enabled.

    • identified · Apr 02, 2026, 12:57 AM UTC

      We've isolated the root cause to an issue within Durable Objects. Cloudflare have an active status page. We're investigating mitigation options.

    • identified · Apr 02, 2026, 02:56 AM UTC

      We are awaiting an update from Cloudflare. As the incident persists, we recommend not deploying new versions of your schema until the incident is resolved to avoid requesting a new Query Engine and encountering a cold start. Workarounds: For Prisma Postgres users we still recommend Direct TCP with connection pooling enabled.

    • monitoring · Apr 02, 2026, 05:43 AM UTC

      A fix has been implemented and we are monitoring the results.

    • resolved · Apr 02, 2026, 09:17 AM UTC

      The incident has been resolved.

    Latest: The incident has been resolved.

  4. Resolved 2h 6m
    Started Mar 27, 2026, 03:19 PM UTC · Resolved Mar 27, 2026, 05:25 PM UTC
    Prisma Postgres
    Timeline · 4 updates
    • 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

    • 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

    • 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.

    • resolved · Mar 27, 2026, 05:25 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

Outage history

Past 90 days · 4 incidents View full outage history →