All Systems Operational

About This Site

This page is dedicated to keeping you informed on status updates from Telnyx.

SIP Trunking Signaling Regions ? Operational
US ? Operational
Europe ? Operational
Australia ? Operational
Canada ? Operational
SIP Trunking Media Anchorsites ? Operational
Chicago, IL Operational
Ashburn, VA Operational
San Jose, CA Operational
Vancouver, Canada Operational
London, UK Operational
Amsterdam, Netherlands Operational
Sydney, Australia Operational
Frankfurt, Germany Operational
Toronto, Canada Operational
Miami, FL Operational
Other Telephony Systems Operational
Messaging Operational
Voice API Operational
Numbering Operational
Number Searching Operational
Number Ordering Operational
Mission Control API ? Operational
East Region Operational
Central Region Operational
West Region Operational
CNAM API Operational
Central Region ? Operational
West Region Operational
LRN Lookup API ? Operational
East Region Operational
Central Region Operational
Switch Data API Operational
East Region ? Operational
Central Region Operational
Intercom Web Application Operational
TeXML Operational
TeXML Operational
Wireless Core Operational
Programmable Fax Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Scheduled Maintenance
Our Telephony Engineers will be performing maintenance on our SIP proxy servers in the Canada region. This maintenance will not disrupt service, but you may notice re-registration of your devices during the maintenance, as our primary and secondary SIP IP addresses are moved between hosts.

Note that our TLS certificate for our SIP proxy server sip.telnyx.ca (192.76.120.31) will be changed during this deployment. This is important for some customers who use an SBC (or other appliance) and have our certificate loaded into the SBC. Note that the same certificate chain is being used with the new certificate, so this should affect only those customers who load our server certificate rather than the CA certificate into the SBC.

This information also applies to some customers who use TLS with desk phones (poly phones, for example) and who have our server certificate loaded into the phones.

The new certificate will have serial number ba:78:29:90:4b:40:ac:9a:a0:8e:02:3e:8a:76:f2:6b. It's available for download from this (non-Telnyx) website https://crt.sh/?d=7343773976 (it does not include the intermediate certificate, which should not be a problem).

Note, too, that the new certificate has a private key with a size of 4096 bits, whereas the current in-use certificate key has a size of 2048 bits. We don’t expect that customers' clients or servers should have a problem with this. If in doubt, please check the documentation of your phone/appliance.

Posted on Aug 17, 17:16 UTC
Our Telephony Engineers will be performing maintenance on our SIP proxy servers in the Australia region. This maintenance will not disrupt service, but you may notice re-registration of your devices during the maintenance, as our primary and secondary SIP IP addresses are moved between hosts.

Note that our TLS certificate for our SIP proxy server sip.telnyx.com.au (103.115.244.145) will be changed during this deployment. This is important for some customers who use an SBC (or other appliance) and have our certificate loaded into the SBC. Note that the same certificate chain is being used with the new certificate, so this should affect only those customers who load our server certificate rather than the CA certificate into the SBC.

This information also applies to some customers who use TLS with desk phones (poly phones, for example) and who have our server certificate loaded into the phones.

The new certificate will have serial number ec:70:68:1f:00:f3:62:b0:c7:36:5f:2c:f5:c2:89:b1. It's available for download from this (non-Telnyx) website https://crt.sh/?d=7343600922 (it does not include the intermediate certificate, which should not be a problem).

Note, too, that the new certificate has a private key with a size of 4096 bits, whereas the current in-use certificate key has a size of 2048 bits. We don’t expect that customers' clients or servers should have a problem with this. If in doubt, please check the documentation of your phone/appliance.

Posted on Aug 17, 17:34 UTC
Mission Control Portal API Response Time ?
Fetching
CNAM API Response Times
Fetching
Switch Data API Response Times
Fetching
LRN Lookup API Response Times
Fetching
V2: Number Lookup API Response Time
Fetching
Past Incidents
Aug 18, 2022
Resolved - This incident had been resolved.

A change in forwarding dial plan caused this issue. The change had been rolled back to resolve this.

Aug 18, 03:40 UTC
Update - We are continuing to monitor for any further issues.
Aug 18, 03:38 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Aug 18, 03:37 UTC
Identified - The issue has been identified and a fix is being implemented.
Aug 18, 03:37 UTC
Investigating - We are currently investigating this issue.
Aug 18, 02:36 UTC
Aug 17, 2022
Resolved - This incident has been resolved.
Aug 17, 22:24 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Aug 17, 17:07 UTC
Identified - The issue has been identified and a fix is being implemented.
Aug 17, 15:42 UTC
Investigating - We are currently investigating this issue.
Aug 17, 14:51 UTC
Aug 16, 2022
Resolved - This incident has been resolved.
Aug 16, 22:09 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Aug 16, 21:59 UTC
Identified - Portal changes might take more time than usual on being applied.
Aug 16, 20:52 UTC
Completed - The scheduled maintenance has been completed.
Aug 16, 22:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Aug 16, 20:00 UTC
Scheduled - One of our roaming partners will be performing maintenance on a critical system.
This maintenance will not disrupt service, but you may notice re-registration of your devices during the maintenance.

