Shippo incident

Delayed posting of webhooks

Minor Resolved View vendor source →

Shippo experienced a minor incident on January 20, 2026 affecting Shippo REST API and Shippo Platform API, lasting 32m. The incident has been resolved; the full update timeline is below.

Started
Jan 20, 2026, 11:49 AM UTC
Resolved
Jan 20, 2026, 12:21 PM UTC
Duration
32m
Detected by Pingoru
Jan 20, 2026, 11:49 AM UTC

Affected components

Shippo REST APIShippo Platform API

Update timeline

  1. investigating Jan 20, 2026, 11:03 AM UTC

    we are currently investigating an issue causing elevated error rates (approximately 33%) impacting outbound tracking webhook updates. As a result, some tracking information may be delayed or temporarily unavailable. Our team is actively working to identify the root cause and resolve the issue.

  2. investigating Jan 20, 2026, 11:04 AM UTC

    We are continuing to investigate this issue.

  3. monitoring Jan 20, 2026, 11:49 AM UTC

    Monitoring – Outbound Tracking Service We have resolved the issue causing elevated error rates for new outbound tracking updates. Some previously affected tracking messages may still be delayed while we work through a backlog. We are monitoring the system closely and will provide another update once all impacted messages have been fully processed.

  4. resolved Jan 20, 2026, 12:21 PM UTC

    Resolved – Outbound Tracking Service The service has been restored and is operating normally, with no impact to new tracking updates. Some tracking updates entered a terminal state (e.g. delivered) during the incident and will require manual correction. We will follow up to resolve these remaining items, which are expected to be limited in scope.