Smarty incident

Older applications affected briefly by TLS modifications

Notice Resolved View vendor source →

Smarty experienced a notice incident on March 1, 2024, lasting —. The incident has been resolved; the full update timeline is below.

Started
Mar 01, 2024, 11:11 PM UTC
Resolved
Mar 01, 2024, 11:11 PM UTC
Duration
—
Detected by Pingoru
Mar 01, 2024, 11:11 PM UTC

Update timeline

  1. resolved Mar 01, 2024, 11:11 PM UTC

    Some modifications were made to TLS certification configurations on one of our load-balancers. Part of the modification adjusted the order in which certificates were presented to clients. Older applications that are unable to properly use Server Name Indication may have been affected adversely by this change. In order to continue supporting older clients, the certificate order was readjusted to maximize compatibility. We suggest updating any applications that call Smarty APIs to be compatible with modern TLS certificate usage. We also suggest ensuring that the hostnames being used in requests to our APIs are current. Hostnames can be found on the documentation pages for the products that you are using. (https://www.smarty.com/docs/cloud)