Is there an Zonos outage?
Zonos status: Systems Active
Last checked: 7 minutes ago
Get notified about any outages, downtime or incidents for Zonos and 1800+ other cloud vendors. Monitor 10 companies, for free.
Last checked: 7 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: Aug. 30, 2024, 5:02 p.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Minor | Started At: Aug. 7, 2024, 7:22 p.m.
Description: **What products were affected and what was the impact?** * All non-legacy products Impact: MAJOR OUTAGE **What timeframe did this issue occur?** | | **Date** | **Time** | | --- | --- | --- | | From: | Aug 5, 2024 | 14:31 MST | | To: | Aug 5, 2024 | 14:48 MST | **How was the issue detected?** Synthetic tests began failing which notified our DevOps team. **What functionality was affected?** Queries to the database were degraded and eventually became unsuccessful. **What problems did this cause?** All non-legacy services experienced degraded performance and a brief major outage where all database queries failed. **What was the resolution of the problem and steps that are being taken for continued follow-up?** The incident was caused by storage exhaustion on one of our production database clusters. We normally have autoscaling and alerting configured on our database clusters; however, in this case the cluster was created as part of a migration, and the proper alerting was not configured. The incident was resolved by allocating additional storage capacity to the affected database cluster. **What mitigation solutions will we put in place to prevent this issue from occurring in the future?** To prevent similar incidents in the future, we are conducting a thorough audit of our infrastructure inventory. This includes reviewing system health and monitoring configurations to ensure proper alerting and maximum visibility into critical infrastructure metrics.
Status: Postmortem
Impact: Critical | Started At: Aug. 5, 2024, 8:30 p.m.
Description: This incident has been resolved.
Status: Resolved
Impact: None | Started At: March 21, 2024, 4:21 p.m.
Description: This incident has been resolved.
Status: Resolved
Impact: None | Started At: March 21, 2024, 4:21 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.
