- Level
- confirmed
- Worst impact
- Degraded
- Components
- Veho
What to do
Check whether you use Shippo Veho. 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 19h 8m it lasted.
Anything that failed between 2026-10-20 20:40 UTC and 2026-10-21 15:48 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 are investigating degraded performance affecting the Veho integration. We are monitoring the situation and will provide updates as more information becomes available.
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-ad5026541e
Is Shippo still down?
No, this incident was resolved 2026-10-21 15:48 UTC. For Shippo's live state, see https://down.guide/shippo.
How long did it last?
19h 8m, from 2026-10-20 20:40 UTC to 2026-10-21 15:48 UTC, by the times Shippo posted.
What was affected?
Shippo named Veho.
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.