Is ShipEngine Down Right Now? Check if there is a current outage ongoing.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are currently investigating long response times and 5xx responses returned for attempts to validate addresses in ShipEngine.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are currently investigating long response times and 5xx responses returned for attempts to validate addresses in ShipEngine.

Effective Friday, May 23, 2025, Canada Post continues to operate with CUPW banning overtime work. Customers may experience delays. At this time, there are NO rotating strikes or national work stoppages. Learn more: https://www.canadapost-postescanada.ca/cpc/en/our-company/news-and-media/corporate-news/negotiations-list.page <b>Global Carrier Update</b> Effective Sunday, May 18th, 2025, UPS will implement a Surge Fee for Air and Ground for UPS shipments as follows: UPS Standard® to Canada: $0.49 USD /pkg, All Other Services to Canada: $0.49 USD/per pound, Canada Origin Domestic: $2.00/pkg CAD, and Canada Export: No Fee. If a Canada Post labour disruption does occur, the UPS Service Guarantee will be suspended for all services in Canada, and Same Day On-Call Pickup service for UPS Standard® will be suspended. Same Day On-Call Pickup will be available for all other services as well as for next or future-day requests. <b>U.S. Carrier Updates</b> Effective Friday, May 23, 2025, GlobalPost Economy International, Standard International, and Go service to Canada are back to normal operations and available. <b>Canadaian Carrier Update</b> Purolator from ShipStation: To continue providing reliable service amidst increased volume, effective Wednesday, May 28th, Purolator has implemented a temporary Surge Fee to shipments destined for Quebec. If a CUPW strike occurs, Canpar and Loomis Express will suspend service to all postal codes where Canada Post handles final delivery. ShipStation API users will see an error message if attempting to ship to these areas.

Effective Friday, May 23, 2025, Canada Post continues to operate with CUPW banning overtime work. Customers may experience delays. At this time, there are NO rotating strikes or national work stoppages.Learn more: https://www.canadapost-postescanada.ca/cpc/en/our-company/news-and-media/corporate-news/negotiations-list.pageGlobal Carrier UpdateEffective Sunday, May 18th, 2025, UPS will implement a Surge Fee for Air and Ground for UPS shipments as follows: UPS Standard® to Canada: $0.49 USD /pkg, All Other Services to Canada: $0.49 USD/per pound, Canada Origin Domestic: $2.00/pkg CAD, and Canada Export: No Fee.If a Canada Post labour disruption does occur, the UPS Service Guarantee will be suspended for all services in Canada, and Same Day On-Call Pickup service for UPS Standard® will be suspended. Same Day On-Call Pickup will be available for all other services as well as for next or future-day requests.U.S. Carrier UpdatesEffective Friday, May 23, 2025, GlobalPost Economy International, Standard International, and Go service to Canada are back to normal operations and available.Canadaian Carrier UpdatePurolator from ShipStation:To continue providing reliable service amidst increased volume, effective Wednesday, May 28th, Purolator has implemented a temporary Surge Fee to shipments destined for Quebec.If a CUPW strike occurs, Canpar and Loomis Express will suspend service to all postal codes where Canada Post handles final delivery. ShipStation API users will see an error message if attempting to ship to these areas.

On 5/6/2025, between approximately 02:24pm to 02:32pm Central, the ShipEngine API returned an elevated rate of 500 status responses. This issue has been resolved.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

We are investigating reports of intermittent timeout errors impacting various endpoints.

This incident has been resolved.

There is currently a technical issue preventing most chat messaged from reaching the support team via in-dashboard chat. We are currently working to correct this issue to restore chat capabilities. In the meantime the support team may be reached at support@shipengine.com

This incident has been resolved.

We are continuing to monitor for any further issues.

ShipEngine is aware of the technical issues impacting Canada Post. We are actively monitoring the status of these issues and will provide updates as they become available. Thank you for your patience! You can also check the status at the carrier's status page, https://status.canadapost.ca/

This incident has been resolved.

There is currently a technical issue preventing ShipEngine users from reaching the support team via in-dashboard chat. We are currently working to correct this issue to restore chat capabilities. In the meantime the support team may be reached at support@shipengine.com

This incident has been resolved.

The issue has been identified and a fix is being implemented.

We are continuing to investigate this issue.

We are investigating reports of widespread errors when attempting to get rates and creating labels with FedEx. Reports of the error "Delegate to an instance method cannot have null 'this'."

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are continuing to work on a fix for this issue.

The issue has been identified and a fix is being implemented.

We are investigating reports of 504 timeout errors impacting label generation for FedEx.

This incident has been resolved.

We have identified an issue preventing successful UPS label creation in the ShipEngine sandbox test environment. The error message returned is "A shipping carrier error occurred: The Shipper's shipper number cannot be used for the shipment". This does not impact production. The underlying cause has been identified and we are working towards a resolution.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are investigating an issue preventing users from successfully accessing their account dashboard. The following error is returned: "Unexpected issue We're encountering an unexpected issue preventing access to the Dashboard. Please try refreshing the page or contact support for immediate help. We appreciate your patience as we address this issue."

