Need help with an issue not listed here? Please contact Telnyx Support via https://telnyx.com/contact-us. For more information, see our Privacy Policy and Terms of Service linked below.
On October 21, between approximately 18:17 and 19:20 UTC, a network infrastructure issue caused intermittent failures across Telnyx services.
Products affected during the disruption:
- Mission Control portal and API - intermittent timeouts and "503 Service Unavailable" errors, in a series of short outages totaling roughly 20 minutes within the window. Account management and configuration actions may have failed intermittently.
- Voice API and TeXML - some outbound call setups failed or timed out, and webhook delivery to application endpoints was delayed or dropped for calls placed during this period. Calls already in progress were not terminated, but new call setup was unreliable.
- WebRTC - some customers experienced failures when initiating new calls or connecting to gateways.
- Call Control - dialing requests intermittently returned HTTP 500 errors, and webhook events for some calls during the window were not delivered.
- Call recordings - recordings may be missing for calls that were active during the window.
- Programmable Wireless - data sessions on some SIMs dropped during the disruption and reconnected automatically as service recovered
A deeper investigation into the underlying cause is ongoing, and we are adding additional monitoring to detect this class of failure earlier. Thank you.
No components marked as affected
Resolved
On October 21, between approximately 18:17 and 19:20 UTC, a network infrastructure issue caused intermittent failures across Telnyx services.
Products affected during the disruption:
- Mission Control portal and API - intermittent timeouts and "503 Service Unavailable" errors, in a series of short outages totaling roughly 20 minutes within the window. Account management and configuration actions may have failed intermittently.
- Voice API and TeXML - some outbound call setups failed or timed out, and webhook delivery to application endpoints was delayed or dropped for calls placed during this period. Calls already in progress were not terminated, but new call setup was unreliable.
- WebRTC - some customers experienced failures when initiating new calls or connecting to gateways.
- Call Control - dialing requests intermittently returned HTTP 500 errors, and webhook events for some calls during the window were not delivered.
- Call recordings - recordings may be missing for calls that were active during the window.
- Programmable Wireless - data sessions on some SIMs dropped during the disruption and reconnected automatically as service recovered
A deeper investigation into the underlying cause is ongoing, and we are adding additional monitoring to detect this class of failure earlier. Thank you.