After the certificate was added to the lrc-service and the service was restarted, uplinks were again being forwarded correctly to the endpoints.
However, data from October 25, 23:45 UTC, to October 26, 10:00 UTC cannot be delivered retroactively. We made every effort to recover and make this data available, but unfortunately this was not technically possible.
Posted Nov 09, 2026 - 11:54 CET
Update
We are currently working with the supplier to retrieve the data that was missing due to the disruption after the 20-10-2026 upgrade. As the data will be delivered in a different format than usual, we are first assessing how best to process and import it on our side.
Posted Oct 21, 2026 - 16:45 CEST
Monitoring
Around 21-10-2026 10:00, the data flow to the app servers was restored. The issue affected specific endpoints and was caused by a certificate not being loaded in the lrc-service.
After the certificate was added to the lrc-service and the service was restarted, uplinks were again forwarded correctly to the endpoints. We will further investigate why this occurred to help prevent recurrence.
Posted Oct 21, 2026 - 11:33 CEST
Identified
We have identified the cause of the issue, which was triggered by a migration initiated by our supplier last night. The issue appears to be resolved, and we are currently seeing incoming messages again; however, we are awaiting official confirmation from our supplier before closing the incident.
Posted Oct 21, 2026 - 10:23 CEST
Investigating
We are currently investigating an issue affecting the delivery of LoRa messages from our supplier to KPN, with impact since 20-10-2026 23:45 CEST. The supplier has been investigating since 08:00 and has confirmed that messages are currently buffered on their side.