Monitoring - A fix has been implemented and we are monitoring the results.
May 20, 2026 - 02:41 UTC
Investigating - We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.
May 20, 2026 - 01:03 UTC
Our Telephony Engineers will perform maintenance on our SIP proxy servers in the Europe region.
Our TLS certificate for our SIP proxy server(s) of sip.telnyx.eu (185.246.41.140 and 185.246.41.141) will be changed during this deployment. This is important for some customers who use an SBC (or other appliance) and have our certificate (or the CA certificate) loaded into the SBC. This information also applies to some customers who use TLS with desk phones (poly phones, for example) and who have the certificate loaded into the phones for TLS. The importance for such customer appliances/devices is that we'll use a new certificate chain (both the intermediate certificate and the root certificate will be changed).
Our new certificate will have this serial number, issuer, and fingerprint. - Serial Number: 0d:b6:4e:4a:b2:a9:8a:a9:6c:8d:40:a7:fe:f4:4e:7b - Issuer: C=US, O=DigiCert Inc, OU=www.digicert.com, CN=Thawte TLS RSA CA G1 - SHA1 Fingerprint: C5:F8:17:3E:2F:CB:37:EA:02:23:18:FC:46:3D:9B:6F:4D:4F:61:2A
The chain is signed by the DigiCert Global Root G2 certificate (SHA1 Fingerprint DF:3C:24:F9:BF:D6:66:76:1B:26:80:73:FE:06:D1:CC:8D:4F:82:A4) chain, which can be downloaded from Digicert's website. - https://cacerts.digicert.com/DigiCertGlobalRootG2.crt.pem
Note In line with CA/Browser Forum standards, this is the last TLS certificate for this service that will include clientAuth (Client Authentication) EKU as well as serverAuth (Server Authentication). When we renew the certificate again later this year (around October 2026), the new certificate will include only the serverAuth EKU. This will be significant for customers who use mTLS (Mutual TLS) for SIP trunks. Before our next certificate renewal, we'll send another update about this. Posted on
May 11, 2026 - 14:32 UTC
Our Telephony Engineers will perform maintenance on our SIP proxy servers in the US region.
Our TLS certificate for our SIP proxy server(s) of sip.telnyx.com (192.76.120.10 and 64.16.250.10) will be changed during this deployment. This is important for some customers who use an SBC (or other appliance) and have our certificate (or the CA certificate) loaded into the SBC. This information also applies to some customers who use TLS with desk phones (poly phones, for example) and who have the certificate loaded into the phones for TLS. The importance for such customer appliances/devices is that we'll use a new certificate chain (both the intermediate certificate and the root certificate will be changed).
Our new certificate will have this serial number, issuer, and fingerprint. - Serial Number: 0d:97:23:dc:a0:7e:60:0d:22:b0:ac:ed:ca:d4:4a:8d - Issuer: C=US, O=DigiCert Inc, OU=www.digicert.com, CN=Thawte TLS RSA CA G1 - SHA1 Fingerprint: 70:7B:25:E9:38:93:68:AB:2B:F7:2C:91:F4:BF:F5:61:71:A0:C7:9C
The chain is signed by the DigiCert Global Root G2 certificate (SHA1 Fingerprint DF:3C:24:F9:BF:D6:66:76:1B:26:80:73:FE:06:D1:CC:8D:4F:82:A4) chain, which can be downloaded from Digicert's website. - https://cacerts.digicert.com/DigiCertGlobalRootG2.crt.pem
Note In line with CA/Browser Forum standards, this is the last TLS certificate for this service that will include clientAuth (Client Authentication) EKU as well as serverAuth (Server Authentication). When we renew the certificate again later this year (around October 2026), the new certificate will include only the serverAuth EKU. This may be significant for customers who use mTLS (Mutual TLS) for SIP trunks. Before our next certificate renewal, we'll send another update about this. Posted on
May 11, 2026 - 14:41 UTC
Past Incidents
May 20, 2026
Unresolved incident: Inbound Calls to Australian DIDs Not Connecting.
Completed -
The scheduled maintenance has been completed.
May 19, 13:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 19, 09:00 UTC
Scheduled -
Our Telephony Engineers will perform maintenance on our SIP proxy servers (sip.telnyx.com) in the US region. This is expected to be non-disruptive.
May 18, 17:43 UTC
Resolved -
The impact from the issue seems to be over.
May 18, 14:28 UTC
Identified -
The issue partially persists and is being worked on by our engineers.
May 14, 11:03 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
May 14, 00:26 UTC
Investigating -
We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon. All cloud storage operations on buckets in us-central-1 might be not operational.
May 13, 21:44 UTC
Completed -
The scheduled maintenance has been completed.
May 15, 10:30 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 15, 08:30 UTC
Scheduled -
The Telnyx team will be performing maintenance on the network nodes carrying data traffic for IMSI1 sessions in the Americas. Connected devices may experienec a brief (about a minute) period of disconnection during this window.
May 12, 16:23 UTC
Completed -
The scheduled maintenance has been completed.
May 15, 10:15 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 15, 08:15 UTC
Scheduled -
Our Telephony Engineers will perform maintenance on our Programmable Voice services in the Europe/US region. This maintenance should not disrupt service.
May 15, 08:11 UTC
Completed -
The scheduled maintenance has been completed.
May 14, 13:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 14, 12:30 UTC
Scheduled -
Our Telephony Engineers will perform maintenance on our TeXML services in the Europe/US region. This maintenance should not disrupt service.
May 14, 12:24 UTC
Completed -
The scheduled maintenance has been completed.
May 13, 14:30 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 13, 11:30 UTC
Scheduled -
Our Telephony Engineers will perform maintenance on our Programmable Voice services in the Europe/US region. This maintenance should not disrupt service.
May 13, 11:25 UTC
Completed -
The scheduled maintenance has been completed.
May 12, 12:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 12, 11:00 UTC
Scheduled -
Our Telephony Engineers will perform maintenance on our TeXML services in the Europe/US region. This maintenance should not disrupt service.
May 12, 10:52 UTC
Completed -
The scheduled maintenance has been completed.
May 11, 18:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 11, 13:01 UTC
Scheduled -
Our Telephony Engineers will be performing an update on our Voice Services across all regions Impact: This update is not expected to disrupt service. Action Required: If you experience any audio issues or dropped calls during this maintenance window, please report them immediately to Telnyx Support.
May 11, 11:52 UTC
Completed -
The scheduled maintenance has been completed.
May 11, 13:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 11, 11:00 UTC
Scheduled -
Our Telephony Engineers will perform maintenance on our Programmable Voice services in the Europe/US region. This maintenance should not disrupt service.
May 11, 10:29 UTC
Completed -
The scheduled maintenance has been completed.
May 11, 10:31 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 11, 04:00 UTC
Scheduled -
Our Telephony Engineers will be performing an update on our Voice Services across all regions Impact: This update is not expected to disrupt service. Action Required: If you experience any audio issues or dropped calls during this maintenance window, please report them immediately to Telnyx Support.
May 8, 17:42 UTC
Completed -
The scheduled maintenance has been completed.
May 8, 12:00 UTC
Update -
Please note this Maintenance window has been extended by an hour to allow for longer monitoring post changes.
May 8, 08:54 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 8, 08:00 UTC
Scheduled -
We will be performing further scheduled maintenance on our wireless infrastructure to core subscriber management capabilities. This enhancement will enable improved network reliability and future feature support.
What to Expect
Active data sessions may experience a momentary pause (under 30 seconds) as devices re-authenticate on our network. Devices reconnect automatically.
May 7, 13:05 UTC
Completed -
Maintenance was completed as planned, without incident.
May 8, 11:02 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 8, 10:00 UTC
Scheduled -
We will be continue migrating all services on wireguard server in Chicago from Equinix infrastructure. The same IP addresses will be used, so impact should be limited to client re-handshake with the new server. No customer action required. This will be 2nd and last phase of migration we have started on 16th April 2026 to complete the server migration.
May 6, 12:22 UTC
Resolved -
We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.
May 7, 22:56 UTC
Identified -
Found the root cause and currently implementing a fix.
May 7, 19:10 UTC
Investigating -
User operations on buckets and objects located in us-central-1 region might be inaccessible. We're currently investigating the issue, and will provide an update soon.
May 7, 17:36 UTC
Completed -
The scheduled maintenance has been completed.
May 7, 18:46 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 7, 17:40 UTC
Scheduled -
Our Telephony Engineers will perform maintenance on our Programmable Voice services in the Europe/US region. This maintenance should not disrupt service.
May 7, 17:38 UTC
Resolved -
The delays in SIM card management actions have been resolved. All operations are processing normally.
May 6, 16:30 UTC
Investigating -
We are investigating reports of delays in SIM card management actions. Actions such as SIM activation, suspension, and profile changes may take longer than expected.
May 6, 14:10 UTC