Shippeo Outage History

Started May 01, 2026, 02:36 PM UTC· resolved May 04, 2026, 07:44 AM UTC

1. investigating May 01, 2026, 02:36 PM UTC

   Dear users, We are currently experiencing an incident affecting the vessel tracking and ETA computation/availability for Ocean shipments. Our technical team will start investigating as soon as possible and take the necessary actions for resolution. We will provide more updates on our progress. Thank you for your patience. -- Chers utilisateurs, Nous avons identifié un incident affectant le tracking des vaisseaux ainsi que le calcul et la disponibilité de l'ETA pour les ordres Ocean. Notre équipe technique va investiguer dès que possible et prendra les mesures nécessaires pour la résolution. Nous vous tiendrons informé sur cet incident. Merci de votre patience.

2. resolved May 04, 2026, 07:44 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 30, 2026, 11:46 AM UTC· resolved Apr 30, 2026, 01:30 PM UTC

1. investigating Apr 30, 2026, 11:46 AM UTC

   We are currently experiencing a delay in the transmission of message-out flows to our partners and customers. Some of you may notice that expected notifications or data exchanges are arriving later than usual or have not yet been received. Our team is actively investigating the root cause. Shipment tracking data continues to be collected — only the outbound delivery of updates is affected. We will provide a next update by 3PM CEST. We apologize for the inconvenience and thank you for your patience.

2. resolved Apr 30, 2026, 01:30 PM UTC

   The issue causing delays in the transmission of message-out flows has been resolved. Our systems have finished processing the backlog of notifications, and outbound data exchanges are now operating normally. Please note that some message-out that were delayed during the incident window (approximately 10:30–14:45 CEST) may now be arriving. This is expected and reflects the backlog being cleared. We apologize for any inconvenience caused.

Read the full incident report →

Started Apr 29, 2026, 10:00 AM UTC· resolved Apr 29, 2026, 10:00 AM UTC

1. resolved Apr 30, 2026, 12:34 PM UTC

   Dear users, An incident caused a delay in the processing of EDI-in files, primarily affecting order and event integrations for a limited number of organizations. This resulted in delayed order and event integration within Shippeo and subsequent transmission to external systems. This is now resolved and a permanent fix has been implemented to avoid future occurrence. Thank you for your understanding. -- Chers utilisateurs, Un incident a causé un retard dans le traitement des fichiers EDI-in, affectant principalement les intégrations d'ordres et d'événements pour un nombre limité d'organisations. Cela a entraîné un retard dans la création des ordres et l'intégration des événements sur la plateforme Shippeo, ce qui a retardé également la transmission aux systèmes externes. Cela est désormais résolu et une solution permanente a été mise en place pour éviter toute récurrence future. Merci de votre compréhension.

Read the full incident report →

Started Apr 14, 2026, 11:53 AM UTC· resolved Apr 15, 2026, 07:09 AM UTC

1. investigating Apr 14, 2026, 11:53 AM UTC

   English Version Dear Users, Since 12:00 CET, an ongoing incident has been impacting several outbound data transmission flows to external systems. Current Impact: GPS Positions: Delayed by approximately 30 minutes. Events & Orders: A delay of up to 1 hour is affecting: Road Events-out (at Order and Handling Unit level). Ocean Events-out. Orders-out. What is NOT Impacted: In-Platform Data: GPS positions and events continue to be correctly captured, processed, and displayed within the Shippeo platform. Specific Flows: Positions-out V2, ETA Events-out Our teams are actively investigating the root cause to restore normal processing speeds. We will provide further updates as the situation evolves. Thank you for your patience and understanding. Version Française Chers Utilisateurs, Depuis 12h00 CET, un incident en cours impacte plusieurs flux de transmission de données vers les systèmes externes. Impact actuel : Positions GPS : Retard d’environ 30 minutes. Événements & Commandes : Un retard allant jusqu’à 1 heure affecte : Les flux "Road Events-out" (au niveau Order et Handling Unit). Les flux "Ocean Events-out". Les flux "Orders-out". Ce qui n'est PAS impacté : Données Plateforme : Les positions GPS et les événements sont toujours correctement collectés, traités et affichés dans l'interface Shippeo. Flux Spécifiques : Les flux Positions-out V2, ETA Events-out Nos équipes investiguent activement afin d'identifier la cause racine et rétablir la fluidité des envois. Nous vous tiendrons informés de l'évolution de la situation. Nous vous remercions pour votre compréhension et votre patience.

