Live  /  EasyPost  /  Incident

EasyPost: Elevated Errors Core API

EasyPost · easypost.comMajor incidentResolved2026-11-11 21:48 UTC
Public — what happened

Summary

EasyPost reported a major incident in which its Core API returned more errors than normal, starting at 21:22 UTC on 2026-11-11. The company said it had fixed the underlying problem and moved to monitoring the service. EasyPost marked the incident resolved at 21:48 UTC the same day, and it did not say who was affected or give further detail on the cause.

Affected

API

As listed on EasyPost’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 see
Customers 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 47, 2026, our weekly internet health report.

The full archive is on the EasyPost status & history page.

Related: EasyPost status & history. SquidGrid is not affiliated with EasyPost.