Shippo: Elevated error rate on FedEx Transaction & shipment service

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 15m it lasted.
Anything that failed between 2026-06-26 16:48 UTC and 2026-06-26 19:02 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.

investigatingJun 26, 2026, 4:48 PM UTC
We are currently experiencing an elevated error rate affecting label generation for FedEx BYOA account. Our team is actively investigating the issue ,We will share further updates as soon as they are available.
provider
identifiedJun 26, 2026, 5:17 PM UTC
FedEx confirmed they are having multiple issue on their rest API service , we are closely working with carrier for resolution
provider
monitoringJun 26, 2026, 6:12 PM UTC
A fix has been implemented and we are monitoring the results.
provider
monitoringJun 26, 2026, 6:57 PM UTC
We are continuing to monitor for any further issues.
provider
resolvedJun 26, 2026, 7:02 PM UTC
This incident has been resolved.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Is Shippo still down?

No, this incident was resolved 2026-06-26 19:02 UTC. For Shippo's live state, see https://down.guide/shippo.

How long did it last?

2h 15m, from 2026-06-26 16:48 UTC to 2026-06-26 19:02 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.