Fluxx Outage History

A fix has been implemented and we are monitoring the results.

AWS has indicated early signs of recovery, though the incident is still active.

New report jobs are now processing normally. We are currently working through a backlog of earlier queued jobs, which may take time to fully clear.

We are impacted by the Microsoft incident and continue to monitor Microsoft status page: https://status.cloud.microsoft/m365/ During this time, Fluxx users may experience issues with Microsoft Add-ins, Document Sync, Azure

We are impacted by the Microsoft incident and continue to monitor Microsoft status page: https://status.cloud.microsoft/m365/ During this time, Fluxx users may experience issues with Microsoft Add-ins, Document Sync, Azure

We are impacted by the Microsoft incident and continue to monitor Microsoft status page: https://status.cloud.microsoft/m365/ During this time, Fluxx users may experience issues with Microsoft Add-ins, Document Sync Azure services back to operational

We are currently experiencing issues due to a current AWS outage and are working with our AWS representatives to restore services with full functionality as soon as possible. We are closely monitoring performance and taking all necessary steps to mitigate impact while services recover.

We are continuing to monitor for any further issues.

We are continuing to monitor the situation closely. AWS has confirmed they are actively working on the issue, and we are expecting their next update at 10:00 AM PST. We will provide additional information as soon as it becomes available.

Our hosting provider, AWS, continues to implement mitigation steps related to a network load balancer issue that is affecting connectivity across several AWS services. This may cause intermittent errors or slow responses in some areas of the Fluxx platform. AWS reports that they are actively working to restore full connectivity and are validating a fix for the affected systems. We will continue to monitor the situation closely and provide another update by 10:45 AM PDT.

Our hosting provider, AWS, reports progress on resolving the issue affecting new EC2 instance launches. Internal systems are beginning to recover in several Availability Zones within the US-EAST-1 region. AWS is extending mitigations to the remaining zones, after which launch errors and connectivity issues are expected to subside.

AWS has identified and mitigated the underlying issue impacting the us-east-1 region. As services recover, our team has taken additional steps to accelerate restoration by cycling affected pods and verifying performance across the platform. Most systems are now recovering, and users should begin to see performance improvements as services continue to stabilize. We’re actively monitoring the remaining infrastructure components to ensure everything is fully restored. Thank you for your patience and understanding during this AWS-related disruption.

AWS has continued to make progress toward full recovery in the US-EAST-1 region. Fluxx systems remain stable, and we’re continuing to monitor closely as AWS services return to pre-event performance levels.

Jira Service Management, Jira along with other Atlassian products are impacted by the AWS outage. Atlassian public cloud provider, AWS, is actively working to mitigate this issue with urgency. Atlassian Status Page for more details: https://status.atlassian.com/

We are seeing ongoing improvements in product performance and overall system stability. While some event processing remains in progress, operational capabilities across Atlassian Cloud services continue to recover.

The throughput issue has been identified and a fix has been implemented. Customer data is still being successfully received, but may be delayed for querying.

Document uploading and validation have been restored. We are addressing impacted documents on affected servers and actively monitoring traffic.

The dashboard loading cause has been identified and a fix has been implemented.