Rewindex

CompaniesPrismaIncidents

Prisma: Accelerate degraded operation

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

Cloudflare outage, Nov 18, 2025 · 77 vendors, 81 incidents

Prisma’s incident started in the same window without naming Cloudflare (timing only, not evidence of a link). (timing only, posted +37 min vs the first vendor naming Cloudflare)

Swipe sideways to see the whole diagram.

same windowCloudflareown incident not archivedWithin an hour13 vendors, 13 blamed CloudflareStytch, Zed, NordLayer +101 to 4 hours later19 vendors, 19 blamed CloudflareGitLab, Gorgias, Cursor +16Later7 vendors, 7 blamed CloudflareRudderStack, Brex, Maven Central +4Prisma (this incident)posted +37 min
same windowCloudflareown incident not archivedWithin an hour13 vendors, 13 blamedCloudflareStytch, Zed, NordLayer +101 to 4 hours later19 vendors, 19 blamedCloudflareGitLab, Gorgias, Cursor +16Later7 vendors, 7 blamed CloudflareRudderStack, Brex, MavenCentral +4Prisma (this incident)posted +37 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/>13 vendors, 13 blamed Cloudflare<br/>Stytch, Zed, NordLayer +10"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>19 vendors, 19 blamed Cloudflare<br/>GitLab, Gorgias, Cursor +16"]:::blames
  root --> h4
  later["Later<br/>7 vendors, 7 blamed Cloudflare<br/>RudderStack, Brex, Maven Central +4"]:::blames
  root --> later
  me["Prisma (this incident)<br/>posted +37 min"]:::me
  root -.->|"same window"| 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 Accelerate

Timeline of updates

  1. identified

    We identified an upstream infrastructure provider issue. Accelerate is experiencing issues while provisioning resources for new query engine instances. The ORM engine binary downloads are also currently impacted. We're working on mitigating and monitoring the situation and gathering more information from the upstream provider. Prisma Postgres direct TCP connections are unaffected.

  2. identified

    Latest update from our infrastructure provider is that the they are continuing to investigate the issue. Prisma Postgres direct TCP remains unaffected.

  3. identified

    The issue has been identified and a fix is being implemented by our upstream provider. Prisma Postgres direct TCP remains unaffected.

  4. monitoring

    The issue has been resolved and we're actively monitoring. Prisma Postgres direct TCP remains unaffected.

  5. resolved

    We're continuing to observe healthy traffic through Prisma Accelerate. This incident has resolved.

Changes Rewindex caught on this incident

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

Prisma profileRecent Prisma incidentsMarkdownJSON