Fluxx had 15 outages in the last 2 years totaling 484h 2m of downtime — averaging 0.6 incidents per month.
There were 15 Fluxx outages since July 16, 2024 totaling 484h 2m of downtime. Each is summarised below — incident details, duration, and resolution information.
AWS latency in EU-WEST-1 Region may affect some Fluxx customers.
AWS has indicated early signs of recovery, though the incident is still active.
AWS has advised that full recovery is expected and services returned to normal.
We are investigating an issue where report and card exports (including Excel exports) are not downloading and remain stuck in a “New” state within the Jobs Queue.
We have identified the root cause of the issue and are working on implementing a fix.
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.
The backlog of report jobs has fully cleared, and all scheduled and ad hoc reports are now processing normally.
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
All products 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.
AWS restored Network Load Balancer health checks, and as recovery progressed, temporary throttles on certain operations were gradually lifted. As of now, all affected AWS services have returned to normal operation. Fluxx systems have remained stable throughout the recovery process, and we continue to monitor performance closely.
Our ticketing and support system powered by Atlassian Jira is currently experiencing an outage due to a global issue with their public cloud provider. If you need support urgently, please email [email protected]. Thank you for your patience with any delayed response in the meantime.
Jira Service Management, Jira along with other Atlassian products are impacted. Atlassian public cloud provider is actively working to mitigate this issue with urgency.
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.
AWS restored Network Load Balancer health checks, and as recovery progressed, temporary throttles on certain operations were gradually lifted. As of now, all affected AWS services have returned to normal operation. Fluxx systems have remained stable throughout the recovery process, and we continue to monitor performance closely.
We are currently investigating this issue.
This incident has been resolved
Maintenance will occur on Start of maintenance window: 7:00 PM PST Estimated end: 7:30 PM PST Estimated duration: 30 Minutes
This incident has been resolved.
We are currently investigating this issue.
We are seeing a querying slowdown in the US. We have identified the cause and are working to mitigate.
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.
This incident has been resolved. We are back to operational for all regions.
We are currently investigating this issue.
This incident has been resolved. We experienced a service degradation affecting some clients, resulting in slow responses and temporary downtime. The root cause was traced to a suboptimal database query using an incorrect index, which increased load on the RDS instance. We resolved the issue by upgrading the affected RDS instance to a larger size, which restored performance. Additionally, a fix addressing the inefficient query has been implemented and will be included in an upcoming release
Maintenance will occur on 4/10/2025 Start of maintenance window: 5:00 PM PST Estimated end: 6:00 PM PST Estimated duration: 1 Hour
This incident has been resolved.
Maintenance will occur on Start of maintenance window: 5:00 PM PST 4/01/2025 Estimated end: 6:00 PM PST 4/01/2025 Estimated duration: 1 hour
This incident has been resolved.
We are currently investigating this issue.
This incident has been resolved.
We are currently experiencing an issue where document validation is causing uploads to hang, impacting some of our servers. Documents are uploaded, but cannot be downloaded after uploading. Our team is actively investigating and working to resolve the problem as quickly as possible.
We have identified the cause of the issue and are taking steps to address this issue on affected servers.
Document uploading and validation have been restored. We are addressing impacted documents on affected servers and actively monitoring traffic.
This incident has been resolved. All impacted documents on affected servers have been cleared. Document uploading and validation services are stable.
We are currently investigating this issue.
The dashboard loading cause has been identified and a fix has been implemented.
We have confirmed all Grantmaker services are once again operational.
We are currently investigating this issue.
A spike of database load caused the system degradation. This incident has been resolved.