Aug 16, 16:27 UTC
Resolved - This incident has been resolved.
Aug 16, 17:23 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Aug 16, 12:24 UTC
Identified - The issue has been identified and a fix is being implemented. Customers may see some 5XX error codes on API V1 endpoints.
Aug 16, 11:51 UTC
Investigating - We are currently investigating this issue.
Aug 16, 11:45 UTC
Resolved - This incident has been resolved.
Aug 16, 03:03 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Aug 16, 00:58 UTC
Identified - The issue has been identified and a fix is being implemented.
Aug 16, 00:56 UTC
Investigating - We have noticed instability in answering machine detection since 19:40 UTC. We are currently investigating.
Aug 16, 00:08 UTC
Aug 15, 2022
Resolved - This incident has now been resolved and full service restored.
Aug 15, 22:44 UTC
Monitoring - The issue has been resolved. We are currently monitoring to ensure no further impact.
Aug 15, 21:17 UTC
Identified - Our partner has identified the issue and is taking immediate corrective measures. We will provide further updates as they become available.
Aug 15, 20:00 UTC
Investigating - We have been informed of an ongoing incident with one of our connectivity partners that is impacting some wireless users in that they are unable to establish a data session. We are working with them to resolve this as quickly as possible.
Aug 15, 19:10 UTC
Aug 14, 2022

No incidents reported.

Aug 13, 2022

No incidents reported.

Aug 12, 2022
Resolved - This incident has been resolved.
Aug 12, 14:20 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Aug 11, 22:29 UTC
Identified - The issue has been identified and a fix is being implemented.
Aug 11, 16:45 UTC
Investigating - We have received an increase in reports of customers noting the error: "403 Connection has no Outbound Profile assigned D38" when attempting to make outbound calls using our SIP Trunking service - even though outbound voice profiles are assigned to SIP Connections.

So far it's believed to only be an issue when new outbound voice profiles are created. Existing outbound voice profiles do not exhibit this behaviour.

The issue has been escalated to our telephony engineers and are investigating at this time.

Aug 11, 15:37 UTC
Aug 11, 2022
Completed - The scheduled maintenance has been completed.
Aug 11, 06:02 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Aug 11, 05:00 UTC
Scheduled - Deployments of SMS gateways will be done. Some inbound and outbound messages may be delayed during the maintenance window.
Aug 11, 04:57 UTC
Aug 10, 2022
Resolved - The alerts we received about High Latency on Call Control calls where in fact a false positive.
No Call Control calls where affected by High Latency.
This was caused by a crash in one of our B2BUAs which affected a very small subset of calls, less than 50. The crash created an edge case and affected an internal process related to our Call Control Alerts but there was no further negative effect on customers.

Aug 10, 14:32 UTC
Investigating - We received alerts relating to high latency for call control calls particularly Dial and Conference commands.

Our engineers are made aware and working on the issue.

Aug 10, 04:34 UTC
Completed - The scheduled maintenance has been completed.
Aug 10, 06:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Aug 10, 05:00 UTC
Scheduled - Deployments of SMS gateways will be done. Some inbound and outbound messages may be delayed during the maintenance window.
Aug 10, 03:44 UTC
Aug 9, 2022
Completed - The scheduled maintenance has been completed.
Aug 9, 06:01 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Aug 9, 04:01 UTC
Scheduled - Telnyx Wireless Infrastructure will be undergoing maintenance to improve data connectivity latency. No impact to users is expected.
Aug 8, 17:34 UTC
Completed - The scheduled maintenance has been completed.
Aug 9, 05:30 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Aug 9, 04:31 UTC
Scheduled - Deployments of SMS gateways will be done. Some inbound and outbound messages may be delayed during the maintenance window.
Aug 9, 02:00 UTC
Aug 8, 2022
Resolved - This incident has now been resolved and full service restored.
Aug 8, 21:00 UTC
Monitoring - The issue has been resolved, We are currently monitoring to ensure no further impact.
Aug 8, 20:31 UTC
Update - Our partner has identified the issue and is taking immediate corrective measures. We will provide further updates as they become available.
Aug 8, 19:40 UTC
Identified - We have been informed of an ongoing incident with one of our connectivity partners that is impacting some wireless users in that they are unable to establish a data session. We are working with them to resolve this as quickly as possible.
Aug 8, 17:20 UTC
Resolved - This incident has been resolved.
Aug 8, 19:52 UTC
Identified - Another delay has accumulated for telephony setting updates to numbers, sip connections and outbound voice profile resources on the mission control portal.

Customers who update these resources may not see these updates take immediate effect.

Engineers continue working to resolve the issue at this time.

Aug 8, 13:08 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Aug 8, 12:07 UTC
Identified - The issue has been identified and a fix is being implemented.
Aug 8, 09:43 UTC
Investigating - We are currently investigating a delay in telephony setting updates to numbers, sip connections and outbound voice profile resources on the mission control portal.

Customers who update these resources may not see these updates to immediate effect.

Aug 8, 08:09 UTC
Aug 7, 2022

No incidents reported.

Aug 6, 2022
Resolved - This incident has been resolved, upon further investigation our engineers were able to clarify that this issue was not customer impacting.
Aug 6, 09:33 UTC
Identified - The issue has been identified and our engineers are working to resolve it. Customers with SIP Connections anchored in Sydney may experience a delay in their SIP Connection or number updates propagating in our system as well as potential inbound/outbound calls being anchored on anchorsites further away than Sydney.
Aug 6, 09:18 UTC
Investigating - We are currently investigating this issue.
Aug 6, 09:16 UTC
Aug 5, 2022
Completed - The scheduled maintenance has been completed.
Aug 5, 06:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Aug 5, 05:00 UTC
Scheduled - Deployments of SMS gateways will be done. Some inbound and outbound messages may be delayed during the maintenance window.
Aug 5, 03:23 UTC
Aug 4, 2022
Completed - The scheduled maintenance has been completed.
Aug 4, 07:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Aug 4, 06:32 UTC
Scheduled - Deployments of SMS gateways will be done. Some inbound and outbound messages may be delayed during the maintenance window.
Aug 4, 06:07 UTC