Is Smarty down?

Last checked 5m ago
Current status
Smarty is up

No incidents right now.

  • Official status page: status.smarty.com
  • Checked every 5 minutes
  • 40 components tracked

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

Real-time Smarty status, recent outages, and incident history: pulled directly from Smarty's official status page at status.smarty.com every 5 minutes. Pingoru tracks 40 Smarty services and has captured 3 incidents in the last 90 days (99.94% uptime). Get email, Slack, Discord, or webhook alerts the moment Smarty reports a new incident, free for 3 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 8,000+ providers
Smarty uptime 99.94% uptime · past 90 days
Mon Wed Fri
JulAugSepOct
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 57m
    Started Sep 26, 2026, 03:51 PM UTC · Resolved Sep 26, 2026, 04:49 PM UTC
    US East 1US East 1US East 1US East 1US East 1US East 1US East 1US East 1US West 1US West 1
    Timeline · 3 updates
    • monitoring · Sep 26, 2026, 03:51 PM UTC

      At 15:23 UTC we began investigating reports of some services being intermittently unavailable. Service has since been fully restored and all systems are operating normally. We are monitoring closely and continuing to investigate the root cause.

    • resolved · Sep 26, 2026, 04:49 PM UTC

      The incident has been resolved. We are conducting a more thorough investigation to discover the root cause.

    • postmortem · Sep 28, 2026, 07:03 PM UTC

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

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

  2. Resolved 2h 23m
    Started Sep 10, 2026, 08:14 PM UTC · Resolved Sep 10, 2026, 10:37 PM UTC
    Account Management Portal
    Timeline · 4 updates
    • investigating · Sep 10, 2026, 08:14 PM UTC

      We are currently investigating Login issues and hope to have a resolution shortly. Product APIs are unaffected and fully operational.

    • investigating · Sep 10, 2026, 08:16 PM UTC

      We are continuing to investigate this issue.

    • investigating · Sep 10, 2026, 08:18 PM UTC

      We are continuing to investigate this issue.

    • resolved · Sep 10, 2026, 10:37 PM UTC

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

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

  3. Resolved 20h 24m
    Started Aug 19, 2026, 12:49 AM UTC · Resolved Aug 19, 2026, 09:13 PM UTC
    US East 1US West 1US Central 1US South 1
    Timeline · 2 updates
    • investigating · Aug 19, 2026, 12:49 AM UTC

      A small number of intermittent 503 Errors for US Street [Address] API are affecting a few requests. This is currently being investigated.

    • resolved · Aug 19, 2026, 09:13 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

Incident record

Since April 2026 · Statuspage by Atlassian · 40 components checked every 5 minutes
50incidents recorded
11last 12 months
3last 90 days
23 hourstypical duration, 12 months

The longest incident in the last year, Intermittent HTTP 5xx Errors Returned by US Street API and US Zip Code API on November 27, 2025, ran for 5 days.

Most affected components, last 12 months

  • US Central 15
  • US East 15
  • US West 15
  • US South 14
  • US Central 12

Latest incidents

  • Monitoring – Intermittent Service Availability September 26, 2026 · 57 minutes · notice

    At 15:23 UTC we began investigating reports of some services being intermittently unavailable. Service has since been fully restored and all systems are…

  • Account Management Portal - Login September 10, 2026 · 2 hours · major outage

    We are currently investigating Login issues and hope to have a resolution shortly. Product APIs are unaffected and fully operational.

  • US Street API returning 503 response codes August 19, 2026 · 20 hours · notice

    A small number of intermittent 503 Errors for US Street [Address] API are affecting a few requests. This is currently being investigated.

Outage history

Past 90 days · 3 incidents View full outage history →