Flexera One – IT Asset Management – EU – Reconciliation Failures
開始 2026年8月13日 1:08 UTC · 4h 49m
Outage重大なインシデント
影響を受けたコンポーネント
IT Asset Management - EU Batch Processing System
investigating
Incident Description: We are currently investigating an issue impacting the reconciliation process within the IT Asset Management platform in the EU region. Affected customers may experience failures when attempting to run reconciliation jobs. As a result, reconciliation processes may not complete successfully, potentially delaying data updates and downstream processing.
Priority: P2
Restoration Activity: Our technical teams have been engaged and are actively working to identify the root cause and restore services. Further updates will be provided as we continue working toward resolution.
monitoring
Our teams identified a configuration issue introduced during the completion of a standard release earlier today, which prevented an instance from successfully communicating with the Reconcile service.
The affected instance's configuration process was successfully re-executed, restoring the required settings and re-establishing connectivity with the Reconcile service. Validation testing confirmed normal service operation, and reconciliation processing has resumed successfully. The environment remains under monitoring to ensure continued stability.
monitoring
We are continuing to monitor for any further issues.
resolved
Following extended monitoring, our teams have confirmed that the platform has remained stable and no recurrence of the issue has been observed since the remediation actions were completed. Reconciliation processing continues to operate normally, connectivity with the Reconcile service remains healthy, and all validation checks have been successful.
Based on the sustained stability of the environment and the absence of any further failures, this incident has been resolved
Flexera One - Cloud Cost Optimization (CCO) - NAM - Service Degradation
開始 2026年8月11日 17:26 UTC · 3h 0m
Outage重大なインシデント
影響を受けたコンポーネント
Cloud Cost Optimization - US
investigating
Incident Description: We are investigating an issue affecting Cloud Cost Optimization (CCO) services in the North America (NAM) region. Customers may experience pages failing to load, prolonged loading behavior, or difficulty accessing certain Cloud Cost Optimization functionality within Flexera One.
Priority: P2
Restoration Activity: Our technical teams are actively investigating the issue and working to restore normal service. Current efforts are focused on identifying the cause of the degradation and validating corrective actions. We will provide additional updates as more information becomes available.
identified
Our investigation has identified the issue affecting certain Cloud Cost Optimization (CCO) functionality in the North America region. Following a recent service migration, some application components were not operating with the expected resource configuration, resulting in certain requests failing to complete and impacted pages remaining in a continuous loading state.
Our technical teams have implemented configuration changes to restore the appropriate resource allocation for the affected services and are currently deploying those changes. We are monitoring recovery and validating service functionality as the update takes effect.
We will provide additional updates as progress continues.
monitoring
The configuration changes have been deployed, and the affected service components are now operating with the intended resource configuration. Our technical teams have observed recovery of the impacted Cloud Cost Optimization (CCO) functionality in the North America region and are performing final validation to confirm service stability.
We will continue to monitor the environment closely and provide a further update once validation activities are complete.
resolved
Following a period of monitoring, services have remained stable and no further issues have been observed.
This incident is now considered resolved.
postmortem
**Description:** Flexera One - Cloud Cost Optimization \(CCO\) - North America - Service Degradation Affecting Certain Functionality
**Timeframe:** August 11, 2026, 9:51 AM PDT – August 11, 2026, 10:45 AM PDT
**Incident Summary**
On August 11, 2026, customers may have experienced issues accessing certain Cloud Cost Optimization \(CCO\) functionality in the North America region. Impacted pages could remain in a continuous loading state and fail to render correctly.
Technical teams began investigating after identifying that certain application requests were not completing successfully. The impact was limited to specific functionality rather than the entire CCO service.
During the investigation, technical teams determined that dependent application services were unable to successfully retrieve required configuration information from a supporting service component, resulting in rendering issues for affected functionality.
Corrective configuration changes were implemented and updated service components were deployed. Following deployment, technical teams validated recovery and continued monitoring the environment to confirm stable operation. All affected functionality subsequently returned to normal operation.
**Root Cause**
During a recent service migration, a supporting application component was deployed with an incorrect resource configuration. As processing demand increased, the affected service components exhausted available resources and became unavailable.
As a result, dependent application services were unable to successfully retrieve required configuration information needed to process certain requests. This resulted in rendering issues affecting specific Cloud Cost Optimization \(CCO\) functionality.
**Remediation Actions**
The following actions were taken during the incident response:
1. Incident Investigation Initiated: Technical teams investigated reports of affected CCO functionality remaining in a continuous loading state and failing to render correctly.
2. Service Dependency Analysis Performed: Technical teams identified that dependent application services were unable to successfully retrieve required configuration information from a supporting service component.
3. Configuration Issue Identified: Investigation determined that a supporting application component had been deployed with an incorrect resource configuration following a recent service migration.
4. Corrective Configuration Changes Applied: Technical teams implemented configuration changes to restore the intended operating parameters for the affected service components.
5. Service Recovery Validation Performed: Updated service components were deployed, affected functionality was validated, and the environment was monitored to confirm stable operation before incident closure.
**Future Preventative Measures**
Following this incident, technical teams reviewed the migration and deployment process associated with the affected service component.
1. Configuration Validation Enhancements: An additional validation step has been added to verify that service configurations are appropriate for forecasted processing requirements following migration activities. This additional review is intended to help identify configuration discrepancies before they can affect production workloads.
継続的な調査中、当社のチームは、問題がFlexera One EU 生産環境とビーコン通信に影響を及ぼす可能性があることを確認しました。 その結果、ビーコン・ツー・プラットフォーム通信に依存する追加の操作は影響を受ける可能性があります。 チームは、根本的な原因を調査し、衝撃のフルスコープを評価し、可能な限り迅速に解決を実施するよう努めています.
**Description:** Flexera One - APAC - Intermittent Service Disruption
## Timeframe
**Timeframe:** July 28, 2026, 3:16 PM PDT - July 28, 2026, 5:39 PM PDT
## Incident Summary
On Tuesday, July 28, 2026, at 3:49 PM PDT, customers using Flexera One services in the APAC region began experiencing intermittent service disruptions affecting multiple applications and platform capabilities. Customers may have encountered login issues, application errors, failed page loads, API errors, and intermittent access to certain Flexera One functionality.
During the incident, multiple services experienced intermittent communication failures with shared platform services. As a result, customers experienced inconsistent application behavior, with some requests succeeding while others failed.
Technical teams investigated the issue across affected applications and platform components to determine the scope and source of the failures. The investigation identified a connectivity issue affecting communication between application services and a shared platform dependency. Corrective configuration changes were implemented to restore service communication and stabilize affected functionality.
Following implementation of the corrective changes, technical teams validated functionality across impacted applications and confirmed that services had returned to normal operation. Continued monitoring showed stable service behavior, and the incident was resolved at 5:40 PM PDT on July 28, 2026.
## Root Cause
Investigation determined that the incident was caused by a connectivity issue introduced during a platform infrastructure migration.
Following the migration, certain application services continued using legacy connection ports when communicating with shared platform services. When affected services restarted, they attempted to communicate using endpoint and port combinations that were no longer aligned with the updated platform configuration.
This configuration mismatch resulted in intermittent communication failures between application services and shared platform components, causing customer-facing application errors and service disruptions across multiple Flexera One services in the APAC region.
## Remediation Actions
The following actions were taken during the incident response:
1. **Incident Investigation Initiated:** Technical teams investigated reports of intermittent failures affecting multiple Flexera One services in the APAC region and assessed the scope of customer impact.
2. **Dependency Analysis Performed:** Technical teams reviewed communication paths between impacted applications and shared platform services to identify the source of the connectivity failures.
3. **Configuration Mismatch Identified:** Investigation determined that certain services were attempting to communicate through legacy ports that were not aligned with the updated platform configuration following the migration.
4. **Platform Configuration Updated:** The required ports were added to the updated platform configuration, restoring connectivity for the affected services.
5. **Service Recovery Validation:** Technical teams validated functionality across impacted applications and confirmed that service communication and customer-facing functionality had returned to normal operation.
## Future Preventative Measures
The following improvements have been identified to further reduce the risk of similar incidents in the future:
1. **Platform Configuration Alignment:** Platform connectivity configurations were updated to ensure application services can communicate with shared platform components using the required connection ports. Maintaining alignment between service connectivity requirements and platform configurations helps reduce the risk of similar connectivity issues following future infrastructure changes.
**Description:** Snow Atlas - APAC - Login Failures and 404 Errors
**Timeframe:** July 26, 2026, 5:00 PM PDT to July 26, 2026, 6:15 PM PDT
**Incident Summary**
On Sunday, 26 July 2026, Flexera experienced a service disruption affecting Snow Atlas customers in the APAC Production environment, resulting in login failures and temporary inability to access Agreement pages. The issue was isolated to the APAc region, with no impact to other production regions.
Investigation by our technical teams determined that the disruption was caused by a backend service communication issue that prevented Agreement data from being retrieved successfully. The condition was consistent with a runtime synchronization issue following recent platform infrastructure maintenance.
Flexera teams validated platform health, restored the affected services, and confirmed successful recovery. Customer access was fully restored, and post-recovery monitoring confirmed stable operations with no recurrence of the underlying service communication errors.
A detailed post-incident review was completed, and corrective measures have been implemented to further strengthen platform resilience and recovery processes.
**Root Cause**
The incident was caused by an application communication failure within the APAC Production environment. A component responsible for processing requests between internal application services did not successfully handle Agreement-related requests, preventing those requests from being completed and resulting in customer-facing 404 errors and failures accessing Agreement pages.
**Contributing Factors**
* The application communication failure occurred following a recent infrastructure upgrade to the APAC Production environment.
* Although the application services and underlying infrastructure remained healthy, an internal service responsible for processing Agreement requests did not fully recover after the upgrade.
* Existing health checks validated application and infrastructure availability but did not verify the successful initialization of the internal communication path following the upgrade.
* The issue was therefore not detected until customers began experiencing login failures and HTTP 404 errors when accessing Agreement pages.
**Remediation Actions**
To restore service, technical teams:
* Confirmed the underlying infrastructure remained healthy throughout the incident.
* Identified the failed internal service communication affecting Agreement requests.
* Restarted the affected application services.
* Validated successful recovery across impacted tenants.
* Continued monitoring to confirm service stability.
**Future Preventative Measures**
* Enhanced Post-Upgrade Validation: Introduce additional validation checks following infrastructure upgrades to verify that critical application components and internal service communications are functioning as expected.
* Improved Monitoring and Alerting: Enhance monitoring and alerting to detect internal service communication failures and responder registration issues more quickly.
* Synthetic Health Checks: Implement synthetic health checks that validate critical customer workflows, including Agreement page functionality, following infrastructure changes.
**Description:** Flexera One – IT Asset Management – North America – Degraded Performance
**Timeframe:** July 20, 2026, 8:13 PM PDT – July 22, 2026, 8:41 AM PDT
**Incident Summary**
On July 20, 2026, at approximately 8:13 PM PDT, an issue began affecting Flexera One IT Asset Management customers in the North America production environment following completion of the production release.
During the affected period, some customers experienced intermittent application slowness, delayed processing, reconcile failures, timeout conditions, and degraded performance across inventory-related workflows. Technical teams investigated performance and reliability issues observed following the release and worked to determine the underlying cause and scope of impact.
The investigation determined that the observed behavior was associated with a defect previously identified in the release. Corrective changes intended to address the defect were included as part of the release activity; however, the corrective changes did not successfully apply across all North America production databases during the deployment process. As a result, some environments continued to experience significantly increased database processing activity during inventory-related operations, contributing to elevated resource consumption, processing delays, timeout conditions, and degraded application performance.
Technical teams worked to successfully deploy the corrective changes across the affected North America production databases. Following deployment, teams performed validation activities and monitored processing workflows to confirm recovery.
By July 22, 2026, at approximately 8:41 AM PDT, validation confirmed successful processing of previously impacted workloads and that the previously observed failure patterns were no longer occurring. The incident was considered resolved and technical teams continued monitoring to confirm service stability.
**Root Cause**
The incident was caused by corrective changes intended to address a previously identified defect not successfully applying across all North America production databases during the release deployment process.
As a result, the underlying defect remained active in affected environments and caused significantly more database processing activity than intended during inventory-related processing operations. This increased workload resulted in elevated resource consumption, processing delays, timeout conditions, and degraded platform performance.
These conditions contributed to intermittent application slowness, delayed processing, reconcile failures, and degraded performance affecting some IT Asset Management functionality within the North America production environment.
**Remediation Actions**
1. **Incident Investigation Initiated:** Technical teams investigated reports of application slowness, processing delays, reconcile failures, and degraded platform performance affecting the North America production environment.
2. **Impact Assessment Performed:** Teams reviewed customer-reported symptoms, system performance data, processing activity, and platform behavior to determine the scope and nature of the issue.
3. **Cause Identified:** Investigation determined that corrective changes intended to address a previously identified defect did not successfully apply across all North America production databases during the release deployment process.
4. **Processing Behavior Corrected:** Technical teams deployed corrections designed to eliminate the inefficient processing behavior that was contributing to elevated database workload, processing delays, timeout conditions, and degraded application performance.
5. **Recovery Validated:** Teams validated the effectiveness of the deployed changes through monitoring and successful execution of previously impacted processing activities.
6. **Post-Restoration Monitoring Performed:** Additional monitoring confirmed that the previously observed failure patterns and performance degradation were no longer occurring and that service stability had been restored.
**Future Preventative Measures**
Based on the investigation, the following follow-up activities have been identified:
* **Processing Logic Improvements:** Technical teams implemented and validated corrective changes to the inventory-processing logic responsible for the increased database workload observed following the release. These changes were designed to eliminate the inefficient processing behavior that contributed to processing delays, reconcile failures, timeout conditions, and degraded application performance.
* **Critical Hotfix Deployment Process Review:** Technical teams will review the deployment process for critical database hotfixes and evaluate alternative approaches to help ensure required corrective changes are successfully applied during future release activities.
**Description:** Flexera One - IT Asset Management - APAC - Missing Menu Items
**Timeframe:** July 12, 2026, 3:00 PM PDT - July 12, 2026, 7:16 PM PDT
**Incident Summary**
On Sunday, July 12, 2026, at 3:00 PM PDT, customers in the APAC production environment began reporting that several IT Asset Management \(ITAM\) menu items, including functionality such as Reports and All Applications, were no longer visible within the Flexera One user interface. Multiple customers were affected, impacting their ability to navigate and access portions of the ITAM application.
Technical teams immediately began investigating the issue and identified authentication-related errors affecting the ITAM user interface. During the investigation, teams reviewed infrastructure health, application behavior, and recent platform changes to determine the source of the problem.
The investigation determined that an application configuration change associated with a newly introduced authentication capability had been incorrectly applied to the production environment. The issue became apparent when application instances were refreshed, resulting in authentication-related failures that prevented certain ITAM menu items from loading correctly for affected users.
Technical teams reverted the affected configuration, refreshed the impacted application instances, and validated recovery across the environment. Following these actions, menu functionality was restored, affected customers confirmed recovery, and the incident was resolved on July 12, 2026, at 7:16 PM PDT after validation and monitoring confirmed normal operation had returned.
**Root Cause**
Investigation determined that an application configuration change associated with a new authentication capability was incorrectly applied to the production environment.
When application instances were subsequently refreshed, the incorrect configuration resulted in authentication-related errors within the ITAM user interface. These errors prevented certain navigation components from loading correctly, causing affected users to experience missing menu items until the configuration was corrected and the affected instances were refreshed.
**Remediation Actions**
The following actions were taken during the incident response:
1. Incident Investigation Initiated: Technical teams began investigating after receiving reports from multiple customers regarding missing ITAM menu items.
2. Application Configuration Reviewed: Recent application and configuration changes were reviewed to identify the source of the menu-loading failures.
3. Incorrect Configuration Identified: Technical teams determined that an authentication-related configuration change had been incorrectly applied to the production environment.
4. Configuration Corrected: The affected configuration was removed from the impacted production instances.
5. Application Instances Refreshed: Impacted application instances were refreshed to ensure the corrected configuration was consistently applied across the environment.
6. Recovery Validation Performed: Technical teams validated menu visibility and functionality across the affected environment and confirmed recovery with impacted customers.
**Future Preventative Measures**
Following the incident, corrective measures were implemented to prevent recurrence of the issue and improve detection of similar conditions in the future.
1. Health Check Monitoring Improvements: The existing health check was updated to detect the application behavior associated with this failure condition. The revised monitoring is designed to identify similar menu-loading and authentication-related application failures more effectively and accelerate detection should a similar issue occur in the future.
2. Deployment Process Reinforcement: The incident highlighted the importance of ensuring new authentication-related features are applied only to their intended environments. The deployment approach and expected application process for these changes have been reinforced with the technical team to reduce the risk of similar configuration issues in the future.
IT Asset Management - EU Inventory UploadIT Asset Management - APAC Inventory Upload
resolved
インシデント説明:APACおよび欧州環境における2026 R1リリース後のFlexera One IT Asset Managementの在庫処理に影響を及ぼす問題を特定しました。 その結果、一部のインベントリーアップロードが正常に処理されなかったため、Flexera One IT Asset Managementで表示されたインベントリーデータが遅延し、最近アップロードされた顧客在庫を反映しません。
優先順位: P2
修復活動:技術チームは、在庫処理に影響を及ぼす能力関連の問題を特定し、ターゲティングされたサービスが影響を受けた地域で再開し、通常の処理を復元しました。 本サービスは、6月24日(水)、2026日(金)、11:00 PM PDT に復元され、在庫ファイルが正常に処理されます。 当社のチームは、持続可能な安定性を確保するためにプラットフォームを監視し続けています。 調査が完了すると、根本的な原因と予防策を詳述するポスト・モルテム報告書が共有されます.
postmortem
**説明:** Flexera One- IT Asset Management-APACとEU - NDI Inventory Import Failures
**時間枠:** 6月 18, 2026, 09:00 AM PDT から 6月 25, 2026, 02:42 AM PDT
**事件要約**
2026年6月24日(水)、11:35 PM PDT、Flexera One IT Asset Management 2026 R1 リリースをオーストラリアおよびヨーロッパ生産環境に展開し、当社のチームは、NDI 在庫ファイルの処理に影響を及ぼす問題を特定しました。 その結果、処理中に失敗した膨大な数の在庫ファイルが、顧客の在庫データに反映されなかったため、Flexera One ITAMに表示された在庫情報は、影響を受けた顧客に発信されます。
技術的なチームはすぐに調査を開始し、2026 R1リリースで導入された在庫処理ワークフロー内で問題が発生したことを決定しました。 繰り返された処理失敗の後に蓄積された在庫ファイルは、在庫更新の成功の完了を防ぎ、影響を受けたサービスの処理負荷の増加に貢献します。
サービスを復元するには、影響を受ける環境に影響を受けたアプリケーションサービスをリフレッシュし、技術的なチームが是正措置を実施しました。 修復活動の後、在庫処理が正常に再開され、新しい在庫アップロードが期待通り処理されました。 継続的な監視により、安定したプラットフォームの動作が確認され、インシデントは、持続的な検証後に解決されたと宣言されました。
**ルート原因**
問題は、Flexera One IT Asset Management 2026 R1リリースで導入された欠陥によって引き起こされ、NDIの在庫ファイルの処理に影響しました。 特定の条件下では、認証および処理ワークフロー内の問題により、在庫ファイルが正常に処理できないため、処理が完了する前に拒否される可能性があります。
壊れたファイルが蓄積されたように、処理能力は繰り返し失敗によってますます消費され、成功した在庫処理を防ぎ、影響を受けた顧客のための在庫の更新を遅らせます。
工場の貢献
* 処理ワークフロー内で蓄積された在庫ファイルが失敗し、影響を受けた在庫サービスのリソース利用率を高めます。
※ 新規在庫処理リクエストの容量を削減した処理負荷が増加しました。
※2026 R1リリースの稼働環境に影響を受けた問題。リリースがまだ展開されていないため、北米産生は影響を受けていません。
**是正措置**
*技術チームは、影響を受けた在庫処理ワークフローを特定し、サービスを復元するための是正措置を実施しました。
* 適用サービスは影響を受けた生産の環境を渡って、正常な目録の処理を回復させました。
※サービス復元後に再開した新しい在庫ファイルの処理
* 処理性能を検証し、持続的な回復を確認するために、環境は強化された監視の下に残ります。
**将来の予防措置**
* リリース検証の改善 - リリース検証手順は、主要なプラットフォームリリース後の在庫処理ワークフローの追加エンドツーエンドのテストを含むように強化されます。
* 処理監視の強化 - 監視および警告は、異常な在庫処理障害の早期検出と処理キュー内の過度のファイル蓄積を提供するために検討および拡張されます。
* 操作性回復力 - 追加の保護具は、処理障害の回復を改善し、顧客の影響を最小限に抑えるために、在庫処理ワークフロー内で実施されます。
* コードの品質と見直しの改善 \(完了\) - ポストインシデントレビューの一環として、通信の失敗が適切に処理され、より広範な処理の影響を受けていないことを確認するために影響を受けたコードを修正しました。 また、今後の変更が承認される前に、レビュー結果が適切に評価され、対処されていることを確認するために開発およびレビュープロセスが強化されています.
公式のインシデント更新を自動翻訳しています。
Flexera One – EU – ログインアクセス無効
開始 2026年6月24日 8:00 UTC · 1h 0m
Outage重大なインシデント
影響を受けたコンポーネント
IT Visibility EUIT Asset Management - EU Login PageIT Asset Management - EU Beacon CommunicationIT Asset Management - EU Inventory UploadCloud License Management - EUIT Asset Management - EU Batch Processing SystemIT Asset Management - EU Business ReportingIT Asset Management - EU SaaS Manager
investigating
インシデント 説明: EU 地域の Flexera One へのログインアクセスに影響を与える問題を特定しました。 Flexera Oneにログインしようとすると、エラーが受けられます。
優先順位: P1
修復活動:当社の技術チームは、問題を積極的に調査し、通常のログイン機能を復元するための是正措置を実施します。 調査・安定化の取り組みは、現在進行中です。
今後も状況を監視し、進捗を継続してアップデートを継続的に提供してまいります.
