Shippeo Outage History

Started Oct 21, 2026, 08:40 AM UTC· resolved Oct 22, 2026, 12:40 PM UTC

1. identified Oct 21, 2026, 08:40 AM UTC

   Dear Users, Between 16 and 17 October, an issue affecting our third-party ocean-tracking provider caused some estimated shipment milestones to be sent to Shippeo as actual events, including dates in the future. As a result, some shipments may display incorrect milestone information, and ETA updates may be delayed or inaccurate. Our teams are working to correct the affected shipment data. We are coordinating with the provider and evaluating the safest way to restore accurate milestone and ETA information. We will share another update once we have confirmed progress. Thank you for your understanding and patience. --- Chers clients, Entre le 16 et le 17 octobre, un incident affectant notre prestataire tiers de suivi maritime a entraîné l’envoi de certaines dates estimées de jalons comme s’il s’agissait d’événements réels, y compris avec des dates situées dans le futur. Par conséquent, certaines commandes maritimes peuvent afficher des informations incorrectes, et les mises à jour des dates estimées d’arrivée (ETA) peuvent être retardées ou inexactes. Nos équipes travaillent à corriger les données concernées. Nous collaborons avec notre partenaire et évaluons la méthode la plus sûre pour rétablir des informations fiables concernant les événements maritimes et les ETA. Nous partagerons une nouvelle mise à jour dès que nous aurons confirmé l’avancement de la correction. Nous vous remercions pour votre compréhension et votre patience.

2. monitoring Oct 22, 2026, 08:07 AM UTC

   A fix has been implemented to remove the inaccurate milestones. The cleanup is currently in progress. We will provide an update once it is complete.

3. resolved Oct 22, 2026, 12:40 PM UTC

   This incident has been resolved, and all inaccurate data has been successfully removed.

Read the full incident report →

Started Oct 20, 2026, 10:55 AM UTC· resolved Oct 20, 2026, 04:01 PM UTC

1. identified Oct 20, 2026, 10:55 AM UTC

   Due to an incident reported by our provider we are experiencing an issue affecting the freshness of data in with our analytics capabilities used by Insights dashboards, exports and Shippeo Ai. Some information, particularly order and container data, may be delayed and may not yet reflect the latest updates on the analytics. Certain analytics features such as Shippeo AI may also be temporarily unable to load the most recent data. Our teams are working with our data-platform provider to restore normal updates as soon as possible

2. identified Oct 20, 2026, 03:23 PM UTC

   We are continuing to work on a fix for this issue. We will update you as soon as possible with further information.

3. resolved Oct 20, 2026, 04:01 PM UTC

   The issue has been resolved, and the data is now up to date on the platform.

Read the full incident report →

Started Oct 15, 2026, 06:00 AM UTC· resolved Oct 15, 2026, 06:45 AM UTC

1. resolved Oct 15, 2026, 01:36 PM UTC

   Dear users, We have experienced some latencies on our web platform this morning from 06:30 to 08:20 CEST, causing delays in accessing and browsing and white pages. Our team has taken immediate action to restore normal service. Thank you for your understanding. ------ Chers utilisateurs, Nous avons rencontré des latences et des cas de pages blanches à la connexion sur notre plateforme web ce matin de 06:30 to 08:20 CEST. Notre équipe a pris des mesures immédiates pour rétablir le service normal. Merci pour votre compréhension.

Read the full incident report →

Started Oct 06, 2026, 11:18 AM UTC· resolved Oct 06, 2026, 01:09 PM UTC

1. investigating Oct 06, 2026, 11:18 AM UTC

   Dear users, We are investigating an issue affecting ETA updates. Some shipments may not display an ETA in the Shippeo platform, and ETA-based notifications or message out sent to external systems may be delayed or unavailable. 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 The issue was first detected on 5 October at approximately 17:00 CEST. The scope and cause are still under investigation.

2. monitoring Oct 06, 2026, 11:43 AM UTC

   The issue affecting ETA updates has been resolved. ETA information is now being generated and displayed normally; ETA-based notifications and message out are operating as expected. The incident affected ETA processing from 5 October at approximately 17:00 CEST until 6 October 13:40 CEST. We are continuing to monitor the service to confirm that volumes remain normal.

3. resolved Oct 06, 2026, 01:09 PM UTC

   The issue affecting ETA updates is now closed.

Read the full incident report →

