Report · Thursday 3 September 2026
From about ten to three this morning, people who rang our numbers heard nothing. Josh did not speak. He was not broken. Telnyx — the phone company that carries our calls — is running an update on its own equipment today. It answers the call, then fails to hand us the caller's voice. We proved that from both ends. There is nothing to fix in our code, and we have a letter ready for them.
What this is not
This is not Josh getting something wrong. It is not the words we give him, not his voice, and not the new work from the last two days. Ninety minutes before the first bad call, three test calls ran the whole way through on the very same setup. Nothing was changed in between.
Only one of these three is yours.
Do Chad and Ted get a warning? That is your call. It is the only thing here waiting on you. We have not contacted either of them.
The letter to Telnyx goes today. Dil has it. Nothing to decide. It is written.
Say yes when you want the three small jobs built. They are at the end of this report. None needs a decision from you. Only an hour from us.
| Time | What happened |
|---|---|
| 1:25am | Three test calls to Chad's line. All three ran the full length. Zero silent. |
| 2:54am | First silent call. Nothing had changed at our end. |
| 3:10am | Dil rings the number himself. Silence. |
| 3:58am | Rings again after a full restart. Silence again. |
| 4:05am | We send the two messages ourselves. Both get through. So our end is fine. |
When somebody rings one of our numbers, Telnyx picks up and then opens a line to our computer to pass the caller's voice across. Opening that line takes two short messages.
The first says hello. The second says here is the call — who rang, which number they rang, and where to send the voice.
All morning, Telnyx has been sending the first message and not the second. So our computer is holding a line open, waiting to be told whose call it is, and being told nothing. Josh never even learns there is somebody there. That is why the silence starts the moment they pick up, rather than partway through.
This was the hard part, and it is worth two minutes. It is the difference between blaming ourselves for a week and writing one letter.
From inside our computer, two very different problems look exactly the same. Either Telnyx never sent the second message, or something between them and us lost it on the way. Our records cannot tell those apart. So we sent the two messages ourselves.
The test that settled it
At 4:05am we opened the same line, to the same web address, from our own server, and sent both messages. Both arrived. Seven minutes earlier, on a real call to the same number over the same route, only one had.
Same address, same route, same equipment, seven minutes apart. Ours carries two messages. Telnyx sends one.
Three other things were ruled out by checking, not by guessing.
It is not the new work on Josh. The same fault appears in our records on 22 July and again on 4 August — weeks before any of this month's work existed. It has happened eleven times in all. Eight of those were this morning.
It is not our server needing a restart. We restarted it. Two calls three minutes later failed the same way, on two separate parts of the system.
Their records and ours match to the split second. Telnyx logs that they began sending us the voice at 8:58:31. They log that the caller hung up at 8:58:45. In those fourteen seconds they sent us one message. Hello.
Telnyx are running an update on the very part of their system that carries voice. Not one update — three, overlapping, all still going, all on the same equipment, across all ten of their regions.
| Started | Ends |
|---|---|
| Monday 11pm | This morning, 9:30am |
| Yesterday 10am | Friday morning, 5am |
| Yesterday, 7pm | This morning, 8am |
All times are ours. We checked these on Telnyx's own status page, not by taking their support chat's word for it.
Their own words
"Our Telephony Engineers will be performing an update on our Voice Services servers across all regions. Impact: this update is not expected to disrupt service. Action required: if you experience any audio issues or dropped calls during this maintenance window, please report them immediately to Telnyx Support."
In plain English: we are working on the machines that carry your calls. It should not break anything. If it does, tell us straight away.
They have asked to be told. We should tell them.
One honest gap. The first of those three windows opened on Monday night, and the phone worked fine for two days after it. Our three good calls at 1:25am this morning were inside all three. So an open window does not on its own mean a broken call. What most likely happened is that their update reached the particular machine handling our calls at about ten to three. That part is our best reading, not a proven fact. Everything else above is measured.
The letter is written and waiting. It gives them the exact call to look at. It puts their own timings next to ours. It quotes the one message we did get. It lists the three things we ruled out on our side.
Then it asks the only question that matters. When will our calls be off the equipment they are working on?
It has not been sent. Anything that goes outside the company waits for a person. Dil has it.
The last of their three windows does not close until five o'clock on Friday morning. So this is not over at eight today. Anyone ringing Chad's or Ted's number between now and then may hear nothing.
We cannot promise it will happen again. We cannot promise it will not. What we can say is that the risk stays open for another day.
We will know the moment it comes back. The phone now writes one plain line in our records every time a call dies this way, and it names the call.
Whether to warn them is your call. We have not contacted either of them.
It will happen again. Phone companies work on their equipment. So the real question is what we have ready.
The honest answer: we planned for this in July, and then we stopped short of finishing it.
Four ways to keep answering when something breaks. They are not rivals — a good answer uses several.
| Plan | Where it stands |
|---|---|
| Ring a real phone if we do not pick up | Built and proven on 10 August. Waiting on one thing: a backup number from Chad and Ted. |
| Reach Claude through Amazon or Google instead | Worth doing. Not started. |
| Use a different company's AI | Later. Cheap to build, expensive to trust — it would need its own full test run. |
| Telnyx's own AI answers when we cannot | The favourite in July. Still the favourite. Not started. |
The uncomfortable part
Three of those four protect against our side failing. This morning our side was fine. A backup that only helps when we are broken does not help when the phone company is.
Knowing before you did. Nobody found out until Dil rang the number. Our system writes every fault into a log file and tells nobody. We wrote that down on 10 August and left it. A short job that rings each number every hour and sends one message when nobody answers would have caught this at ten to three.
Hanging up on a line that never starts. When we get "hello" and nothing follows, we sit and wait. If we cut that line off after a few seconds, the call could roll on to a real phone instead. That would turn silence into a ringing mobile.
One setting that is currently wrong for this. Our phone setup tells Telnyx to keep retrying us. Our own July notes say this must be off, or the call can never roll on to a real phone. Today it is on. It is one box to change. It should be changed at the same time as the backup number, not on its own.
None of these three is a big build. All three were half-known already, written in our own notes, and left for a quieter day. This morning is the argument for the quieter day.
Yesterday's real job is done, and it worked.
Josh used to go silent when several people rang at once. Eight callers, three heard him. We found why: he was one worker doing every job in turn. He can now do four at a time.
The proof came in at 1:25 this morning, ninety minutes before any of the trouble above. Three test calls, all three answered, all three ran over six minutes, none silent — against three of eight silent the day before. That result stands. It is simply unlucky that a phone company fault arrived an hour later and looked, at first glance, like the same thing.
Booked Solid Inspector · written 3 September 2026, and updated after checking Telnyx's own status page.
Written by Claude Code for Ken. The letter to Telnyx is with Dil and has not been sent.