Rewindex

CompaniesAptibleIncidents

Aptible: Delayed and Timed-out requests to the Aptible LLM Gateway

MinorStatus: resolvedStarted Resolved (19 h)4 updatesstspg.io (opens in new tab)
Part of an outage event

GitHub outage, Jul 16, 2026 · 14 vendors, 16 incidents

Aptible’s incident started in the same window without naming GitHub (timing only, not evidence of a link). (timing only, posted +1 h 26 min vs GitHub’s own post)

Swipe sideways to see the whole diagram.

same windowGitHubposted 21:05 UTCWithin an hour1 vendorSentry1 to 4 hours later7 vendors, 5 blamed GitHubRender, CodeRabbit, CircleCI, Bitrise +3Aptible (this incident)posted +1 h 26 min
same windowGitHubposted 21:05 UTCWithin an hour1 vendorSentry1 to 4 hours later7 vendors, 5 blamed GitHubRender, CodeRabbit, CircleCI,Bitrise +3Aptible (this incident)posted +1 h 26 min
Aptible is outlined in red. Groups show up to a few vendors each; the event page lists every incident.
Mermaid source
flowchart LR
  root["GitHub<br/>posted 21:05 UTC"]:::root
  h1["Within an hour<br/>1 vendor<br/>Sentry"]:::names
  root --> h1
  h4["1 to 4 hours later<br/>7 vendors, 5 blamed GitHub<br/>Render, CodeRabbit, CircleCI, Bitrise +3"]:::blames
  root --> h4
  me["Aptible (this incident)<br/>posted +1 h 26 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: Aptible LLM Gateway

Timeline of updates

  1. identified

    We are aware of delayed and timed-out requests to the LLM Gateway. We have made some changes to help minimize the impact while engineers continue to address the root cause.

  2. monitoring

    We have increased resource capacity, and we are monitoring the results.

  3. monitoring

    After a regression in performance starting at 9:57 UTC (5:57 EDT) and lasting until 11:12 UTC (7:12 EDT), we've deployed a potential fix and updated our service scaling. We are continuing to monitor whether these changes fully resolve the issue before closing this incident.

  4. resolved

    Following the fixes deployed per the previous update, we have seen stable performance on the LLM Gateway since 7:12 EDT and are resolving the issue. The root cause of this issue was a severe performance degradation in 3 specific endpoints: • `GET /models` • `GET /v1/models` • `GET /metadata/models` ...all of which return a list of available models. The performance issue on these endpoints was severe enough to cause significant request queueing and degraded performance for other unaffected endpoints. The fix we deployed added caching on this endpoint to ensure fast responses. Since those fixes have been deployed, we are no longer seeing request queueing or impacts to other LLM Gateway API endpoints.

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

Aptible profileRecent Aptible incidentsMarkdownJSON