Poland - Long Code SMS Failures
Affected: EMEA
Timeline · 2 updates
- investigating Apr 15, 2026, 10:10 PM UTC
We are currently investigating this issue.
- resolved Apr 16, 2026, 02:38 PM UTC
This incident has been resolved.
Telnyx Outage History
Telnyx is up right nowTelnyx had 52 outages in the last 2 years totaling 793h 58m of downtime — averaging 2.1 incidents per month.
There were 52 Telnyx outages since February 22, 2026 totaling 793h 58m of downtime. Each is summarised below — incident details, duration, and resolution information.
Verify API Timeouts
Affected: API V2
Timeline · 1 update
- resolved Apr 15, 2026, 05:53 PM UTC
We identified and fixed an issue with our verify API endpoint.
Telnyx Cloud Storage Central Region degradation
Affected: Telnyx Storage
Timeline · 2 updates
- investigating Apr 13, 2026, 09:10 PM UTC
We are currently investigating this issue.
- resolved Apr 14, 2026, 10:05 PM UTC
This incident has been resolved.
AI Assistants with Nova3 STT not functioning if Numerals or Smart Format is null
Timeline · 3 updates
- investigating Apr 11, 2026, 02:14 PM UTC
We are currently investigating this issue.
- identified Apr 11, 2026, 03:22 PM UTC
The issue has been identified and a fix is being implemented.
- resolved Apr 11, 2026, 03:56 PM UTC
This incident has been resolved.
rtc.telnyx.com certificate expired
Timeline · 2 updates
- investigating Apr 05, 2026, 12:06 AM UTC
We are currently investigating this issue.
- resolved Apr 11, 2026, 04:17 PM UTC
This incident has been resolved.
Delayed Availability of Wireless Usage Reports (WDR)
Affected: Programmable Wireless
Timeline · 2 updates
- investigating Apr 04, 2026, 04:01 PM UTC
We are currently investigating this issue.
- resolved Apr 11, 2026, 04:16 PM UTC
This incident has been resolved.
Wireless Product API Instability
Affected: Programmable WirelessAPI Gateway
Timeline · 3 updates
- investigating Apr 03, 2026, 09:03 AM UTC
We are aware of instability affecting our Wireless Products API endpoints. The incident began at approximately 08:25 UTC. Our engineering team is actively investigating the root cause. Further updates will be provided as information becomes available.
- monitoring Apr 03, 2026, 09:45 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Apr 03, 2026, 10:39 AM UTC
This incident has been resolved.
AI Assistants - Page Not Loading
Affected: Mission Control Portal UI
Timeline · 3 updates
- investigating Mar 30, 2026, 09:19 AM UTC
We are currently investigating this issue.
- monitoring Mar 30, 2026, 09:50 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Mar 30, 2026, 11:59 AM UTC
Issues with accessing AI Assistants via EU and AU origins has now been resolved. US region customers were unaffected
Unplanned Maintenance - Mobile Data Services (US Region)
Affected: Programmable Wireless
Timeline · 2 updates
- investigating Mar 30, 2026, 04:59 AM UTC
We are performing unplanned maintenance on mobile packet core infrastructure in the US region. This maintenance is expected to last approximately 10 minutes. A small subset of mobile data customers may experience brief session interruptions during this window. Active data connections will be re-established automatically in most cases. Affected users may need to toggle airplane mode on for 10 seconds and then off to restore connectivity. We will provide an update once the maintenance is complete.
- resolved Mar 30, 2026, 04:59 AM UTC
Duplicate incident - please disregard.
Degraded Wireless Data Sessions - IMSI 1 - Ashburn
Affected: Programmable Wireless
Timeline · 2 updates
- investigating Mar 21, 2026, 07:38 AM UTC
We are investigating degraded wireless data sessions for IMSI 1 subscribers roaming through our Ashburn site. Affected subscribers may experience failed session establishment or intermittent data connectivity. Our team is actively investigating the root cause and will provide updates as more information becomes available.
- resolved Mar 21, 2026, 09:15 AM UTC
Root cause identified: No actual PGW session failure. During the Sydney Sparkle outage at ~19:00 UTC, Australian devices were temporarily routed through Ashburn LBO proxies. Once Sydney recovered, these sessions became stale. The proxy session drop 12 hours later was automatic TTL cleanup of these orphaned sessions. No action required.
Degraded Wireless Data Sessions - IMSI 1 - Sydney
Affected: Programmable Wireless
Timeline · 2 updates
- identified Mar 20, 2026, 09:27 PM UTC
We are experiencing degraded wireless data sessions for IMSI 1 subscribers roaming through our Sydney site. Affected subscribers may experience intermittent data connectivity or session drops. The root cause has been identified as GTP echo timeouts from an upstream roaming partner, causing automatic session resets. Sessions are gradually rebuilding as devices re-attach. Our team is actively monitoring recovery and has engaged the upstream partner for investigation.
- resolved Mar 20, 2026, 10:38 PM UTC
The upstream roaming partner has confirmed the root cause was a service impact on their outbound roaming solution starting at approximately 22:10 UTC. The issue has been identified and partial recovery was observed from 21:59 UTC. GTP echo timeouts have stopped since 19:19 UTC and data sessions have recovered to approximately 88% of baseline levels. The remaining sessions are expected to fully recover as devices re-attach over the next steering cycle. No further action required on our side. We will continue to monitor.
Usage Reports down
Affected: Usage Reports
Timeline · 4 updates
- investigating Mar 19, 2026, 03:53 PM UTC
We are currently investigating this issue.
- investigating Mar 19, 2026, 03:55 PM UTC
We are currently investigating this issue.
- monitoring Mar 19, 2026, 04:00 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Mar 19, 2026, 04:10 PM UTC
This incident has been resolved.
Wireless SIM Provisioning Delays
Affected: Programmable Wireless
Timeline · 3 updates
- investigating Mar 19, 2026, 02:01 PM UTC
We are currently investigating intermittent failures affecting eSIM purchases and SIM card network registration. Existing active SIM cards and data sessions are not affected — this issue only impacts new provisioning operations. Our engineering team is actively investigating the root cause and working toward resolution. We will provide updates as more information becomes available.
- monitoring Mar 19, 2026, 03:25 PM UTC
A fix has been implemented and we are monitoring the results. eSIM purchases and SIM card network registration should be recovering. We will continue to monitor and confirm full resolution.
- resolved Mar 24, 2026, 01:29 PM UTC
This incident has been resolved.
Wireless Roaming - Diameter Connectivity Degradation
Affected: Programmable Wireless
Timeline · 6 updates
- investigating Mar 15, 2026, 02:00 PM UTC
We are currently investigating this issue.
- investigating Mar 15, 2026, 02:09 PM UTC
We are currently investigating this issue. European roaming services are fully impacted, affecting IMSI1, IMSI2, and IMSI3 subscribers. IMSI5 in the US is experiencing intermittent failures.
- investigating Mar 15, 2026, 02:10 PM UTC
We are currently investigating this issue. Roaming services are fully impacted across Europe, Canada, Latin America, and Asia, affecting IMSI1, IMSI2, and IMSI3 subscribers. IMSI5 retains partial service in the US only.
- identified Mar 15, 2026, 03:14 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Mar 15, 2026, 03:22 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Mar 15, 2026, 03:42 PM UTC
This incident has been resolved.
Intermittent Connectivity Issues Affecting Wireless Services
Timeline · 3 updates
- investigating Mar 14, 2026, 10:54 AM UTC
We are currently investigating this issue.
- monitoring Mar 14, 2026, 12:01 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Mar 14, 2026, 12:52 PM UTC
This incident has been resolved.
zai-org/GLM-5 model unavailable
Affected: US East RegionUS Central RegionUS West Region
Timeline · 3 updates
- investigating Mar 12, 2026, 10:36 AM UTC
Starting around 08:50 UTC, the zai-org/GLM-5 model became unavailable for inference requests. Our team is investigating an issue with the underlying cluster. Customers can use Kimi K2.5 as an alternative in the meantime.
- monitoring Mar 12, 2026, 01:46 PM UTC
A fix has been implemented and we are monitoring the results to make sure all is working as expected
- resolved Mar 12, 2026, 10:45 PM UTC
This incident has been resolved.
Wireless API instability
Timeline · 2 updates
- investigating Mar 11, 2026, 02:22 PM UTC
We are currently investigating this issue.
- resolved Mar 11, 2026, 07:01 PM UTC
This incident has been resolved.
Intermittent issues affecting Wireless eSIMs management
Affected: Programmable Wireless
Timeline · 3 updates
- investigating Mar 10, 2026, 11:13 AM UTC
We are currently investigating this issue. Delete eSIM and purchase eSIM functionalities are affected.
- identified Mar 10, 2026, 05:05 PM UTC
The issue has been identified and a fix is being implemented.
- resolved Mar 10, 2026, 05:28 PM UTC
This incident has been resolved.
RCS Delivery Issues
Affected: API V2
Timeline · 5 updates
- investigating Mar 05, 2026, 10:55 PM UTC
We are currently investigating an issue with delivery for a subset of RCS agents. Messages are accepted downstream but are not being delivered. Inbound remains unaffected.
- investigating Mar 05, 2026, 11:19 PM UTC
We are currently investigating an issue with delivery for a subset of RCS agents. - Outbound messages are accepted downstream but are not being delivered. - Inbound messages are also not reaching us.
- identified Mar 06, 2026, 01:16 AM UTC
The issue has been identified and a fix is being implemented.
- monitoring Mar 06, 2026, 02:34 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Mar 06, 2026, 02:36 AM UTC
This incident has been resolved.
me-central-1 (Dubai) region impaired
Timeline · 2 updates
- investigating Mar 02, 2026, 11:50 AM UTC
We are currently investigating this issue.
- resolved Mar 11, 2026, 06:59 PM UTC
This incident has been resolved.
Outage for Port In Orders
Timeline · 3 updates
- investigating Feb 27, 2026, 03:09 PM UTC
We are currently investigating this issue.
- monitoring Feb 27, 2026, 04:42 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Feb 27, 2026, 05:54 PM UTC
This incident has been resolved.
10DLC Messaging - Elevated rate of 40011's
Affected: NORAM
Timeline · 3 updates
- investigating Feb 24, 2026, 06:58 PM UTC
We are currently investigating this issue with an elected rate of API rejections (40011) when sending outbound 10DLC messages.
- monitoring Feb 24, 2026, 07:33 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Feb 24, 2026, 08:06 PM UTC
This incident has been resolved.
Telnyx API Availability Issues
Affected: API V2
Timeline · 8 updates
- investigating Feb 23, 2026, 03:38 PM UTC
We are currently investigating this issue with latency over our API when sending outbound messages. We're also investigating failures with MMS sending.
- monitoring Feb 23, 2026, 03:46 PM UTC
A fix has been implemented and we are monitoring the results.
- investigating Feb 23, 2026, 03:53 PM UTC
We are currently investigating this issue.
- investigating Feb 23, 2026, 03:57 PM UTC
We are currently investigating this issue.
- identified Feb 23, 2026, 04:04 PM UTC
We have identified a networking issue impacting traffic reaching the Telnyx API gateways. The root cause has been identified, and a fix is currently being implemented. Traffic to api.telnyx.com is showing signs of recovery and resolution. We are actively working to restore full functionality across all other impacted sites.
- identified Feb 23, 2026, 04:07 PM UTC
We believe api.telnyx.eu should be reachable now.
- monitoring Feb 23, 2026, 04:10 PM UTC
We believe all sites should be reachable now. We will continue to monitor the results.
- resolved Feb 24, 2026, 03:45 AM UTC
This incident has been resolved.
Audio Degredation causing choppy/one-way audio
Timeline · 3 updates
- investigating Feb 23, 2026, 02:40 PM UTC
Our engineering team are actively investigating this issue.
- monitoring Feb 23, 2026, 04:09 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Feb 24, 2026, 03:53 AM UTC
This incident has been resolved.