Shippo incident: UPS Service Degradation

Affected components

• UPS

1. resolvedOct 5, 2026, 12:40 UTC

   This incident has been resolved.

2. investigatingOct 4, 2026, 23:56 UTC

   We are experiencing an interruption in UPS tracking events from the carrier. Our team has reached out to UPS and is actively monitoring the situation. During this time, tracking updates may be delayed but will be sent once the carrier's API is restored

What APIStatus.watch saw

• Oct 4, 2026, 23:58 UTCoperational → degraded
• Oct 5, 2026, 12:43 UTCdegraded → operational

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• OVHcloud: [GRA][Storage] - Object Storage S3 incident notificationMajor · Oct 3, 2026, 03:06 UTC
• Akamai: Origin Server Connectivity Issues with Elevated Errors in APAC RegionMinor · Sep 22, 2026, 14:28 UTC
• Cloudflare: Cloudflare One Clients are incorrectly challenged on some sitesMinor · Sep 22, 2026, 19:23 UTC
• Zoom: Service Degradation Affecting Customer Using Polycom Devices Going OfflineMinor · Sep 25, 2026, 17:45 UTC
• Twilio: MMS Delivery Delays from a Subset of Twilio Long Codes to GCI United StatesMinor · Sep 26, 2026, 03:16 UTC
• Clerk: Development instances only - Apple rejecting emailsMinor · Sep 28, 2026, 15:23 UTC
• Supabase: Intermittent latency in Eastern USMinor · Sep 29, 2026, 16:26 UTC
• Cloudflare: Issues with Workers Build failing to startMinor · Oct 3, 2026, 05:54 UTC
• Snyk: Issues API V3 Service - DegradedMinor · Oct 3, 2026, 19:49 UTC
• Zoom: Service Degradation Affecting Zoom Rooms Management and Workspaces Management in SA01.Minor · Oct 4, 2026, 23:19 UTC

How often does Shippo have incidents?

Shippo reported 75 incidents in the last 90 days, 48 of them major or critical. A typical incident lasted 2h 27m. See Shippo's uptime and incident history