Started Oct 02, 2026, 09:37 AM UTC· resolved Oct 02, 2026, 08:05 PM UTC

1. investigating Oct 02, 2026, 09:37 AM UTC

   Dear users, We are currently experiencing technical difficulties affecting login and platform access. Our team is actively working to resolve these issues and restore full functionality. Thank you for your patience and understanding. ------ Chers utilisateurs, Nous rencontrons actuellement des difficultés techniques affectant la connexion et l'accès à la plateforme. Notre équipe technique travaille activement à résoudre ces problèmes et à rétablir toutes les fonctionnalités. Nous vous remercions de votre patience et de votre compréhension.

2. investigating Oct 02, 2026, 09:45 AM UTC

   We are continuing to investigate this issue.

3. investigating Oct 02, 2026, 12:49 PM UTC

   We are continuing to investigate this issue.

4. monitoring Oct 02, 2026, 03:26 PM UTC

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

5. resolved Oct 02, 2026, 08:05 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 05, 2026, 09:30 PM UTC· resolved Sep 06, 2026, 02:21 PM UTC

1. investigating Sep 05, 2026, 09:30 PM UTC

   Dear users, We are currently experiencing an issue with our provider that is impacting ETA computations for Road and Ocean shipments. This issue has been ongoing since approximately 09:00 Paris time on September 5, 2026. The following symptoms have been observed on our platform: - No ETA displayed or updated for Road and Ocean orders - No ETA transmitted to external systems - No ETA-based notifications (SMS and/or email) are sent Our technical team will investigate and resolve this issue as soon as possible. Thank you for your understanding and patience. -- Chers utilisateurs, Nous rencontrons actuellement un problème avec notre fournisseur qui impacte la génération d'ETA Route et Ocean. Cet incident a débuté le 5 Septembre 2026 depuis environ 09h00 (heure de Paris). Les symptômes ci-dessous sont visibles sur la plateforme : - Aucun ETA affiché ou mis à jour pour les ordres Route et Ocean - Aucun ETA transmis aux systèmes externes - Aucune notification basée sur l'ETA (SMS, e-mail et/ou Whatsapp) n'est envoyé Notre équipe technique va investiguer ce problème pour rétablir le service dès que possible. Merci de votre compréhension et de votre patience. Nous vous remercions de votre compréhension et de votre patience.

2. monitoring Sep 05, 2026, 11:07 PM UTC

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

3. resolved Sep 06, 2026, 02:21 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 19, 2026, 10:26 AM UTC· resolved Aug 19, 2026, 05:28 PM UTC

1. investigating Aug 19, 2026, 10:26 AM UTC

   Dear users, We are experiencing an issue affecting the synchronisation of data in Shippeo Insights dashboards, exports and ShippeoAI. Visible symptoms: Insights remains accessible, but the data displayed in Insights dashboards, exports and ShippeoAI has not been updated since 17 August 2026. Root cause: The root cause is currently under investigation. Next steps: Our team is actively working to restore data synchronisation and ensure that the latest data is available across Insights dashboards, exports and ShippeoAI. Thank you for your understanding and patience. --- Chers utilisateurs, Nous rencontrons actuellement un problème affectant la synchronisation des données dans les tableaux de bord Insights, les exports et ShippeoAI. Symptômes visibles : Insights reste accessible, mais les données affichées dans les tableaux de bord Insights, les exports et ShippeoAI n’ont pas été mises à jour depuis le 17 août 2026. Cause : La cause exacte du problème est actuellement en cours d’investigation. Prochaines étapes : Notre équipe travaille activement à rétablir la synchronisation des données et à garantir la disponibilité des données les plus récentes dans les tableaux de bord Insights, les exports et ShippeoAI. Nous vous remercions pour votre compréhension et votre patience.

2. monitoring Aug 19, 2026, 01:20 PM UTC

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

3. resolved Aug 19, 2026, 05:28 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 23, 2026, 07:06 AM UTC· resolved Jul 27, 2026, 12:56 PM UTC

1. identified Jul 23, 2026, 07:06 AM UTC

   We are currently experiencing delays in the processing of ocean tracking data for some shipments tracked with EDI315. Tracking milestones and status updates may appear later than usual. Our teams are actively investigating the root cause, which has been traced to a performance issue with a third-party file transfer service. No data is being lost — all updates will be processed once the issue is resolved.

