Shippo Status
Real-time updates of Shippo issues and outages
Shippo status is Operational
Correos
EVRi
GLS
La Poste
Royal Mail (Storefeeder)
Active Incidents
No active incidents
Recently Resolved Incidents
We have detected an elevated error rate from Correos's Tracking API. Our team has contacted the carrier and we are 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 EVRi Transaction API. Our team has contacted the carrier, and we are monitoring the situation.
We have detected an elevated error rate from GLS's shipment API. Our team has contacted the carrier, and we are monitoring the situation.
We have detected an elevated error rate from GLS_US's Shipment API. Our team has contacted the carrier and we are monitoring the situation.
We have detected an elevated error rate from LaPoste Tracking API. Our team has contacted the carrier and we are 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 Royal_mail_sf Tracking API. Our team has contacted the carrier and we are monitoring the situation. During this time, tracking updates may be delayed but will be sent once the carrier’s API is restored
Shippo Outage Survival Guide
Shippo Components
Shippo REST API
Shippo Web Dashboard
Shippo Carrier APIs
USPS
UPS
FedEx
Airterra
APC Postal
APG
Aramex
Asendia US
Australia Post
Axlehire
Better Trucks
Canada Post
CDL
Chronopost
Colissimo
Correos
We have detected an elevated error rate from Correos's Tracking API. Our team has contacted the carrier and we are 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
DHL eCommerce
DHL Express
DHL Germany
DPD DE
DPD UK
ePost Global
EVRi
We have detected an elevated error rate from EVRi Transaction API. Our team has contacted the carrier, and we are monitoring the situation.
Globegistics
Fastway Australia
GLS
We have detected an elevated error rate from GLS_US's Shipment API. Our team has contacted the carrier and we are monitoring the situation.
We have detected an elevated error rate from GLS's shipment API. Our team has contacted the carrier, and we are monitoring the situation.
La Poste
We have detected an elevated error rate from LaPoste Tracking API. Our team has contacted the carrier and we are monitoring the situation. During this time, tracking updates may be delayed but will be sent once the carrier’s API is restored
Lasership
LSO
Mondial Relay
Maergo
OnTrac
OrangeDS
Passport
Newgistics
Pitney Bowes
Poste Italiane
Purolator
Royal Mail (InterSoft)
Royal Mail (Storefeeder)
We have detected an elevated error rate from Royal_mail_sf Tracking API. Our team has contacted the carrier and we are monitoring the situation. During this time, tracking updates may be delayed but will be sent once the carrier’s API is restored
Sendle
Swyft
UDS
RR Donnelley
Veho
parcel_perform
Shippo Platform API
Shippo Alternatives
Canada Post
The Canadian Union of Postal Workers (CUPW) has announced it began a national strike on Friday, November 15, at 12:01 a.m. ET. Mail and parcels will not be processed or delivered for the duration of the national strike, and some post offices will be closed. Items will be delivered as quickly as possible once operations resume. See Canada Post's negotiations page for updates.
UPS US
We are investigating reports of higher than usual occurrences of timed out requests to get rates and labels which specify a UPS carrier.
Existing UPS connections which were not proactively migrated to us OAuth will now return the following error: A shipping carrier error occurred: Access keys are no longer available. Please reconnect XXXXX account number using OAuth.
UPS account address/invoice information is no longer accepted as a method to authenticate the UPS account connection. UPS connections that were set up using address/invoice information in the past will need to be reauthorized using OAuth.
To reconnect/reauthorize your existing UPS connection please follow the process outlined here: https://help.shipengine.com/hc/en-us/articles/27535412505115-How-to-Reauthorize-Your-UPS-Account
You will need the following:
- the UPS website login for the given UPS account.
- a Name/Nickname populated for the connection in ShipEngine. If one is not displayed in the Name column you may set one via the Rename button in the 3-dots menu
- The UPS account's country code and postal code must be set for the given UPS account. You may set these via the Edit button in the 3-dots menu
- To repeat this process for each individual UPS connection that you have and intend to keep using.
If you do not have access to the account dashboard or would prefer to reconnect your existing UPS account via API request, you can use the Reconnect request outlined here: https://www.shipengine.com/docs/carriers/ups/#:~:text=Example%20Reconnect%20Call