Live  /  Shippo  /  Incident

Shippo: UPS Transaction Service Degradation

Shippo · goshippo.comMajor incidentResolved2026-11-01 10:22 UTC
Public — what happened

Summary

Shippo reported a major incident beginning at 09:50 UTC on 2026-11-01, in which it saw a higher-than-normal rate of errors with UPS's Transaction API. Shippo said this meant shipping labels could not be created, and that it had contacted UPS and was monitoring while waiting for word from the carrier. The incident is marked resolved as of 10:22 UTC, though the text provided does not say what was done to fix it.

Affected

UPS

As listed on Shippo’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 Shippo 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 Shippo: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Shippo report →

More from Shippo

Covered in The Squid’s Ink, Week 45, 2026, our weekly internet health report.

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

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