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…”
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: Prisma Console is experiencing a partial outage
After: An upstream infra provider is experiencing issues which is impacting our services. We are monitoring the situation.
AddedUpdateinvestigating#8
Before: not present
After: 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.
AddedUpdatemonitoring#9
Before: not present
After: A fix has been deployed by Cloudflare and our all services appear to have come back online. We're continuing to monitor.
AddedUpdatemonitoring#10
Before: not present
After: We are continuing to monitor for any further issues.