2. investigating Apr 14, 2026, 01:52 PM UTC

   We are continuing to investigate this issue.

3. monitoring Apr 14, 2026, 02:55 PM UTC

   Update: We have identified the root cause of the current delays. Our technical team has implemented immediate workarounds to restore normal processing speeds. These improvements are currently being monitored, and we will provide a final update as soon as the issue is fully resolved

4. resolved Apr 15, 2026, 07:09 AM UTC

   Final Update: We are pleased to confirm that the processing delays have been fully resolved. Following the implementation of our technical workarounds, system performance returned to normal processing times as of Tuesday, April 14th, at night. Our team has monitored the environment throughout the subsequent cycles to ensure stability, and all operations are now functioning as expected. We apologize for any inconvenience this may have caused and appreciate your patience while we worked to rectify the issue.

Read the full incident report →

Started Apr 08, 2026, 03:30 PM UTC· resolved Apr 08, 2026, 04:00 PM UTC

1. resolved Apr 08, 2026, 03:28 PM UTC

   English --------- Dear users, The Insights module was unavailable today between 4:30 PM and 5:00 PM CET. The issue has now been resolved, and the service is back to normal. No other services were impacted, and no data was lost. Thank you for your understanding. ------------- Français --------- Chers utilisateurs, Le module Insights a été indisponible aujourd’hui entre 16h30 et 17h00 CET. L’incident est désormais résolu et le service est revenu à la normale. Aucun autre service n’a été impacté et aucune donnée n’a été perdue. Nous vous remercions pour votre compréhension.

Read the full incident report →

Started Apr 07, 2026, 04:03 PM UTC· resolved Apr 07, 2026, 04:11 PM UTC

1. resolved Apr 08, 2026, 07:12 AM UTC

   Dear users, The web platform was temporarily inaccessible on the 07/04/2026 between 18:03 and 18:11 CEST. Other services remained unaffected, and no data was lost during this period. Our technical team has identified the root cause and took the necessary actions to restore the service. Thanks for your understanding. --- Chers utilisateurs, La plateforme web a été temporairement inaccessible le 07/04/2026, entre 18h03 et 18h11 (CEST). Nous tenons à préciser que les autres services n'ont pas été affectés et qu'aucune donnée n'a été perdue durant cette période. Notre équipe technique a identifié la cause et a pris les mesures nécessaires pour rétablir le service. Nous vous remercions pour votre compréhension.

Read the full incident report →

Started Mar 24, 2026, 02:29 PM UTC· resolved Mar 24, 2026, 02:57 PM UTC

1. investigating Mar 24, 2026, 02:29 PM UTC

   Dear users, Since 14:00 CET, an ongoing incident has been impacting the transmission of GPS positions to certain clients. As a result, GPS positions are not being sent to external systems. Please note that GPS positions continue to be correctly captured, processed, and displayed within Shippeo. Only the outbound transmission flow “Positions-out” is affected. Our teams are actively investigating the root cause and will provide further updates in the coming hours. Thank you for your understanding and patience. --- Chers utilisateurs, Depuis 14h00 CET, un incident en cours impacte l’envoi des positions GPS vers certains client. En conséquence, les positions GPS ne sont pas transmises aux systèmes externes. Veuillez noter que les positions GPS sont toujours correctement collectées, traitées et affichées dans Shippeo. Seul le flux sortant « Positions-out » est impacté. Nos équipes investiguent activement afin d’identifier la cause racine et fourniront des mises à jour dans les prochaines heures. Nous vous remercions pour votre compréhension et votre patience.

2. resolved Mar 24, 2026, 02:57 PM UTC

   This incident has been resolved. Position outflows are now functioning correctly, and positions are being successfully shared with client systems. Thank you for your understanding.

