Shippeo incident

[INCIDENT] Delays on the transmission of Events-out on Road and Ocean to external systems

Major Resolved View vendor source →

Shippeo experienced a major incident on April 14, 2026 affecting Events Tracking and Events Tracking and 1 more component, lasting 19h 15m. The incident has been resolved; the full update timeline is below.

Started
Apr 14, 2026, 11:53 AM UTC
Resolved
Apr 15, 2026, 07:09 AM UTC
Duration
19h 15m
Detected by Pingoru
Apr 14, 2026, 11:53 AM UTC

Affected components

Events TrackingEvents TrackingGPS trackingEDI

Update timeline

  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.