Is Aruba User Experience Insight down?

We are investigating an issue during the process of assigning sensors to a group on our dashboard. Users will notice that when a sensor is assigned to a new or existing group, that assignment does not reflect correctly on the Experience page of the dashboard.

We have identified the cause of the issue and are working on a fix for it.

A fix has been released to correctly represent the sensor group assignments on the Experience page of the dashboard. This fix ensures that any changes going forward are correctly updated. We are also resolving any inconsistencies in existing assignments. We are monitoring the roll out.

We are continuing to monitor for any further issues.

This incident has been resolved.

The certificate issued by public LibreSpeed servers has expired. As a result, any UXI sensor executing a LibreSpeed test against the public servers will raise an alert due to the expired certificate. Turning off the "secure" toggle on the LibreSpeed test configuration forces the sensor to skip any TLS validation of LibreSpeed test. This is a temporary solution to work around the expired certificate error but may not be appropriate for some environments. Alternatively the alert can be muted on the dashboard itself, however the test will not be run due to the failed certificate validation. If your environment depends on the output of LibreSpeed throughput tests and an insecure configuration for the test is not possible, it's recommended that you configure a local LibreSpeed server to continue executing the tests. For instructions on configuring a local LibreSpeed server please review the following support article: https://help.capenetworks.com/en/articles/5463729-testing-throughput-latency-and-jitter-with-librespeed

The certificate issued by public facing LibreSpeed servers has been updated and the sensors should resolve any open errors which were created against the service shortly. Please revert any changes applied to your dashboard configuration to account for this error as the core issue itself has been resolved.