Rewindex

CompaniesKoyebIncidents

Koyeb: 500s on APIs

unknownStatus: resolvedStarted Resolved (2 min)2 updatesstatus.koyeb.com (opens in new tab)
Part of an outage event

Azure west us outage, Jul 23, 2026 · 25 vendors, 26 incidents

Koyeb’s incident started in the same window without naming Azure (timing only, not evidence of a link). (timing only, posted +11 min vs the first vendor naming Azure)

Swipe sideways to see the whole diagram.

same windowAzure west usown incident not archivedWithin an hour2 vendors, 1 blamed AzureJFrog, Optimizely1 to 4 hours later2 vendors, 2 blamed AzureWiz, Sumo LogicLater1 vendorContentstackKoyeb (this incident)posted +11 min
same windowAzure west usown incident not archivedWithin an hour2 vendors, 1 blamed AzureJFrog, Optimizely1 to 4 hours later2 vendors, 2 blamed AzureWiz, Sumo LogicLater1 vendorContentstackKoyeb (this incident)posted +11 min
Koyeb is outlined in red. Groups show up to a few vendors each; the event page lists every incident.
Mermaid source
flowchart LR
  root["Azure west us<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>2 vendors, 1 blamed Azure<br/>JFrog, Optimizely"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>2 vendors, 2 blamed Azure<br/>Wiz, Sumo Logic"]:::blames
  root --> h4
  later["Later<br/>1 vendor<br/>Contentstack"]:::names
  root --> later
  me["Koyeb (this incident)<br/>posted +11 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: APIControl Panel

Timeline of updates

  1. investigating

    We are investigating this issue. Existing deployments are working not affected..

  2. resolved

    This incident has been resolved..

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

Koyeb profileRecent Koyeb incidentsMarkdownJSON