Shiphero 장애 기록

1. 2026년 10월 2일 오후 6:37 UTCinvestigating

   우리는 우리의 호스팅 플랫폼 AWS와 함께, 체계에 접근하는 일반적인 느린의 보고입니다.

2. 2026년 10월 2일 오후 7:07 UTCmonitoring

   속도 문제점은 해결되었습니다, 우리는 감시입니다.

3. 2026년 10월 2일 오후 7:16 UTCresolved

   우리는이 상태를 닫고 반복에서이 속도 문제를 완화하는 변경을합니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 9월 30일 오후 7:10 UTCinvestigating

   우리는 현재 약 3pm에서 시작된 문제점을 조사하고 있습니다. 우리의 내부 경고는 플랫폼에 접근하는 문제점을 보고했습니다. 우리의 팀은 서비스를 복원하기 위해 적극적으로 노력하고 있습니다.

2. 2026년 9월 30일 오후 7:17 UTCidentified

   문제는 우리의 endpoints에 영향을 미치고 복원 작업에 영향을 미쳤습니다.

3. 2026년 9월 30일 오후 7:56 UTCidentified

   사용자는 ShipHero의 많은 부분에 로그인 할 수 없습니다. 이 문제는 우리의 허가 관리와 관련이 있습니다. 가능한 한 빨리 해결하기 위해 노력하고 있습니다.

4. 2026년 9월 30일 오후 8:22 UTCidentified

   우리는 우리가 해결에 가까이 있고 다른 갱신을 곧 제공할 것입니다 믿습니다.

5. 2026년 9월 30일 오후 8:26 UTCmonitoring

   ShipHero는 액세스를 복원하는 수정을 배포했습니다. 우리는 우리의 Permissions 관리 서비스를 감시하는 것을 계속할 것입니다 그러나 ShipHero로 돌아가고 정상적인 가동을 재개하기 위하여 이 사건에 의해 충격을 받는 고객을 조언합니다.

6. 2026년 9월 30일 오후 10:14 UTCresolved

   이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 9월 28일 오후 3:06 UTCidentified

   USPS는 현재 지불 허가 API를 가진 불안정성을 경험하고 있습니다. 일부 계정은 USPS 라벨을 인용, 인쇄 또는 표시 할 때 sporadically 401 오류가 표시됩니다. USPS 계정을 다시 연결하지 마십시오. 이것은 캐리어를 완전히 분리하고 배송에서 당신을 방지 할 것입니다. 당신의 연결은 우리의 측에 건강하고 서비스는 일단 USPS가 문제점을 해결한 후에 자동적으로 재개할 것입니다. 우리는 감시하고 우리가 뉴스가 있는 것처럼 곧 새롭게 할 것입니다.

2. 2026년 9월 28일 오후 10:55 UTCresolved

   우리는 지난 4 시간 동안 오류가 발생하지 않았으므로이 상태를 닫습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 8월 31일 오전 2:39 UTCinvestigating

   배송에 주문할 때. 당신은 볼 수 있습니다: 우리는 이 순서를 가공할 수 없습니다 우리는 문제 처리 순서를 발견했습니다. 나중에 시도하거나 ShipHero 지원에 문의하십시오. 자주 묻는 질문 잘못된 숫자 입력 값 : **** 우리는 가능한 한 신속하게 해결하기 위해 노력하고 있습니다.

2. 2026년 8월 31일 오전 2:49 UTCidentified

   문제와 해결을 확인했습니다.

3. 2026년 8월 31일 오전 3:29 UTCresolved

   이 문제는 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 22일 오후 6:15 UTCidentified

   Veho는 API 변경으로 ShipHero 내에서 다운되며 인용에서 비활성화되었습니다. Veho 통합을 확인하면 다시 활성화됩니다.

2. 2026년 7월 22일 오후 8:12 UTCresolved

   Veho는 re-enabled이고 뒤 온라인

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 10일 오후 3:33 UTCinvestigating

   We are investigating reports from barcode scans not registering during the picking process in the mobile app.

2. 2026년 7월 10일 오후 3:47 UTCidentified

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

3. 2026년 7월 10일 오후 3:56 UTCmonitoring

   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.

4. 2026년 7월 10일 오후 4:21 UTCresolved

   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.

1. 2026년 6월 26일 오후 5:28 UTCinvestigating

   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.

2. 2026년 6월 26일 오후 8:06 UTCinvestigating

   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.

3. 2026년 6월 27일 오전 12:29 UTCresolved

   This incident has been resolved.

1. 2026년 6월 3일 오후 2:27 UTCinvestigating

   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.

