- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 9of 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 1m it lasted.
Anything that failed between 2026-10-28 21:01 UTC and 2026-10-28 21:02 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
- monitoring
This was a platform-side incident affecting credential creation. A service update deployed at 14:36 UTC introduced a fault in the component that validates credential connections during creation, so `POST /v2/telephony_credentials` returned 503 from ~14:55 to ~15:58 UTC. A rollback was applied at ~15:54 UTC and credential creation has been healthy since 15:58 UTC.
provider
- resolved
A rollback was applied at ~15:54 UTC and credential creation has been healthy since 15:58 UTC.
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-b8ca5ccde9
Is Telnyx still down?
No, this incident was resolved 2026-10-28 21:02 UTC. For Telnyx's live state, see https://down.guide/telnyx.
How long did it last?
1m, from 2026-10-28 21:01 UTC to 2026-10-28 21:02 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.