Shippo incident: Royal Mail InterSoft Tracking Degradation (Third-Party Issue)

1. resolvedMay 18, 2026, 16:54 UTC

   This incident has been resolved.

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.

• GitHub: Incident with ActionsCritical · May 5, 2026, 13:37 UTC
• Netlify: Agent Runner failures on new projectsCritical · May 5, 2026, 20:53 UTC
• GitHub: Disruption with some GitHub servicesCritical · May 6, 2026, 11:21 UTC
• GitHub: Incident with Pull RequestsCritical · May 6, 2026, 15:25 UTC
• GitHub: CCR and CCA failing to start for PR commentsCritical · May 7, 2026, 05:02 UTC
• Grafana Cloud: Metrics read errors in prod-ap-south-1 regionCritical · May 7, 2026, 07:18 UTC
• ReadMe: Issues Creating New ChangelogsCritical · May 7, 2026, 23:43 UTC
• Datadog: Delayed Monitors NotificationsCritical · May 8, 2026, 00:06 UTC
• Upstash: QStash US Region Service DisruptionCritical · May 8, 2026, 09:46 UTC
• Cursor: Degraded Agent PerformanceCritical · May 12, 2026, 02:24 UTC

How often does Shippo have incidents?

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