Flexera One IT Asset Management – NAM – Beacon Connectivity Issues

Update timeline

1. investigating May 07, 2026, 04:49 PM UTC

   Incident Description: We are currently investigating an issue affecting Beacon connectivity in the Flexera One IT Asset Management application in the North America region. Customers using Beacon may experience connectivity errors when attempting to upload inventory data or download Beacon-related updates. Priority: P2 Restoration Activity: Our technical teams are actively investigating the issue and working to restore normal Beacon upload and download functionality. We will provide updates as more information becomes available.

2. identified May 07, 2026, 06:07 PM UTC

   Our technical teams have identified the issue as a routing/configuration problem affecting Beacon communication following recent maintenance activity in the North America environment. This is preventing Beacon from successfully completing upload and download requests. Teams are working on the required configuration update to restore Beacon connectivity. We will provide another update as restoration work continues.

3. resolved May 07, 2026, 07:38 PM UTC

   Technical teams completed the required updates to restore communication through the affected service path in the North America environment. Upload and download requests are now completing successfully, and functionality has been validated. We will continue monitoring to ensure the service remains operational. This incident has been resolved.

4. postmortem May 21, 2026, 06:52 AM UTC

   **Description:** Flexera One – IT Asset Management – North America – Beacon Connectivity Issues **Timeframe:** Wednesday, May 6, 2026, 9:33 PM PDT – Thursday, May 7, 2026, 11:35 AM PDT ## Incident Summary On Wednesday, May 6, 2026, at approximately 9:33 PM PDT, a scheduled backend infrastructure change was performed in the North America production environment. Following this change, an issue was introduced that affected Beacon connectivity for Flexera One IT Asset Management customers in the North America region. During the affected period, customers experienced failures when attempting to upload or download data through Beacon. The issue affected Beacon API and configuration service connectivity, preventing successful uploads and downloads across the US production environment. The following morning, technical teams began investigating the issue after customer reports were received. During the investigation, it was identified that a configuration introduced during the infrastructure change was directing Beacon traffic to an incorrect backend path, preventing successful connectivity. Once the configuration was corrected, Beacon uploads and downloads began processing successfully. Multiple customers confirmed successful Beacon connectivity following the fix. By Thursday, May 7, 2026, at approximately 11:35 AM PDT, service was confirmed restored and the incident was considered resolved. Affected Beacon uploads would have automatically retried following service restoration. Technical teams continued monitoring following restoration to ensure recovery progressed as expected. ## Root Cause The incident was caused by a backend infrastructure change that introduced a configuration mismatch in the North America production environment. As a result, Beacon connectivity requests were directed to an incorrect backend path, causing all Beacon uploads and downloads to fail during the affected period. Once the configuration was corrected to point to the appropriate path, connectivity was restored. ## Remediation Actions The following actions were taken during the incident response: 1. **Configuration Corrected:** The affected configuration was updated to restore Beacon connectivity to the correct backend path. 2. **Beacon Connectivity Validated:** Technical teams confirmed that Beacon uploads and downloads were processing successfully following the correction. 3. **Customer Confirmation Received:** Multiple customers confirmed successful Beacon connectivity. 4. **Post-Restoration Monitoring Performed:** Recovery activity was monitored after restoration to ensure services continued operating as expected. ## Future Preventative Measures The following follow-up actions were identified during the incident: 1. **Cross-Team Change Coordination:** We are reviewing coordination procedures between teams involved in backend infrastructure changes to ensure that dependent services are validated before and after changes are applied. 2. **Remaining Region Updates:** Configuration updates for other regions are being coordinated as part of upcoming scheduled releases to ensure consistency and prevent similar occurrences.