Smarty incident

API Certificate Chain Updated — Older Runtimes May Need Trust Store Update

Notice Resolved View vendor source →
Started
Apr 24, 2026, 05:39 PM UTC
Resolved
Apr 17, 2026, 01:00 AM UTC
Duration
Detected by Pingoru
Apr 24, 2026, 05:39 PM UTC

Update timeline

  1. resolved Apr 24, 2026, 05:39 PM UTC

    At 00:00 UTC on April 17, A scheduled certificate renewal updated the CA chain served by api.smartystreets.com. The change was made without advance notice to integrators, and the new chain is anchored by Sectigo roots (USERTrust ECC Certification Authority and USERTrust RSA Certification Authority) that are not present in some older trust stores. Clients on current operating systems, browsers, and runtimes continue to work without change. Connections may fail for systems that: - Use a custom or pinned TLS trust bundle that does not include USERTrust ECC Certification Authority. - Run Java 8 installations predating update 51 (mid-2015) or earlier Java versions — these do not ship USERTrust ECC Certification Authority in the default cacerts keystore. - Run other environments with outdated trust stores, including older Android devices, legacy embedded and IoT hardware, and air-gapped systems. To restore connectivity, affected systems should either update to a current runtime or add the Sectigo roots (USERTrust ECC Certification Authority and USERTrust RSA Certification Authority) to their trust store. Please reach out to support for assistance.

Looking to track Smarty downtime and outages?

Pingoru polls Smarty's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Smarty reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Smarty alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Smarty for free

5 free monitors · No credit card required