ShipEngine Outage History

The ShipEngine API experienced elevated timeout rates and performance degradation that affected some users for 21.2 hours. Users reported increased frequency of timeouts when accessing the service. The incident was resolved after investigation and remediation efforts.

The ShipEngine API experienced elevated timeout rates and performance degradation that impacted some users for 4.5 hours. Users reported increased frequency of timeouts when accessing the service. The issue was identified and resolved with a fix implementation.

ShipEngine experienced a major incident where the account dashboard failed to display all active carrier connections, with users reporting that only USPS remained visible while other carriers disappeared and could not be re-added due to error messages. The issue affected the ShipEngine API Dashboard for 2.5 hours before being resolved with a fix that was monitored to ensure stability.

The ShipEngine API experienced elevated timeout rates and performance degradation that impacted some users for 1.6 hours. A fix was implemented which reduced error rates, and the service was monitored until full resolution was confirmed. The incident was fully resolved after investigating and addressing the underlying cause.

Sendle halted all shipments across Australia, Canada, and the US as of January 11th, with all scheduled pickups from January 12th onward being cancelled. In-transit parcels were delivered at the discretion of delivery partners, while CouriersPlease confirmed they would deliver existing Sendle consignments in their network but cease future pickups. The incident was resolved after approximately 51 days with users advised to utilize alternative carriers during the disruption.

UPS implemented a change to their dimensional weight calculation system for US and Canadian shipments, requiring package dimensions to be rounded up to the nearest whole centimeter or inch effective January 11, 2026. This affected UPS shipping services in both the US and Canada through ShipEngine's platform. The incident was monitored and subsequently resolved after the changes were fully implemented.