Prisma’s incident blames AWS as the cause. (hop 1, posted +8 h 9 min vs AWS’s own post)
“…Accelerate degraded operation in us-east-1 region We're continuing to see healthy operation of services in us-east-1 region. This incident has been resolved. Description: We identified an upstream inf…”
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 in us-east-1 region
AddedImpact#2
Before: not present
After: major
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2025-10-20 15:19 UTC
AddedResolved time#5
Before: not present
After: 2025-10-20 21:13 UTC
AddedAffected components#6
Before: not present
After: Prisma Accelerate
AddedUpdateidentified#7
Before: not present
After: Description: We identified an upstream infrastructure provider issue affecting the us-east-1 region. Accelerate is experiencing issues while provisioning resources for new query engine instances.
We're working on mitigating and monitoring the situation and gathering more information from the upstream provider.
Prisma Postgres direct TCP connections are unaffected.
AddedUpdatemonitoring#8
Before: not present
After: The upstream infrastructure provider has mitigated the issue and we're observing recovery. We'll keep monitoring the services status.
AddedUpdateresolved#9
Before: not present
After: We're continuing to see healthy operation of services in us-east-1 region. This incident has been resolved.