Is Telnyx down?
Last checked 2m agoNo incidents right now.
Telnyx is operational right now. Last checked 2m ago; the most recent incident resolved 1d ago.
Real-time Telnyx status, recent outages, and incident history: pulled directly from Telnyx's official status page at status.telnyx.com every 5 minutes. Pingoru tracks 116 Telnyx services and has captured 180 incidents in the last 90 days (97.71% uptime). Get email, Slack, Discord, or webhook alerts the moment Telnyx reports a new incident, free for 3 monitors, no credit card.
Recent outages & incidents
Past 90 days- API V1API V2API V1API V2
Timeline · 5 updates
- investigating · Oct 30, 2026, 07:09 PM UTC
We’re investigating an issue with webhook delays on a subset of traffic. Sending does not remain affected.
- investigating · Oct 30, 2026, 07:09 PM UTC
Status: Investigating We’re investigating an issue with webhook delays on a subset of traffic. Sending does not remain affected. Affected components API V2 (Degraded performance) API V1 (Degraded performance)
- resolved · Oct 30, 2026, 09:23 PM UTC
We believe the issue is now resolved
- resolved · Oct 30, 2026, 09:23 PM UTC
Status: Resolved We believe the issue is now resolved Affected components API V1 (Operational) API V2 (Operational)
- resolved · Oct 30, 2026, 09:23 PM UTC
Status: Resolved We believe the issue is now resolved Affected components API V2 (Operational) API V1 (Operational)
Latest: Status: Resolved We believe the issue is now resolved Affected components API V2 (Operational) API V1 (Operational)
-
- US East RegionUS Central RegionUS West RegionAPI V2API V2
Timeline · 5 updates
- investigating · Oct 29, 2026, 02:50 PM UTC
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.
- investigating · Oct 29, 2026, 02:50 PM UTC
Status: 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. Affected components API V2 (Degraded performance) US East Region (Degraded performance) US Central Region (Degraded performance) US West Region (Degraded performance)
- resolved · Oct 29, 2026, 03:15 PM UTC
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.
- resolved · Oct 29, 2026, 03:15 PM UTC
Status: 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. Affected components API V2 (Operational) US East Region (Operational) US Central Region (Operational) US West Region (Operational)
- resolved · Oct 29, 2026, 03:15 PM UTC
Status: 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. Affected components US East Region (Operational) US Central Region (Operational) US West Region (Operational) API V2 (Operational)
Latest: Status: 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 ca…
-
- USEuropeAustraliaCanadaMiddle EastUSEuropeAustraliaMiddle EastUS
Timeline · 5 updates
- monitoring · Oct 28, 2026, 09:01 PM 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.
- monitoring · Oct 28, 2026, 09:01 PM UTC
Status: 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. Affected components Europe (Degraded performance) Canada (Degraded performance) US (Degraded performance) Australia (Degraded performance) Asia (Beta) (Degraded performance) Middle East (Degraded performance)
- resolved · Oct 28, 2026, 09:02 PM UTC
A rollback was applied at ~15:54 UTC and credential creation has been healthy since 15:58 UTC.
- resolved · Oct 28, 2026, 09:02 PM UTC
Status: Resolved A rollback was applied at ~15:54 UTC and credential creation has been healthy since 15:58 UTC. Affected components Australia (Operational) Asia (Beta) (Operational) Middle East (Operational) Europe (Operational) Canada (Operational) US (Operational)
- resolved · Oct 28, 2026, 09:02 PM UTC
Status: Resolved A rollback was applied at ~15:54 UTC and credential creation has been healthy since 15:58 UTC. Affected components Asia (Beta) (Operational) Middle East (Operational) Europe (Operational) Canada (Operational) US (Operational) Australia (Operational)
Latest: Status: Resolved A rollback was applied at ~15:54 UTC and credential creation has been healthy since 15:58 UTC. Affected components Asia (Beta) (Operational) Middle East (Operation…
-
- Programmable Wireless
Timeline · 5 updates
- monitoring · Oct 28, 2026, 05:18 PM UTC
Unexpected “Is Voice” usage and charges have been corrected. We’ve tuned IMS signalling traffic and corrected incorrect VoLTE rating.
- monitoring · Oct 28, 2026, 05:18 PM UTC
Status: Monitoring Unexpected “Is Voice” usage and charges have been corrected. We’ve tuned IMS signalling traffic and corrected incorrect VoLTE rating. Affected components Programmable Wireless (Degraded performance)
- resolved · Oct 30, 2026, 12:55 AM UTC
Resolved
- resolved · Oct 30, 2026, 12:55 AM UTC
Status: Resolved Resolved Affected components Programmable Wireless (Operational)
- resolved · Oct 30, 2026, 12:55 AM UTC
Status: Resolved Resolved Affected components Programmable Wireless (Operational)
Latest: Status: Resolved Resolved Affected components Programmable Wireless (Operational)
-
- Programmable Wireless
Timeline · 7 updates
- monitoring · Oct 28, 2026, 05:14 PM UTC
We’ve expanded the NAT pool and are monitoring recovery. Metrics indicate underlying issue has been resolved.
- monitoring · Oct 28, 2026, 05:14 PM UTC
Status: Monitoring We’ve expanded the NAT pool and are monitoring recovery. Metrics indicate underlying issue has been resolved. Affected components Programmable Wireless (Degraded performance)
- monitoring · Oct 28, 2026, 07:17 PM UTC
Monitoring Recovery
- monitoring · Oct 28, 2026, 07:17 PM UTC
Status: Monitoring Monitoring Recovery Affected components Programmable Wireless (Operational)
- resolved · Oct 28, 2026, 08:09 PM UTC
NAT errors resulted in user-plane issues for some users.
- resolved · Oct 28, 2026, 08:09 PM UTC
Status: Resolved NAT errors resulted in user-plane issues for some users. Affected components Programmable Wireless (Operational)
- resolved · Oct 28, 2026, 08:09 PM UTC
Status: Resolved NAT errors resulted in user-plane issues for some users. Affected components Programmable Wireless (Operational)
Latest: Status: Resolved NAT errors resulted in user-plane issues for some users. Affected components Programmable Wireless (Operational)
-
See the full Telnyx outage history
46 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.
Browse Telnyx outage history →Or sign up free to get alerts when Telnyx breaks · 10 free monitors · No credit card
Incident record
Since April 2026 · incident.io · 116 components checked every 5 minutesThe longest incident in the last year, Ongoing incident with several services. on July 15, 2026, ran for 35 days. 270 maintenance windows announced in the same period.
Most affected components, last 12 months
- Programmable Wireless37
- Programmable Wireless9
- NORAM7
- NORAM7
- NORAM7
Latest incidents
- Messaging Webhook Delays
We’re investigating an issue with webhook delays on a subset of traffic. Sending does not remain affected.
- Delays with Messaging Webhooks, Mission Control Number and Porting ordering/configurations
Our engineers are investigating an issue causing delays to messaging webhook deliveries which began at approximately 14:20UTC. The issue may also delay Mission…
- Telephony tokens 503s error
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…
- Messaging Webhook Delays ResolvedStarted Oct 30, 2026, 07:09 PM UTC · Resolved Oct 30, 2026, 09:23 PM UTC · 2h 14m
- Started Oct 29, 2026, 02:50 PM UTC · Resolved Oct 29, 2026, 03:15 PM UTC · 24m
- Telephony tokens 503s error ResolvedStarted Oct 28, 2026, 09:01 PM UTC · Resolved Oct 28, 2026, 09:02 PM UTC · 46s
- Started Oct 28, 2026, 05:18 PM UTC · Resolved Oct 30, 2026, 12:55 AM UTC · 1d 7h
- Wireless session drops in DC2 ResolvedStarted Oct 28, 2026, 05:14 PM UTC · Resolved Oct 28, 2026, 08:09 PM UTC · 2h 55m
- MMS API Delivery Issues ResolvedStarted Oct 27, 2026, 06:28 PM UTC · Resolved Oct 27, 2026, 09:01 PM UTC · 2h 33m
- Started Oct 23, 2026, 04:07 PM UTC · Resolved Oct 23, 2026, 09:10 PM UTC · 5h 2m
- Started Oct 22, 2026, 03:43 PM UTC · Resolved Oct 23, 2026, 09:01 PM UTC · 1d 5h