2. monitoring Jul 23, 2026, 02:28 PM UTC

   Our teams have identified the root cause of the delays affecting ocean tracking data updates and have applied corrective measures. The system is now processing data again and we are closely monitoring to confirm full recovery. The data pipeline is processing normally and the backlog of ocean tracking updates is being progressively cleared. We expect full recovery shortly and will post a final update once confirmed. No data has been lost.

3. resolved Jul 27, 2026, 12:56 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 21, 2026, 07:29 AM UTC· resolved Jul 22, 2026, 07:39 AM UTC

1. investigating Jul 21, 2026, 07:29 AM UTC

   We are currently experiencing a new disruption affecting ocean shipment tracking updates July 20, 2026 at ~12:25 PM. Tracking data for ocean shipments may appear outdated or not refreshing as expected. We identified and resolved a related issue yesterday (July 20), but a new interruption began shortly after. Our teams have been alerted and are actively investigating the root cause. Our technical team is currently investing this new occurence.

2. identified Jul 21, 2026, 09:01 AM UTC

   We are providing an update on the ongoing disruption affecting ocean shipment tracking. Our investigation has confirmed that the issue is wider than initially assessed: all ocean shipment tracking updates (including 315 and EDIFACT connections) are currently impacted, including milestone events, ETA calculations, and position updates — not only webscrapper provider tracked shipments. Our teams are actively working on restoring the service. While we do not expect significant data loss, some tracking events occurring during this period may not be fully recovered depending on the data received from our carrier partners. We will provide full clarity on this point as soon as possible. We sincerely apologize for the disruption.

3. monitoring Jul 21, 2026, 02:10 PM UTC

   We are pleased to confirm that our teams have restored processing and ocean shipment tracking data is now actively being caught up. No data has been lost during this incident. Tracking information may still appear delayed while the backlog is being processed, but updates will progressively return to normal. We are monitoring the situation closely and will confirm full restoration as soon as it is complete. We apologize for the disruption and thank you for your patience.

4. resolved Jul 22, 2026, 07:39 AM UTC

   We are pleased to confirm that the disruption affecting ocean shipment tracking, which began on July 16, 2026, has been fully resolved as of July 21, 2026 at ~3:30 PM CEST. What happened: A configuration change deployed on July 16 caused tracking data to stop processing silently for ocean shipments. This was detected on July 20 and initially addressed, but the recovery process triggered a secondary disruption that expanded to affect all ocean tracking services. A structural fix was deployed on July 21, fully restoring the service. Impact: Tracking updates — including milestones, ETA calculations, and position data — were delayed or unavailable across ocean shipments during this period. No tracking data was lost. Our teams are continuing to monitor closely service behaviour to ensure full stability. We sincerely apologize for the extended disruption and the impact this has had on your operations. We have identified the root causes and are implementing measures to prevent recurrence.

Read the full incident report →

Started Jul 20, 2026, 09:16 AM UTC· resolved Jul 20, 2026, 11:55 AM UTC

1. investigating Jul 20, 2026, 09:16 AM UTC

   We are currently experiencing an issue affecting the real-time tracking updates for ocean shipments since 16/07. As a result, some tracking information may not reflect the latest status and could appear outdated or delayed. All shipment data is being safely stored. No data has been lost. Our teams are actively working on a fix, and tracking updates will be restored and back-filled once resolved. We apologize for the inconvenience and will provide a further update within the next hour.

2. monitoring Jul 20, 2026, 11:37 AM UTC

   We have identified and resolved the root cause of the delays affecting ocean shipment tracking updates. A fix was deployed earlier today and tracking data is now being actively processed. You may still notice some residual delays as we work through the backlog of updates. No tracking data has been lost, and all information will be fully restored. We expect tracking to return to normal progressively over the coming hours. We will confirm once the service is fully back to normal. We apologize for the disruption and thank you for your patience.

3. resolved Jul 20, 2026, 11:55 AM UTC

   This incident has been resolved. Ocean shipment tracking updates are now fully operational and all delayed data has been successfully processed — no information has been lost. We apologize for the disruption experienced between July 16 and July 20, and thank you for your patience.

Read the full incident report →

Started Jun 29, 2026, 01:55 PM UTC· resolved Jun 29, 2026, 03:45 PM UTC

