- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Kimi-K2.6
- Down Index
- 27of 100
What to do
Check whether you use Telnyx Kimi-K2.6. 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 36m it lasted.
Anything that failed between 2026-09-28 16:46 UTC and 2026-09-28 17:21 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.
Root cause
We have identified the cause and are working on a fix.Read the postmortem
Updates from Telnyx 3
- investigating
We are investigating issues with Kimi K2.6 using our Chat Completions endpoint. Voice Assistants using K2.6 are unaffected.
provider
- identified
We have identified the cause and are working on a fix.
provider
- resolved
This is resolved
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-fae3d97edb
Is Telnyx still down?
No, this incident was resolved 2026-09-28 17:21 UTC. For Telnyx's live state, see https://down.guide/telnyx.
How long did it last?
36m, from 2026-09-28 16:46 UTC to 2026-09-28 17:21 UTC, by the times Telnyx posted.
What was affected?
Telnyx named Kimi-K2.6.
What caused it?
Telnyx wrote: "We have identified the cause and are working on a fix." The postmortem: https://status.telnyx.com/incidents/01M3MFWPHQD3XE9SCTB2MRY9CP
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.