All Systems Operational
US Street Address API Operational
us-east Operational
us-central Operational
us-west Operational
International Street API ? Operational
us-east Operational
us-central Operational
us-west Operational
US ZIP Code API Operational
us-east Operational
us-central Operational
us-west Operational
US Autocomplete API Operational
US Autocomplete Pro API Operational
US Extract API Operational
us-east Operational
us-central Operational
us-west Operational
Account Management Portal ? Operational
Public Website Operational
Forward Proxy API Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
had a major outage
had a partial outage
US Street Address API: Single Lookup Processing Latency (included in SLA)
Fetching
US ZIP Code API: Application Processing Latency (included in SLA)
Fetching
US Street Address API: Uptime
Fetching
US ZIP Code API: Uptime
Fetching
US Autocomplete API: Uptime
Fetching
US Autocomplete Pro API: Uptime
Fetching
US Extract API: Uptimes
Fetching
International Street Address API: Uptime
Fetching
Past Incidents
Feb 20, 2020

No incidents reported today.

Feb 19, 2020

No incidents reported.

Feb 18, 2020
Resolved - The final shutdown of support for TLS v1.0 and v1.1 has been completed across all SmartyStreets APIs and services. From this point on we will only accept connections that use TLSv1.2 and above.
Feb 18, 18:17 UTC
Feb 17, 2020

No incidents reported.

Feb 16, 2020

No incidents reported.

Feb 15, 2020

No incidents reported.

Feb 14, 2020

No incidents reported.

Feb 13, 2020
Resolved - For approximately 12 hours hours spanning from yesterday through this morning a number of addresses submitted for validation to our International Street Address API for GBR (United Kingdom/Great Britain) FRA (France) and JPN (Japan) were failing. The issue was corrected at 7:30am Mountain Time / 9:00am Eastern Time.

We have identified the root cause of the issue related to the data build process from our partner data feeds. We are in the process of expanding the integrity checks run on each data feed to further ensure correctness of the data.
Feb 13, 22:39 UTC
Feb 12, 2020
Resolved - On Tuesday 18 February 2020 at 16:30 UTC (11:30 ET, 09:30 MT) we will be shutting down all support for TLS v1.0 and v1.1. This shutdown will be final.
Feb 12, 17:51 UTC
Feb 11, 2020
Completed - The scheduled maintenance has been completed.
Feb 11, 23:30 UTC
Update - TLS v1.1 and below are not currently being accepted. This will remain in effect for the duration of the maintenance window. This should only affect clients who are trying to access our services with older versions of TLS.
Feb 11, 17:02 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 11, 16:30 UTC
Scheduled - The next scheduled outage, for anyone using TLS 1.0 or 1.1, will be on Tuesday 11 February 2020 from 09:30 until 16:30 Mountain Time (16:30 - 23:30 UTC).
Feb 5, 20:16 UTC
Feb 10, 2020
Resolved - During the upgrade of one of our datacenters, the Forward Proxy API in that datacenter was unavailable. The service outage was brief. The service is back to 100%.
Feb 10, 07:00 UTC
Feb 9, 2020

No incidents reported.

Feb 8, 2020

No incidents reported.

Feb 7, 2020
Resolved - A small number of customers were affected by a deployment to a single facility wherein the configuration did not contain all legacy domain names for various services.

For example, the official domain name for the US Street API service is:
https://us-street.api.smartystreets.com/

An older (legacy) domain name for the same service is:
https://api.smartystreets.com

Further, this same issue touches a handful of other services including:
us-extract.api.smartystreets.com (legacy: extract-beta.api.smartystreets.com)
us-autocomplete.api.smartystreets.com (legacy: autocomplete.api.smartystreets.com)

The issue was manifest from 9:00 AM Eastern Time until 10:15 AM Eastern Time, at which time the configuration was rolled back pending review. Further, various automated tools which conduct systems test are being updated to verify legacy domain name compatibility.
Feb 7, 16:16 UTC
Feb 6, 2020

No incidents reported.