Flexera incident
Snow Atlas - Australia - Data Ingestion and Export Disruption
Flexera experienced a major incident on June 2, 2026 affecting Snow Atlas - Australia and Snow Atlas API - Australia, lasting 1h 32m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jun 02, 2026, 02:46 PM UTC
Incident Description: We are currently investigating reports of Snow Atlas being inaccessible in the Australia region. The issue began following a scheduled maintenance window that extended beyond the planned downtime. Customers in the Australia region may be unable to access Snow Atlas at this time. Priority: P1 Restoration Activity: Our technical team is actively working to restore access and remediate the issue. We are continuing to monitor progress closely and will provide further updates as remediation efforts continue.
- investigating Jun 02, 2026, 03:20 PM UTC
We are continuing to investigate the issue affecting Snow Atlas in the Australia region following the scheduled maintenance window that extended beyond the planned downtime. Initial reports indicated that Snow Atlas was unavailable; however, based on the latest update, customers can now access the Snow Atlas application in the Australia region and view existing data. At this time, customers may be unable to ingest new data or export data while remediation efforts continue. Ingestion and export requests are currently queuing and are expected to be processed once data ingestion is re-enabled. Our technical team is continuing work to restore full functionality, and we will provide further updates as progress is made.
- resolved Jun 02, 2026, 04:18 PM UTC
Snow Atlas functionality in the Australia region has been restored. Customers can now access the Snow Atlas application, and data ingestion and export functionality are available again. The issue occurred after a scheduled maintenance window extended beyond the planned downtime. During the maintenance activity, some required deployment and configuration steps took longer than expected, which delayed the restoration of full service. We will continue to monitor the service to ensure continued stability. A full post-mortem report containing a detailed incident summary, root cause, and future preventative measures will be shared in the coming days.