Is there an Zonos outage?
Zonos status: Systems Active
Last checked: 3 minutes ago
Get notified about any outages, downtime or incidents for Zonos and 1800+ other cloud vendors. Monitor 10 companies, for free.
Last checked: 3 minutes ago
Get notified about any outages, downtime or incidents for Zonos and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for Zonos.
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 NowOutlogger tracks the status of these components for Xero:
| Component | Status |
|---|---|
| Classify | Active |
| Dashboard | Active |
| International Checkout | Active |
| Quoter | Active |
| Landed Cost | Active |
| Landed Cost API | Active |
| Landed Cost API (GraphQL) | Active |
| Landed Cost API (Legacy) | Active |
| Plugins | Active |
| BigCommerce Duty Tax | Active |
| Magento Duty Tax | Active |
| Salesforce Duty Tax | Active |
| Shopify Checkout | Active |
| Shopify Duty Tax | Active |
View the latest incidents for Zonos and check for official updates:
Description: This incident has been resolved.
Status: Resolved
Impact: Major | Started At: Nov. 12, 2024, 8:27 p.m.
Description: ### What products were affected and what was the impact? Landed Cost API, Checkout Impact: CRITICAL ### What timeframe did this issue occur? | **Date** | **Time** | | --- | --- | | November 8, 2024 | 8:50am - 10:26am MST | ### How was the issue detected? A spike in error logs triggered an alert to our Engineering team, who responded immediately to the issue. ### What functionality was affected? Landed Cost quotes that use our automated item classification service failed. ### What problems did this cause? If an HS Code was not provided in the API request to Landed Cost, and the automatic classification service was enabled, then the landed cost quote would fail. When the landed cost quote fails, shoppers may not be able to place their order. ### What was the resolution of the problem and steps that are being taken for continued follow-up? The root cause of the issue was a deployment issue with the item service used for automatic classification. While the issue was detected immediately, resolution required rebuilding and redeploying services, which took longer than expected. After services were rebuilt and redeployed, the system health was validated and normal operations resumed. ### What mitigation solutions will we put in place to prevent this issue from occurring in the future? We discovered that this issue was due, in part, to a deficiency in our deployment procedures. We are working to update the procedure to prevent any future issues. We are also creating a synthetic test in our lower environments that will catch similar issues before they can be deployed into production.
Status: Postmortem
Impact: Major | Started At: Nov. 8, 2024, 4 p.m.
Description: **What products were affected and what was the impact?** On **Saturday, October 12, 2024, at 22:30 UTC**, we experienced an outage that impacted the ability of some Shopify merchants to retrieve landed cost quotes for international orders. This outage lasted until **Sunday, October 13, 2024, at 21:33 UTC**, during which time affected merchants may have been unable to display accurate landed cost calculations to their customers, potentially affecting international checkouts and purchase completions. The root cause of the outage was an API permission issue that was introduced during a routine deployment. Unfortunately, the synthetic tests for the Landed Cost API flow didn’t immediately flag the issue, which caused an extremely uncharacteristic delay to the resolution. It's important to note that this issue was caused by a very unique set of circumstances. We have just finished an extremely complex and expansive migration project to move all of our merchants to a robust and secure new system. This issue was directly caused by processes related to this now complete migration. Impact: critical **What timeframe did this issue occur?** | **Date** | **Time** | | --- | --- | | October 12, 2024 | 22:30 UTC | | October 13, 2024 | 21:33 UTC | **How was the issue detected?** The engineering team noticed a warning of failed quotes in the log files. **What functionality was affected?** All landed cost requests during the outage failed for affected merchants. **What problems did this cause?** Shoppers of affected merchants were unable to get landed cost quotes, and in many cases complete their checkout. **What was the resolution of the problem and steps that are being taken for continued follow-up?** Once the issue was identified, our team acted swiftly to permission issue. After thorough testing, we confirmed the API was fully restored at **21:33 UTC** on Sunday. **What mitigation solutions will we put in place to prevent this issue from occurring in the future?** * **Expanded test coverage**: We are enhancing our synthetic tests to include additional token and permission checks, ensuring that potential issues like this are caught earlier. * **Improved log classifications**: We’re updating our logging processes to better distinguish between warnings and errors, which will enable faster detection and resolution of similar problems in the future.
Status: Postmortem
Impact: Critical | Started At: Oct. 12, 2024, 8:30 p.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Minor | Started At: Oct. 8, 2024, 1:48 a.m.
Description: ### **What products were affected and what was the impact?** * Landed Cost API ### Impact: * DEGRADED SERVICE ### **What timeframe did this issue occur?** | | **Date** | **Time** | | --- | --- | --- | | From: | Sep 30, 2024 | 16:44 MST | | To: | Sep 30, 2024 | 18:12 MST | ### **How was the issue detected?** Synthetic test failures alerted our team. ### **What functionality was affected?** Increased latency on landed cost quotes, plus a period where landed cost quotes failed. ### **What problems did this cause?** Landed cost quotes were slow to return and/or failed to return. ### **What was the resolution of the problem and steps that are being taken for continued follow-up?** The problem was caused by a very large message added to our message queue that could not be consumed due to insufficient resources. The immediate resolution was to increase maximum allocated memory to allow the message queue to clear. ### **What mitigation solutions will we put in place to prevent this issue from occurring in the future?** To prevent this from happening again, we have decreased the total allowed message size by both the producers and consumers. We are also evaluating techniques to make the message queue more robust to this type of failure.
Status: Postmortem
Impact: Major | Started At: Sept. 30, 2024, 10:44 p.m.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.
