- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 15of 100
What to do
Check whether your product depends on Telnyx. 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 25m it lasted.
Anything that failed between 2026-10-29 14:50 UTC and 2026-10-29 15:15 UTC may need a replay.Subscribe to Telnyx's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=telnyx works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Telnyx 2
- investigating
Our engineers are investigating an issue causing delays to messaging webhook deliveries which began at approximately 14:20UTC. The issue may also delay Mission Control and Porting ordering and configuration updates, and 503 responses may be seen. Our team is actively investigating this and updates will be posted here.
provider
- resolved
Our team found the root cause of this issue to be due to a network blip leading to various service issues. It was confirmed to be brief and all services are now caught up as of 15:15UTC.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-6072f82d67
Is Telnyx still down?
No, this incident was resolved 2026-10-29 15:15 UTC. For Telnyx's live state, see https://down.guide/telnyx.
How long did it last?
25m, from 2026-10-29 14:50 UTC to 2026-10-29 15:15 UTC, by the times Telnyx posted.
What caused it?
Telnyx hasn't published a root cause. If it does, it shows here.
Where does this come from?
Telnyx's official status page, https://status.telnyx.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.