Prisma: Accelerate degraded operation in us-east-1 region
AWS us-east-1 outage, Oct 20, 2025 · 141 vendors, 181 incidents
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…”
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["AWS us-east-1<br/>posted 07:11 UTC"]:::root
before["Posted before AWS did<br/>5 vendors, 4 blamed AWS<br/>Salesforce, Descope, Ashby +2"]:::blames
root --> before
h1["Within an hour<br/>18 vendors, 17 blamed AWS<br/>Asana, Firebolt, Monday.com +15"]:::blames
root --> h1
h4["1 to 4 hours later<br/>30 vendors, 29 blamed AWS<br/>SingleStore, Loops, Buildkite +27"]:::blames
root --> h4
later["Later<br/>45 vendors, 44 blamed AWS<br/>RudderStack, Airbyte, Unbounce +42"]:::blames
root --> later
p0["Twilio<br/>posted +15 min"]:::blames
root --> p0
k0["BigCommerce<br/>+2 h 46 min"]:::hop2
p0 -->|"blamed Twilio"| k0
p1["Webflow<br/>posted +4 h 37 min, did not name AWS"]:::timing
root -.-> p1
k1["Rootly<br/>+10 h 23 min"]:::hop2
p1 -->|"blamed Webflow"| k1
p2["Baseten<br/>posted +4 min"]:::blames
root --> p2
k2["Zed<br/>+26 h 20 min"]:::hop2
p2 -->|"blamed Baseten"| k2
me["Prisma (this incident)<br/>posted +8 h 9 min"]:::me
later --- meFull 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
- identified
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.
- monitoring
The upstream infrastructure provider has mitigated the issue and we're observing recovery. We'll keep monitoring the services status.
- resolved
We're continuing to see healthy operation of services in us-east-1 region. 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.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).