We experienced issues with our ingestion engine exposed through HTTP during 02:28-02:31 - 02:55-02:57, and 03:13 - 03:17 UTC on February 2nd. Access to end-users web apps was also affected by the issue, avoiding visualizing data stored at Ubidots.
During the issue time windows, our HTTP servers responded 50x standard errors, so users should have been able to capture the error and to set values read in their devices to be sent later.
The problem raised due to unexpected behavior at our internal DB, that derivates in the creation of non-valid indexes.