Flexera is currently experiencing a minor incident affecting Flexera Community, which began 19h ago. The vendor's full update timeline is below.
Affected components
Update timeline
- identified Sep 16, 2026, 09:04 AM UTC
Incident Description: We are currently experiencing an issue affecting the Flexera Community site. Due to an ongoing outage impacting a third-party service provider, customers may be unable to access the Flexera Community portal or may experience intermittent and unreliable behaviour. Additionally, customers may be unable to create, update, or interact with support cases through the Community site. Emails sent to [email protected] during this period may not be received or processed until the underlying outage has been resolved. Priority: P3 Restoration Activity: Our technical teams are actively monitoring the situation and working with the third-party provider to track restoration efforts. We will continue to assess customer impact and provide further updates as additional information becomes available.
- identified Sep 16, 2026, 12:31 PM UTC
The service provider has successfully validated the fix in a test environment and has begun deploying it across all affected instances. The rollout is progressing on a region-by-region basis, and services are returning to normal in regions where deployment has been completed.
- monitoring Sep 16, 2026, 07:25 PM UTC
Our service provider reports that service telemetry has remained healthy following deployment of the mitigation. Community remains accessible at this time, and no confirmed ongoing impact has been identified. We will continue monitoring the environment to ensure ongoing stability while final validation activities are completed. We will provide a further update as additional information becomes available.
- monitoring Sep 16, 2026, 10:00 PM UTC
Our service provider has declared the underlying incident resolved following successful mitigation and extended validation. Community remains accessible, and no confirmed ongoing impact has been identified. Monitoring throughout the recovery period has not identified any additional issues. This incident is now considered resolved.