Shippo outage: Axlehire Shipment and Tracking Outage

Affected components

• Axlehire

1. resolvedSep 24, 2026, 11:49 UTC

   This incident has been resolved.

2. investigatingSep 24, 2026, 08:51 UTC

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

What APIStatus.watch saw

• Sep 24, 2026, 08:00 UTCoperational → degraded
• Sep 24, 2026, 08:55 UTCdegraded → partial outage
• Sep 24, 2026, 09:00 UTCpartial outage → operational

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Supabase: Permission errors in the Supabase DashboardCritical · Sep 24, 2026, 10:37 UTC
• OVHcloud: [EU-WEST-PAR][Network] - Public network incident notificationMajor · Sep 23, 2026, 14:28 UTC
• OVHcloud: [EU-WEST-PAR][Containers & Orchestration] - Managed Kubernetes Service incident notificationMajor · Sep 23, 2026, 14:57 UTC
• OVHcloud: [EU-SOUTH-MIL-B][Public Cloud] - Block Storage incident notificationMajor · Sep 24, 2026, 09:07 UTC
• Twilio: Voice Call Failures from a Subset of Twilio Phone Numbers to Hong KongMinor · Sep 12, 2026, 00:16 UTC
• Twilio: SMS Delivery Receipt Delays from a Subset of Twilio Short Codes to Liberty Mobile Puerto RicoMinor · Sep 20, 2026, 17:47 UTC
• Twilio: Voice Call Post Dial Delay from Twilio Phone Numbers to Jazz PakistanMinor · Sep 21, 2026, 06:10 UTC
• Akamai: Increased latency during upstream provider maintenance in Singapore, Hong Kong, and JapanMinor · Sep 22, 2026, 00:30 UTC
• Akamai: Origin Server Connectivity Issues with Elevated Errors in APAC RegionMinor · Sep 22, 2026, 14:28 UTC
• Hugging Face: Slower downloads in the Asia-Pacific regionMinor · Sep 22, 2026, 18:48 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