2. 2026년 6월 3일 오후 2:50 UTCmonitoring

   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.

3. 2026년 6월 3일 오후 3:56 UTCresolved

   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/).

1. 2026년 3월 16일 오후 4:51 UTCinvestigating

   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.

2. 2026년 3월 16일 오후 5:21 UTCmonitoring

   Shippo says they have resolved the issue.

3. 2026년 3월 16일 오후 5:22 UTCresolved

   This incident has been resolved.

1. 2026년 1월 29일 오후 10:26 UTCidentified

   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.

2. 2026년 1월 30일 오전 12:20 UTCresolved

   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!

1. 2025년 12월 10일 오후 4:53 UTCinvestigating

   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/

2. 2025년 12월 10일 오후 5:03 UTCmonitoring

   DHL is reporting that the APIs are recovering, and we are seeing an increase in successful requests. We will continue to monitor.

3. 2025년 12월 10일 오후 5:04 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 2025년 12월 10일 오후 5:22 UTCresolved

   The DHL API is now fully functional.

1. 2025년 12월 1일 오전 2:03 UTCinvestigating

   We are aware of a problem with our platform and we currently investigating it.

2. 2025년 12월 1일 오전 2:17 UTCidentified

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

3. 2025년 12월 1일 오전 2:18 UTCidentified

   We are continuing to work on a fix for this issue

4. 2025년 12월 1일 오전 2:21 UTCmonitoring

   A fix has been implemented and we are monitoring the results

5. 2025년 12월 1일 오전 2:28 UTCresolved

   This incident has been resolved

1. 2025년 11월 18일 오후 1:25 UTCinvestigating

   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.

2. 2025년 11월 18일 오후 1:39 UTCmonitoring

   Shippo services have returned to operational status. We will continue to monitor the stability of this connection.

3. 2025년 11월 18일 오후 5:12 UTCresolved

   This incident has been resolved.

1. 2025년 11월 6일 오후 6:42 UTCinvestigating

   We see slowness across the system and are investigating.

2. 2025년 11월 6일 오후 6:59 UTCresolved

   The slowness is resolved. Thank you for your patience.

1. 2025년 10월 20일 오전 8:07 UTCidentified

   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.

2. 2025년 10월 20일 오후 1:41 UTCidentified

   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.

3. 2025년 10월 20일 오후 2:43 UTCidentified

   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.

4. 2025년 10월 20일 오후 8:24 UTCidentified

   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.

5. 2025년 10월 20일 오후 8:44 UTCidentified

   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.

6. 2025년 10월 20일 오후 11:11 UTCidentified

   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

7. 2025년 10월 20일 오후 11:40 UTCresolved

   All ShipHero Components have been restored to operational status.

1. 2025년 8월 13일 오후 8:56 UTCinvestigating

   Shipping labels can't be printed or opened due to "Access denied" errors. We've identified the issue and are working on a fix.

2. 2025년 8월 13일 오후 9:00 UTCidentified

   The issue has been identified and a fix is being implemented

3. 2025년 8월 13일 오후 9:19 UTCmonitoring

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

4. 2025년 8월 14일 오전 12:52 UTCresolved

   This incident has been resolved.

1. 2025년 8월 5일 오후 9:17 UTCinvestigating

   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.

2. 2025년 8월 5일 오후 9:19 UTCinvestigating

   We are continuing to investigate this issue.

3. 2025년 8월 6일 오후 8:56 UTCmonitoring

   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.

4. 2025년 8월 12일 오후 1:51 UTCresolved

   This incident has been resolved.

1. 2025년 6월 30일 오후 7:29 UTCinvestigating

   We are currently investigating a problem with access to our ShipHero Endpoints

2. 2025년 6월 30일 오후 7:33 UTCidentified

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

3. 2025년 6월 30일 오후 7:34 UTCmonitoring

   A fix has been implemented and we are monitoring system performance.

4. 2025년 6월 30일 오후 7:38 UTCresolved

   This incident has been resolved.

1. 2025년 6월 18일 오전 9:01 UTCinvestigating

   We are currently investigating this issue

2. 2025년 6월 18일 오전 9:14 UTCresolved

   We have determined the cause of the issue and services are performing as usual

1. 2025년 5월 21일 오후 8:56 UTCinvestigating

   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.

2. 2025년 5월 21일 오후 9:54 UTCmonitoring

   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

3. 2025년 5월 21일 오후 10:05 UTCmonitoring

   We are continuing to monitor for any further issues. However we want to restate that access to ShipHero and our system performance remains operational.

4. 2025년 5월 22일 오전 12:12 UTCresolved

   This incident has been resolved.