Degraded

Degraded performance of some of our services

While we have been updating our services to the latest version and introducing new features to our platform, we have observed that some of our services have experienced delayed reactions and increased latencies. Occasionally, brief outages lasting a few seconds have also occurred. Rest assured, our platform remains operational, and no data has been lost. However, we have noticed a decline in performance. We are actively working to resolve this issue and restore our platform’s full functionality.

Degraded

Ingestion services for NRI and DRI receivers disrupted

We are experiencing difficulties in receiving data from Network Remote ID (NRI) and Direct Remote ID (DRI) receiver devices. Certain Dronetag Mini and Dronetag RIDER devices may fail to transmit data and authorize upon initialization. We are currently investigating the matter.

Degraded

Detection Duplications for Some RID Receivers

We’ve identified an issue affecting some users of our RID receivers, resulting in unusually high amounts of detection duplications. Our investigation indicates that this impacts only users with multiple receivers operating in the same location and detecting the same RID aircraft. We are actively working on a fix and will provide updates as we make progress.

Degraded

RID Receivers Traffic Endpoint Malfunction

We experienced a period of degraded performance affecting our product's data ingestion pipeline, specifically impacting the DRI traffic endpoint. During the incident window, a subset of inbound data was not successfully received by the system, resulting in potential partial data loss.

Network Remote ID data was not affected by this incident. These data streams continued to flow and be processed without interruption. The integrity, availability, and completeness of Network Remote ID data have been fully preserved throughout the incident period.

Impact: Between 15 April 2025 at around 17:00 GMT and 16 April 2025 at 12:00 GMT, some data transmitted to the DRI traffic endpoint may not have been ingested or persisted as expected. This may have led to data gaps or inconsistencies for customers utilizing this endpoint during the affected timeframe.

We sincerely apologize for any inconvenience this incident may have caused and thank you for your continued trust in our service.