Company Logo

Is there an Zonos outage?

Zonos status: Systems Active

Last checked: 2 minutes ago

Get notified about any outages, downtime or incidents for Zonos and 1800+ other cloud vendors. Monitor 10 companies, for free.

Subscribe for updates

Zonos outages and incidents

Outage and incident data over the last 30 days for Zonos.

There have been 1 outages or incidents for Zonos in the last 30 days.

Severity Breakdown:

Tired of searching for status updates?

Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!

Sign Up Now

Components and Services Monitored for Zonos

Outlogger tracks the status of these components for Xero:

Classify Active
Dashboard Active
International Checkout Active
Quoter Active
Landed Cost API Active
Landed Cost API (GraphQL) Active
Landed Cost API (Legacy) Active
BigCommerce Duty Tax Active
Magento Duty Tax Active
Salesforce Duty Tax Active
Shopify Checkout Active
Shopify Duty Tax Active
Component Status
Classify Active
Dashboard Active
International Checkout Active
Quoter Active
Active
Landed Cost API Active
Landed Cost API (GraphQL) Active
Landed Cost API (Legacy) Active
Active
BigCommerce Duty Tax Active
Magento Duty Tax Active
Salesforce Duty Tax Active
Shopify Checkout Active
Shopify Duty Tax Active

Latest Zonos outages and incidents.

View the latest incidents for Zonos and check for official updates:

Updates:

  • Time: Dec. 14, 2023, 5:45 p.m.
    Status: Postmortem
    Update: **What products were affected and what was the impact?** * Checkout * Landed Cost \(Legacy\) * Landed Cost API   Impact: * Checkout MAJOR OUTAGE * Landed Cost \(Legacy\) MAJOR OUTAGE * Landed Cost API SERVICE DEGRADATION     **What timeframe did this issue occur?** |   | **Date** | **Time** | | --- | --- | --- | | From: | December 13, 2023 | 3:02 MST | | To: | December 13, 2023 | 5:35 MST |   **How was the issue detected?** There was increased database load and request timeouts. This was detected by the monitoring system and the team was notified. ‌ **What functionality was affected?** Shipping Quotes for the checkout process and Landed Cost \(Legacy\) API were directly affected. Landed Cost API was indirectly affected by the increased load on the database server. ‌ **What problems did this cause?** In the process of removing invalid data from the database a database table index became corrupted causing increased latency and load on the database server. The affected table was for providing flat rate shipping rates to the landed cost \(legacy\) service. The landed cost service is used by the checkout process to calculate shipping rates for international orders. This caused the landed cost \(legacy\) and checkout processes to fail when attempting to calculate shipping. This also caused landed cost API to fail intermittently with timeouts because of the increased load on the database.   ‌ **What was the resolution of the problem and steps that are being taken for continued follow-up?** A patch was deployed to disable the flat rate charts and allow partial recovery and to allow for correcting the affected database table. The affected database table was restored and the flat rate charts were re-enabled. ‌ ‌ **What mitigation solutions will we put in place to prevent this issue from occurring in the future?** This issue occurred in our legacy database system. The data removal was done to improve query performance, and the operation should have been safe. Though index corruption is a very rare and unexpected outcome, we are doing two things to mitigate this risk and prevent future failure cases: 1. migrating legacy services to a more robust database technology, and 2. creating an additional review policy for potentially destructive database operations.
  • Time: Dec. 14, 2023, 1 a.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: Dec. 14, 2023, 12:59 a.m.
    Status: Monitoring
    Update: We are continuing to monitor for any further issues.
  • Time: Dec. 13, 2023, 11:21 p.m.
    Status: Monitoring
    Update: A fix has been implemented and we are monitoring the results.
  • Time: Dec. 13, 2023, 11:17 p.m.
    Status: Identified
    Update: The issue has been identified and a fix is being implemented.
  • Time: Dec. 13, 2023, 10:22 p.m.
    Status: Investigating
    Update: We are currently investigating this issue.

