Historial de interrupciones de Shiphero

1. 2 de octubre de 2026 a las 18:37 UTCinvestigating

   Junto a nuestra plataforma de alojamiento AWS, estamos investigando informes de lentitud general que accede al sistema.

2. 2 de octubre de 2026 a las 19:07 UTCmonitoring

   El problema de velocidad se ha resuelto, estamos monitoreando.

3. 2 de octubre de 2026 a las 19:16 UTCresolved

   Estamos cerrando este estado y haciendo un cambio para mitigar este problema de velocidad de la repetición.

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

1. 30 de septiembre de 2026 a las 19:10 UTCinvestigating

   Actualmente estamos investigando un problema que comenzó a aproximadamente 3pm. Nuestras alertas internas reportaron un problema accediendo a la plataforma. Nuestro equipo está trabajando activamente para restaurar los servicios.

2. 30 de septiembre de 2026 a las 19:17 UTCidentified

   Se identificó una cuestión que afectaba a nuestros puntos finales y trabajaba para restaurarlos.

3. 30 de septiembre de 2026 a las 19:56 UTCidentified

   Los usuarios no pueden acceder a muchas partes de ShipHero. La cuestión está relacionada con nuestra gestión de permisos. Estamos trabajando para resolver lo más rápido posible.

4. 30 de septiembre de 2026 a las 20:22 UTCidentified

   Creemos que estamos cerca de la resolución y proporcionaremos otra actualización en breve.

5. 30 de septiembre de 2026 a las 20:26 UTCmonitoring

   ShipHero implementó una solución para restaurar el acceso. Seguiremos monitoreando la salud de nuestro servicio de Gestión de Permisiones, pero estamos asesorando a clientes que fueron afectados por este evento para iniciar sesión en ShipHero y reanudar operaciones normales.

6. 30 de septiembre de 2026 a las 22:14 UTCresolved

   Este incidente ha sido resuelto.

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

1. 28 de septiembre de 2026 a las 15:06 UTCidentified

   USPS está experimentando inestabilidad con su API de autorización de pago. Algunas cuentas pueden ver esporádicamente 401 errores al citar, imprimir o manifestar etiquetas USPS. Por favor no vuelva a conectar su cuenta de USPS, ya que esto desconectará completamente el transportista y le impedirá el envío. Su conexión es saludable a nuestro lado y el servicio se reanudará automáticamente una vez que el USPS resuelva el problema. Estamos monitoreando y actualizaremos en cuanto tengamos noticias.

2. 28 de septiembre de 2026 a las 22:55 UTCresolved

   No hemos visto ningún error en las últimas 4 horas para cerrar este estado.

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

1. 31 de agosto de 2026 a las 2:39 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. 31 de agosto de 2026 a las 2:49 UTCidentified

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

3. 31 de agosto de 2026 a las 3:29 UTCresolved

   Esta cuestión se ha resuelto.

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

1. 22 de julio de 2026 a las 18:15 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. 22 de julio de 2026 a las 20:12 UTCresolved

   Veho se puede volver y volver en línea

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

1. 10 de julio de 2026 a las 15:33 UTCinvestigating

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

2. 10 de julio de 2026 a las 15:47 UTCidentified

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

3. 10 de julio de 2026 a las 15: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. 10 de julio de 2026 a las 16: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. 26 de junio de 2026 a las 17: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. 26 de junio de 2026 a las 20: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. 27 de junio de 2026 a las 0:29 UTCresolved

   This incident has been resolved.

1. 3 de junio de 2026 a las 14: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. 3 de junio de 2026 a las 14: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. 3 de junio de 2026 a las 15: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. 16 de marzo de 2026 a las 16: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. 16 de marzo de 2026 a las 17:21 UTCmonitoring

   Shippo says they have resolved the issue.

3. 16 de marzo de 2026 a las 17:22 UTCresolved

   This incident has been resolved.

1. 29 de enero de 2026 a las 22: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. 30 de enero de 2026 a las 0: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. 10 de diciembre de 2025 a las 16: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. 10 de diciembre de 2025 a las 17: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. 10 de diciembre de 2025 a las 17:04 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 10 de diciembre de 2025 a las 17:22 UTCresolved

   The DHL API is now fully functional.

1. 1 de diciembre de 2025 a las 2:03 UTCinvestigating

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

2. 1 de diciembre de 2025 a las 2:17 UTCidentified

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

3. 1 de diciembre de 2025 a las 2:18 UTCidentified

   We are continuing to work on a fix for this issue

4. 1 de diciembre de 2025 a las 2:21 UTCmonitoring

   A fix has been implemented and we are monitoring the results

5. 1 de diciembre de 2025 a las 2:28 UTCresolved

   This incident has been resolved

1. 18 de noviembre de 2025 a las 13: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. 18 de noviembre de 2025 a las 13:39 UTCmonitoring

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

3. 18 de noviembre de 2025 a las 17:12 UTCresolved

   This incident has been resolved.

1. 6 de noviembre de 2025 a las 18:42 UTCinvestigating

   We see slowness across the system and are investigating.

2. 6 de noviembre de 2025 a las 18:59 UTCresolved

   The slowness is resolved. Thank you for your patience.

1. 20 de octubre de 2025 a las 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. 20 de octubre de 2025 a las 13: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. 20 de octubre de 2025 a las 14: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. 20 de octubre de 2025 a las 20: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. 20 de octubre de 2025 a las 20: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. 20 de octubre de 2025 a las 23: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. 20 de octubre de 2025 a las 23:40 UTCresolved

   All ShipHero Components have been restored to operational status.

1. 13 de agosto de 2025 a las 20: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. 13 de agosto de 2025 a las 21:00 UTCidentified

   The issue has been identified and a fix is being implemented

3. 13 de agosto de 2025 a las 21:19 UTCmonitoring

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

4. 14 de agosto de 2025 a las 0:52 UTCresolved

   This incident has been resolved.

1. 5 de agosto de 2025 a las 21: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. 5 de agosto de 2025 a las 21:19 UTCinvestigating

   We are continuing to investigate this issue.

3. 6 de agosto de 2025 a las 20: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. 12 de agosto de 2025 a las 13:51 UTCresolved

   This incident has been resolved.

1. 30 de junio de 2025 a las 19:29 UTCinvestigating

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

2. 30 de junio de 2025 a las 19:33 UTCidentified

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

3. 30 de junio de 2025 a las 19:34 UTCmonitoring

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

4. 30 de junio de 2025 a las 19:38 UTCresolved

   This incident has been resolved.

1. 18 de junio de 2025 a las 9:01 UTCinvestigating

   We are currently investigating this issue

2. 18 de junio de 2025 a las 9:14 UTCresolved

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

1. 21 de mayo de 2025 a las 20: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. 21 de mayo de 2025 a las 21: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. 21 de mayo de 2025 a las 22: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. 22 de mayo de 2025 a las 0:12 UTCresolved

   This incident has been resolved.