- Level
- confirmed
- Worst impact
- Degraded
- Components
- UPS
What to do
Check whether you use EasyPost UPS. 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 5h 7m it lasted.
Anything that failed between 2025-06-24 15:26 UTC and 2025-06-24 20:33 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
EasyPost is seeing issues with the UPS. We are investigating and communicating with UPS and will provide updates. We apologize for the inconvenience.
provider
- identified
Engineers have identified the slowdowns. Our next update will be at 11:AM PST.
provider
- identified
Our engineers our continuing to work on a fix. We apologize for the inconvenience.
provider
- resolved
Our systems have been stable for the past few hours. We will notify if anything changes.
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-12aa038b79
Is EasyPost still down?
No, this incident was resolved 2025-06-24 20:33 UTC. For EasyPost's live state, see https://down.guide/easypost.
How long did it last?
5h 7m, from 2025-06-24 15:26 UTC to 2025-06-24 20:33 UTC, by the times EasyPost posted.
What was affected?
EasyPost named UPS.
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.