Respond.io experienced a major incident on July 17, 2026 affecting Voice (Voice), lasting 19d 2h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Jul 17, 2026, 07:00 AM UTC
We found an issue affecting our Voice Calls feature , with some inbound and outbound calls not connecting properly since July 17. Our team is looking into the cause.
- investigating Jul 17, 2026, 10:00 AM UTC
We have traced these call failures to an authentication issue with our upstream voice provider, Telnyx, rather than an issue within respond.io itself. We are in contact with their team to confirm the cause. Telnyx also has an ongoing issue on their side related to processing delays, which may be...
- investigating Jul 26, 2026, 04:21 PM UTC
The issue became more significant on July 26 between 4:21 PM and 6:55 PM UTC, when a higher volume of inbound and outbound calls failed to connect. We are working with Telnyx to identify the cause.
- investigating Jul 27, 2026, 09:36 AM UTC
Telnyx has confirmed that our account is active and in good standing, and was never suspended. They believe the failures may be linked to a processing delay on their platform that began July 16, which could have caused our account to be temporarily and incorrectly flagged. We are continuing to...
- investigating Jul 27, 2026, 11:10 AM UTC
Telnyx has escalated this internally to their engineering team for further investigation. We are waiting on their findings and will share another update as soon as we have more information.
- resolved Aug 05, 2026, 09:00 AM UTC
This issue is now resolved. Between 17 July and 5 August, intermittent authentication failures with our upstream voice provider caused some inbound and outbound calls not to connect, with the highest volumes on 26 July and 4 August. The failures were not caused by any suspension or...