- Level
- confirmed
- Worst impact
- Partial outage
- Components
- UPS
What to do
Check whether you use Shippo UPS. 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 3h 25m it lasted.
Anything that failed between 2026-05-08 16:46 UTC and 2026-05-08 20:11 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 3
- investigating
As of 16:30 UTC, the majority of Shippo's UPS authentication token renewal requests have failed over the past 75 minutes, causing intermittent errors with UPS rate quotes and label generation for accounts that use UPS. Shippo engineering is in active contact with UPS to coordinate a resolution and is reviewing token renewal patterns on our side.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
provider
- 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-c160903336
Is Shippo still down?
No, this incident was resolved 2026-05-08 20:11 UTC. For Shippo's live state, see https://down.guide/shippo.
How long did it last?
3h 25m, from 2026-05-08 16:46 UTC to 2026-05-08 20:11 UTC, by the times Shippo posted.
What was affected?
Shippo named UPS.
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.