Shippo outage: Elevated error rate on Third party vendor Tracking API

Affected components

• Pitney Bowes

1. resolvedAug 25, 2026, 14:27 UTC

   This incident has been resolved.

2. investigatingAug 25, 2026, 05:18 UTC

   We are experiencing some issues in the tracking API with Third party vendor. We have reached out to the carrier and are actively monitoring the status of these issues. We will provide further updates soon.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Shippo's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• DigitalOcean: Cloud Control Panel and APICritical · Aug 24, 2026, 17:14 UTC
• Confluent Cloud: Elevated error rates and latencies in Azure Southeast Asia regionMajor · Aug 25, 2026, 04:17 UTC
• OVHcloud: [GRA5/6/7/8/9/11][Compute - Instance] - Instance incident notificationMajor · Aug 25, 2026, 06:24 UTC
• Confluence: Notifications are delayedMajor · Aug 25, 2026, 08:42 UTC
• Supabase: 401 errors due to JWT rejectionsMinor · Aug 14, 2026, 02:23 UTC
• Telnyx: Programmable Wireless data loss in AustraliaMinor · Aug 17, 2026, 19:27 UTC
• Akamai: Reporting data availability issues in 'Traffic by Hostname' reportMinor · Aug 20, 2026, 16:43 UTC
• Sentry: Errors alerting degraded in US regionMinor · Aug 25, 2026, 09:38 UTC
• Grafana Cloud: Incident Management unavailable in US CentralMinor · Aug 25, 2026, 10:39 UTC

How often does Shippo have incidents?

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