Störungsverlauf von Smarty

1. 26. September 2026 um 15:51 UTCmonitoring

   Um 15:23 UTC begannen wir, Berichte über einige Dienste zu untersuchen, die intermittierend nicht verfügbar waren. Der Service wurde seitdem vollständig wiederhergestellt und alle Systeme funktionieren normal. Wir beobachten aufmerksam und untersuchen weiterhin die Ursachen.

2. 26. September 2026 um 16:49 UTCresolved

   Der Vorfall wurde behoben. Wir führen eine gründlichere Untersuchung durch, um die Ursache zu entdecken.

3. 28. September 2026 um 19:03 UTCpostmortem

   **Zusammenfassung nach dem Vorfall** Am 26. September 2026, von 15:28 bis 15:39 UTC, scheiterten Anfragen an unsere APIs sporadisch. Ein großer Teil der Anträge wurde mehrere Minuten lang abgelehnt. Einige Regionen erholten kurzzeitig Teilkapazität bei 15:30 UTC. Was passiert ist: Ein Server in einem internen System, von dem unsere Load Balancer abhängen, hat keinen Speicherplatz mehr, ist aber nicht ordnungsgemäß an einen Peer-Node übergeben worden. Als dieses System aufhörte zu antworten, begannen verschiedene Load Balancer in den Regionen automatisch neu zu starten. Unsere Ingenieure verlegten das betroffene System um 15:37 UTC auf einen gesunden Server, und der Service wurde bis 15:39 UTC vollständig wiederhergestellt. Was wir tun: Wir haben die Festplattenkapazität erhöht und die Protokollspeicherung auf dem betroffenen System geändert, so dass der Speicherplatz auf diese Weise nicht wieder erschöpft ist. Wir ändern auch, wie sich unsere Load Balancer verhalten, wenn dieses System nicht verfügbar ist, so dass sie weiterhin den Datenverkehr bedienen, anstatt herunterzufahren, und wir fügen eine Warnung hinzu, die das Problem gelöst hätte, bevor es Sie betroffen hätte.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 10. September 2026 um 20:14 UTCinvestigating

   Wir untersuchen derzeit Login-Probleme und hoffen, in Kürze eine Lösung zu haben. Produkt-APIs sind nicht betroffen und voll funktionsfähig.

2. 10. September 2026 um 20:18 UTCinvestigating

   Wir werden dieses Problem weiter untersuchen.

3. 10. September 2026 um 22:37 UTCresolved

   Das Problem ist gelöst. Der einzige Dienst, der betroffen war, war das Account Management Portal. Dieser Vorfall hat keinen Einfluss auf den Produktionsverkehr zu unseren APIs (Adressverifizierung, Autovervollständigung, Geocodierung usw.)

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 19. August 2026 um 00:49 UTCinvestigating

   Eine kleine Anzahl von intermittierenden 503-Fehlern für die US Street [Address]-API betrifft einige Anfragen. Dies wird derzeit untersucht.

2. 19. August 2026 um 21:13 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 21. Juli 2026 um 22:30 UTCidentified

   Ab 19:00 Uhr UTC führt eine unerwartete Eingabe dazu, dass ein kleiner Prozentsatz der Anfragen 503 Antwortcodes von der US Street Address API zurückgibt. Die Auflösung ist derzeit im Gange, und ein Update wird auf dieser Seite veröffentlicht, wenn es abgeschlossen ist.

2. 21. Juli 2026 um 22:33 UTCidentified

   Wir arbeiten weiter an einer Lösung für dieses Problem.

3. 21. Juli 2026 um 22:56 UTCmonitoring

   Ein Fix wurde implementiert und wird in die Flotte eingeführt. Wir beobachten die Ergebnisse.

4. 21. Juli 2026 um 23:10 UTCmonitoring

   Der Rollout ist abgeschlossen. Wir beobachten weiter.

5. 22. Juli 2026 um 00:34 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 3. Juni 2026 um 20:17 UTCresolved

   SUMMARY 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 intermediate path expiring in approximately nine months. Rotating well ahead of that deadline guarantees uninterrupted certificate issuance and renewal with no disruption to your integrations. THE CHAIN OF TRUST A TLS certificate is never validated on its own. It is verified through a chain that links the connection back to a root certificate your device already trusts. Today, our certificates chain like this: Your connection → Smarty leaf certificate → Let's Encrypt intermediate → ISRG Root X1 After this update, they will chain like this: Your connection → Smarty leaf certificate → Let's Encrypt Generation Y intermediate (YR / YE) → ISRG Root YR / YE → ISRG Root X1 (via cross-sign) The destination is unchanged. Both the old and new paths terminate at ISRG Root X1, the RSA root that ships in every current major trust store. Let's Encrypt cross-signed its new Generation Y roots with the existing X1 and X2 roots specifically so that anything already trusting X1 continues to work without modification. The path is longer; the anchor of trust is identical.