1. investigating Jun 29, 2026, 01:55 PM UTC

   Dear users, Since 14:00 CEST, an ongoing incident is affecting the upload and/or download of PODs on the web platform and via events-out. We are actively investigating the root cause and will provide updates in the coming hours. Thank you for your understanding and patience in the meantime. --- Chers utilisateurs, Un incident est en cours depuis 14h (heure FR) et affecte l'import et/ou le téléchargement des PODs sur la plateforme web et via les events-out. Nous investiguons activement pour identifier la cause et nous vous fournirons plus d'informations dans les prochaines heures. Merci de votre compréhension et de votre patience.

2. monitoring Jun 29, 2026, 02:27 PM UTC

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

3. resolved Jun 29, 2026, 03:45 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 26, 2026, 02:58 PM UTC· resolved Jun 29, 2026, 06:59 AM UTC

1. identified Jun 26, 2026, 02:58 PM UTC

   Dear users, We are currently experiencing delays in the delivery of tracking events and position updates. Some data that would normally appear in real time may be delayed by up to 1 hour. Our technical team has identified the source of the issue and is actively working on a fix. No data is being lost — all events will be delivered once normal processing resumes. We apologize for the inconvenience and will provide an update within the next hour.

2. resolved Jun 29, 2026, 06:59 AM UTC

   The delay has been resolved at 2 am on Saturday 27th June. The service has operated normally since.

Read the full incident report →

Started Jun 26, 2026, 04:00 AM UTC· resolved Jun 27, 2026, 01:30 AM UTC

1. resolved Jun 30, 2026, 01:03 PM UTC

   Dear users, We have identified an incident that affected orders created prior to 26/06 at 06:00 CEST or between 26/06 at 06:00 and 29/06 03:30 CEST for a specific list of Shippeo organizations with pull API integrations. This issue has been resolved since 29/03 at 03:30 CEST and all orders created afterward are now tracked as expected. Thank you for your understanding.

Read the full incident report →

Started Jun 23, 2026, 04:23 PM UTC· resolved Jun 25, 2026, 07:20 AM UTC

1. investigating Jun 23, 2026, 04:23 PM UTC

   Dear users, We have identified an incident that is affecting the data freshness on the Insights dashboards, leading to out-of-date data being displayed. We are actively investigating the root cause and will provide updates shortly. Thank you for your understanding and patience in the meantime. --- Chers utilisateurs, Nous avons identifié un incident qui affecte la mise à jour des données sur les tableaux de bord Insights, entraînant l'affichage de données obsolètes. Nous investiguons activement pour identifier la cause et reviendrons vers vous dès que possible. Merci de votre compréhension et de votre patience.

2. identified Jun 24, 2026, 08:02 AM UTC

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

3. resolved Jun 25, 2026, 07:20 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 23, 2026, 12:00 PM UTC· resolved Jun 23, 2026, 12:00 PM UTC

1. resolved Jun 23, 2026, 01:38 PM UTC

   We inform you that next Tuesday, at 2:00 PM EU/Paris, we will be activating our latest features and platform improvements. This update is part of our monthly release cycle designed to deliver enhancements more efficiently with minimal impact on your operations. This process will have no impact on data collection or the processing of active orders. If you notice any unexpected behavior after this update, please contact our support team at: [email protected]. -- Nous vous informons que mardi prochain, à 14h00 EU/Paris, nous procéderons à l'activation de nos dernières fonctionnalités et améliorations de la plateforme. Cette mise à jour s'inscrit dans notre cycle de déploiement mensuel, conçu pour livrer des améliorations plus efficacement tout en minimisant l'impact sur vos opérations. Cette intervention n'aura aucun impact sur la collecte des données ni sur le traitement des ordres en cours. Si vous constatez des comportements inhabituels après cette mise à jour, n'hésitez pas à contacter notre équipe support à : [email protected].

Read the full incident report →

Started Jun 22, 2026, 02:59 PM UTC· resolved Jun 22, 2026, 04:36 PM UTC

1. identified Jun 22, 2026, 02:59 PM UTC

   We are currently aware of an issue affecting the Shippeo mobile application. Some users may be experiencing difficulties searching for shipments within the app, as well as pairing via tracking links. Our team has identified the issue and is actively working on a fix.

2. monitoring Jun 22, 2026, 03:09 PM UTC

   A fix has been implemented and the Tour search and tracking link pairing functionalities are operational. We are monitoring the situation.

3. resolved Jun 22, 2026, 04:36 PM UTC

   The incident has been resolved. The mobile app services operate as expected.

