Vendor reports: degradedOpen · vendor status “degraded”Official status API

Degraded Service: Insights API and Boards Inaccessible

Reported by Vapi · AI & ML · source last read 4 min ago

Official source (opens in a new tab)
Vendor start
Nov 10, 2026, 00:27 UTC
Vendor's clock
Resolved
Not yet
Still open
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
Not available
Needs both vendor times

Affected scope

Not stated by the vendor

The vendor's feed gives no region for this incident. It is not assumed to be global.

Potential relevance

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

What to check on your side

Verification steps only. Statuswall cannot see your systems.

  • Watch 5xx, 429 (rate limit) and timeout rates on calls to the Vapi API.
  • If you route to more than one model or provider, check whether fallback traffic is behaving.
  • Check retry queues and background jobs that call the API, which can back up quietly.
  • Check error rates, latency and timeouts in your own monitoring for requests that depend on Vapi.
  • Look at synthetic checks and alerts that exercise Vapi.
  • Compare with recent deploys on your side, so a coincidental change is not blamed on the vendor.
  • Follow the vendor's official incident page for scope changes and resolution.

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. Nov 10, 2026, 00:27 UTCVendor-reported startVendor time

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