We are investigating an issue with the resampled data downloads, API endpoint, and map data
Updates
Resolution
We added a bundled timezone database, so timezone handling no longer depends on the underlying system. We also added automated tests that catch this class of issue before release. All resampled data and map history are available again for every device, including the time range of this incident.
Cause
A platform update on November 19th, 2026, changed the system timezone database. It no longer recognized some legacy timezone names that resampled data relies on.
We have implemented a fix and will push to production shortly.
Beginning around 4 PM ET on November 19th, 2026, requests for resampled (hourly, 8-hour, and daily) data returned errors for some devices. This affected the /v1/data/resampled/ API endpoint and the 24-hour history charts on the map. Only devices configured with certain older timezone names, such as US/Eastern, were affected.
Impact:
- API: resampled data requests for affected devices returned HTTP 500 errors.
- Map: the 24-hour history chart didn’t load for affected devices.
- Unaffected: data collection. All sensors kept reporting normally, no data was lost, and raw and final data downloads kept working.
← Back