Header Image
Active Incident

Updated a few seconds ago

Incident Status

Operational

Components

Management Portal, API Servers, Remote Tunnels

Locations

portal.telit.com / portal-us.telit.com, portal-de.telit.com, portal-dev.telit.com



September 1, 2026 5:12PM EDT
September 1, 2026 9:12PM UTC
IDENTIFIED

We want to make you aware of a change from our Certificate Authority (CA) that may require action in environments where certificate trust stores are managed explicitly and not automatically. We recently renewed our public server certificate as per regular operational maintenance, and albeit from the same Authority this time our certificate has been signed by a different root that is itself more recent than the previous root. This change was issued by the CA without prior notification, which limited our ability to provide advance notice. As a result, any system, application, gateway, device, or security appliance that relies on the previous root certificate or has a restricted set of trusted certificate authorities may be unable to validate certificates issued under the new trust chain. Note however that such inability is more likely to happen on very old devices as the more recent root is already 7 years old anyway. What you may need to do • Review trusted root certificates in your environment. • Install or approve the new CA root certificate if it is not already trusted. • Verify that any certificate pinning, custom trust stores, firewall inspection devices, or TLS validation policies are updated to recognize the new root. • Test connectivity to ensure certificate validation completes successfully. Potential symptoms • TLS or SSL connection failures • "Certificate signed by unknown authority" errors • "Self-signed certificate" errors • Certificate trust validation failures • Unexpected service connectivity interruptions We understand certificate trust changes can be disruptive, particularly when they occur without advance notice. Our team has already updated our services to use the new certificate chain and is available to assist customers who encounter validation issues related to this change. If you have questions or need the current certificate chain for validation purposes, please contact our support team. We apologize for any inconvenience and appreciate your understanding.

September 1, 2026 5:15PM EDT
September 1, 2026 9:15PM UTC
IDENTIFIED

DEV-US has been updated for testing Prod-US and Prod-DE will be updated September 2nd 2026

September 2, 2026 12:18PM EDT
September 2, 2026 4:18PM UTC
IDENTIFIED

Prod-DE and Prod-US updates delayed to September 3rd 2026

September 8, 2026 8:02PM EDT
September 9, 2026 12:02AM UTC
IDENTIFIED

Prod-US certificates were updated today to api , HTTPS and portal UI. Prod-DE certificates were updated HTTPS and portal UI. customers that had failing devices today will need to review the following: • Review trusted root certificates in your environment. • Install or approve the new CA root certificate if it is not already trusted. • Verify that any certificate pinning, custom trust stores, firewall inspection devices, or TLS validation policies are updated to recognize the new root. • Test connectivity to ensure certificate validation completes successfully.

Management Portal




Operational

API Servers




Operational

Remote Tunnels




Operational

Carrier Synchronization




Operational

Carrier real-time information (RADIUS/SS7)




Operational

Carriers




Operational

Connectivity




Operational

Docs Site




Operational

Locations