Smarty logo

Is Smarty Down?

SaaSLive status, outages, and incident history

No. Smarty is up right now.

Every monitored Smarty system is operational as of August 11, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 31m agoLive, rechecked every 60s
How we know: the official Smarty status page, PulsAPI's own check every 60 seconds, and outage reports from engineers. How PulsAPI monitoring works

Smarty Component Status

The main Smarty systems on this page. All 20 are operational right now.

20operational
Account Management Portal
Operational
Download API » US East 1
Operational
Download API » US South 1
Operational

17 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Download API » US West 1, Forward Proxy API » US Central 1, Forward Proxy API » US East 1, Forward Proxy API » US West 1, International Street [Address] API » US Central 1, International Street [Address] API » US East 1, International Street [Address] API » US South 1, International Street [Address] API » US West 1, International [Address] Autocomplete API » US Central 1, International [Address] Autocomplete API » US East 1, International [Address] Autocomplete API » US South 1, International [Address] Autocomplete API » US West 1, and 5 more.

Create a free account

Component statuses may change independently during partial outages.

Recent Smarty Outages & Incidents

Incident history from the official Smarty status page, including resolution updates.

Uptime history4 days observed
Aug 8100.00% averageAug 11
US Street API returning 503 response codesResolved Jul 21, 2026 · 2h 3mResolved

This incident has been resolved. --- [2026-07-21T23:10:17.637Z] (monitoring) The rollout is complete. We are continuing to monitor. --- [2026-07-21T22:56:16.615Z] (monitoring) A fix has been implemented and is rolling out to the fleet. We are monitoring the results. --- [2026-07-21T22:34:20.943Z] (identified) We are continuing to work on a fix for this issue. --- [2026-07-21T22:30:26.057Z] (identified) 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.

Scheduled TLS Certificate Update — Let's Encrypt Intermediate RotationResolved Jun 3, 2026 · 0 minResolved

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.

Live Smarty Outage Reports

Problems reported by engineers using Smarty. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Smarty problems reported yet.

Something wrong with Smarty on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Smarty

Smarty publishes a public status page at status.smarty.com covering 50 components, including US Street [Address] API, US East 1 and International Street [Address] API. PulsAPI tracks Smarty outages, degraded performance and incident history in real time, alongside the rest of your SaaS stack.

Over the past 30 days, PulsAPI has measured Smarty uptime at 100.00%. Response times, incident history, and SLA tracking for Smarty are available on the PulsAPI dashboard.

Smarty Status FAQ

Is Smarty down right now?

PulsAPI checks Smarty every 60 seconds. The verdict at the top of this page comes from the latest poll of the official Smarty status feed and refreshes automatically, so you are not looking at a stale cached answer.

What should I do if Smarty is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Smarty recovers.

How do I check Smarty uptime history?

PulsAPI tracks Smarty uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 100.00%. A free PulsAPI account unlocks the full 90-day SLA history and incident timeline for Smarty.

How fast does PulsAPI detect Smarty outages?

PulsAPI polls the official Smarty status page every 60 seconds and usually delivers alerts to Slack, Discord, Microsoft Teams, PagerDuty, or email in under 4 seconds after detection. That is often faster than someone on your team notices on their own.

Does PulsAPI track individual Smarty components?

Yes. PulsAPI monitors 20 individual Smarty components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Smarty goes down?

Yes. Create a PulsAPI account and subscribe to Smarty. Email alerts are included on the free Starter plan. Paid plans add Slack, Discord, Microsoft Teams, PagerDuty, and webhooks whenever Smarty status changes.

How do I report an issue with Smarty to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Smarty problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Smarty?

Yes. PulsAPI's Starter plan includes up to 10 monitored services with email alerts, and the 30-day free trial requires no credit card. You can monitor Smarty alongside up to 9 other services at pulsapi.com/signup.

Track Smarty with the rest of your stack

Monitor 2461+ cloud services from one dashboard and get alerts when Smarty status changes.

Start free trial