Notice history

Oct 2025

Resolved
October 09, 2025 at 4:24 AM
Resolved
October 09, 2025 at 4:24 AM
The incident affecting the EU1 region of The Things Industries (TTI) — and consequently the Datacake LoRaWAN Network Server (LNS) — has been resolved.
TTI has confirmed that services in the EU1 region are fully operational again. LoRaWAN data ingestion and related functionality have returned to normal.
We will continue to monitor system performance, but no further impact is expected.
For reference, see TTI’s incident report: https://status.thethings.industries/incidents/8bvwyj791rrm.
Monitoring
October 08, 2025 at 1:22 PM
Monitoring
October 08, 2025 at 1:22 PM
The Things Industries (TTI) has implemented a fix for the issue affecting the EU1 region. Both TTI and Datacake are now monitoring the situation to ensure full recovery of all affected LoRaWAN data flows.
We will continue to observe system performance and provide further updates if necessary.
Investigating
October 08, 2025 at 10:10 AM
Investigating
October 08, 2025 at 10:10 AM
We are currently observing a partial outage impacting the EU1 region of The Things Industries (TTI). This affects both the Datacake LoRaWAN Network Server (LNS) and customers who operate their own TTI instances in the EU1 region.
As a result, some LoRaWAN devices may experience delayed or missing uplinks until the issue is resolved.
The incident originates from TTI’s infrastructure. For the latest updates, please refer to their official status page: https://status.thethings.industries/incidents/8bvwyj791rrm.
We are monitoring the situation closely and will update this post as more information becomes available.

Resolved
October 10, 2025 at 7:43 AM
Resolved
October 10, 2025 at 7:43 AM
The issue causing incomplete historical data display for certain devices has been resolved. All data is now fully accessible across dashboards and the application.
What Happened:
We identified an issue where historical data from early to mid-September 2025 was not appearing in queries and visualizations for specific devices in certain retention plans. The root cause was traced to a bug in our time-series database software related to Bloom filters on compressed data chunks. These filters were incorrectly marking data as non-existent, causing the database to skip chunks that actually contained the requested data.
Resolution:
Our database vendor Timescale identified and fixed a software bug in their compression filtering logic. The fix has been applied to our database instance, and all queries now return complete and accurate results.
Data Safety:
All data remained safely stored throughout this incident. No data was lost or corrupted - it was simply not being returned in certain filtered queries due to the database software bug.
We appreciate Timescale's quick response in identifying and resolving this issue. We apologize for any confusion or inconvenience this may have caused and thank you for your patience.
Investigating
October 06, 2025 at 11:56 AM
Investigating
October 06, 2025 at 11:56 AM
We are currently experiencing an issue where dashboards and other parts of the application may show incomplete historical data for certain devices in specific retention plans.
Data from early to mid-September 2025 may not be visible in queries and visualizations for affected devices, though all data remains safely stored and intact.
We have identified the root cause as a database indexing issue with our external database vendor and are working directly with their support team to resolve it.

All systems operational

Oct 2025

Sep 2025

Aug 2025

Datacake - Notice history

All systems operational

Notice history

Oct 2025

Sep 2025

Aug 2025