Vendor reports: degradedResolved · vendor status “resolved”Official status API

Increase in 429 errors with LLM Gateway requests using Haiku 4.5

Reported by AssemblyAI · AI & ML · source last read just now

Official source (opens in a new tab)
Vendor start
Feb 9, 2026, 19:53 UTC
Vendor's clock
Resolved
Feb 10, 2026, 00:33 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
4 h 40 min
From vendor start and resolution

Summary

Built from the facts below, no AI

Potential impact, not a confirmed outage of your systems.

What the vendor confirmed

  • AssemblyAI reports degraded: "Increase in 429 errors with LLM Gateway requests using Haiku 4.5".[E1, E2]
  • The vendor marked it resolved at 2026-02-10 00:33 UTC.[E3, E7]

Affected products and regions

  • Components: LLM Gateway.[E6]

What is unknown

  • Which regions are affected: the vendor did not say.[E5]
  • Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.

Last update in these facts: 2026-02-10 00:33 UTC · summary s1, evidence 7fe6e13b40eee553

Evidence (7)
  1. E1AssemblyAI reports degraded. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Increase in 429 errors with LLM Gateway requests using Haiku 4.5". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2026-02-09 19:53 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6Components the vendor attached: LLM Gateway. (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2026-02-10 00:33 UTC. (vendor) source (opens in a new tab)

Affected scope

Not stated by the vendor

Components: LLM Gateway

No region Statuswall recognises is stated for this incident (place names and provider-specific codes are not converted). It is not assumed to be global.

Potential relevance

AssemblyAI is not in your stack. Follow it to see whether reports like this fall inside the regions you use.

Timeline

Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.

  1. Feb 9, 2026, 19:53 UTCVendor-reported startVendor time
  2. Feb 10, 2026, 00:33 UTCVendor-reported resolutionVendor time

No changes observed yet. Statuswall began recording changes on incidents in November 2026.