Is Zonos down?

Last checked 1m ago
Current status
Zonos is up

No incidents right now.

Official status page: https://status.zonos.com · Polled every 5 minutes · 15 components tracked

Zonos is operational right now. Last checked 1m ago; the most recent incident resolved 9d ago.

Real-time Zonos status, recent outages, and incident history — pulled directly from Zonos's official status page at https://status.zonos.com every 5 minutes. Pingoru tracks 15 Zonos services and has captured 4 incidents in the last 90 days (98.63% uptime). Get email, Slack, Discord, or webhook alerts the moment Zonos reports a new incident — free for 5 monitors, no credit card.

Users who monitor Zonos also follow these eCommerce services: Shopify Stripe PayPal Blackbaud NetSuite Squarespace BigCommerce Cybersource Gorgias PayFast View all 6,000+ providers
Zonos uptime 98.63% uptime · past 90 days
Mon Wed Fri
JunJulAugSep
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 59m
    Started Sep 04, 2026, 11:56 PM UTC · Resolved Sep 05, 2026, 12:56 AM UTC
    Classify
    Timeline · 4 updates
    • investigating · Sep 05, 2026, 12:08 AM UTC

      We are currently investigating this issue.

    • identified · Sep 05, 2026, 12:09 AM UTC

      The issue has been identified and a fix is being implemented.

    • monitoring · Sep 05, 2026, 12:21 AM UTC

      A fix has been implemented and we are monitoring the results.

    • resolved · Sep 05, 2026, 12:56 AM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  2. Resolved 42m
    Started Sep 04, 2026, 05:18 PM UTC · Resolved Sep 04, 2026, 06:00 PM UTC
    Classify
    Timeline · 4 updates
    • investigating · Sep 04, 2026, 05:29 PM UTC

      We are currently investigating this issue.

    • identified · Sep 04, 2026, 05:30 PM UTC

      The issue has been identified and a fix is being implemented.

    • monitoring · Sep 04, 2026, 05:30 PM UTC

      A fix has been implemented and we are monitoring the results.

    • resolved · Sep 04, 2026, 07:47 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  3. Resolved 1h 36m
    Started Aug 03, 2026, 09:00 PM UTC · Resolved Aug 03, 2026, 10:36 PM UTC
    Landed Cost APIInternational CheckoutShopify Duty TaxZonos Prepay (iOS)Landed Cost API (Legacy)BigCommerce Duty TaxZonos Prepay (Android)QuoterMagento Duty TaxLanded Cost API (GraphQL)
    Timeline · 8 updates
    • investigating · Aug 03, 2026, 09:23 PM UTC

      We are currently investigating this issue.

    • identified · Aug 03, 2026, 09:24 PM UTC

      The issue has been identified and a fix is being implemented.

    • identified · Aug 03, 2026, 09:36 PM UTC

      We are continuing to work on a fix for this issue.

    • identified · Aug 03, 2026, 09:57 PM UTC

      We are continuing to work on a fix for this issue.

    • monitoring · Aug 03, 2026, 09:57 PM UTC

      A fix has been implemented and we are monitoring the results.

    • monitoring · Aug 03, 2026, 10:36 PM UTC

      We are continuing to monitor for any further issues.

    • resolved · Aug 03, 2026, 10:36 PM UTC

      This incident has been resolved.

    • postmortem · Sep 09, 2026, 08:06 PM UTC

      ## **Incident Summary** On August 3, 2026, Zonos experienced elevated error rates affecting Landed Cost and related services. The incident began at approximately 2:52 PM MDT and was resolved at 3:51 PM MDT, resulting in approximately 59 minutes of degraded service. The incident was a partial outage: requests continued to be processed throughout the event, but a significant portion of requests relying on the affected service returned errors. ## **Impact** The primary affected service experienced an approximately 50% error rate for GraphQL requests during the incident window. As a result, customers using Landed Cost experienced intermittent request failures, while other requests continued to process successfully. Because Landed Cost relies on shared platform services, the underlying issue also resulted in elevated error rates across some related workflows. ## **Root Cause** The incident was triggered by a production deployment that began using a newly introduced data access path within our platform. Under production request volume, this access pattern generated significantly more database activity than anticipated. This exhausted available database connections within a supporting service and caused requests depending on that service to fail. The underlying issue had not manifested previously because the affected functionality had not yet been exercised at production scale. ## **Resolution** Our engineering team initially rolled back a related service deployment while investigating the source of the errors. When this did not resolve the issue, the Landed Cost deployment that activated the problematic access pattern was rolled back. Service recovered immediately following that rollback. A permanent correction was subsequently deployed to optimize the database access pattern and route the affected workload appropriately. ## **Preventive Actions** Following the incident, we reviewed both the immediate failure and how it propagated through dependent services. We are taking several actions to reduce the likelihood and potential impact of similar incidents, including: * Adding additional monitoring and alerting for database connection saturation. * Strengthening safeguards and review practices for database queries against partitioned data. * Expanding testing of newly activated data-access patterns under production-like load. * Reviewing service isolation and failure handling to reduce the impact a degraded dependency can have on other platform services. * Reviewing similar data-access patterns across the platform for the conditions identified during this incident. We apologize for the disruption this incident caused. We will continue using the findings from this event to improve the resilience and observability of the Zonos platform.

    Latest: ## **Incident Summary** On August 3, 2026, Zonos experienced elevated error rates affecting Landed Cost and related services. The incident began at approximately 2:52 PM MDT and wa…

  4. Resolved 2h 22m
    Started Jul 08, 2026, 07:15 PM UTC · Resolved Jul 08, 2026, 09:38 PM UTC
    Classify
    Timeline · 4 updates
    • investigating · Jul 08, 2026, 07:41 PM UTC

      We are currently investigating this issue.

    • identified · Jul 08, 2026, 07:42 PM UTC

      The issue has been identified and a fix is being implemented.

    • monitoring · Jul 08, 2026, 07:42 PM UTC

      A fix has been implemented and we are monitoring the results.

    • resolved · Jul 08, 2026, 09:00 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

Outage history

Past 90 days · 4 incidents View full outage history →