Is Smarty down?

Last checked 3m ago
Current status
Smarty is up

No incidents right now.

Official status page: https://status.smarty.com · Polled every 5 minutes · 40 components tracked

Smarty is operational right now. Last checked 3m ago; the most recent incident resolved 7d ago.

Real-time Smarty status, recent outages, and incident history — pulled directly from Smarty's official status page at https://status.smarty.com every 5 minutes. Pingoru tracks 40 Smarty services and has captured 2 incidents in the last 90 days (99.78% uptime). Get email, Slack, Discord, or webhook alerts the moment Smarty reports a new incident — free for 5 monitors, no credit card.

Users who monitor Smarty also follow these Security services: Duo Security LastPass 1Password Barracuda Rapid7 Palo Alto Networks KnowBe4 Incapsula SentinelOne Keeper View all 6,000+ providers
Smarty uptime 99.78% uptime · past 90 days
Mon Wed Fri
AprMayJunJul
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 2h 3m
    Started Jul 21, 2026, 10:30 PM UTC · Resolved Jul 22, 2026, 12:34 AM UTC
    US East 1US West 1US Central 1US South 1
    Timeline · 5 updates
    • identified · Jul 21, 2026, 10:30 PM UTC

      Starting from 19:00 UTC, unexpected input is resulting in a small percentage of requests returning 503 response codes from the US Street Address API. Resolution is currently underway, and an update will be posted to this page when it is complete.

    • identified · Jul 21, 2026, 10:33 PM UTC

      We are continuing to work on a fix for this issue.

    • monitoring · Jul 21, 2026, 10:56 PM UTC

      A fix has been implemented and is rolling out to the fleet. We are monitoring the results.

    • monitoring · Jul 21, 2026, 11:10 PM UTC

      The rollout is complete. We are continuing to monitor.

    • resolved · Jul 22, 2026, 12:34 AM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  2. Resolved
    Started Jun 03, 2026, 08:17 PM UTC · Resolved Jun 03, 2026, 08:17 PM UTC
    Timeline · 1 update
    • resolved · Jun 03, 2026, 08:17 PM UTC

      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.

    Latest: 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…

Outage history

Past 90 days · 2 incidents View full outage history →