Outage fallbacks · Research · 18 Nov 2026
A fallback for when ElevenLabs goes down
What failed on the Handyman Bury line, how other companies keep a voice agent line answering through an outage, which fallbacks are worth having, and what each one costs.
Recommendation
The short answer
Put our own relay in front of each agent with an 8-second ring timer. If the voice agent has not answered by then, the caller goes to a backup. A standby agent on a second platform comes later, and Retell is the one to trial.
- The findingElevenLabs did not refuse the Bury call. It left it ringing for 19 seconds until the caller hung up. Telnyx's free failover only reacts to a refusal, so it would not have helped.
- Do firstAdd the ring timer to the relay we already have (
execution/call_desk/app.py). It costs about $0.002 a minute and works call by call. - Do nextA watchdog that places a test call on a schedule and messages Telegram when the agent does not answer. ElevenLabs' status page runs up to 2 hours 49 minutes behind.
- ThenTrial one standby agent on Retell on a demo line. It costs nothing while idle and about $5 for an hour of outage calls.
- Do not buyElevenLabs Enterprise for its SLA, a human answering service, or Vapi.
From our own Telnyx call records
What happened on 18 Nov
ElevenLabs opened an incident at 15:34. Our call to the Bury line at 15:58 was never answered. By 17:54 the line was connecting again, with the incident still open.
18 November 2026, times in UTC (the same as UK time)
Why Telnyx's free failover would have missed it
An outage where ElevenLabs refuses the call
18 November: ElevenLabs lets it ring
- The Bury line has one route and nothing behind it. One address (
sip.rtc.elevenlabs.io), no second route, no call forwarding. A failed call has nowhere to go. - ElevenLabs has no setting for this. Its only resilience option is a backup language model, which does nothing when the call never starts (ElevenLabs docs).
- One caveat. This rests on a single call record. Other outages may refuse calls outright, and a second route would catch those.
How often, and what they owe us
ElevenLabs' record
This will happen again. The fallback will be used regularly, not once.
- About 13incidents in 2026 where phone calls failed to connect or dropped, in ten and a half months. Five were in the EU only.
- 11h 37mof telephony trouble posted in the last 86 days, about 99.4% clear. 18 November is not in that figure: ElevenLabs did not tag it as telephony.
- About 12 hourswas the worst outage, on 31 July, in the EU and India. The US was down longer.
- 35m to 2h 49mis how long after the real start ElevenLabs first posts. The status page is too slow to be our alarm.
- Noneis the uptime promised on our plan. The service is "as is". An SLA exists only on Enterprise, and its terms are not published.
"Resolved" has also relapsed inside the same incident at least three times this year, so a fallback should stay armed after the all-clear. (ElevenLabs incident data; third-party archive; terms)
The pattern others publish
What other companies do
They build a ladder. Each rung catches a different failure, and the last rung needs no AI provider at all. Twilio published the clearest version on 4 November 2026 (Twilio).
| Rung | What it catches | Who offers it |
|---|---|---|
| Backup speech or language model | One supplier failing while the platform is up | ElevenLabs, Retell, Vapi, LiveKit |
| Fallback number on the platform | Sending calls elsewhere by hand | Retell "backup mode", Vapi fallback destination |
| Carrier reroute | The platform refusing calls | Telnyx second route and forward on failure; Twilio equivalents |
| Relay with a ring timer | The platform stalling, as on 18 November | Telnyx TeXML and Twilio TwiML |
| Scheduled test calls | Knowing within minutes | Monitoring vendors advise every 5 to 15 minutes |
- A fallback run by the platform that is down is weak. The only user report found was a Vapi customer whose fallback number did not fire in a test (Vapi support thread).
- Published uptime promises cluster at 99.9%. That still allows about 8.8 hours down a year.
- No agency has written up what it does. Searches of Reddit, Discord and similar found nothing first-hand. A tested fallback with a written procedure puts us ahead of what is public.
From a free setting to a standby agent
Our options
The test for each one: would it have caught the 18 November call?
| Option | Caught 18 Nov? | Standing cost | Cost in use | Effort |
|---|---|---|---|---|
| A. Second route on the Telnyx connection | No | $0 | $0 | Minutes, but needs somewhere to point |
| B. Telnyx "forward on failure" to a phone | No | $0.20 a number a month | Two billed call legs | Minutes |
| C. Our relay with an 8-second ring timer, then voicemail and an alert | Yes | $0 | About $0.002 a minute on every call | Days. Extends the relay we have |
| D. Relay, then the client's staff line, then voicemail | Yes | $0 | About $0.024 a minute to a UK mobile, $0.009 to a US one | C, plus a number from each client and Roman's agreement |
| E. Relay, then a standby agent on a second platform | Yes | $0 | About $0.06 to $0.08 a minute while it answers | Weeks, then upkeep |
| F. Human answering service | Yes, through the relay | $49 a month or more | $2.99 a minute | A script per client |
| W. Watchdog: scheduled test call and Telegram alert | Detects, does not rescue | $0 | About 9 cents a test call at worst | Days. Starts from a script we have |
The call path we would build
- 1The voice agent on ElevenLabs answers, as now. The relay gives it 8 seconds.Every call
- 2A standby agent on a second platform takes the call if the first does not answer.Later, option E
- 3The client's own staff line or mobile rings next.Option D
- 4Voicemail, with a Telegram alert saying "taken by backup". No AI provider is involved.Option C
Things to know before building
- A and B still help. They catch outages where ElevenLabs refuses calls. They are just not enough alone.
- A cost trap on D. If the forwarded leg shows the caller's own number, a UK mobile leg can bill up to $0.835 a minute, not $0.02. Show the business's number.
- The relay puts our VPS in the call path. Telnyx has a fallback address for when the VPS is down. Agent transfers to a human are the likeliest thing to break behind a relay and need testing on a copy.
- The silent case stays open. If the agent answers and says nothing, no phone network setting notices. Only the watchdog catches that.
Reliable companies for a second agent
Which standby platform
No platform has had a clean year. A standby earns its place by failing at different times from ElevenLabs, not by a better record.
Retell AI
Trial this one- A separate company from ElevenLabs and from Telnyx's AI layer.
- Documented connection from a Telnyx line.
- Calmest recent status page: its worst recent event lasted 13 minutes.
- Against: slowest in one open speed test, and some users report Telnyx setup problems.
$0 idle. About $0.07 to $0.08 a minute. 20 calls at once.
Telnyx AI Assistants
Second choice- No second supplier, no extra hop, and the cheapest.
- Against: it failed on us on 28 July. 17 calls in a row were answered and silent, which a ring timer cannot detect.
- Against: it shares the carrier with the main path, and voice choices are locked.
$0 idle. About $0.06 a minute. 500 calls at once.
OpenAI Realtime or LiveKit Cloud
Only if we want to own code- The most independent of ElevenLabs.
- Against: we would write and run the agent ourselves.
- Against: users report failed inbound calls on OpenAI's phone connection.
$0 to $50 a month idle. $0.05 to $0.38 a minute.
Vapi
Ruled out- Two long outages on its bring-your-own-line service in October: 12 hours 18 minutes and 7 hours 47 minutes.
- 41 of 246 test calls never connected in one benchmark.
- It reported failures across three speech suppliers on 18 November, ElevenLabs included.
$0 to $29 a month idle. About $0.08 to $0.13 a minute.
Also ruled out: Hume EVI (reported retired), Deepgram and Gemini Live (no direct phone connection), Bland and Synthflow (no reliability evidence), and a second ElevenLabs region (Enterprise only, and not a failover).
Three cautions on any standby
- The voice. A good British voice without ElevenLabs is unproven on every platform. It needs a listening test on a handset.
- The clinic. If its calls count as health data, a standby needs its own signed agreement first. Vapi charges $2,000 a month for that and Telnyx lists $2,500. Retell says its agreement is self-serve, in its own marketing. Until that is settled, the clinic's fallback is its staff line and voicemail.
- The upkeep. A second prompt, tools and test pack must be kept in step with the main agents. That time will cost more than the cash.
List prices read on 18 Nov 2026, at £1 = $1.32
Pricing
A standby is cheap because it sits idle. What matters is whether there is a monthly fee, and how many calls it can take at once when every line falls over together.
| Platform | Monthly fee, idle | Per minute in use | Calls at once | Fee for our Telnyx line |
|---|---|---|---|---|
| ElevenLabs, as now | Our plan | $0.08 plus the model | By plan | None |
| Retell AI | $0 | $0.08, or $0.11 with a premium voice | 20 | None |
| Telnyx AI Assistants | $0 | About $0.06 | 500 | None |
| Bland | $0 | $0.14 flat | 10 | None |
| Vapi | $29 for 10 lines | $0.08 to $0.13 | 10 | None |
| LiveKit Cloud | $50 for 20 lines | About $0.05, plus our own code | 20 | Included minutes |
Added cost of a full-day outage: 500 call minutes across 10 lines
| Other costs | Price | Note |
|---|---|---|
| A two-hour outage on Retell, about 60 call minutes | $5 (£4) | $3.60 on Telnyx AI Assistants |
| The relay itself | About $0.002 a minute | Telnyx's fee per call leg, on every call |
| Watchdog test calls | $65 a month hourly, $260 every 15 minutes | Worst case, if each test bills a full ElevenLabs minute at the overage rate |
| Text to a caller | UK $0.05, US about $0.009 | Telnyx's own pages disagree on the UK rate |
| Bought-in test call monitoring (Cekura) | $0.25 a test minute | No monthly fee. Others are quote only |
Recommendations
What to do, in order
- 1
Add the 8-second ring timer to the relay and put the Bury demo line behind it. The backup is voicemail plus a Telegram alert. Test it against a dead address.
- 2
Build the watchdog. A test call to one line on a schedule, plus a free check of ElevenLabs' status feed, alerting on Telegram.
- 3
Take the tested design to Roman for the live client lines. Agree for each client what the backup is: their staff line, then voicemail.
- 4
Check the backup language model is switched on for each live agent. Looking is read-only.
- 5
Build one standby agent on Retell for a demo line. Run the test pack and a listening test. Extend to live lines only if it passes.
- 6
Promise clients what we control. "A caller always reaches something": the voice agent, then their own staff, then a voicemail that alerts them. Not an uptime percentage.
Do not buy: ElevenLabs Enterprise for the SLA (an SLA pays credits, it does not answer calls), a human answering service, or Vapi. Nothing in this plan releases, ports or deletes a number, and Roman's connection is left alone until he agrees to a change.
Read this before acting
What is not verified
- Nothing here has been tested with a real call. Every claim about fit comes from documentation.
- Whether ElevenLabs sent a "ringing" signal before stalling, and what it returns in other outages.
- The cause and full length of the 18 November incident. It was still open at 18:33.
- Whether the relay can reach ElevenLabs over the connection type ElevenLabs requires. Test this first.
- The exact cost of the relay's second leg, and UK per-minute rates on our account.
- Whether Retell's health-data agreement is really free and self-serve.
- Twelve-month incident totals for any platform. Official pages keep 90 days and trackers disagree.
- What other agencies do. No first-hand account was found.
Where the figures come from
Sources
- Our own Telnyx call records and connection settings, read 18 Nov 2026
- ElevenLabs 18 Nov incident
- ElevenLabs incident data
- ElevenLabs incidents, third-party archive
- ElevenLabs terms and agent pricing
- ElevenLabs SIP trunking
- Telnyx failover and retries
- Telnyx TeXML Dial
- Telnyx pricing and AI pricing
- Twilio failover guidance, 4 Nov 2026
- Retell reliability, status, pricing
- Retell's Telnyx guide
- Vapi status and pricing
- Speed benchmarks, as relayed by Telnyx
- LiveKit pricing
- PATLive pricing
- Hamming on monitoring (vendor claim)