Read the full incident report →

Started Mar 24, 2026, 09:31 AM UTC· resolved Mar 24, 2026, 01:25 PM UTC

1. investigating Mar 24, 2026, 09:31 AM UTC

   Dear users, Our container export platform is currently inaccessible since 23/03 6:00 pm CET . Other services remained unaffected, and no data was lost during this period. Our technical team is currently investigating this issue to solve it as soon as possible. Thank you for your patience and understanding. --- Chers utilisateurs, Les exports de données conteneurs sont inaccessibles depuis le 23/03 18h CET. Nous tenons à préciser que les autres services n'ont pas été affectés et qu'aucune donnée n'a été perdue durant cette période. Notre équipe technique est en train d'investiguer cette anomalie pour la résoudre le plus rapidement possible. Merci de votre patience et de votre compréhension.

2. identified Mar 24, 2026, 09:47 AM UTC

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

3. monitoring Mar 24, 2026, 11:18 AM UTC

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

4. resolved Mar 24, 2026, 01:25 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 23, 2026, 07:12 PM UTC· resolved Mar 24, 2026, 04:52 PM UTC

1. identified Mar 23, 2026, 07:12 PM UTC

   Dear Users, We are currently investigating an issue affecting the quality of ocean shipment ETA calculations. Some vessel schedule updates have not been processed since March 15, which may result in less accurate ETAs for ocean shipments. Our team has identified the root cause and is working on reprocessing the missing data. We expect to resolve this issue by March 24, 2026. We will provide a further update by March 24, 2026 at 12:00 EU/Paris or sooner if the situation changes. We apologize for any inconvenience this may cause. --- Chers utilisateurs, Nous examinons actuellement un problème affectant la qualité des calculs des heures d'arrivée prévues (ETA) pour les ordres maritimes. Certaines mises à jour des horaires des navires n'ont pas été traitées depuis le 15 mars, ce qui peut entraîner une dégradation de la précision des ETA pour les ordres maritimes. Notre équipe a identifié la cause du problème et s'efforce de retraiter les données manquantes. Nous prévoyons de résoudre ce problème d'ici le 24 mars 2026. Nous vous tiendrons informés d'ici le 24 mars 2026 à 12h00 EU/Paris, ou plus tôt si la situation évolue. Nous vous prions de nous excuser pour la gêne occasionnée.

2. monitoring Mar 24, 2026, 11:14 AM UTC

   Our team is actively reprocessing missing vessel schedule data to restore the accuracy of ocean ETA calculations. We have successfully processed data through March 19th and are currently working on reprocessing schedules from March 21st and 23rd. This work is progressing as planned and we expect to complete the reprocessing later today. Once complete, all ocean ETAs will be based on the most up-to-date vessel schedule information available. We will provide a final update once the reprocessing is complete or by 18:00 EU/Paris if additional time is needed. We thank you for your patience.

3. resolved Mar 24, 2026, 04:52 PM UTC

   Reprocessing of previous schedule data is now completed and all ocean ETAs are now based on the most up-to-date vessel schedule information available. The incident is now resolved.

Read the full incident report →

Started Mar 17, 2026, 04:20 PM UTC· resolved Mar 25, 2026, 09:45 AM UTC

1. identified Mar 17, 2026, 04:20 PM UTC

   Dear users, We have been experiencing an issue that is causing delays in processing and displaying Black Swan events on our web platform for Ocean scope. Our team is actively working on a solution to resolve this issue as quickly as possible. Thank you for your understanding. ------ Chers utilisateurs, Nous rencontrons actuellement un problème qui entraîne des retards dans le traitement et l’affichage des événements Black Swan sur notre plateforme web pour le scope Ocean. Nos équipes travaillent activement à la résolution de ce problème dans les plus brefs délais. Nous vous remercions pour votre compréhension.

2. identified Mar 20, 2026, 09:14 AM UTC

   A fix was released yesterday to help mitigate delays in processing Black Swan events. However, the delay remains significant, and our team continues to work on further improvements to fully resolve the issue. More updates will follow. Thank you for your understanding.

