Shippo outage: Elevated error rate on Deutsche Post Transaction API

Affected components

• Deutsche Post

1. resolvedSep 1, 2026, 00:26 UTC

   This incident has been resolved.

2. monitoringAug 31, 2026, 23:58 UTC

   We are beginning to see recovery on the carrier's end; however, we have not yet received confirmation from Deutsche Post. We will continue to monitor the situation and share an update as soon as we have more information

3. monitoringAug 31, 2026, 23:58 UTC

   A fix has been implemented and we are monitoring the results.

4. investigatingAug 31, 2026, 23:16 UTC

   We have detected an elevated error rate from Deutsche Post Transaction API. Our team has contacted the carrier and we are monitoring the situation. During this time, Label generation will be unavailable please retry once the carrier's API is restored.

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.

• Discord: Some servers and other services (voice calls, activities) not available for some usersMajor · Aug 31, 2026, 22:54 UTC
• OVHcloud: [EU-SOUTH-MIL][Containers & Orchestration] - Managed Private Registry incident notificationMinor · Aug 26, 2026, 15:00 UTC
• Snowflake: INC20000150Minor · Aug 28, 2026, 00:07 UTC
• Snyk: Partial Broker Service DegradationMinor · Aug 30, 2026, 14:32 UTC
• Zoom: Service Degradation Affecting Zoom Node.Minor · Sep 1, 2026, 00:11 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