Read the full incident report →

Started Jun 15, 2026, 03:45 PM UTC· resolved Jun 15, 2026, 05:12 PM UTC

1. resolved Jun 16, 2026, 12:20 PM UTC

   Due to an internal incident, on 15/06 between 17:45 and 19:12 CEST, some notifications may have been delivered with a delay of up to 1 hour 30 minutes. Our team quickly identified and resolved an internal system configuration issue that was preventing our notification service from operating normally. During the incident, notifications were not lost they were queued and delivered with delay once the issue was fixed. We have resolved the issue affecting notification delivery. All notifications are now being dispatched normally.

Read the full incident report →

Started Jun 14, 2026, 08:05 AM UTC· resolved Jun 15, 2026, 07:41 AM UTC

1. investigating Jun 14, 2026, 08:05 AM UTC

   Dear users, We have identified an issue affecting the dispatch of ETA updates event for Ocean shipments, resulting in delay and/or missing ETA predictions for Ocean containers on your end since June 12th, 2026 evening. Our engineering team has been alerted and a thorough investigation will be conducted to identify the root cause. We will keep you informed on our progress.

2. resolved Jun 15, 2026, 07:41 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 11, 2026, 12:51 PM UTC· resolved Jun 12, 2026, 07:43 AM UTC

1. investigating Jun 11, 2026, 12:51 PM UTC

   Dear users, We are currently investigating an issue affecting the dispatch of milestone and ETA updates event for ocean shipments. Some ETA predictions and milestone events for ocean containers may be delayed or missing on your end since June 9th, 2026. Our engineering team has been alerted and is actively investigating the root cause. We are working to restore the full and timely delivery of tracking data as quickly as possible. Thank you for your patience.

2. monitoring Jun 11, 2026, 03:59 PM UTC

   Our engineering team has identified the root cause of the issue affecting ETA and milestone updates for ocean shipments and has deployed a fix. Early results show that tracking update volumes are returning to normal levels. We are closely monitoring the situation to confirm full stability. We will provide a further update once we have confirmed the fix is fully stable. Thank you for your patience.

3. resolved Jun 12, 2026, 07:43 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 11, 2026, 07:37 AM UTC· resolved Jun 11, 2026, 09:35 AM UTC

1. investigating Jun 11, 2026, 07:37 AM UTC

   Dear users, The web platform has been inaccessible since June 10th evening for some users. Our technical team has identified the root cause, and a fix will be developed to resolve this incident promptly. Further updates will be provided within the hour. We appreciate your patience and understanding. --- Chers utilisateurs, La plateforme web est inaccessible depuis le 10 juin fin de journée pour certains utilisateurs. Notre équipe technique a identifié la cause, et un correctif sera développé pour résoudre cet incident rapidement. Plus d'informations seront fournies dans les prochaines heures. Nous vous remercions de votre patience et de votre compréhension.

2. identified Jun 11, 2026, 07:49 AM UTC

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

3. resolved Jun 11, 2026, 09:35 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 04, 2026, 02:03 PM UTC· resolved Jun 04, 2026, 02:17 PM UTC

1. identified Jun 04, 2026, 02:03 PM UTC

   Dear users, Since 15:00 CEST, an issue is affecting the processing of flows-in and transmission of flows-out. Our technical team has implemented a fix to mitigate the delay and is currently monitoring the situation. We appreciate your understanding and patience on this matter. -- Chers utilisateurs, Un problème affecte le traitement des flux entrants et la transmission des flux sortants depuis 15h. Notre équipe technique a déployé un correctif pour diminuer le délai et surveille actuellement la situation. Merci pour votre compréhension.

2. resolved Jun 04, 2026, 02:17 PM UTC

   This incident has been resolved.

Read the full incident report →

Started May 18, 2026, 06:39 AM UTC· resolved May 18, 2026, 08:19 AM UTC

1. investigating May 18, 2026, 06:39 AM UTC

   Dear users, Since 8:00 PM UTC+2 on 17/05, we have experienced delays in dispatching vessel positions and Shippeo ETA messages within the Ocean scope. ETA computation and ingestion of position on the platform are not impacted. Our technical team is investigating the issue to restore the service as soon as possible. Thank you for your understanding and patience.

