Time: Oct. 23, 2024, 4:38 p.m.

Status: Resolved

Update: We have addressed the delay and are now operating at normal service levels. Thank you for your understanding and patience.

Time: Oct. 23, 2024, 12:12 p.m.

Status: Monitoring

Update: Since 9:00 AM UTC+2 on 23/10, we have been experiencing some delays in the processing and dispatch of events and positions within the Ocean scope. As a result, you may notice delays in receiving these messages. Our technical team has identified the root cause and implemented enhancements to address the issue. We expect to fully resolve the delay and restore normal processing by 18:00 UTC+2 on 23/10. Thank you for your understanding and patience.

Time: Oct. 22, 2024, 8:27 p.m.

Status: Resolved

Update: Dear users, Some delays in creating the orders via the Orders-in flow may have been observed between 16:00 UTC and 19:30 UTC. A fix has been implemented at 19:30 UTC. The incident is now resolved, no data have been lost. -- Bonjour, Des retards à la création d'ordres via le flux Orders-in ont pu être observés entre 16:00 UTC et 19:30 UTC. Un fix a été implémenté à 19:30 UTC. L'incident est maintenant résolu, il n'y a pas eu de pertes de données.

Time: Oct. 22, 2024, 7:03 p.m.

Status: Investigating

Update: Dear users, You may have noticed some issues with the Orders-in flow through our API. Our technical team is already investigating, and a fix should be implemented soon. More updates will follow. Thanks for your understanding. --- Bonjour, Nous avons identifié un problème impactant les flux entrants Orders-in via notre API. Nos équipes techniques investiguent sur ce sujet et un correctif devrait être déployé rapidement. Nous vous tiendrons informé dès que possible. Merci de votre compréhension.

Time: Oct. 22, 2024, 5:48 p.m.

Status: Resolved

Update: Dear Users, On 17/09/2024 at 18:00 CEST, we encountered instability with our Ocean integration services, specifically affecting the processing of files from Ocean shipping lines. As a result, some users may have experienced missing milestone events for tracked containers since that date. We identified and fixed the bug on 07/10, ensuring no further occurrences from that date onward. However, the missed milestone events were not sent via events-out during the affected period. We are currently in the process of recovering and reintegrating all missed milestones and replaying the events-out messages. This recovery process began on 07/10 and is expected to be fully completed by 25/10. We appreciate your understanding and patience as we work to fully restore service.

Time: Oct. 8, 2024, 12:18 p.m.

Status: Resolved

Update: This incident has been resolved.

Time: Oct. 8, 2024, 9:22 a.m.

Status: Monitoring

Update: Dear users, An incident is currently affecting the sending of Ocean positions-out and Ocean events-out flows. A potential fix has been deployed and we are actively monitoring the resolution. We thank you in advance for your understanding.

Time: Oct. 7, 2024, 11:13 a.m.

Status: Resolved

Update: Dear users, Our technical team has implemented a fix this morning to address the issue with "not trackable" containers. Existing orders have also been updated, and we should now be able to track them.

Time: Oct. 4, 2024, 1:17 p.m.

Status: Identified

Update: Dear users, We have identified tracking issues affecting certain Ocean containers in Shippeo following the release on 17/09. Some users may have observed containers marked as "not trackable" in their accounts. Our technical team has identified the root cause, and a solution is being prepared for implementation at the beginning of next week. As a temporary workaround, users may send an order update with the MBL reference to initiate tracking.