This incident has been resolved.

DPD have confirmed they are working to resolve the issue on their end.

There are technical issues impacting DPD UK resulting in carrier API timeouts. We are actively monitoring the status of the issue and will provide updates as they become available.

This incident has been resolved.

We are aware of an issue impacting Purolator at this time. We are monitoring this issue, and will provide updates when they become available! You can also monitor the status through Purolator's Status Page: http://status.purolator.com/

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We have received reports of widespread timeouts impacting multiple ShipEngine API endpoints and the account dashboard. Engineering is investigating the cause and working towards a resolution.

This incident has been resolved.

We are seeing improved performance at this time, and we are working on a permanent resolution for this issue.

We are investigating an issue causing 400 responses to be returned intermittently when attempting to process UPS requests. The error returned in association with this issue is: "Could not refresh authorization credentials in timely manner."

This incident has been resolved.

We are seeing improved performance and are continuing to monitor.

We are aware of issues impacting UPS rating and label generation, and we are currently investigating this.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are receiving reports of users receiving the error "A shipping carrier error occurred: Could not refresh authorization credentials in timely manner" when using UPS. We are aware of this issue and are currently investigating this.

This incident has been resolved.

A fix has been released, and we are seeing improved performance. We are continuing to monitor this!

The reported errors include "A shipping carrier error occurred: Could not refresh authorization credentials in timely manner." when processing UPS requests, as well as an "Unexpected issue" error on login. We are still investigating this, and we will follow up once there is more information!

We are aware of technical issues impacting the ShipEngine Platform. We are investigating this, and will provide updates as they become available to us. Thank you for your patience!

This incident has been resolved.

We are seeing improved performance, and we are continuing to monitor for a full recovery.

We are aware of an issue impacting label generation via the /v1/labels endpoint, and we are currently investigating this.

A fix has been issued for this issue.

We have identified an issue preventing UPS label creation in the test environment and are working toward issuing a fix.

UPS has reported the issue as resolved at this time.

UPS has not yet reported the underlying issue as resolved. A workaround implemented yesterday continues to allow for labels to be created and rates to be retrieved for existing UPS account connections. We are currently seeing issues creating new UPS account connections in ShipEngine.

We have seen a substantial improvement and are no longer seeing errors from the UPS API at this time. You should once again be able to process UPS labels and get rates successfully. We are continuing to monitor to ensure a full resolution.

UPS has confirmed they are experiencing a technical outage. They have not yet provided an ETA for resolution.

UPS has confirmed they are experiencing a technical outage.

We are aware of and investigating issues rating and creating labels with UPS.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are investigating API request timeouts and issues logging into the ShipEngine dashboard.

This incident has been resolved.

An additional issue has been confirmed which is causing a low but persistent level of error responses to continue being returned for some users. The primary impact currently is slower than normal response times. This issue is being addressed and we are continuing to monitor for a complete resolution.

Error rates have returned to normal and we are monitoring to ensure a complete resolution.

We are investigating an issue causing 400 responses to be returned when attempting to rate UPS services and create UPS labels. The error returned in association with this issue is: "Could not refresh authorization credentials in timely manner."

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are investigating an intermittent issue preventing users from logging into their account dashboard. The error displayed in browser is: "Unexpected issue We're encountering an unexpected issue preventing access to the Dashboard. Please try refreshing the page or contact support for immediate help. We appreciate your patience as we address this issue."

This incident has been resolved.

ShipEngine is aware of the technical issues impacting the ShipEngine Platform. We are actively working to resolve this issue. We will provide updates as they become available to us. Thank you for your patience! - Ability to create and download label

This incident has been resolved.

We are continuing to work on a fix for this issue.

We are looking into reports from users indicating that they are unable to continue communicating via chat once an initial reply has been received from a ShipEngine support agent. User messages show as undelivered and support agents are not seeing them. You may reach support directly at support@shipengine.com if needed while this problem exists.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are aware of an issue causing the following error to be returned on attempts to create UPS labels: "A shipping carrier error occurred: Cannot implicitly convert type '<>f__AnonymousType135<string>' to 'SS.Proxies.UPSShipService.UPSSecurityServiceAccessToken'" The root cause has been identified and a fix is being implemented currently.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are investigating issues creating labels. A 400 response with the following error is returned: "Unexpected carrier pipeline error. Object reference not set to an instance of an object." This is impacting label creation for multiple carriers.

This incident has been resolved.

Error rates have dropped. We are continuing to monitor for a full recovery.

We are seeing widespread errors when attempting to create labels with Stamps.com. Some instances present as a 504 while others as a 400 response and the following message returned: "A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 40 - Could not open a connection to SQL Server)" We are investigating the underlying cause

This incident has been resolved.

