Skip to main content
Shippo

APG Tracking disruption

Partial outage Lasted 2h 32m · started · Shippo's page

Level
confirmed
Worst impact
Partial outage
Components
APG
Down Index
29of 100

What to do

  • Check whether you use Shippo APG. 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 2h 32m it lasted.

    Anything that failed between 2026-09-05 19:12 UTC and 2026-09-05 21:44 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

    We are experiencing an interruption in APG tracking events from the carrier. Our team has reached out to APG and is actively monitoring the situation. During this time, tracking updates may be delayed but will be sent once the carrier's API is restored.

    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-0ccdd553c5

Is Shippo still down?

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

How long did it last?

2h 32m, from 2026-09-05 19:12 UTC to 2026-09-05 21:44 UTC, by the times Shippo posted.

What was affected?

Shippo named APG.

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.