Updates:

  • Time: Dec. 14, 2023, 5:45 p.m.
    Status: Postmortem
    Update: **What products were affected and what was the impact?** * Checkout * Landed Cost \(Legacy\) * Landed Cost API   Impact: * Checkout MAJOR OUTAGE * Landed Cost \(Legacy\) MAJOR OUTAGE * Landed Cost API SERVICE DEGRADATION     **What timeframe did this issue occur?** |   | **Date** | **Time** | | --- | --- | --- | | From: | December 13, 2023 | 3:02 MST | | To: | December 13, 2023 | 5:35 MST |   **How was the issue detected?** There was increased database load and request timeouts. This was detected by the monitoring system and the team was notified. ‌ **What functionality was affected?** Shipping Quotes for the checkout process and Landed Cost \(Legacy\) API were directly affected. Landed Cost API was indirectly affected by the increased load on the database server. ‌ **What problems did this cause?** In the process of removing invalid data from the database a database table index became corrupted causing increased latency and load on the database server. The affected table was for providing flat rate shipping rates to the landed cost \(legacy\) service. The landed cost service is used by the checkout process to calculate shipping rates for international orders. This caused the landed cost \(legacy\) and checkout processes to fail when attempting to calculate shipping. This also caused landed cost API to fail intermittently with timeouts because of the increased load on the database.   ‌ **What was the resolution of the problem and steps that are being taken for continued follow-up?** A patch was deployed to disable the flat rate charts and allow partial recovery and to allow for correcting the affected database table. The affected database table was restored and the flat rate charts were re-enabled. ‌ ‌ **What mitigation solutions will we put in place to prevent this issue from occurring in the future?** This issue occurred in our legacy database system. The data removal was done to improve query performance, and the operation should have been safe. Though index corruption is a very rare and unexpected outcome, we are doing two things to mitigate this risk and prevent future failure cases: 1. migrating legacy services to a more robust database technology, and 2. creating an additional review policy for potentially destructive database operations.
  • Time: Dec. 14, 2023, 1 a.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: Dec. 14, 2023, 12:59 a.m.
    Status: Monitoring
    Update: We are continuing to monitor for any further issues.
  • Time: Dec. 13, 2023, 11:21 p.m.
    Status: Monitoring
    Update: A fix has been implemented and we are monitoring the results.
  • Time: Dec. 13, 2023, 11:17 p.m.
    Status: Identified
    Update: The issue has been identified and a fix is being implemented.
  • Time: Dec. 13, 2023, 10:22 p.m.
    Status: Investigating
    Update: We are currently investigating this issue.

Updates:

  • Time: Sept. 21, 2023, 9:32 p.m.
    Status: Postmortem
    Update: **What products were affected and what was the impact?** Our Landed Cost APIs \(GraphQL\) were impacted. Impact: MAJOR OUTAGE   **What timeframe did this issue occur?** |   | **Date** | **Time** | | --- | --- | --- | | From: | Sep 19, 2023 | 15:30 MST | | To: | Sep 19, 2023 | 15:44 MST |   **How was the issue detected?** Error rates triggered alarm monitors. **What functionality was affected?** Landed cost quotes for some stores could not be returned. ‌ **What problems did this cause?** Some merchants were unable to retrieve landed cost quotes. ‌ **What was the resolution of the problem and steps that are being taken for continued follow-up?** We discovered a configuration error in a previous release. Due to caching, scheduled synthetic test failures in the development environment lagged behind the deployment to the production environment. We fixed the configuration error, released the fix, and confirmed issue resolution via manual and automated testing. **What mitigation solutions will we put in place to prevent this issue from occurring in the future?** We will expire caches more quickly in the development environment for synthetic tests to identify potential problems prior to deployment to the production environment.
  • Time: Sept. 19, 2023, 10:04 p.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: Sept. 19, 2023, 9:50 p.m.
    Status: Monitoring
    Update: A fix has been implemented and we are monitoring the results.
  • Time: Sept. 19, 2023, 9:40 p.m.
    Status: Identified
    Update: The issue has been identified and a fix is being implemented.
  • Time: Sept. 19, 2023, 9:36 p.m.
    Status: Investigating
    Update: We are currently investigating this issue.

Updates:

  • Time: Sept. 21, 2023, 9:32 p.m.
    Status: Postmortem
    Update: **What products were affected and what was the impact?** Our Landed Cost APIs \(GraphQL\) were impacted. Impact: MAJOR OUTAGE   **What timeframe did this issue occur?** |   | **Date** | **Time** | | --- | --- | --- | | From: | Sep 19, 2023 | 15:30 MST | | To: | Sep 19, 2023 | 15:44 MST |   **How was the issue detected?** Error rates triggered alarm monitors. **What functionality was affected?** Landed cost quotes for some stores could not be returned. ‌ **What problems did this cause?** Some merchants were unable to retrieve landed cost quotes. ‌ **What was the resolution of the problem and steps that are being taken for continued follow-up?** We discovered a configuration error in a previous release. Due to caching, scheduled synthetic test failures in the development environment lagged behind the deployment to the production environment. We fixed the configuration error, released the fix, and confirmed issue resolution via manual and automated testing. **What mitigation solutions will we put in place to prevent this issue from occurring in the future?** We will expire caches more quickly in the development environment for synthetic tests to identify potential problems prior to deployment to the production environment.
  • Time: Sept. 19, 2023, 10:04 p.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: Sept. 19, 2023, 9:50 p.m.
    Status: Monitoring
    Update: A fix has been implemented and we are monitoring the results.
  • Time: Sept. 19, 2023, 9:40 p.m.
    Status: Identified
    Update: The issue has been identified and a fix is being implemented.
  • Time: Sept. 19, 2023, 9:36 p.m.
    Status: Investigating
    Update: We are currently investigating this issue.