We have observed ongoing issues creating FedEx labels in the ShipEngine sandbox. Currently a 500s response is returned with the error message: "An unexpected error occurred." The issue has been reported and we are monitoring for improvement.

This incident has been resolved.

We are investigating reports of widespread timeouts encountered when attempting to get rates and create labels with FedEx.

This incident has been resolved.

We are currently investigating widespread reports of issues creating UPS labels. A 400 response has been observed with the following error message returned on attempts to create UPS labels: "License system not available"

This incident has been resolved.

We are currently investigating widespread reports of issues creating UPS labels. A 400 response has been observed with the following error message returned on attempts to create UPS labels: "XML Shipping System is unavailable, please try again later"

This issue has been resolved.

We are investigating reports of errors and increased latency with FedEx label creation and rate shopping requests.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We have received widespread reports of issues rating UPS shipments and creating UPS labels, with the following error response returned: "A shipping carrier error occurred: The remote server returned an error: (403) Forbidden." or "A shipping carrier error occurred: XML Shipping System is unavailable, please try again later."

This incident has been resolved.

Increased error rates began at approximately 8:15amCST for some users, with the impact becoming more widespread between 8:30amCST and 9:00amCST. We have seen a return to baseline error rates as of approximately 9:30amCST. Engineering is investigating the issue further to ensure a full return to service.

We are investigating reports of widespread timeouts encountered when attempting to get rates from the ShipEngine API.

We are aware of an issue that impacted the /v1/addresses/validate endpoint and we have resolved the problem. All systems should now be working as expected.

This incident has been resolved.

DPD Netherlands is experiencing issues when creating labels - "shipping carrier error occurred: Error: Unexpected close tag (Generic)" and "A shipping carrier error occurred: We are unable to process your request at this time - please try again later (Generic)." Our team is currently investigating the root cause.

This has been resolved.

We are seeing improved performance at this time, and we are continuing to monitor this.

We are investigating reports of higher than expected latency with FedEx rate and label creation requests.

This incident has been resolved.

We have identified an issue present when attempting to create Stamps.com labels within the sandbox/test environment. Most attempts to produce test labels via the Stamps Sandbox account are receiving the following error response: "A shipping carrier error occurred: Insufficient account balance. Account exception Exception with code 0x00560101; module 86, category 1, item 1" We have confirmed that this response is due to an underlying configuration issue present with the Stamps.com test environment that the ShipEngine sandbox connects to. Additional updates will be made here as the issue is corrected.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

An update for the dotNet SDK has been published. Development is continuing to investigate the underlying change that instigated this issue.

The issue has been identified and a fix is being implemented.

We are investigating reports of the error "Requested value 'no_rates_returned' was not found." being encountered by SDK users when attempting to rate shipments.

This incident has been resolved.

We are seeing improved performance with USPS tracking. We are monitoring to confirm a complete resolution.

We are aware of instances of the following message being returned when tracking USPS shipments: "An unexpected system error has occurred. Please try again later or contact the System Administrator." We are investigating this issue and are monitoring for improved functionality.

This incident has been resolved.

A fix has been implemented and we are currently monitoring the status.

We are investigating reports of higher than expected latency when getting USPS rates via Stamps.com and Endicia carriers.

This incident has been resolved.

The cause has been identified and a fix has been implemented. We are monitoring to confirm a complete resolution.

We have received reports of the PNG label download resource URL not being present in the response content of successful createLabel requests where it would be expected to populate by default.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We have observed a higher than normal rate of 400/500 responses for attempts to create labels. The underlying cause is being investigated and steps towards remediation worked on.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are investigating reports of timeouts and gateway errors that are being encountered when attempting to create labels and get rates.

This issue has been resolved.

A fix has been implemented and we are currently monitoring the status.

We are investigating reports of timeout errors impacting Rating, Label Generation, and Shipment Creation.

This incident has been resolved.

We are investigating an issue which is preventing newly created ShipEngine accounts from being logged into on the ShipEngine account dashboard. This issue is also impacting the ability for these account to successfully utilize the ShipEngine API.

This incident has been resolved.

A fix has been implemented and error rates have dropped. We are continuing to monitor for a complete resolution.

Beginning today at approximately 01:54CST we began receiving the following error response for some attempts to rate and create labels using Stamps.com services: "A shipping carrier error occurred: Due to changes in the way rates are calculated for domestic USPS offshore service, you will need to update to the latest version of the Stamps.com software to continue printing this label.\n\nClick \"More Info\" to proceed to our software download page." This behavior has been reported to the Stamps engineering team and they are investigating the cause and working to remediate the issue.

This incident has been resolved.

We are aware of instances of the following message being returned for some Stamps.com produced USPS labels when attempting to track them via /v1/tracking or on the USPS website directly: "Tracking information will not be displayed because this package was shipped with counterfeit postage. Please contact the merchant or seller with any questions." Stamps is aware of the issue and working on steps towards remediation.