Previous incidents

May 2025
May 26, 2025
1 incident

Mercedes-Benz data not available

Resolved May 26 at 05:19pm CEST

Starting 2025.05.26 14:40 UTC we have noticed that the data delivery of Mercedes-Benz data is interrupted. We have informed the OEM and waiting for their reply.

Update: Problem resolved at 2025.05.26 15:30 UTC

May 06, 2025
1 incident

Mercedes-Benz data not available

Resolved May 06 at 07:11pm CEST

Starting 2025.05.06 18:30 CEST we have noticed that the data delivery of Mercedes-Benz data is interrupted. We have informed the OEM and waiting for their reply.

This issue only impacting Mercedes-Benz data on all delivery methods(Streaming/Rest)

it was resolved at 21:15 CEST.

May 05, 2025
1 incident

Activation delay for Ford vehicles

Resolved May 05 at 02:06pm CEST

We are currently facing delays in new Ford activations. You might see vehicles staying in the pending state longer than normal due to this. We are currently evaluating a manual workaround while the root cause is being addressed.

There's no impact on data delivery.

April 2025
No incidents reported
March 2025
Mar 06, 2025
1 incident

Renault risk of data feed instabilities

Resolved Mar 06 at 07:10am CET

Renault has been faced with instabilities with the dataflow this week. They are still analysing to identify the root-causes, and until there is a resolution, there is continued risk of instability in the upcoming days, on approximately the same time slot (05.00 AM to 09.00AM CET).

We will let you know as soon as we have new information.

Mar 04, 2025
1 incident

Disruption in Renault Vehicle Data

Resolved Mar 04 at 02:12pm CET

Renault had an incident on vehicle data delivery starting 06.00 CET until 09:24 CET.

According to the OEM and our monitoring, the Incident is resolved and the
backlog of messages are processed.

Mar 03, 2025
1 incident

Disruption in Renault Vehicle Data

Resolved Mar 03 at 06:30am CET

Starting at 05:30 UTC, we have stopped receiving vehicle data from the Renault feed. We have reported the issue to the OEM and are awaiting further updates. Our team is actively monitoring the situation, and we will provide updates as soon as we have more information.

Update: The issue was resolved at 13:30 UTC and backlog of messages is currently being processed.