ShipHero Outage History

The issue has been identified and we're currently implementing a fix.

USPS's API is having issues with when establishing new connections or editing existing connections. We have reported the issue and are monitoring closely. We recommend you don't edit any existing USPS connections until the incident is resolved.

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

We are continuing to work on a fix for this issue

Public cloud provider AWS is suffering an outage on one of their main regions, this is affecting our systems https://health.aws.amazon.com/health/status We are monitoring the situation.

Update: As 09:30am Amazon Health Dashboard reported that they are making progress on resolving the issue. For details: https://health.aws.amazon.com/health/status We have had limited reports of intermittent latency, otherwise ShipHero is operational. ShipHero Support will continue to monitor AWS for progress updates and resolution of this incident.

AWS is currently in the process of recovering affected services. As systems are restored, we will be conducting data integrity checks. Please refrain from taking any manual corrective actions while the system synchronizes and catches up. We appreciate your patience and understanding. We will continue to provide period updates.

AWS is recovering and therefore ShipHero is recovering. Please be patient, if you're trying to create a label and it's taking time, wait for the label to generate don't try to print again for up to 2 minutes to make sure you don't get two labels. Don't clear totes or make other changes, please wait until the system catches up.

Update: AWS continues to recover and stabilize infrastructure performance. While we have been able to confirm improvement with our own internal monitoring and performance tools, we are aware that our Dashboards and Searches are in the process of catching up and are " Out of Sync by several hours.. This was expected and the process to catch up and reach synchronization is in-flight. We will update Status Page once we have caught up. Thank you for your continued patience as we recover from this outage event.

Update: The AWS outage has improved. ShipHero's platform team is monitoring our performance and encouraged by the mitigation by AWS and our system's ability to catch up. Remaining known issues: 1. USPS modern, their API is still having issues 2. Order importing is still catching up. We expect it to reach synchronization with the next 2 - 4 hours We will continue to monitor our logs and systems until all our affected component have been restored to operational Thank you

The issue has been identified and a fix is being implemented

The issue has been identified and we have resolved the issue. We will monitor the system .

The root cause had been identified and we have successfully contained the issue.

UPS’s API is returning rates without discounts for some customers. This is occurring across shipping platforms and is related to an incident on the UPS side. Shipped orders will be billed at the correct amount with discount so you can continue to use UPS. Just be aware, the rates will show incorrectly in some cases

FedEx labels are not generating. This seems to be because last night FedEx turned off access to the API we were using for address validation. We've contacted FedEx and are also looking at how to bypass from our end.

We have spoken to the correct people at FedEx and they are working on finding a resolution. We will update here as soon as we get an update.

Do not clear totes and do not update inventory. You can keep shipping. Once the issue is resolved totes will be cleared and inventory will update.

Some labels can't be printed due to "invalid numeric input values" errors. We've identified the issue and are working on a fix.

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

Do not reprocess orders if you have an order with this issue please leave it as is and wait until the issue is resolved to reprint. Reprocessing orders or clearing and repicking orders will not resolve the issue. Not all orders have this issue but any order you reprocess and any new order will have this issue. We are close to deploying a change that we expect to fix this issue. We will post an update once fixed.