Telnyx Outage History
Telnyx is up right nowPingoru has recorded 161 incidents for Telnyx: 161 in the last 12 months and 47 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 16 | 396 of 720 (55%) |
| May 2026 | 29 | 526 of 744 (71%) |
| June 2026 | 15 | 719 of 720 (100%) |
| July 2026 | 16 | 591 of 744 (79%) |
| August 2026 | 13 | 581 of 744 (78%) |
| September 2026 | 19 | 311 of 720 (43%) |
| October 2026 | 13 | 105 of 591 (18%) |
Incidents, newest first
Minor September 9, 2026 Failed/delayed call recording deliveries, faxes and conference establishment 1d 1h
Started Sep 09, 2026, 02:53 PM UTC· resolved Sep 10, 2026, 03:59 PM UTC
- investigating Sep 09, 2026, 02:53 PM UTC
Our engineering teams are currently investigating an issue contributing to failed/delayed call recording deliveries. Impact was also observed with faxing and conference establishment, beginning around 14:00UTC.
- monitoring Sep 09, 2026, 03:54 PM UTC
This issue has been mitigated at this time and is being monitored by our team.
- resolved Sep 10, 2026, 03:59 PM UTC
This issue is marked as resolved
Major September 8, 2026 Edge Compute StatefulActor Deploys Partial Outage 25m
Started Sep 08, 2026, 09:29 PM UTC· resolved Sep 08, 2026, 09:54 PM UTC
- investigating Sep 08, 2026, 09:29 PM UTC
Edge Compute StatefulActor deployments are currently unavailable. We are actively investigating the issue.
- identified Sep 08, 2026, 09:33 PM UTC
We have identified the root cause and are actively working on remediation.
- monitoring Sep 08, 2026, 09:41 PM UTC
We have implemented a fix and are monitoring the recovery process.
- resolved Sep 08, 2026, 09:54 PM UTC
Edge Compute StatefulActor ship runtime is now operational.
Minor September 2, 2026 Intermittent delays for some outbound messages 8d 18h
Started Sep 02, 2026, 09:33 PM UTC· resolved Sep 11, 2026, 04:08 PM UTC
- identified Sep 02, 2026, 09:33 PM UTC
Some outbound messages may experience delivery delays. We are investigating and will update as we learn more.
- monitoring Sep 03, 2026, 01:58 PM UTC
We have applied a fix and are seeing significant improvement in delivery delays for outbound messages. We are monitoring to confirm the issue is fully resolved.
- resolved Sep 11, 2026, 04:08 PM UTC
This is resolved
Minor September 1, 2026 GLM-5.3 Degradation 2h 7m
Started Sep 01, 2026, 04:41 PM UTC· resolved Sep 01, 2026, 06:49 PM UTC
- investigating Sep 01, 2026, 04:41 PM UTC
We are investigation degradation for GLM-5.3 inference
- monitoring Sep 01, 2026, 05:49 PM UTC
We are monitoring GLM-5.3 performance
- resolved Sep 01, 2026, 06:49 PM UTC
This is resolved
Major September 1, 2026 Cloud Storage Partially Unavailable in All Regions 1h 2m
Started Sep 01, 2026, 06:04 AM UTC· resolved Sep 01, 2026, 07:06 AM UTC
- investigating Sep 01, 2026, 06:04 AM UTC
Telnyx object storage read and write operations are intermittently unavailable. We are currently investigating the issue.
- identified Sep 01, 2026, 07:02 AM UTC
We have identified the root cause and are working on remediation.
- resolved Sep 01, 2026, 07:06 AM UTC
The incident has been resolved, the systems recovering.
Minor August 27, 2026 Telnyx Ultra voices not available, affecting Assistant creation and update 25m
Started Aug 27, 2026, 01:25 PM UTC· resolved Aug 27, 2026, 01:51 PM UTC
- investigating Aug 27, 2026, 01:25 PM UTC
We are investigating issues with Telnyx Ultra voices not returning from the voices endpoint. This is preventing customers from saving AI Assistants with a Telnyx Ultra voice.
- identified Aug 27, 2026, 01:30 PM UTC
We have identified the issue and are working on a fix
- monitoring Aug 27, 2026, 01:45 PM UTC
The fix has been deployed and we are monitoring
- resolved Aug 27, 2026, 01:51 PM UTC
This is resolved
Notice August 24, 2026 Outbound Canadian PSTN calls issues 1d
Started Aug 24, 2026, 08:07 PM UTC· resolved Aug 25, 2026, 08:30 PM UTC
- investigating Aug 24, 2026, 08:07 PM UTC
We are investigating the issue at the moment. Updates to follow.
- resolved Aug 25, 2026, 08:30 PM UTC
The issue has been resolved.
Critical August 24, 2026 Telnyx Cloud Storage Outage Across All Regions 31m
Started Aug 24, 2026, 02:05 AM UTC· resolved Aug 24, 2026, 02:37 AM UTC
- identified Aug 24, 2026, 02:05 AM UTC
We have identified the root cause and are actively working on remediation. Telnyx storage read and write operations are unavailable across all regions.
- resolved Aug 24, 2026, 02:37 AM UTC
The incident has been resolved and all cloud storage services are operational.
Major August 19, 2026 AI Assistants with Data Locality Australia Failing 51m
Started Aug 19, 2026, 02:28 PM UTC· resolved Aug 19, 2026, 03:19 PM UTC
- investigating Aug 19, 2026, 02:28 PM UTC
Investigating issues with Australian AI Assistants
- identified Aug 19, 2026, 02:53 PM UTC
We have identified the root cause and are working on a fix
- resolved Aug 19, 2026, 03:19 PM UTC
This incident has been resolved
Minor August 17, 2026 Programmable Wireless data loss in Australia 9d 18h
Started Aug 17, 2026, 07:27 PM UTC· resolved Aug 27, 2026, 01:53 PM UTC
- monitoring Aug 17, 2026, 07:27 PM UTC
We experienced SIM data loss in Australia, issue was mitigated, we're monitoring situation.
- resolved Aug 27, 2026, 01:53 PM UTC
Issue was resolved
Major August 15, 2026 Network connectivity issues in Frankfurt 16d 9h
Started Aug 15, 2026, 03:58 AM UTC· resolved Aug 31, 2026, 01:30 PM UTC
- identified Aug 15, 2026, 03:58 AM UTC
Network connectivity issues caused by underlying vendor
- identified Aug 15, 2026, 08:47 AM UTC
Vendor is actively working to restore connectivity. Programmable Wireless services are affected in all supported regions.
- monitoring Aug 19, 2026, 03:58 PM UTC
A workaorund was implemented to bypass the impacted AWS service. This enabled data sessions to be re-established. A maintenance window is schedule on Friday morning UTC to move the connectivity back from the workaround solution to the AWS Direct Connects.
- resolved Aug 31, 2026, 01:30 PM UTC
Closing
Minor August 13, 2026 Wireless session drops 6d 6h
Started Aug 13, 2026, 09:13 AM UTC· resolved Aug 19, 2026, 03:14 PM UTC
- investigating Aug 13, 2026, 09:13 AM UTC
We're noticing session drop for Wireless Product. Team is investigating issue currently.
- investigating Aug 13, 2026, 10:42 AM UTC
The impact has been isolated to the Australian site.
- identified Aug 13, 2026, 02:20 PM UTC
Issue was identified
- monitoring Aug 13, 2026, 02:48 PM UTC
Mitigation fix was applied. We're monitoring situation closely.
- resolved Aug 19, 2026, 03:14 PM UTC
Issue was resolved
Major August 11, 2026 Local calls to a Few European countries are failing with SIP 503 Service Unavailable 6h 13m
Started Aug 11, 2026, 08:52 AM UTC· resolved Aug 11, 2026, 03:05 PM UTC
- investigating Aug 11, 2026, 08:52 AM UTC
We are currently investigating an increase in calls failing with SIP 503 Service Unavailable errors affecting local outbound call termination to European destinations. Customers may experience Local call failures when attempting to reach European destinations Sweden, Denmark etc. Our telephony team is actively working on a resolution.
- monitoring Aug 11, 2026, 10:04 AM UTC
Our telephony team has implemented a fix and we are actively monitoring traffic.
- resolved Aug 11, 2026, 03:05 PM UTC
This issue was mititaged as of `Tue Aug 11 09:44:44 UTC 2026`
Notice August 10, 2026 Deepgram Flux High Latency 42m
Started Aug 10, 2026, 03:47 PM UTC· resolved Aug 10, 2026, 04:29 PM UTC
- investigating Aug 10, 2026, 03:47 PM UTC
We are investigating high latency for deepgram flux transcription affecting voice api and voice ai assistants.
- monitoring Aug 10, 2026, 04:01 PM UTC
We have mitigated the issue and are monitoring
- resolved Aug 10, 2026, 04:29 PM UTC
This is resolved
Major August 7, 2026 Calls experiencing one-way/dead air audio, call drops and missing call recordings 3d 6h
Started Aug 07, 2026, 03:02 PM UTC· resolved Aug 10, 2026, 09:19 PM UTC
- investigating Aug 07, 2026, 03:02 PM UTC
Our engineering team is currently investigating reports of issues affecting calls with the following symptoms: - Dead/One way audio transmission - Premature Call Drops - Missing/Delayed Call Recordings We will continue to update our status page with the latest findings.
- identified Aug 07, 2026, 03:36 PM UTC
Root Cause was identified and mitigated.
- monitoring Aug 07, 2026, 03:39 PM UTC
We continue to monitor following the earlier mitigation. Services remain stable and no new reports of impact have been received. A final update will follow once resolution is confirmed.
- resolved Aug 10, 2026, 09:19 PM UTC
This incident has been resolved now.
Minor August 7, 2026 Outbound Calls routed through Amsterdam and Frankfurt receiving error code TM1 50m
Started Aug 07, 2026, 01:05 PM UTC· resolved Aug 07, 2026, 01:55 PM UTC
- monitoring Aug 07, 2026, 01:05 PM UTC
Some outbound calls in Amsterdam and Frankfurt anchorsites began failing with error code TM1 between 9.15 - 12.50 UTC today. Errors have currently ceased and our engineering team is monitoring status at this time.
- resolved Aug 07, 2026, 01:55 PM UTC
This issue is now confirmed resolved as of 13.25 UTC by our engineering team. We continue to monitor traffic signs.
Minor August 5, 2026 Elevated API errors and missing cost data 18h 34m
Started Aug 05, 2026, 08:55 PM UTC· resolved Aug 06, 2026, 03:30 PM UTC
- identified Aug 05, 2026, 08:55 PM UTC
We are experiencing elevated error rates affecting a small percentage of Messaging API requests. Affected requests may return a 503 or 504 error and can be safely retried. Separately, cost data may be missing or incomplete on some records. This affects the cost field on inbound message webhooks, and call cost for Programmable Voice and TeXML. Message delivery is not affected. We have identified the cause as a degraded internal dependency and are working on a resolution. We will provide an update within 30 minutes.
- identified Aug 05, 2026, 09:39 PM UTC
Error rates remain elevated and intermittent, with periods of improvement followed by renewed impact. A percentage of Messaging API requests may return 503 or 504 errors and can be safely retried. Cost data may still be missing on some records. Message delivery remains unaffected. We have identified the cause and work on a resolution is ongoing. We will update this page as the situation develops.
- identified Aug 06, 2026, 02:21 AM UTC
Inbound Messaging APIs have returned to normal operation. The remaining impact is on retrieving message records. A percentage of GET /v2/messages/{id} requests may return a 503 or 504 error and can be safely retried. Sending messages, message delivery, and delivery webhooks are unaffected. Cost data may be missing on some records created earlier during this incident. Work on a resolution is ongoing.
- monitoring Aug 06, 2026, 01:41 PM UTC
Error rates have returned to normal and message retrieval is operating as expected. Some recently created message records may still take longer than usual to appear while a processing backlog clears. We are monitoring to confirm the fix holds.
- monitoring Aug 06, 2026, 02:03 PM UTC
All services are operating normally. Some message records created earlier during this incident may still take longer than usual to appear while a processing backlog clears. We are monitoring to confirm.
- resolved Aug 06, 2026, 03:30 PM UTC
This incident has been resolved. All services are operating normally
Critical August 4, 2026 SDK Client Credential API Failure 1d 16h
Started Aug 04, 2026, 05:19 PM UTC· resolved Aug 06, 2026, 09:29 AM UTC
- investigating Aug 04, 2026, 05:19 PM UTC
customers may receive HTTP 503 responses from the Client Credential API, which can prevent telephony token creation or validation. This may cause Voice SDK authentication failures, failed registrations, and new call setup failures. Existing active calls are likely unaffected unless they require a fresh token/API call.
- monitoring Aug 04, 2026, 07:00 PM UTC
We identified a capacity issue in the backend service that manages telephony tokens and client SDK credentials. This caused intermittent failures for some credential-related API requests. We increased the number of service pods and raised CPU and memory allocation to better handle request volume. Since making these changes, we are no longer seeing the related 503 errors at the API gateway. The service is currently stable, and we will continue monitoring closely while the incident remains in the monitoring phase.
- resolved Aug 06, 2026, 09:29 AM UTC
We identified and mitigated a capacity issue in the backend service that manages telephony tokens and client SDK credentials. This caused intermittent HTTP 503 responses for some credential-related API requests. After increasing service capacity and resource allocation, the service remained stable throughout the monitoring period. We will continue reviewing capacity settings to help prevent recurrence.
Minor July 28, 2026 503s on endpoints related to accounts, number config, and sip config 1h 31m
Started Jul 28, 2026, 07:32 PM UTC· resolved Jul 28, 2026, 09:04 PM UTC
- investigating Jul 28, 2026, 07:32 PM UTC
503s on endpoints related to accounts, number config, and sip config
- monitoring Jul 28, 2026, 07:55 PM UTC
Issue identified and patched. Monitoring
- resolved Jul 28, 2026, 09:04 PM UTC
After monitoring of the initial fixes implemented to resolve the issue, we have not seen any recurrences of the problem. We are marking this as resolved but will continue to monitor.
Minor July 27, 2026 Service Degradation in Australia 2d 16h
Started Jul 27, 2026, 03:08 PM UTC· resolved Jul 30, 2026, 08:06 AM UTC
- investigating Jul 27, 2026, 03:08 PM UTC
We are currently investigating an issue affecting services in the Australia region. Customers may experience intermittent connectivity issues, increased latency, or failed requests when accessing some Telnyx services.
- identified Jul 27, 2026, 03:15 PM UTC
Our engineering teams have identified the underlying infrastructure issue and are actively working to restore full service. We are monitoring the situation closely and will continue to provide updates as more information becomes available. We apologise for the disruption and appreciate your patience while we work to resolve the issue.
- monitoring Jul 28, 2026, 09:22 AM UTC
Our engineering teams have restored the underlying infrastructure issue as of 22:00 UTC on 27th July 2026. They continue to monitor the environment to confirm that connectivity and service performance remain stable. Customers should begin seeing recovery across affected services in the Australia region.
- resolved Jul 30, 2026, 08:06 AM UTC
Following a period of monitoring, connectivity and service performance have remained stable. Customers should no longer experience issues across affected services in the Australia region. We apologise for the disruption and appreciate your patience.
Minor July 24, 2026 eSIM purchases failing 3h 49m
Started Jul 24, 2026, 10:46 AM UTC· resolved Jul 24, 2026, 02:36 PM UTC
- identified Jul 24, 2026, 10:46 AM UTC
eSIM purchases are failing currently, we have identified the cause and are working on the resolution
- monitoring Jul 24, 2026, 02:13 PM UTC
Pools restocked
- resolved Jul 24, 2026, 02:36 PM UTC
Stock replenished to healthy levels.
Minor July 22, 2026 Investigating T-Mobile MMS Delivery Report Issues 17h 16m
Started Jul 22, 2026, 10:15 PM UTC· resolved Jul 23, 2026, 03:31 PM UTC
- investigating Jul 22, 2026, 10:15 PM UTC
We are currently investigating an issue affecting MMS message delivery to T-Mobile, where some messages are resulting in a `delivery_unconfirmed` status. The issue has been escalated to our downstream partner for further investigation, and we are currently awaiting additional updates. We will provide more information as it becomes available.
- resolved Jul 23, 2026, 03:31 PM UTC
The issue affecting MMS delivery reports to T-Mobile has been resolved. MMS delivery reports are now processing as expected.
Minor July 20, 2026 Intermittent loss of mobile data on some SIMs after a period of inactivity 13d 22h
Started Jul 20, 2026, 11:25 PM UTC· resolved Aug 03, 2026, 10:13 PM UTC
- investigating Jul 20, 2026, 11:25 PM UTC
We are aware that some SIMs can stop passing data after a period of inactivity, even though the device still shows full signal and a mobile connection. When this happens, data does not resume on its own. _Workaround:_ the connection is restored as soon as the device re-registers with the network. • On phones, tablets and other devices with a user interface, toggling Airplane Mode off and on does this immediately. • On IoT and embedded devices without that option, power-cycling the device or restarting the modem has the same effect. Devices that send or receive data regularly are much less likely to be affected. We have identified the area responsible and are working with our vendor on a fix. We will post further updates as we make progress
- monitoring Aug 01, 2026, 07:49 AM UTC
Corrective measures have been taken to address these issues globally. We are currently monitoring stability over the next 72 hours to ensure no further recurrence.
- resolved Aug 03, 2026, 10:13 PM UTC
This issue was resolved on Friday, July 31, at approximately 3:00 PM CST.
Major July 17, 2026 Data Connectivity Issues - Europe 3h 56m
Started Jul 17, 2026, 09:11 PM UTC· resolved Jul 18, 2026, 01:07 AM UTC
- investigating Jul 17, 2026, 09:11 PM UTC
Data Connectivity Issues - Europe
- monitoring Jul 17, 2026, 10:23 PM UTC
A change was made in the network and connectivity has been restored.
- resolved Jul 18, 2026, 01:07 AM UTC
Issue is resolved
Minor July 16, 2026 Billing records processing lag 34d 2h
Started Jul 16, 2026, 12:23 PM UTC· resolved Aug 19, 2026, 03:06 PM UTC
- monitoring Jul 16, 2026, 12:23 PM UTC
There is a delay in processing of billing records.
- resolved Aug 19, 2026, 03:06 PM UTC
Billing records are being processed normally