Rewindex

CompaniesZedIncidents

Zed: Edit Prediction timeouts

unknownStatus: resolvedStarted Resolved (23 min)3 updatesstatus.zed.dev (opens in new tab)
Part of an outage event

AWS us-east-1 outage, Oct 20, 2025 · 141 vendors, 181 incidents

Zed’s incident is a second hop: it blames Baseten, which was affected by AWS. (hop 2, posted +26 h 20 min vs AWS’s own post)

“…rediction timeouts We've identified the issue and are working with our inference provider Baseten to fix it.. This incident has been resolved.. We implemented a fix and are currently monitoring the re…”

Swipe sideways to see the whole diagram.

blamed Twilioblamed Webflowblamed Basetenblamed BasetenAWS us-east-1posted 07:11 UTCPosted before AWS did5 vendors, 4 blamed AWSSalesforce, Descope, Ashby +2Within an hour18 vendors, 17 blamed AWSAsana, Firebolt, Monday.com +151 to 4 hours later30 vendors, 29 blamed AWSSingleStore, Loops, Buildkite +27Later45 vendors, 44 blamed AWSRudderStack, Airbyte, Unbounce +42Twilioposted +15 minBigCommerce+2 h 46 minWebflowposted +4 h 37 min, did not name AWSRootly+10 h 23 minBasetenposted +4 minZed+26 h 20 minZed (this incident)posted +26 h 20 min
blamed Twilioblamed Webflowblamed Basetenblamed BasetenAWS us-east-1posted 07:11 UTCPosted before AWS did5 vendors, 4 blamed AWSSalesforce, Descope, Ashby +2Within an hour18 vendors, 17 blamed AWSAsana, Firebolt, Monday.com+151 to 4 hours later30 vendors, 29 blamed AWSSingleStore, Loops, Buildkite+27Later45 vendors, 44 blamed AWSRudderStack, Airbyte,Unbounce +42Twilioposted +15 minBigCommerce+2 h 46 minWebflowposted +4 h 37 min, did notname AWSRootly+10 h 23 minBasetenposted +4 minZed+26 h 20 minZed (this incident)posted +26 h 20 min
Zed is outlined in red. Groups show up to a few vendors each; the event page lists every incident.
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["Zed (this incident)<br/>posted +26 h 20 min"]:::me
  p2 -->|"blamed Baseten"| 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: Edit Prediction

Timeline of updates

  1. identified

    We've identified the issue and are working with our inference provider Baseten to fix it..

  2. monitoring

    We implemented a fix and are currently monitoring the result..

  3. resolved

    This incident has been resolved..

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

Zed profileRecent Zed incidentsMarkdownJSON