Flexera One – IT Asset Management – North America – Beacon Communication Errors

Update timeline

1. investigating Nov 15, 2025, 08:04 AM UTC

   Incident Description: We are investigating an issue impacting beacon connectivity in the North America region. The affected customers may experience errors when attempting to upload or download data through beacon endpoints, including messages indicating “502 error (Bad Gateway).” Priority: P2 Restoration Activity: Our teams are actively investigating reports of connection failures. Initial findings indicate that certain beacon endpoints are returning errors when processing requests. Technical teams are reviewing routing and endpoint configurations to identify the cause and restore normal operation.

2. resolved Nov 15, 2025, 08:28 AM UTC

   Our teams identified that the issue was caused by a recent configuration change and successfully deployed a fix. All related errors have cleared, and services have been restored to normal operation.

3. postmortem Dec 01, 2025, 08:35 PM UTC

   **Description:** Flexera One – IT Asset Management – North America – Beacon Communication Errors **Timeframe:** November 14, 2025, 10:40 PM PST – November 15, 2025, 12:05 AM PST **Incident Summary** On November 14, 2025, starting at 10:40 PM PST, customers in the North America region may have experienced issues when attempting to upload or download data through their IT Asset Management \(ITAM\) beacons. The disruption resulted in “502 Bad Gateway” errors when beacons attempted to communicate with the beacon endpoint. Inventory data uploads continued to function, but adapters, policies, and other configuration downloads were impacted. The issue was identified shortly after it began and was traced to a configuration change introduced during a recent update. The change was intended for a later software version and was not compatible with the current production release. This caused newly scaled backend service instances to start in an incomplete configuration state, preventing them from successfully serving beacon requests. A correction was deployed to adjust the configuration logic for the current production version. Once applied, beacon communication was restored, and backend services resumed normal operation. Full recovery was confirmed at 12:05 AM PST. **Root Cause** The disruption occurred because a configuration change associated with an upcoming software version was unintentionally applied in the production environment, which is running an earlier release. This caused new backend service instances to initialize without required configuration components, resulting in failed responses to beacon download and communication requests. Once the correct version-specific configuration logic was applied, all beacon endpoint services returned to normal function. **Remediation Actions** 1. Configuration Correction Applied: The configuration logic was updated to ensure that only applicable steps execute for the current production release. 2. Beacon Endpoint Services Restored: All backend service instances were corrected and returned to a healthy operational state. 3. Traffic Recovery Confirmed: Beacon connectivity was fully restored, with “502 Bad Gateway” errors no longer observed. 4. Validation Performed: Post-restoration validation confirmed that upload and download operations were functioning as expected. **Future Preventative Measures** To prevent recurrence, Flexera is implementing the following improvements: • Strengthening version-specific safeguards for configuration changes to ensure new components or logic do not apply prematurely in production. • Enhancing validation steps during deployment to confirm all backend service instances start in a fully healthy configuration state.