Rewindex

CompaniesKoyebIncidents

Koyeb: Login failure

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

AWS outage, Jul 16, 2026 · 27 vendors, 29 incidents

Koyeb’s incident started in the same window without naming AWS (timing only, not evidence of a link). (timing only, posted +16 min vs AWS’s own post)

Swipe sideways to see the whole diagram.

blamed Anthropicsame windowAWSposted 08:44 UTCPosted before AWS did2 vendors, 1 blamed AWSFusionAuth, UpstashWithin an hour2 vendors, 2 blamed AWSCoda, GrammarlyAnthropicposted −5 min, did not name AWSGitHub, GitHub Copilot+12 h 21 minKoyeb (this incident)posted +16 min
blamed Anthropicsame windowAWSposted 08:44 UTCPosted before AWS did2 vendors, 1 blamed AWSFusionAuth, UpstashWithin an hour2 vendors, 2 blamed AWSCoda, GrammarlyAnthropicposted −5 min, did not nameAWSGitHub, GitHub Copilot+12 h 21 minKoyeb (this incident)posted +16 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["AWS<br/>posted 08:44 UTC"]:::root
  before["Posted before AWS did<br/>2 vendors, 1 blamed AWS<br/>FusionAuth, Upstash"]:::blames
  root --> before
  h1["Within an hour<br/>2 vendors, 2 blamed AWS<br/>Coda, Grammarly"]:::blames
  root --> h1
  p0["Anthropic<br/>posted −5 min, did not name AWS"]:::timing
  root -.-> p0
  k0["GitHub, GitHub Copilot<br/>+12 h 21 min"]:::hop2
  p0 -->|"blamed Anthropic"| k0
  me["Koyeb (this incident)<br/>posted +16 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: Control Panel

Timeline of updates

  1. identified

    The upstream provider we use for authentication is going through a major incident. Login attempts to the control panel are failing. Direct API usage through tokens is working as expected and the running workloads are 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