All Systems Operational

About This Site

Do you want notifications for when our stuff breaks? Check out our RSS feed: https://status.smarty.com/history.rss
You can even integrate it into your Slack so you never miss an alert! Everyone uses Slack, right?

US Street [Address] API Operational
US East 1 Operational
US West 1 Operational
US Central 1 Operational
US South 1 Operational
International Street [Address] API ? Operational
US East 1 Operational
US West 1 Operational
US Central 1 Operational
US South 1 Operational
US [Address] Autocomplete Pro API Operational
US East 1 Operational
US West 1 Operational
US Central 1 Operational
US South 1 Operational
International [Address] Autocomplete API Operational
US East 1 Operational
US West 1 Operational
US Central 1 Operational
US South 1 Operational
US Extract API Operational
US East 1 Operational
US West 1 Operational
US Central 1 Operational
US South 1 Operational
US Reverse Geo API Operational
US East 1 Operational
US West 1 Operational
US Central 1 Operational
US South 1 Operational
US ZIP Code API Operational
US East 1 Operational
US West 1 Operational
US Central 1 Operational
US South 1 Operational
US Enrichment API Operational
US East 1 Operational
US West 1 Operational
US Central 1 Operational
US South 1 Operational
Forward Proxy API Operational
US East 1 Operational
US West 1 Operational
US Central 1 Operational
Download API Operational
US East 1 Operational
US West 1 Operational
US South 1 Operational
Account Management Portal ? Operational
Public Website Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
System Metrics Month Week Day
US Street [Address] API: Slowest Single Lookup Processing Latency (default SLA: 500ms application process latency) ?
Fetching
US Extract API: Slowest Single Lookup Processing Latency (default SLA: 2000ms application process latency)
Fetching
US ZIP Code API: Slowest Single Lookup Processing Latency (default SLA: 250ms application process latency)
Fetching
US [Address] Autocomplete Pro API: Slowest Single Lookup Processing Latency (default SLA: 100ms application process latency)
Fetching
International Street Address API: Slowest Single Lookup Processing Latency (default SLA: 1000ms application process latency)
Fetching
US Reverse Geocoding API: Slowest Single Lookup Processing Latency (default SLA: 200ms application process latency)
Fetching
International Address Autocomplete API: Slowest Single Lookup Processing Latency
Fetching
Past Incidents
Jan 13, 2025

No incidents reported today.

Jan 12, 2025

No incidents reported.

Jan 11, 2025

No incidents reported.

Jan 10, 2025
Intermittent HTTP 503 Errors
Resolved - 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.
Jan 10, 21:12 UTC
Jan 9, 2025

No incidents reported.

Jan 8, 2025

No incidents reported.

Jan 7, 2025

No incidents reported.

Jan 6, 2025

No incidents reported.

Jan 5, 2025

No incidents reported.

Jan 4, 2025

No incidents reported.

Jan 3, 2025

No incidents reported.

Jan 2, 2025

No incidents reported.

Jan 1, 2025

No incidents reported.

Dec 31, 2024

No incidents reported.

Dec 30, 2024
Intermittent HTTP 503 Errors:
Resolved - 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.
Dec 30, 22:32 UTC
← Incident History Powered by Atlassian Statuspage