- Level
- confirmed
- Worst impact
- Degraded
- Components
- UPS
- Regions
- us
What to do
Check whether you use EasyPost UPS in us. 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 5m it lasted.
Anything that failed between 2026-07-08 20:38 UTC and 2026-07-09 00:43 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 3
- identified
UPS operations are degraded due to rate limiting by UPS. We are aware and monitoring the status.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
provider
- resolved
UPS operations have returned to normal. Some impacted customers may need to re-authenticate their BYOA accounts. See https://support.easypost.com/hc/en-us/articles/26635027512717-UPS-OAuth-2-0-Update#:~:text=Account%20Authorization for more details.
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-71f75ee325
Is EasyPost still down?
No, this incident was resolved 2026-07-09 00:43 UTC. For EasyPost's live state, see https://down.guide/easypost.
How long did it last?
4h 5m, from 2026-07-08 20:38 UTC to 2026-07-09 00:43 UTC, by the times EasyPost posted.
What was affected?
EasyPost named UPS in us.
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.