Minor impactResolvedCommunication

Telnyx incident: Telephony tokens 503s error

Telnyx reported this minor-impact incident on its official status page on Oct 28, 2026, 21:01 UTC. It was resolved after 1 min.

Right now Telnyx is degraded. Live Telnyx status →

🔔 Get alerted when Telnyx has issuesFree · email alerts · no credit card
Oct 28, 2026, 21:01 UTC
started
Oct 28, 2026, 21:02 UTC
resolved
1 min
duration
Minor
impact

Timeline

updates from Telnyx's status page ↗
  1. resolvedOct 28, 2026, 21:02 UTC

    A rollback was applied at ~15:54 UTC and credential creation has been healthy since 15:58 UTC.

  2. monitoringOct 28, 2026, 21:01 UTC

    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.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Telnyx's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does Telnyx have incidents?

Telnyx reported 36 incidents in the last 90 days, 18 of them major or critical. A typical incident lasted 2h 33m. See Telnyx's uptime and incident history

← Previous: Unexpected wireless voice usage and charges (Oct 28, 2026)Next: Delays with Messaging Webhooks, Mission Control Number and Porting ordering/configurations (Oct 29, 2026) →
Telnyx incident on Oct 28, 2026: Telephony tokens 503s error · APIStatus.watch