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)
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.
What changed
Struck in red is what Prisma removed; blue is what they added. Muted text is unchanged context.
BeforeAfter
AddedTitle#1
Before: not present
After: Accelerate degraded operation
AddedImpact#2
Before: not present
After: major
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2025-11-18 12:06 UTC
AddedResolved time#5
Before: not present
After: 2025-11-18 19:12 UTC
AddedAffected components#6
Before: not present
After: Prisma Accelerate
AddedUpdateidentified#7
Before: not present
After: 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.
AddedUpdateidentified#8
Before: not present
After: Latest update from our infrastructure provider is that the they are continuing to investigate the issue.
Prisma Postgres direct TCP remains unaffected.
AddedUpdateidentified#9
Before: not present
After: The issue has been identified and a fix is being implemented by our upstream provider.
Prisma Postgres direct TCP remains unaffected.
AddedUpdatemonitoring#10
Before: not present
After: The issue has been resolved and we're actively monitoring.
Prisma Postgres direct TCP remains unaffected.
AddedUpdateresolved#11
Before: not present
After: We're continuing to observe healthy traffic through Prisma Accelerate. This incident has resolved.