ShipEngine had 47 outages in the last 2 years totaling 12507h 49m of downtime — averaging 1.9 incidents per month.
There were 47 ShipEngine outages since September 26, 2024 totaling 12507h 49m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently seeing performance degradation when calling the Royal Mail and Parcel Force APIs.
Carrier was contacted and is reviewing the issue on his side.
The carrier solved the issue on his side, and the performance went back to normal.
We are aware of an issue causing latency when accessing ShipStation API, and we are actively investigating this issue. This is impacting multiple features, including label generation.
We are continuing to investigate this issue.
This incident has been resolved.
We are aware of an issue causing an increased rate of timeout errors resulting in 499 and 502 errors across various endpoints for some users. We are currently investigating this, and will provide an update once we have more information.
This incident has been resolved.
We have observed a high frequency of errors returned while attempting to perform various functions with UPS accounts such as rating and label creation. While the error rate is elevated, it is not universally impacting all UPS accounts similarly. The following error is returned: A shipping carrier error occurred: Invalid Authentication Information The cause of this issue is being investigated.
The service provider has confirmed a restoration of functionality. Error rates have begun to fall. We are continuing to monitor to ensure a full recovery.
This incident has been resolved.
We are currently investigating reports of a problem preventing some users from being able to successfully log into the account dashboard.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Effective May 22, 2026 GlobalPost’s Southern California (LAX/Cypress, CA) processing hub has temporarily suspended operations due to a local evacuation order following a chemical leak. All pickups and drop-offs in the LAX area will be delayed, and packages currently at the facility are being held.
We are aware of an issue impacting label generation for FedEx from ShipStation for certain users. We are investigating this, and will provide an update once there is additional information.
We have confirmed that the issue is related to an ongoing issue with the carrier. We will provide an additional update once the issue has been resolved.
FedEx Continues to report issues with their API. We will provide another update once there is further information.
We are continuing to work with FedEx to find a resolution. The specific error is "Unable to create FedEx shipment. We apologize for the inconvenience. This action cannot be completed at this time. Please try again later.."
We are aware of an issue preventing ShipEngine/ShipStationAPI dashboard access/login attempts from being completed successfully. We are investigating the underlying cause.
An outage with a third party service provider has been identified as the cause of account dashboard login issues. We are working with the provider to restore functionality.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are investigating reports of an increased frequency of timeouts and performance degradation impacting some users.
This incident has been resolved
We are investigating reports of an issue that is preventing the account dashboard from displaying all carrier connections as expected.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are aware of an issue causing an increased rate of timeout errors across various endpoints for some users. We are currently investigating this, and will provide an update once we have more information.
We have identified the cause of this issue. A fix has been put in place, and we are monitoring the results.
This incident has been resolved.
Purolator is reporting that users are experiencing a Country Code error when printing labels. The issue is under investigation on the carrier side.
This incident has been resolved by the carrier.
Sendle has announced that all shipments have been halted as of January 11th, and any pickups pending on January 12th or later will be cancelled. Any parcels that have already been picked up and are in transit will be delivered at the discretion of the delivery partner. We recommend utilizing alternative carriers. CouriersPlease has advised that all current Sendle AU shipments are being held by CouriersPlease until further notice. We will provide a further update once we have received one from CouriersPlease around the next steps. 13/01 - CouriersPlease has advised that all Sendle consignments that are held in the CouriersPlease network will be delivered. No further pickups of Sendle consignments will occur going forward.
This incident has been resolved.
Dimensional weight – effective 11 January 2026: Package dimensions will be rounded up to the nearest whole centimeter or inch.
This incident has been resolved.
Identified - ShipStation is aware of the technical issues impacting the ShipStation Platform. We are actively working to resolve this issue. We will provide updates as they become available to us. Thank you for your patience!
This incident has been resolved
We are receiving intermittent reports of the error "A shipping carrier error occurred: The remote server returned an error: (403) Forbidden" when getting rates and creating labels for UPS. We are currently investigating into the issue and coordinating with UPS.
This incident has been resolved.
Australia Post: Shipments to the US: Effective 7 November 2025, Australia Post is unable to confirm at this time when services will resume for 'International Courier' branded services to the US. Learn more. Australia Post: Shipments to CA: Effective 11 November 2025: Australia Post will resume all remaining postal services. Learn more. Sendle: Shipments to CA: Effective 2 December 2025, shipments are still paused while Canada Post works through backlogs. They will resume service once Canada Post's network returns to normal operations.Learn more.
This incident has been resolved.
The potential for extremely high volume between some US Postal codes may add one day in transit to a limited number of air shipments. UPS 2nd Day Air® shipments on December 15,16 and 17, 2025 & UPS 3 Day Select® shipments on December 1,2,8,9,15 and 16, 2025 Learn more.
This incident has been resolved.
There are issues logging into the dashboard due to an outage currently affecting Cloudflare https://www.cloudflarestatus.com/. We are closely monitoring the issue. It can also impact some of the carrier API.
Cloudflare implemented the fix on their side: Monitoring - A fix has been implemented and we are monitoring the results. Dec 05, 2025 - 09:12 UTC
This incident has been resolved. Cloudflare implemented the fix on their side and it solved the issue.
An aircraft accident has taken place at Worldport, UPS’s main hub in the United States. As a result, UPS is making the some operational adjustments: The money-back guarantee (also known as the UPS® Service Guarantee) is currently active for some Air and International services, see details here.
This incident has been resolved.
Canadian Carriers Canada Post: Canada Post and the CUPW have reached agreements in principle but have yet to finalize tentative collective agreements for signing. At this time, strike/lockout activity is suspended. Learn more. UPS: Effective December 7, 2025, and until further notice, UPS has implemented a $1.00 CAD Surge Fee on all Canada Domestic and Import/Export Ground/Air shipments. Purolator:Effective December 8, 2025, Purolator has removed the temporary $15.00 surcharge to select rural postal codes, including across Atlantic Canada, Quebec outside of Montréal/Québec City, Northern Ontario, and rural parts of the Prairies and BC. Purolator apologizes for the inconvenience.
This incident has been resolved.
ShipStation API is currently experiencing performance issues due to an ongoing AWS service issue. We are actively monitoring their status and its impact on our platform. We will provide updates as they become available. Thank you for your patience. You can view the AWS Health Dashboard here: https://health.aws.amazon.com/health/status?path=service-history
This incident has been resolved.
We are investigating reports of the following errors being returned at a high rate when attempting to get rates and create labels: "carrier_id xxxxxxx not found" "warehouse_id yyyyyyy not found"
A fix has been implemented and we are monitoring the results.
This incident has been resolved.