Telematics inSights Incident History

At 7:49 AM UTC the queue of Flespi intervals was fully dissolved and alert delays issue is completely resolved at this time. This completes the restoration of service. We apologize for the degraded performance over the last 18 hours. Flespi intends to publish detailed incident report later in July. We will share it here.

Our system is still working through the backlog of calculator intervals recalculated by Flespi - it's taking significantly longer that expected. It appears the recalculation might have been applied to all stored device messages. It is likely to take several more hours. Alerts will continue being delayed during this time.

Following analytics system restoration on Flespi side there's a significant number of alerts in the backlog, which are now being processed. Due to this new alerts coming in with delay. Once the backlog clears the system is expected to become fully operational

At 21:49 UTC Flespi reported that all systems were stable and the load was fully under control. They were still restoring analytics intervals with an estimated 2 more hours until fully restored.

We are experiencing degraded Telemetry Engine performance due to an ongoing connectivity incident affecting our telemetry provider, Flespi. The issue began affecting our platform at approximately 13:15 UTC time on July 10, 2026. The application remains available and its core functionality continues to operate. However, users may experience intermittent high response times when loading telemetry-dependent data, slower page loads, or occasional requests that require refreshing the web page. Flespi has reported problems with uplink connections to its datacenters while its provider mitigates a large-scale DDoS attack and reroutes traffic through a traffic-filtering service. Short intermittent disruptions may continue during this process. We are actively monitoring the situation and will provide another update as service performance stabilizes.