Incident During the Deployment of a New Release on April 21, 2026

[Updated on April 23, 2026]

On April 21, 2026, during the deployment of a new version of the Live Objects platform, an incident occurred starting at 10:15 AM CEST. This update involved complex changes to the data bus, including FIFO MQTT, which did not perform as expected despite prior testing.

The impact was as follows:

• LoRaWAN messages were successfully collected and stored, but messages from around 10:15 AM to 12:25 PM CEST could not be routed to client servers.
  However, these messages remain accessible via the portal or Data streams & Data search APIs.
  
  We have a replay mechanism in the routing rules for messages that were not delivered during this period.
  This mechanism will be activated only upon request to ensure it doesn’t impact clients’ data processing who may not support it. If you’d like to take advantage of this feature, please contact Live Objects technical support via this form or email.
  
  
• Devices using MQTT, LwM2M, and x-connector experienced connection issues to the platform between 10:15 AM and 2:00 PM CEST. Additionally, there was a temporary inability to collect, store, and route messages from SMS, MQTT, LwM2M, and x-connector devices to client servers.
  
  
• Unfortunately, pending messages in the FIFO queues at the start of the incident (10:15 AM CEST) have been lost.

The root causes of this incident are under analysis. The update to the data bus evolution has been postponed to a later date.

We sincerely apologize for any inconvenience caused.
We will regularly update this blog as the situation progresses.