Skydio Cloud Outage History

Axon body-worn camera and fleet camera locations were unavailable in DFR Command from approximately 12:10 PM PT to 1:10 PM PT. Body-worn and fleet camera markers did not display on the map during this time. The issue originated on the Skydio side and has been fixed. All integrations are back online. If you experience any further issues, please reach out to Skydio Support.

From August 21 at 12:00 PM PT to August 23 at 4:15 PM PT, some customers attempting to "Fly Now" via the Fleet Page saw a tooltip saying "Run Mode Not Supported." This was resolved after entering and exiting Remote Flight Deck and could have delayed some manually initiated flights via Skydio Cloud. Scheduled missions were not affected. A fix has been deployed and this issue is now resolved. We are continuing to monitor system performance.

The deployed fix corrected the issue. This incident is now resolved.

We've been monitoring the situation, and the issue has not reoccurred.

We have resolved an issue affecting Skydio Cloud from 1:46 PM PT to 4:54 PM PT that resulted in degraded livestream quality from drones and docks, as well as some devices in Fleet Manager incorrectly appearing offline.

T-Mobile has announced that service has been restored. If you are still experiencing issues, please reach out.

From 3:55AM to 4:15AM PST, AWS had a region-wide outage that impacted multiple services, specifically causing network disconnects across the region. More details are available here: https://health.aws.amazon.com/health/status This outage caused the majority of Skydio devices to disconnect, showing offline. During this time, actively flying vehicles would have returned to their dock, and drones could not be launched. As soon as the AWS outage resolved, the devices reconnected and flight was able to resume.

This issue has been resolved.

We identified the root cause and rotated the nodes. We've monitored the system and everything in the Australia and Japan regions should be working.

This incident has been resolved.

We've identified that there is a resource leak in the underlying streaming service that we run, and under certain types of load, the server can get stuck. We've reduced the load and will be spending time to fix the resource leak. In addition, we are also working on expanding the cluster to multiple regions as a fallback initiative.

Skydio's live streaming and RFD functionality was degraded from approximately 5:35 PT to 6:45 PT. During this time, one of Skydio's media servers unexpectedly entered a degraded state, causing a portion of customers to experience intermittent errors when live streaming and connecting to RFD. The problematic server was removed from the pool which restored service. We are adding protections to prevent this class of bug from reoccurring and are improving our monitoring to reduce our response time.

We identified an error that impacted 65 customers with early access to the Fusus CAD integration. The issue was caused by an access policy configuration error. We deployed a fix, and the issue has been resolved. If you experience any further issues, please reach out to Skydio Support.

After updating to Cayley Minor Hotfix 2, customers should no longer see "Unsupported SW Version." We are adding extra safeguards into our SW roll out process to ensure this does not happen again.

We have fully root caused the issue and determined that our mitigation has fixed the issue. We are adding extra safe guards into our code to ensure that this class of bugs does not resurface, and we are improving our monitoring so that we can improve our response time. We are sincerely grateful to the pilots and customers who helped us root cause this issue by confirming our mitigations. Your help is greatly appreciated.

This incident has been resolved, no new issues have been reported.

This incident has been resolved, and no new reports of Pathfinder issues have been reported.

The incident has been resolved as of 4:45pm PST. We've validated that all Skydio customers are up and running as expected.

This incident has been resolved.

This incident has been resolved.

This incident has been resolved.

Incident is fully resolved. We have root caused the issue down to a configuration change that had an unexpected result when applied via our automated CI engine. We have a path to eliminating this class of issues going forward and will take action to get those safeguards in place.

This incident has been resolved.

We had a minor incident with a routine maintenance operation on our AWS RDS database. The estimated impacted time from AWS was 30 seconds, but in reality took closer to 2 minutes. We are monitoring the situation but think the situation is resolved.

The issue has been mitigated. New media should sync to Axon Evidence as per usual. Historical files that failed to sync will be reattempted over the course of the week.