- Level
- confirmed
- Worst impact
- Partial outage
- Components
- USPS
What to do
Check whether you use Shippo USPS. 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 43m it lasted.
Anything that failed between 2026-08-20 11:12 UTC and 2026-08-20 11:55 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
- investigating
We have detected an elevated error rate from USPS Shipment API. Our team has contacted the carrier and we are monitoring the situation. During this time, rates will be unavailable please retry once the carrier's API is restored.
provider
- resolved
The issue has been resolved and the service is operating normally.
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-0b9b6ba435
Is Shippo still down?
No, this incident was resolved 2026-08-20 11:55 UTC. For Shippo's live state, see https://down.guide/shippo.
How long did it last?
43m, from 2026-08-20 11:12 UTC to 2026-08-20 11:55 UTC, by the times Shippo posted.
What was affected?
Shippo named USPS.
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.