3. monitoring Mar 23, 2026, 04:08 PM UTC

   Our team has been working on a new fix that will help mitigate delays in processing Black Swan events on large data set, which is currently being deployed. We will continue monitoring the situation and provide a further update by 19:00 EU/Paris. We apologize for the inconvenience and thank you for your patience.

4. resolved Mar 25, 2026, 09:45 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 16, 2026, 12:08 PM UTC· resolved Mar 16, 2026, 04:23 PM UTC

1. investigating Mar 16, 2026, 12:08 PM UTC

   Dear users, A surge in database activity triggered 4 minutes of intermittent service degradation across our API and platform, beginning at 10:28 This resulted in: - API Performance Degradation: Increased response times and intermittent 520 errors for API requests - Platform Unavailability: The Shippeo platform is intermittently unavailable. We are conducting a thorough investigation to identify the root cause and restore the service. Thank you for your patience and understanding. ____ Chers utilisateurs, Nous avons rencontré des perturbations intermittentes pendant 4 minutes à partir de 10h28, affectant notre API et notre plateforme suite à un pic d'activité de la base de données. Ceci a entraîné : Dégradation des performances de l'API : Augmentation des temps de réponse et erreurs 520 intermittentes sur les requêtes API. Indisponibilité de la plateforme : La plateforme Shippeo est par intermittence inaccessible. Nous menons actuellement une investigation approfondie pour identifier la cause racine et rétablir le service. Nous vous remercions de votre patience et de votre compréhension.

2. resolved Mar 16, 2026, 04:23 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 11, 2026, 02:46 PM UTC· resolved Mar 12, 2026, 04:27 PM UTC

1. identified Mar 11, 2026, 02:46 PM UTC

   Dear Users, Between March 10 at 11:00 AM and March 11 at 1:00 PM (CET), our EDI 315 integration (Direct Carrier Connection) experienced an issue causing missing or delayed tracking milestones on Ocean orders. The issue has been fixed and our team is currently working to identify and replay all affected files to restore missing data. Impacted orders will progressively return to their correct state once we process the replays. We apologize for the inconvenience and will confirm once data recovery is complete. Thank you. -------- Chers utilisateurs, Entre le 10 mars à 11h00 et le 11 mars à 13h00 (CET), notre intégration EDI 315 (connexion directe avec les transporteurs) a rencontré un incident entraînant l’absence ou le retard de certains jalons de suivi sur les commandes Ocean. Le problème a été résolu et notre équipe travaille actuellement au lancement du processus de rejeu de l’ensemble des fichiers impactés afin de restaurer les données manquantes. Les commandes concernées retrouveront progressivement leur état correct une fois que ces rejouements seront traités. Nous vous présentons nos excuses pour la gêne occasionnée et vous confirmerons dès que la récupération complète des données sera terminée. Merci.

2. monitoring Mar 11, 2026, 04:25 PM UTC

   We have started replaying the impacted events. We will update you once this replay is finalised.

3. monitoring Mar 12, 2026, 08:59 AM UTC

   Hello, the replay has been finalised. Please note that due to the high number of replayed events, we are still processing some of them, so they may not yet be visible on the platform. Processing will continue throughout the day.

4. resolved Mar 12, 2026, 04:27 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 27, 2026, 04:05 PM UTC· resolved Feb 27, 2026, 06:11 PM UTC

1. investigating Feb 27, 2026, 04:05 PM UTC

   Dear users, We are experiencing intermittent issues affecting our API and platform following a surge in database activity. This resulted in: - API Performance Degradation: Increased response times and intermittent 520 errors for API requests - Platform Unavailability: The Shippeo platform is intermittently unavailable. We are conducting a thorough investigation to identify the root cause and restore the service. Thank you for your patience and understanding. --- Chers utilisateurs, Nous rencontrons actuellement des problèmes intermittents affectant notre API et notre plateforme suite à une augmentation soudaine de l'activité de la base de données. Cela entraine : - Une dégradation des performances de l'API : augmentation des temps de réponse et erreurs 520 intermittentes pour les requêtes API. - Une indisponibilité de la plateforme : la plateforme Shippeo est temporairement indisponible. Nous menons actuellement une enquête approfondie afin d'identifier la cause profonde du problème et de rétablir le service. Nous vous remercions de votre patience et de votre compréhension.