2. monitoring May 18, 2026, 07:47 AM UTC

   Dear users, The problem was identified and corrected. The queue is now re-processing all messages accumulated. Our technical team is monitoring the re-processing and we will confirm once the service is back to normal. Thank you for your understanding and patience.

3. resolved May 18, 2026, 08:19 AM UTC

   The accumulated backlog has been reprocessed and the service is now back to normal.

Read the full incident report →

Started May 12, 2026, 03:59 PM UTC· resolved May 12, 2026, 05:47 PM UTC

1. monitoring May 12, 2026, 03:59 PM UTC

   Dear Users, We are currently experiencing delays in processing Order-in messages on our platform. What's happening: As of approximately 16:45 CEST today, our Order-in processing is experiencing delays of around 5 minutes to integrate orders on our systems. Impact on your operations: • Order-in messages are being processed, but with a delay of up to one hour • If your integration performs order creation and immediate follow-up actions (such as chartering or pairing) within seconds, you may temporarily encounter "order not found" errors until the initial order has been fully processed Current status: Our systems are processing the queue and we are actively monitoring the situation. Order data integrity is maintained - this is a processing delay only, not a data loss issue. Recommended action: If you encounter "order not found" errors for recently created orders, please retry your request later on. All orders are being processed successfully, just with additional latency. We will provide an update as soon as possible. Thank you for your patience and understanding. Best regards, --- Chers Utilisateurs, Nous connaissons actuellement des délais dans le traitement des messages Order-in sur notre plateforme. Situation actuelle : Depuis environ 16h45 CEST aujourd'hui, le traitement des Order-in connaît des délais d'environ 5 minutes pour intégrer les ordres dans nos systèmes. Impact sur vos opérations : • Les messages Order-in sont traités, mais avec un délai pouvant aller jusqu’à 1 heure. • Si votre intégration effectue la création d'ordres suivie d'actions immédiates (telles que l'affrètement ou l'appairage) en quelques secondes, vous pourriez rencontrer temporairement des erreurs "order not found" jusqu'à ce que l'ordre initial soit entièrement traité Statut actuel : Nos systèmes traitent la file d'attente et nous surveillons activement la situation. L'intégrité des données est maintenue - il s'agit uniquement d'un délai de traitement, sans perte de données. Action recommandée : Si vous rencontrez des erreurs "order not found" pour des ordres récemment créés, veuillez réessayer votre requête plus tard. Tous les ordres sont traités avec succès, avec simplement une latence supplémentaire. Nous vous fournirons une mise à jour dès que possible. Merci pour votre patience et votre compréhension.

2. resolved May 12, 2026, 05:47 PM UTC

   This incident has been resolved and the processing queue is now operating at normal

Read the full incident report →

Started May 11, 2026, 10:29 AM UTC· resolved May 11, 2026, 10:45 AM UTC

1. investigating May 11, 2026, 10:29 AM UTC

   We are currently investigating an issue affecting some users' ability to log in to the Shippeo platform. Affected users may see an error message when attempting to sign in Invalid_request : No client found. Workaround available: You can access the platform directly via http://web.shippeo.com to bypass this issue in the meantime. Our team is actively working to identify and resolve the root cause. We will provide the next update within 1 hour. We apologize for the inconvenience and thank you for your patience.

2. resolved May 11, 2026, 10:45 AM UTC

   The issue affecting users' ability to log in to the Shippeo platform has been resolved. All services are now operating normally and users can log in without any issues. We apologize for the inconvenience caused. If you are still experiencing any difficulties, please do not hesitate to contact our support team.

Read the full incident report →

Started May 07, 2026, 10:00 AM UTC· resolved May 07, 2026, 10:00 AM UTC

1. resolved May 07, 2026, 12:37 PM UTC

   Dear users, We have experienced some delay in integrating EDI files related to events for specific carriers. Please be assured that no data has been lost. This incident only affected the timely integration of incoming events and the transmission to external systems. This was resolved since 14:14 UTC+1. All events have been integrated successfully. Thank you for your understanding -- Chers utilisateurs, Un incident a causé un retard dans l'intégration des fichiers EDI relatifs aux événements de certains transporteurs. Soyez assurés qu'aucune donnée n'a été perdue. Cet incident a uniquement retardé l'intégration des événements et la transmission aux systèmes externes. Le problème a été résolu depuis 14h14 UTC+1. Tous les événements ont été intégrés avec succès. Merci de votre compréhension.

Read the full incident report →