1. 24. April 2026 um 17:39 UTCresolved

   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.

1. 16. März 2026 um 22:35 UTCresolved

   Around 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.

1. 6. März 2026 um 17:59 UTCinvestigating

   We are currently investigating an increase in 503 Service Unavailable errors. We will provide an update as soon as more information is available.

2. 6. März 2026 um 21:16 UTCmonitoring

   The issue has been identified and we are currently monitoring overall system health.

3. 10. März 2026 um 15:58 UTCresolved

   The 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.

1. 18. Februar 2026 um 00:40 UTCresolved

   Around 19:15 UTC an incorrect configuration was deploy to our US Extract API service. The problem was quickly detected and reverted.

1. 27. November 2025 um 00:32 UTCmonitoring

   We've identified an issue affecting one of our redundant facilities. As a precaution, it has been taken out of active rotation while we investigate.

2. 1. Dezember 2025 um 17:07 UTCresolved

   This incident has been resolved.

1. 30. Oktober 2025 um 22:36 UTCmonitoring

   During a routine data deployment, we noticed a brief spike in 5xx error responses. Systems have since stabilized, and we're investigating the root cause to confirm the issue is fully resolved and to prevent similar behavior in future deployments.

2. 4. November 2025 um 15:35 UTCresolved

   This incident has been resolved.

1. 18. Juli 2025 um 16:25 UTCresolved

   We have become aware that Google services have been exhibiting some intermittent failures. As a result, anyone using "Login with Google" to access their account dashboard on our website may also experience a failure to login. When Google is able to resolve the issues they are having, the login will continue to work as normal. In the meantime, if you have created a username and password, you should be able to use those to login.

1. 15. Mai 2025 um 14:32 UTCresolved

   We discovered that the "API Keys" page in our Account dashboard web site was not able to retrieve the lists of keys from the backend service. This has now been fixed.

1. 18. März 2025 um 22:11 UTCresolved

   Around 19:10 UTC, increased traffic exposed resource limitations caused by a previously implemented algorithm update, leading to issues on several servers hosting some of our services (US Street API, US Extract API) in one of our data centers due to insufficient RAM. To ensure stability and service reliability, the affected servers have been decommissioned and replaced with upgraded hardware.

1. 26. Februar 2025 um 20:31 UTCresolved

   The US Enrichment API intermittently returned HTTP 500 codes in a single data center on 2025 February 26 around 17:00 UTC. The issue has been resolved as of 17:35 UTC.

1. 7. Februar 2025 um 21:15 UTCresolved

   Around 18:00 UTC, one of our facilities experienced a network routing issue that lasted for about 30 minutes. The facility was removed from DNS rotation until the network issue had been resolved. If you have not yet read through our "Technical Requirements" and "Best Practices" documentation, this could be a good opportunity to become familiar with those important and helpful documents. - https://www.smarty.com/docs/cloud/requirements#retry - https://www.smarty.com/docs/cloud/best-practices

1. 10. Januar 2025 um 21:12 UTCresolved

   From 01/08 12pm UTC to 01/09 9am UTC some requests to the US Street [Address] API instances experienced an intermittent issue with certain malformed addresses that caused some requests to not get a response, returning HTTP 503 errors to those requests. This affected a small number of requests and the error has since been resolved.

1. 30. Dezember 2024 um 22:32 UTCresolved

   During a regular upgrade of our control plane, several controller nodes became unresponsive. This resulted in various routing issues which were manifest by intermittent HTTP 503 errors visible in the HTTP response to some callers. Our monitoring systems alerted our Operations Engineering Team of the anomaly and, as a result, the affected cluster, located in our US Central region (Chicago), was immediately removed from production rotation. The affected cluster has been restored to full health by provisioning new cloud resources using our IaC (infrastructure as code) systems. Following this, the cluster was confirmed to be was healthy via our automated monitoring and was subsequently re-introduced into active rotation.

1. 20. Dezember 2024 um 16:11 UTCresolved

   On 2024 December 19, around 22-24:00 UTC, some users may have received the HTTP 299 code in response to requests from one of our loadbalancers. The reason for this response has been identified and remediated. We would like to take this opportunity to remind our users to familiarize themselves with our best practices. https://www.smarty.com/docs/cloud/best-practices

1. 9. Dezember 2024 um 19:45 UTCresolved

   Around 15:00 (3pm) UTC on 2024 November 28, a single IP address at one of our datacenters experienced a routing issue that caused some requests to be "null routed", which may have resulted in some clients experiencing 500 level errors during that time. This issue persisted until 17:00 (5pm) UTC on 2024 November 28, at which time our upstream provider resolved the issue. Our recommendation to clients to mitigate an issue such as this in the future is to maintain a pool of active TCP connections to the server nodes and to only send traffic over active, healthy TCP connections. Then a background "thread" (or programmatic equivalent) could attempt to connect to the suspect IPv4 address. Once that connection has determined to be healthy, regular traffic can be resumed over that TCP connection.