2. monitoring Feb 27, 2026, 04:35 PM UTC

   The platform experienced two periods of intermittent service disruption Today at 16:25 – 16:35 and 16:45 – 17:00: During this window, our API were unavailable and requests may have been rejected with 520 errors, and the access to the Platform was not possible. Our technical team has relaunched the EDI Inbound and Outbound services which reduce the surge on our database. Since, system connectivity has been restored, and we are currently monitoring the situation to ensure all queued messages are processed correctly.

3. monitoring Feb 27, 2026, 05:06 PM UTC

   The corrective actions have successfully restored service. All systems are now operating normally: - API response times back to normal levels - Platform fully accessible We are still monitoring the situation closely

4. resolved Feb 27, 2026, 06:11 PM UTC

   All services were fully restored since 17:00 CET with queued messages processed. The incident is now closed Thank you for your patience during this brief disruption.

Read the full incident report →

Started Feb 24, 2026, 09:06 AM UTC· resolved Feb 24, 2026, 05:37 PM UTC

1. identified Feb 24, 2026, 09:06 AM UTC

   Dear users, Since 02:00 AM Paris time, we have been experiencing an incident affecting the processing of events for Parcel orders. As a result, tracking for Parcel orders created after 02:00 AM has not yet started. This issue is limited to Parcel orders and does not affect Road or Ocean shipments. Our technical team is actively working to implement a fix and restore normal activity. Thank you for your patience and understanding. ----- Chers utilisateurs, Depuis 02h00 (heure de Paris), un incident affecte le traitement des événements pour les ordres Parcel. En conséquence, le tracking des ordres Parcel créés après 02h00 est impacté. Cet incident est isolé aux ordres Parcel et n’affecte pas les ordres Route ou Ocean. Notre équipe technique travaille activement sur la mise en place d’un correctif pour rétablir la situation. Merci pour votre patience et votre compréhension.

2. monitoring Feb 24, 2026, 11:15 AM UTC

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

3. resolved Feb 24, 2026, 05:37 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 23, 2026, 02:39 PM UTC· resolved Feb 25, 2026, 08:14 AM UTC

1. investigating Feb 23, 2026, 02:39 PM UTC

   Dear Users, Since 17/02/2026 at 15:00 CET, we are experiencing instability with our Ocean integration services, affecting milestones processing from our Data Provider. This results in orders missing tracking and milestones. This issue do not affect orders using EDI315 (Direct carrier connection). We are currently investigating the root cause of this issue. Thank you for your understanding and patience as we work to fully restore the service. --- Chers utilisateurs, Depuis le 17/02/2026 à 15h00 CET, nous rencontrons une instabilité avec nos services d'intégration Ocean, affectant le traitement des jalons (milestones) provenant de notre fournisseur de données. Cela entraîne des ordres sans suivi ni jalons. Ce problème n'affecte pas les ordres utilisant l'EDI315 (connexion directe avec le transporteur maritime). Nous sommes actuellement en train d'investiguer la cause de ce problème. Nous vous remercions de votre compréhension et de votre patience pendant que nous travaillons à la pleine restauration du service.

2. identified Feb 23, 2026, 03:10 PM UTC

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

3. identified Feb 23, 2026, 05:46 PM UTC

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

4. monitoring Feb 23, 2026, 06:09 PM UTC

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

5. identified Feb 24, 2026, 08:32 AM UTC

   While our previous fix resolved a significant portion of the issue, we have identified that some ocean orders are still affected and are currently missing tracking updates. Our engineering team is actively investigating the root cause of these remaining cases and is working to implement a targeted fix as quickly as possible. We sincerely apologize for the inconvenience and thank you for your understanding and patience as we work to fully restore the service. We will provide a further update as soon as we have more information. -- Bien que notre précédent correctif ait résolu une grande partie du problème, nous avons identifié que certains ordres ocean sont toujours impactées et ne reçoivent pas de mises à jour de tracking. Notre équipe technique est activement en train d'investiguer la cause de ces cas résiduels et travaille à l'implémentation d'un correctif ciblé dans les plus brefs délais. Nous vous présentons nos sincères excuses pour la gêne occasionnée et vous remercions pour votre compréhension et de votre patience pendant que nous œuvrons à la restauration complète du service. Nous vous fournirons une mise à jour dès que nous aurons de nouvelles informations.

