Rewindex

CompaniesBasetenIncidents

Baseten: Elevated errors on new model builds. Existing models are not affected

MinorStatus: resolvedStarted Resolved (37 min)3 updatesstspg.io (opens in new tab)
Part of an outage event

AWS us-east-1 outage, Oct 9, 2026 · 17 vendors, 18 incidents

Baseten’s incident started in the same window without naming AWS (timing only, not evidence of a link). (hop 1, posted −1 h 4 min vs the first vendor naming AWS)

Swipe sideways to see the whole diagram.

same windowAWS us-east-1own incident not archivedWithin an hour5 vendors, 2 blamed AWSConvex, Temporal Cloud, JFrog, PlanetScale +1Later1 vendor, 1 blamed AWSChargebeeBaseten (this incident)posted −1 h 4 min
same windowAWS us-east-1own incident not archivedWithin an hour5 vendors, 2 blamed AWSConvex, Temporal Cloud,JFrog, PlanetScale +1Later1 vendor, 1 blamed AWSChargebeeBaseten (this incident)posted −1 h 4 min
Baseten 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/>own incident not archived"]:::inferred
  h1["Within an hour<br/>5 vendors, 2 blamed AWS<br/>Convex, Temporal Cloud, JFrog, PlanetScale +1"]:::blames
  root --> h1
  later["Later<br/>1 vendor, 1 blamed AWS<br/>Chargebee"]:::blames
  root --> later
  me["Baseten (this incident)<br/>posted −1 h 4 min"]:::me
  root -.->|"same window"| 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: Model Management API

Timeline of updates

  1. investigating

    We are currently investigating this issue.

  2. monitoring

    A fix has been implemented and we are monitoring the results.

  3. resolved

    This incident has been resolved.

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

Baseten profileRecent Baseten incidentsMarkdownJSON