Smarty Status Page

Sep 26, 2026 · resolved Sep 26

**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 partial capacity at 15:30 UTC. What happened: a server in an internal system that our load balancers depend upon ran out of disk space but didn’t fail over properly to a peer node. When that system stopped answering, various load balancers across the regions began restarting automatically. Our engineers moved the affected system to a healthy server at 15:37 UTC, and service was fully restored by 15:39 UTC. What we are doing: we have increased disk capacity and changed log retention on the affected system so it cannot run out of space this way again. We are also changing how our load balancers behave when that system is unavailable, so they keep serving traffic instead of shutting down, and we are adding alerting that would have caught the problem before it affected you.

Sep 10, 2026 · resolved Sep 10

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

Aug 19, 2026 · resolved Aug 19

This incident has been resolved.

Jul 21, 2026 · resolved Jul 22

This incident has been resolved.

Jun 3, 2026 · resolved Jun 3

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.

Is Smarty down right now?

No — Smarty is up. All systems operational as of Oct 12, 2:43 AM UTC.

What is Smarty's current status?

Smarty: All Systems Operational. Alert24 checks Smarty's status page continuously and can notify you the moment it changes.

How do I get alerted when Smarty goes down?

Alert24 monitors Smarty and 3,700+ other cloud and SaaS providers. When an outage is detected it updates your status page automatically and pages your on-call team — no manual checks. Start free at alert24.net.