Updates:

  • Time: Aug. 22, 2023, 11 p.m.
    Status: Postmortem
    Update: **What products were affected and what was the impact?** Our Landed Cost APIs \(REST and GraphQL\) were impacted. During the outage, all API requests were unauthorized. Impact: MAJOR OUTAGE   **What timeframe did this issue occur?** |   | **Date** | **Time** | | --- | --- | --- | | From: | August 15, 2023 | 10:40 MST | | To: | August 15, 2023 | 11:02 MST |   **How was the issue detected?** We were immediately alerted by our monitoring system. **What functionality was affected?** No landed cost quotes could be returned due to authentication failures. ‌ **What problems did this cause?** wrong auth URL. used the discovery instead of the public. ‌ **What was the resolution of the problem and steps that are being taken for continued follow-up?** We discovered a configuration error in a previous release. We fixed the configuration error, released the fix, and confirmed issue resolution via manual and automated testing. **What mitigation solutions will we put in place to prevent this issue from occurring in the future?** We are improving documentation on environment configuration, and clarifying how to properly configure service discovery. We are also improving testing procedures to catch similar issues before they are introduced into production.
  • Time: Aug. 22, 2023, 11 p.m.
    Status: Postmortem
    Update: **What products were affected and what was the impact?** Our Landed Cost APIs \(REST and GraphQL\) were impacted. During the outage, all API requests were unauthorized. Impact: MAJOR OUTAGE   **What timeframe did this issue occur?** |   | **Date** | **Time** | | --- | --- | --- | | From: | August 15, 2023 | 10:40 MST | | To: | August 15, 2023 | 11:02 MST |   **How was the issue detected?** We were immediately alerted by our monitoring system. **What functionality was affected?** No landed cost quotes could be returned due to authentication failures. ‌ **What problems did this cause?** wrong auth URL. used the discovery instead of the public. ‌ **What was the resolution of the problem and steps that are being taken for continued follow-up?** We discovered a configuration error in a previous release. We fixed the configuration error, released the fix, and confirmed issue resolution via manual and automated testing. **What mitigation solutions will we put in place to prevent this issue from occurring in the future?** We are improving documentation on environment configuration, and clarifying how to properly configure service discovery. We are also improving testing procedures to catch similar issues before they are introduced into production.
  • Time: Aug. 22, 2023, 5:18 p.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: Aug. 22, 2023, 5:18 p.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: Aug. 22, 2023, 5:02 p.m.
    Status: Monitoring
    Update: We are continuing to monitor for any further issues.
  • Time: Aug. 22, 2023, 5:02 p.m.
    Status: Monitoring
    Update: We are continuing to monitor for any further issues.
  • Time: Aug. 22, 2023, 5:02 p.m.
    Status: Monitoring
    Update: A fix has been implemented and we are monitoring the results.
  • Time: Aug. 22, 2023, 5:02 p.m.
    Status: Monitoring
    Update: A fix has been implemented and we are monitoring the results.
  • Time: Aug. 22, 2023, 4:54 p.m.
    Status: Identified
    Update: The issue has been identified and a fix is being implemented.
  • Time: Aug. 22, 2023, 4:54 p.m.
    Status: Identified
    Update: The issue has been identified and a fix is being implemented.
  • Time: Aug. 22, 2023, 4:51 p.m.
    Status: Investigating
    Update: We are currently investigating this issue.
  • Time: Aug. 22, 2023, 4:51 p.m.
    Status: Investigating
    Update: We are currently investigating this issue.

Check the status of similar companies and alternatives to Zonos

NetSuite
NetSuite

Systems Active

ZoomInfo
ZoomInfo

Systems Active

SPS Commerce
SPS Commerce

Systems Active

Miro
Miro

Systems Active

Field Nation
Field Nation

Systems Active

Outreach
Outreach

Systems Active

Own Company

Systems Active

Mindbody
Mindbody

Systems Active

TaskRabbit
TaskRabbit

Systems Active

Nextiva
Nextiva

Systems Active

6Sense

Systems Active

BigCommerce
BigCommerce

Systems Active

Frequently Asked Questions - Zonos

Is there a Zonos outage?
The current status of Zonos is: Systems Active
Where can I find the official status page of Zonos?
The official status page for Zonos is here
How can I get notified if Zonos is down or experiencing an outage?
To get notified of any status changes to Zonos, simply sign up to OutLogger's free monitoring service. OutLogger checks the official status of Zonos every few minutes and will notify you of any changes. You can veiw the status of all your cloud vendors in one dashboard. Sign up here
What does Zonos do?
Zonos streamlines global trade and delivery through cross-border APIs and tax apps, enabling companies to sell abroad with ease.