- Level
- confirmed
- Worst impact
- Partial outage
- Components
- FedEx
Summary
Shippo says it is investigating a spike in errors on FedEx's Address Validation API, detected through its internal monitoring system. The provider says it is still analyzing the impact and has contacted the carrier.
Written by anthropic/claude-haiku-5.5 from Shippo's own updates.
What to do
Check whether you use Shippo FedEx. 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 51m it lasted.
Anything that failed between 2026-11-07 04:33 UTC and 2026-11-07 07:24 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’re seeing a spike in errors on FedEx’s Address Validation API detected through our internal monitoring system. Impact: Our team is still analyzing the impact. We’ve reached out to the carrier. We’ll update you as soon as we have more information.
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-264a65e68b
Is Shippo still down?
No, this incident was resolved 2026-11-07 07:24 UTC. For Shippo's live state, see https://down.guide/shippo.
How long did it last?
2h 51m, from 2026-11-07 04:33 UTC to 2026-11-07 07:24 UTC, by the times Shippo posted.
What was affected?
Shippo named FedEx.
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.