What happened?
⚠️ Between 11:04 and 11:35 AM UTC, a subset of requests to our Flespi telemetry backend began returning 403 Forbidden. Flespi support was contacted, who indicated that problem was related to a failed rolling deployment of one of their microservices, which caused that service to start up incorrectly and reject valid calls.

Impact:
Only requests routed to the mis-started node were affected.
No customer-facing functionality was disrupted—our main Fleet and TSP Admin apps remained fully operational.
We first detected it on a single simulator device during routine testing; no live customer devices were impacted.

Resolution:
Flespi team indicated they rolled back the failed service deployment and fixed the problem.
We verified that all flespi API calls are now succeeding.
We monitored logs and metrics to ensure full recovery.

Status:
✅ Fully resolved as of 11:35 AM UTC.
We apologize for any confusion this may have caused and appreciate your patience.

Please reach out to us at support@telematicsinsights.ai if you observe any lingering issues.