Historial de interrupciones de Shiphero

1. August 31, 2026 at 2:39 AM UTCinvestigating

   Al abrir pedidos en envío. puede ver: No podemos procesar esta orden Encontramos una orden de procesamiento de problemas *****. Por favor, intente de nuevo más tarde, o contacte con ShipHero. Ocultar detalles Valor de entrada numérico inválido: **** Estamos trabajando en resolver esto lo antes posible.

2. August 31, 2026 at 2:49 AM UTCidentified

   Hemos identificado el problema y trabajando en una solución.

3. August 31, 2026 at 3:29 AM UTCresolved

   Esta cuestión se ha resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 22, 2026 at 6:15 PM UTCidentified

   Veho está dentro de ShipHero debido a un cambio de API y ha sido deshabilitado de la citación. Lo volveremos a hacer cuando confirmemos que la integración Veho está de vuelta al pleno funcionamiento.

2. July 22, 2026 at 8:12 PM UTCresolved

   Veho se puede volver y volver en línea

Traducido automáticamente desde la actualización oficial del incidente.

1. July 10, 2026 at 3:33 PM UTCinvestigating

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

2. July 10, 2026 at 3:47 PM UTCidentified

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

3. July 10, 2026 at 3:56 PM 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. July 10, 2026 at 4:21 PM 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. June 26, 2026 at 5:28 PM 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. June 26, 2026 at 8:06 PM 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. June 27, 2026 at 12:29 AM UTCresolved

   This incident has been resolved.

1. June 3, 2026 at 2:27 PM 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. June 3, 2026 at 2:50 PM 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. June 3, 2026 at 3:56 PM 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. March 16, 2026 at 4:51 PM 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. March 16, 2026 at 5:21 PM UTCmonitoring

   Shippo says they have resolved the issue.

3. March 16, 2026 at 5:22 PM UTCresolved

   This incident has been resolved.

1. January 29, 2026 at 10:26 PM 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. January 30, 2026 at 12:20 AM 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. December 10, 2025 at 4:53 PM 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. December 10, 2025 at 5:03 PM UTCmonitoring

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

3. December 10, 2025 at 5:04 PM UTCmonitoring

   We are continuing to monitor for any further issues.

4. December 10, 2025 at 5:22 PM UTCresolved

   The DHL API is now fully functional.

1. December 1, 2025 at 2:03 AM UTCinvestigating

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

2. December 1, 2025 at 2:17 AM UTCidentified

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

3. December 1, 2025 at 2:18 AM UTCidentified

   We are continuing to work on a fix for this issue

4. December 1, 2025 at 2:21 AM UTCmonitoring

   A fix has been implemented and we are monitoring the results

5. December 1, 2025 at 2:28 AM UTCresolved

   This incident has been resolved

1. November 18, 2025 at 1:25 PM 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. November 18, 2025 at 1:39 PM UTCmonitoring

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

3. November 18, 2025 at 5:12 PM UTCresolved

   This incident has been resolved.

1. November 6, 2025 at 6:42 PM UTCinvestigating

   We see slowness across the system and are investigating.

2. November 6, 2025 at 6:59 PM UTCresolved

   The slowness is resolved. Thank you for your patience.

1. October 20, 2025 at 8:07 AM 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. October 20, 2025 at 1:41 PM 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. October 20, 2025 at 2:43 PM 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. October 20, 2025 at 8:24 PM 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. October 20, 2025 at 8:44 PM 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. October 20, 2025 at 11:11 PM 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. October 20, 2025 at 11:40 PM UTCresolved

   All ShipHero Components have been restored to operational status.

1. August 13, 2025 at 8:56 PM 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. August 13, 2025 at 9:00 PM UTCidentified

   The issue has been identified and a fix is being implemented

3. August 13, 2025 at 9:19 PM UTCmonitoring

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

4. August 14, 2025 at 12:52 AM UTCresolved

   This incident has been resolved.

1. August 5, 2025 at 9:17 PM 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. August 5, 2025 at 9:19 PM UTCinvestigating

   We are continuing to investigate this issue.

3. August 6, 2025 at 8:56 PM 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. August 12, 2025 at 1:51 PM UTCresolved

   This incident has been resolved.

1. June 30, 2025 at 7:29 PM UTCinvestigating

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

2. June 30, 2025 at 7:33 PM UTCidentified

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

3. June 30, 2025 at 7:34 PM UTCmonitoring

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

4. June 30, 2025 at 7:38 PM UTCresolved

   This incident has been resolved.

1. June 18, 2025 at 9:01 AM UTCinvestigating

   We are currently investigating this issue

2. June 18, 2025 at 9:14 AM UTCresolved

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

1. May 21, 2025 at 8:56 PM 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. May 21, 2025 at 9:54 PM 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. May 21, 2025 at 10:05 PM 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. May 22, 2025 at 12:12 AM UTCresolved

   This incident has been resolved.

1. May 13, 2025 at 9:20 PM UTCinvestigating

   We are currently investigating a performance degradation between Shopify and ShipHero causing order imports to take longer than usual.

2. May 13, 2025 at 10:03 PM UTCinvestigating

   We are continuing to investigate this active issue and are monitoring progress on restoration of service performance.

3. May 13, 2025 at 10:52 PM UTCidentified

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

4. May 13, 2025 at 10:54 PM UTCresolved

   This incident has been resolved.

1. April 21, 2025 at 12:27 PM UTCinvestigating

   DHL Ecommerce is down we are investigating.

2. April 21, 2025 at 2:06 PM UTCresolved

   DHL has resolved the issue.

1. November 25, 2024 at 7:43 PM UTCinvestigating

   UPS is responding with errors on calls. We've contacted our UPS support representative and are awaiting a resolution. We'll update here as we know more.

2. November 25, 2024 at 8:05 PM UTCmonitoring

   Issue seems to be resolved, we're monitoring.

3. November 25, 2024 at 8:17 PM UTCresolved

   There haven't been any errors recently so we're closing the status and we are continuing to monitor internally.