Smarty Outage History
10 incidents recorded over the last 365 days, 10 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Smarty Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Sep 26, 2026 | Monitoring – Intermittent Service Availability**Post-incident summary** On September 26, 2026, from 15:28 to 15:39 UTC, requests to our APIs failed sporadically. A large portion of requests were refused outright for several minutes. A few regions briefly recovered… | 57 min | Resolved |
| Sep 10, 2026 | Account Management Portal - LoginThe 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.) | 2h 23m | Resolved |
| Aug 19, 2026 | US Street API returning 503 response codesThis incident has been resolved. | 20h 24m | Resolved |
| Jul 21, 2026 | US Street API returning 503 response codesThis incident has been resolved. | 2h 3m | Resolved |
| Jun 3, 2026 | Scheduled TLS Certificate Update — Let's Encrypt Intermediate RotationSUMMARY 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… | 0 min | Resolved |
| Apr 24, 2026 | API Certificate Chain Updated — Older Runtimes May Need Trust Store UpdateAt 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… | -11079 min | Resolved |
| Mar 16, 2026 | US [Address] Autocomplete Pro API went offline briefly in one datacenterAround 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. | 0 min | Resolved |
| Mar 6, 2026 | Intermittent 503 Errors for US Street [Address] APIThe 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… | 93h 58m | Resolved |
| Feb 18, 2026 | US Extract API briefly returned incorrect HTTP status codeAround 19:15 UTC an incorrect configuration was deploy to our US Extract API service. The problem was quickly detected and reverted. | 1h 19m | Resolved |
| Nov 27, 2025 | Intermittent HTTP 5xx Errors Returned by US Street API and US Zip Code APIThis incident has been resolved. | 112h 34m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Smarty incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Smarty Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Smarty acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Smarty outage in this window ran 4d 16h, against a mean recovery of 1d 1h. If you depend on Smarty in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.