54 Shiphero incidents · февраль 2023 г. — official updates, affected components, duration and resolution details.
Мы вместе с нашей хостинговой платформой AWS изучаем сообщения об общей медленности доступа к системе.
Проблема скорости решена, мы отслеживаем.
Мы закрываем этот статус и вносим изменения, чтобы смягчить эту проблему скорости.
Автоматический перевод официального обновления инцидента.
В настоящее время мы расследуем вопрос, который начался примерно в 3 часа дня. Наши внутренние оповещения сообщили о проблеме с доступом к платформе. Наша команда активно работает над восстановлением сервиса.
Была выявлена проблема, затрагивающая наши конечные точки и работающая над их восстановлением.
Пользователи не могут войти во многие части ShipHero. Это связано с нашим управлением разрешениями. Мы работаем над тем, чтобы решить проблему как можно быстрее.
Мы считаем, что мы близки к решению и вскоре предоставим еще одно обновление.
ShipHero развернул исправление для восстановления доступа. Мы будем продолжать следить за состоянием здоровья нашей службы управления разрешениями, но советуем клиентам, которые пострадали от этого события, вернуться в ShipHero и возобновить нормальные операции.
Этот инцидент был урегулирован.
Автоматический перевод официального обновления инцидента.
USPS в настоящее время испытывает нестабильность с API авторизации платежей. Некоторые учетные записи могут иногда видеть ошибки 401 при цитировании, печати или проявлении ярлыков USPS. Пожалуйста, не подключайте свою учетную запись USPS повторно, так как это полностью отключит перевозчика и не позволит вам осуществлять доставку. Ваше соединение является здоровым на нашей стороне, и обслуживание автоматически возобновится, как только USPS решит проблему. Мы отслеживаем и будем обновлять, как только у нас появятся новости.
За последние 4 часа мы не видели никаких ошибок, поэтому мы закрыли этот статус.
Автоматический перевод официального обновления инцидента.
При открытии заказов на доставку. Вы можете увидеть: Мы не можем обработать этот приказ Мы обнаружили проблему с обработкой заказа *****. Пожалуйста, попробуйте еще раз позже или свяжитесь со службой поддержки ShipHero. Скрыть подробности Недействительное числовое значение ввода: **** Мы работаем над тем, чтобы решить это как можно быстрее.
Мы определили проблему и работаем над исправлением.
Этот вопрос решен.
Автоматический перевод официального обновления инцидента.
Veho упал в ShipHero из-за изменения API и был отключен от цитирования. Мы возобновим работу, когда подтвердим, что интеграция с Veho вернулась к полноценному функционированию.
Veho снова включен и снова онлайн
Автоматический перевод официального обновления инцидента.
We are investigating reports from barcode scans not registering during the picking process in the mobile app.
The issue has been identified and we're currently implementing a fix.
A fix has been deployed to the Mobile App and we are Monitoring the results. If you ran into this issue, please do one of the following: 1. Fully close the app and reopen it, or, 2. Switch users (PIN) and log back in. This should resolve the scanning error. If you still see the error after that, please let support know your app version and device.
The incident has been resolved. If you ran into this issue, please do one of the following: 1. Fully close the app and reopen it, or, 2. Switch users (PIN) and log back in. This should resolve the scanning error. If you still see the error after that, please let support know your app version and device. Thank you.
Our monitoring and alerting tools detected an issue with FedEx's API at approximately 12:06pm EST (2026-06-26). Our carrier team contacted FedEx and they confirmed they are investigating an intermittent issue with their API. We recommend monitoring both ShipHero Status Page and FedEx to stay informed on progress.
We are monitoring the FedEx API issue and have observed an intermittent behavior with the API issue. ShipHero recommends contacting FedEx support for updates if impacted and continuing to monitor FedEx and ShipHero Status pages.
This incident has been resolved.
ShipHero's internal monitoring reported elevated error rates from Shopify affecting some API requests. ShipHero Customers may experience intermittent issues with inventory updates, inventory synchronization, and/or order retrieval. For additional information we recommend subscribing and checking the Shopify Status page (https://www.shopifystatus.com/). We will continue to monitor the health of this connection and report status.
ShipHero's internal monitoring is no longer reporting elevated error rates from Shopify affecting API requests. Inventory updates, inventory synchronization, and order retrieval operations are currently processing normally. For additional information, we recommend subscribing to and checking the Shopify Status page (https://www.shopifystatus.com/). We will continue to monitor the health of this integration and reporting status.
ShipHero's internal monitoring is no longer reporting elevated error rates from Shopify affecting API requests. Inventory updates, inventory synchronization, and order retrieval operations are processing normally. Shopify has also marked this incident as resolved. We will continue to monitor the health of this connection through our standard monitoring processes. For additional information regarding this incident, please refer to the Shopify Status page (https://www.shopifystatus.com/).
Shippo has a partial outage which will block Cheapest if you have Shippo connected. If you use our direct USPS Modern solution you won't be affected. See https://status.goshippo.com/ for status of Shippo.
Shippo says they have resolved the issue.
This incident has been resolved.
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.
Good news! USPS has resolved the technical issues that were preventing connection updates. Their support team confirmed that the OAuth API is back online and stable. We’ve lifted our recommendation to avoid editing connections. Everything is a "go" for your USPS settings. Thank you for your patience while we monitored this!
DHL is experiencing issues with their API which is impacting quoting and label generation. Label generation using "cheapest" may fail if DHL is an included carrier. You can disable quoting for DHL to temporarily remove it and continue shipping using other carriers. More details can be found here: https://status.api.dhlecs.com/
DHL is reporting that the APIs are recovering, and we are seeing an increase in successful requests. We will continue to monitor.
We are continuing to monitor for any further issues.
The DHL API is now fully functional.
We are aware of a problem with our platform and we currently investigating it.
The issue has been identified and a fix is currently being implemented
We are continuing to work on a fix for this issue
A fix has been implemented and we are monitoring the results
This incident has been resolved
Shippo is down maybe due to cloudflare outage. You can use our direct USPS integration to continue generating USPS labels. Cheapest will be affected if Shippo is connected because they aren’t responding to quotes.
Shippo services have returned to operational status. We will continue to monitor the stability of this connection.
This incident has been resolved.
We see slowness across the system and are investigating.
The slowness is resolved. Thank you for your patience.
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
All ShipHero Components have been restored to operational status.
Shipping labels can't be printed or opened due to "Access denied" errors. We've identified the issue and are working on a fix.
The issue has been identified and a fix is being implemented
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating an issue related to the "Upgraded TikTok Shipping Feature". Until otherwise notified, we are advising ShipHero customers "Not to Upgrade". We are in communication with TikTok integration and development resources and will update this incident as soon as TikTok provides further clarity and confirmation of next steps on upgrade compatibility.
We are continuing to investigate this issue.
ShipHero Engineering in partnership with TikTok implemented a solution for this issue. We are currently monitoring the health of the API Integration and will continue to monitor over the next business day. Please communicate any new issues observed (Post Aug 6 5pm EST) to ShipHero Technical Support.
This incident has been resolved.
We are currently investigating a problem with access to our ShipHero Endpoints
The issue has been identified and we have resolved the issue. We will monitor the system .
A fix has been implemented and we are monitoring system performance.
This incident has been resolved.
We are currently investigating this issue
We have determined the cause of the issue and services are performing as usual
We are currently investigating an issue that is impacting some users from accessing www.shiphero.com This issue does not impact the use of our Warehouse Management solution. We have had limited reports of users that have book marked sites like login.shiphero.com experiencing delays or inability to load the login screen, this is due to a redirect that is effected by the issue we are investigating. Please load your ShipHero application by using app.shiphero.com or from our Knowledge Page https://software-help.shiphero.com/hc/en-us which are working normally.
We have observed improvement on this issue. Your ability to access shiphero.com should be working. We will continue to monitor the performance of this website
We are continuing to monitor for any further issues. However we want to restate that access to ShipHero and our system performance remains operational.
This incident has been resolved.
