
Shippo Status
Real-time updates of Shippo issues and outages
Shippo status is Minor Service Outage
Shippo Carrier API
Canada Post
Correos
Deutsche Post
parcel_perform
You're checking on Shippo - but is your own site converting?
Outages aren't the only thing that costs you visitors.
Get a visual audit that shows exactly where your site loses conversions.
Free, takes 2 minutes.
Active Incidents
We have detected an elevated error rate from Canada Post Shipment API. We have reached out to the carrier and are actively monitoring the status of this issue and will keep you posted on this.
Recently Resolved Incidents
We are experiencing an interruption in Correos tracking events from the carrier. Our team has reached out to them 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.
We have detected an elevated error rate from Deutche 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.
Shippo Outage Survival Guide
Shippo Components
Shippo REST API
Shippo Web Dashboard
Shippo Carrier API
USPS
UPS
FedEx
Airterra
APC Postal
APG
Aramex
Asendia US
Australia Post
Axlehire
Better Trucks
Canada Post
We have detected an elevated error rate from Canada Post Shipment API. We have reached out to the carrier and are actively monitoring the status of this issue and will keep you posted on this.
CDL
Chronopost
Colissimo
Correos
We are experiencing an interruption in Correos tracking events from the carrier. Our team has reached out to them 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.
CouriersPlease
Deutsche Post
We have detected an elevated error rate from Deutche 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.