Aruba User Experience Insight Outage History

We have mitigated an intermittent DNS resolution issue affecting connectivity between UXI sensors and cdn.capenetworks.io. During the incident, more than half of the deployed sensor fleet was intermittently unable to resolve the domain, preventing affected sensors from reaching the UXI CDN. DNS protection and traffic-filtering controls have been applied, and connectivity is currently stable. We continue to monitor sensor recovery and are working with our DNS technology provider to identify the source of the elevated DNS traffic and establish a permanent corrective action. The UXI impact was first observed on October 1, 2026. Root-cause analysis remains in progress.

Both issues have been resolved.

The issue has been resolved, the root cause of the regression was a change in how the sensor interprets configuration and resulted in the EAP state machine on the sensor failing to correctly proceed with 802.1x authentication. This issue was not wide spread and only affected a subset of sensors in specific environments. The regression fix was only applied to affected devices, regular firmware update cycles will resume in the comings days and not further action or intervention is needed.

The Network management page has been restored to normal operation. We are not seeing any more errors when editing Wired and Wireless networks. Users would have observed these issues between 3 September at 22:00 and 23:37 UTC.

Between 04:15 and 07:00 UTC the Webhook system experienced an issue that caused message sending to be delayed. Customers with Webhooks configured would have experienced a delay in received their webhook. When the issue was patched, the backlog of Webhooks were processed and sent.

We have resolved the problem. This was due to a configuration change which has subsequently been reverted. There was no data loss for any customers or users.

We have resolved this now. There should not be any delays in sensor issue data.

A recent configuration change to our Public API caused some requests to fail with a 502 error. We've patched the change and confirmed the issue is resolved.

This incident has been resolved.

This incident has been resolved.

This incident has been resolved.

We have observed no further instability, the issue has been resolved and new account provisioning should work as expected.

This issue has been resolved.

This issue appears to be resolved.

This incident has been resolved.

This incident has been resolved.

This incident has been resolved.

Between 10:39 UTC and 11:18 UTC the Issue processing pipeline had stalled. During this time, issues updates were not being processed. No issues were lost during this period. We were able to restore the pipeline and process the backlog of issues.

We discovered an issue which resulted in incidents being delayed when sent to Data Push. This started on December 9th until today. We have fixed this issue and do not expect the incidents to be delayed anymore.

This incident has been resolved.

The cause was a server hardware failure. Our systems automatically replaced this but we needed to manually intervene for smooth recovery.

This incident has been resolved.

We experienced an issue in the pipeline between the UXI servers and GreenLake that caused: • Delays when provisioning new UXI Application Instances. • Failures when logging into the UXI Dashboard via GreenLake. The issue has now been resolved. All pending UXI Application Instance provisioning requests have been processed, and users are once again able to log into the UXI Dashboard using GreenLake. We appreciate your patience and apologize for any disruption this may have caused.

This incident has been resolved.