Live / EasyPost / Incident
EasyPost: Degraded UPS performance
EasyPost · easypost.comResolved2026-10-08 16:58 UTC
Public — what happened
Summary
EasyPost reported on October 8, 2026 that requests involving the carrier UPS were timing out more often than usual, starting at 15:45 UTC. By 16:28 UTC, the company said it had found the cause, though it did not describe it, and noted that UPS shipping rate lookups and package tracking were the affected functions. EasyPost marked the incident as resolved at 16:58 UTC.
Affected
UPS, UPSDAP
Timeline
- Started — 2026-10-08 15:45 UTC
- Investigating — 2026-10-08 15:45 UTC
- Identified — 2026-10-08 16:28 UTC
- Resolved — 2026-10-08 16:58 UTC · 1h 13m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach EasyPost against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for EasyPost: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the EasyPost report →
More from EasyPost
Covered in The Squid’s Ink, Week 42, 2026, our weekly internet health report.