Looking for an update now? Check the current status, or follow Telnyx for future changes.
25.6%of 43 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
September 2026
23.1%
26
20
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Jul 23Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
Incident History
No source-attested incident records are available for the current collector history. Older legacy archive records remain available below.
Legacy Incident Archive
89 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
August 2026
Telnyx Cloud Storage Outage Across All Regions
criticalSource not attested
Last archived state: resolved
View archived record details
identified
We have identified the root cause and are actively working on remediation. Telnyx storage read and write operations are unavailable across all regions.
AI Assistants with Data Locality Australia Failing
majorSource not attested
Last archived state: resolved
View archived record details
identified
We have identified the root cause and are working on a fix
investigating
Investigating issues with Australian AI Assistants
Wireless session drops
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Mitigation fix was applied. We're monitoring situation closely.
identified
Issue was identified
investigating
The impact has been isolated to the Australian site.
investigating
We're noticing session drop for Wireless Product. Team is investigating issue currently.
Local calls to a Few European countries are failing with SIP 503 Service Unavailable
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
Our telephony team has implemented a fix and we are actively monitoring traffic.
investigating
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.
Deepgram Flux High Latency
Source not attested
Last archived state: resolved
View archived record details
monitoring
We have mitigated the issue and are monitoring
investigating
We are investigating high latency for deepgram flux transcription affecting voice api and voice ai assistants.
Calls experiencing one-way/dead air audio, call drops and missing call recordings
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
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.
identified
Our engineering team has identified the root cause of this issue and applied a mitigation. Call audio, call stability, and call recordings should now be operating normally.
investigating
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.
Outbound Calls routed through Amsterdam and Frankfurt receiving error code TM1
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
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.
Elevated API errors and missing cost data
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
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.
monitoring
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.
identified
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.
identified
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
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 upd...
SDK Client Credential API Failure
criticalSource not attested
Last archived state: resolved
View archived record details
monitoring
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...
investigating
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.
July 2026
503s on endpoints related to accounts, number config, and sip config
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Issue identified and patched. Monitoring
investigating
503s on endpoints related to accounts, number config, and sip config
