Variable Extraction Model Routing Failures

What to do

• Check whether your product depends on Bland AI. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.

  Anything that failed between 2026-10-05 19:47 UTC and 2026-10-05 18:00 UTC may need a replay.

• Subscribe to Bland AI's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=bland works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Bland AI 1

1. resolvedOct 5, 2026, 6:00 PM UTC

   At 11:15 AM PDT a provider side routing update caused variable extraction requests for fail for some customers. Some post call features were also affected including summary generations and analysis schemas. Fully recovered at 12:11 PM. Timeline: 11:15 AM - Requests begin erroring as the change starts rollout in provider's cluster. 11:20 AM - Rollout completes, error rates for affected models reaches 100%. 11:35 AM - Automated alarms page on call engineering, issue is raised to provider immediately. 11:45 AM - Bland engineering identifies issue as a routing change that expects a new model base URL. 11:50 AM - An override to the new base URL is applied, update begins rolling out to Bland clusters. 12:11 PM - All rollouts completed, error rates return to normal levels.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.