- Level
- confirmed
- Worst impact
- Degraded
- Components
- FedEx
What to do
Check whether you use EasyPost 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 4h 37m it lasted.
Anything that failed between 2025-10-27 16:18 UTC and 2025-10-27 20:55 UTC may need a replay.Subscribe to EasyPost's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=easypost works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from EasyPost 4
- investigating
We are currently investigating this issue.
provider
- monitoring
FedEx APIs have been returning elevated error rates and slower than normal responses, but look to be recovering. We will continue to monitor.
provider
- monitoring
FedEx API performance has largely recovered, however error rates are still elevated and we are still experiencing occasional periods of high p95 and rating timeouts.
provider
- resolved
FedEx API has returned to normal error rates and response times.
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-1fe8074b26
Is EasyPost still down?
No, this incident was resolved 2025-10-27 20:55 UTC. For EasyPost's live state, see https://down.guide/easypost.
How long did it last?
4h 37m, from 2025-10-27 16:18 UTC to 2025-10-27 20:55 UTC, by the times EasyPost posted.
What was affected?
EasyPost named FedEx.
What caused it?
EasyPost hasn't published a root cause. If it does, it shows here.
Where does this come from?
EasyPost's official status page, https://www.easypoststatus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.