https://approjects-vendor-status-watch.static.hf.space/v/smarty.htmlIncidents from Smarty's public status page, polled daily.Wed, 16 Sep 2026 12:28:20 +0000https://stspg.io/jwy3bh7dmk8ssmarty:2026-09-10T20:14:19.000ZThu, 10 Sep 2026 20:14:19 +0000The issue has been resolved. The only service that was affected was the Account Management Portal. This incident did NOT affect production traffic to our APIs (address verification, autocomplete, geocoding, etc.)https://stspg.io/ypyfzw098h38smarty:2026-08-19T00:49:27.819ZWed, 19 Aug 2026 00:49:27 +0000This incident has been resolved.https://stspg.io/2v8f0gsgk88nsmarty:2026-07-21T22:30:26.021ZTue, 21 Jul 2026 22:30:26 +0000This incident has been resolved.https://stspg.io/c9zvmdnlppqhsmarty:2026-06-03T20:17:59.811ZWed, 03 Jun 2026 20:17:59 +0000SUMMARY We are rotating the Let's Encrypt intermediate certificates used to issue the TLS certificates that secure our services. Our certificates will continue to chain to the same trusted root — ISRG Root X1 — but through Let's Encrypt's new "Generation Y" intermediate hierarchy. For the vast majority of customers, no action is required. If your systems validate our certificates against the public root store — the default for virtually all browsers, operating systems, and HTTP client libraries — this change is completely transparent. The only customers who may be affected are those who pin a specific Let's Encrypt intermediate certificate. WHY WE'RE MAKING THIS CHANGE The intermediate certificates currently in our chain are approaching the end of their lifecycle, with the existing ihttps://stspg.io/0kzl5v88jz4jsmarty:2026-04-17T01:00:00.000ZFri, 17 Apr 2026 01:00:00 +0000At 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 environhttps://stspg.io/853bzk2k3nvpsmarty:2026-03-16T22:35:27.603ZMon, 16 Mar 2026 22:35:27 +0000Around 22:00 UTC the US [Address] Autocomplete Pro API service in one of our datacenters went offline due to a misconfiguration. The problem was quickly identified and rectified. All other datacenters were unaffected.https://stspg.io/1zysqrngclz6smarty:2026-03-06T17:59:46.691ZFri, 06 Mar 2026 17:59:46 +0000The issue has been resolved. A small number of nodes experienced large memory consumption which resulted in a few 503 errors being returned. This has been resolved and measures have been put in place to mitigate this in the future. Additional alerts and monitors have also been put in place.https://stspg.io/mrjvygh5qdp3smarty:2026-02-18T00:40:55.196ZWed, 18 Feb 2026 00:40:55 +0000Around 19:15 UTC an incorrect configuration was deploy to our US Extract API service. The problem was quickly detected and reverted.https://stspg.io/jhsmcg246pxhsmarty:2025-11-27T00:32:50.746ZThu, 27 Nov 2025 00:32:50 +0000This incident has been resolved.https://stspg.io/1drg07qjv85gsmarty:2025-10-30T22:36:27.977ZThu, 30 Oct 2025 22:36:27 +0000This incident has been resolved.