6. monitoring Feb 24, 2026, 02:09 PM UTC

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

7. resolved Feb 25, 2026, 08:14 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 17, 2026, 05:00 PM UTC· resolved Feb 17, 2026, 05:00 PM UTC

1. resolved Feb 17, 2026, 09:15 PM UTC

   Dear users, We identified an incident that affected the dispatch of ETA event towards external systems from 18:05 to 18:50 Paris time. The situation is back to normal now. We thank you for your understanding. -- Chers utilisateurs, Nous avons identifié un incident ayant affecté l’envoi d'ETA vers les systèmes externes de 18:05 à 18:50 (Paris). La situation est redevenue normale à présent. Nous vous remercions pour votre compréhension.

Read the full incident report →

Started Feb 11, 2026, 06:26 PM UTC· resolved Feb 11, 2026, 07:51 PM UTC

1. monitoring Feb 11, 2026, 06:26 PM UTC

   Dear users, An issue with our database affected the ETA computation from 18:30 CET to 19:15 CET on 11/02. The following symptoms were observed during that timeframe: - No ETA displayed or updated on the platform - No ETA transmitted to external systems - No ETA-based notifications (SMS and/or email) are sent A fix has been implemented to restore the service and our team are monitoring the situation. Some ETAs may continue to be generated with a delay while we work through the backlog that accumulated during the incident. Thank you for your understanding and patience. -- Chers utilisateurs, Un problème avec notre base de données a affecté le calcul de l'ETA Road de 18:30 CET à 19:15 CET le 11/02. Les symptômes suivants ont été observés : - L'absence d'affichage de l'ETA sur la plateforme web - L'absence de transmission de l'ETA aux systèmes externes - L'absence d'envoi de notifications basées sur l'ETA (SMS et/ou email) Un correctif a été mis en place pour rétablir le service et nos équipes surveillent la situation. Certaines ETA continuent d'être générées avec un délai, le temps que nous résorbions le retard accumulé lors de l'incident. Merci de votre compréhension et de votre patience.

2. resolved Feb 11, 2026, 07:51 PM UTC

   The incident is now resolved and the service is back to normal with no delay in ETA computation since 20:20 CET -- L'incident est désormais résolu et le service est revenu à la normale, sans retard dans le calcul des ETA depuis 20h20 CET.

Read the full incident report →

Started Feb 11, 2026, 02:34 PM UTC· resolved Feb 12, 2026, 09:21 AM UTC

1. investigating Feb 11, 2026, 02:34 PM UTC

   Dear users, Since Monday, 09/02, an incident has affected the integration of certain events for Road orders. As a result, you may notice the following on our platform: Some erroneous events-in lead to multiple retries sent to our systems from our clients' systems. No missing data is to be noted; only erroneous events were impacted. Our team is actively investigating the root cause and will provide updates in the coming hours. We appreciate your understanding and patience. --- Chers utilisateurs, Depuis le lundi 09/02, un incident impacte l’intégration de certains événements liés aux commandes Road. Par conséquent, vous pourriez constater sur notre plateforme : Certains événements erronés entraînent des tentatives d'envoi multiples depuis les systèmes de nos clients. Aucune donnée n’est manquante ; seuls les événements erronés ont été impactés. Notre équipe enquête activement sur la cause de cet incident et vous tiendra informés des évolutions dans les prochaines heures. Nous vous remercions de votre compréhension et de votre patience.

2. investigating Feb 11, 2026, 05:02 PM UTC

   We are continuing to investigate this issue.

3. monitoring Feb 12, 2026, 07:58 AM UTC

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

4. resolved Feb 12, 2026, 09:21 AM UTC

   This incident has been resolved.

Read the full incident report →