Rewindex

CompaniesPrismaIncidents

Prisma: Prisma Console is experiencing a partial outage

MajorStatus: resolvedStarted Resolved (26 min)5 updatesstspg.io (opens in new tab)
Part of an outage event

Cloudflare outage, Dec 5, 2025 · 46 vendors, 46 incidents

Prisma’s incident blames Cloudflare as the cause. (hop 1, posted +16 min vs the first vendor naming Cloudflare)

“…experiencing a partial outage This incident has been resolved. A fix has been deployed by Cloudflare and our all services appear to have come back online. We're continuing to monitor. An upstream infr…”

Swipe sideways to see the whole diagram.

Cloudflareown incident not archivedWithin an hour18 vendors, 18 blamed CloudflareUnbounce, Expo, GitLab +151 to 4 hours later1 vendor, 1 blamed CloudflareKlaviyoLater2 vendors, 2 blamed CloudflareBitrise, Sigma ComputingPrisma (this incident)posted +16 min
Cloudflareown incident not archivedWithin an hour18 vendors, 18 blamedCloudflareUnbounce, Expo, GitLab +151 to 4 hours later1 vendor, 1 blamed CloudflareKlaviyoLater2 vendors, 2 blamed CloudflareBitrise, Sigma ComputingPrisma (this incident)posted +16 min
Prisma is outlined in red. Groups show up to a few vendors each; the event page lists every incident.
Mermaid source
flowchart LR
  root["Cloudflare<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>18 vendors, 18 blamed Cloudflare<br/>Unbounce, Expo, GitLab +15"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>1 vendor, 1 blamed Cloudflare<br/>Klaviyo"]:::blames
  root --> h4
  later["Later<br/>2 vendors, 2 blamed Cloudflare<br/>Bitrise, Sigma Computing"]:::blames
  root --> later
  me["Prisma (this incident)<br/>posted +16 min"]:::me
  h1 --- me

Full event: timeline, evidence and all vendors →

Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.

Affected components: Prisma AcceleratePrisma ConsolePrisma Data Platform ConsolePrisma Postgres

Timeline of updates

  1. investigating

    An upstream infra provider is experiencing issues which is impacting our services. We are monitoring the situation.

  2. investigating

    Description: An upstream provider, Cloudflare, is experiencing an outage of critical services. The following services are impacted: Accelerate: Users are unable to connect to their database via Accelerate Console: Console is unavailable and returns a 500 error page. Prisma Postgres: Direct TCP is unaffected, users querying via Accelerate will be unable to to connection. Affected users: All users Root cause: Upstream infrastructure provider Workarounds: Please use direct TCP when connecting to your Prisma Postgres database.

  3. monitoring

    A fix has been deployed by Cloudflare and our all services appear to have come back online. We're continuing to monitor.

  4. monitoring

    We are continuing to monitor for any further issues.

  5. resolved

    This incident has been resolved.

Changes Rewindex caught on this incident

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).

Prisma profileRecent Prisma incidentsMarkdownJSON