Skip to main content
Shippo

OnTrac Service Degradation

Degraded Lasted 37m · started · Shippo's page

Level
confirmed
Worst impact
Degraded
Components
OnTrac

What to do

  • Check whether you use Shippo OnTrac. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 37m it lasted.

    Anything that failed between 2026-10-21 02:39 UTC and 2026-10-21 03:15 UTC may need a replay.
  • Subscribe to Shippo's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=shippo works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Shippo 2

  1. investigating

    Hi Team, we are currently observing an elevated error rate on OnTrac's Transaction API. Label generation will be unavailable; tracking and rating are not impacted. We have reached out to OnTrac and are actively monitoring the situation. We will provide a further update as soon as we receive one from the carrier.

    provider

  2. resolved

    This incident has been resolved.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-da71c225e1

Is Shippo still down?

No, this incident was resolved 2026-10-21 03:15 UTC. For Shippo's live state, see https://down.guide/shippo.

How long did it last?

37m, from 2026-10-21 02:39 UTC to 2026-10-21 03:15 UTC, by the times Shippo posted.

What was affected?

Shippo named OnTrac.

What caused it?

Shippo hasn't published a root cause. If it does, it shows here.

Where does this come from?

Shippo's official status page, https://status.goshippo.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.