Brillium Status Page

Sep 29, 2026 · resolved Sep 30

# Post-Incident Review and Service Improvement Summary **Incident Date:** September 2026 **Status:** Resolved **Audience:** Business Users, Customers, Partners, and Stakeholders **Reference:** [Brillium Incident Notification](https://status.brillium.com/incidents/cwhy3m4twtv3) and [Brillium Scheduled Maintenance Notice](https://status.brillium.com/incidents/gwxjcnszbpby) ## Executive Summary During a period of unusually high system activity, a subset of Brillium customers experienced intermittent access and performance issues while using the platform. While the majority of users remained unaffected, some customers encountered difficulties completing actions within the application. The issue was isolated to a legacy component responsible for managing user sessions. Under heavier-than-normal traffic conditions, this component experienced contention that prevented some user sessions from being processed efficiently, resulting in delayed responses or temporary interruptions. No customer data was lost, altered, exposed, or compromised at any time during this event. The incident affected system availability only and did not impact the confidentiality, integrity, or security of customer information. Brillium's Operations and Engineering teams responded immediately, identified the root cause, implemented a corrective solution, and conducted extensive validation before releasing the fix. Following successful testing, the solution was deployed incrementally to a limited group of customers and monitored closely before broader rollout. The platform is operating normally. ## What Happened? Brillium utilizes technology that maintains a user's active session while they work within the platform. This session management capability ensures that users remain authenticated and can move seamlessly between application functions. During periods of elevated platform activity, a legacy component involved in this process became a bottleneck. Specifically, the system's session coordination mechanism was unable to efficiently handle the volume of simultaneous session activity, causing some session requests to wait longer than expected. As demand increased, this created intermittent service degradation for a subset of users. It is important to note that this issue was related solely to session management and application availability. It was not caused by a cybersecurity incident, unauthorized access attempt, software defect affecting customer data, or infrastructure failure. ## Customer Impact Some customers may have experienced: * Intermittent application responsiveness * Delayed page loads * Temporary session interruptions * Difficulty accessing specific areas of the platform during peak activity periods Customers not utilizing the affected application paths generally experienced normal service. ### What Was Not Impacted The following remained protected throughout the event: * Customer assessment data * Candidate data * User account information * Assessment content * Reports and analytics * Integrations and stored records * Security controls and access management There is no evidence of data loss, data corruption, unauthorized access, or privacy impact. ## Root Cause The root cause was identified as a limitation within a legacy session-management architecture. The affected component relied upon a centralized mechanism for tracking active user sessions. Under high transaction volumes, this mechanism could become constrained, reducing the system's ability to process concurrent session updates efficiently. As platform demand increased, contention within that process created temporary delays that affected some customer experiences. The issue was related to system scalability rather than security, data integrity, or infrastructure capacity. ## Immediate Response Upon detection of the issue, Brillium initiated its incident response process, which included: 1. Immediate monitoring and investigation. 2. Identification and isolation of the affected component. 3. Development of a corrective workaround. 4. Extensive internal testing and quality validation. 5. Controlled deployment to a limited set of customer environments. 6. Continuous monitoring to verify successful resolution. 7. Execution of scheduled maintenance activities to support the corrective actions and long-term stability improvements. The workaround successfully mitigated the issue and restored normal operation. ## Validation Process Before broad deployment, Brillium followed a controlled release methodology to minimize customer risk. The corrective solution was: * Tested in non-production environments. * Subjected to high-load validation scenarios. * Released to a limited group of customers. * Monitored for stability and performance. * Verified through operational metrics and customer observations. The results confirmed that the identified issue was resolved. ## Long-Term Improvements While the immediate issue has been addressed, Brillium is implementing a strategic modernization initiative designed to eliminate this category of issue entirely. ### Planned Platform Enhancement Brillium will replace the remaining legacy session-management architecture with a modern stateless architecture. A stateless design eliminates dependency on centralized session coordination mechanisms and provides significant operational benefits, including: * Greater scalability under heavy usage * Improved platform resilience * Faster recovery during traffic spikes * Reduced risk of session-related bottlenecks * Improved operational efficiency * Enhanced long-term reliability This modernization effort aligns with Brillium's broader platform scalability and cloud modernization roadmap. ## SOC 2 Compliance Considerations Brillium maintains its commitment to SOC 2 security, availability, and operational control requirements. During this incident: ✅ Incident management procedures were followed. ✅ Monitoring and alerting controls functioned as designed. ✅ The issue was investigated, documented, and remediated. ✅ Corrective actions were validated prior to broader deployment. ✅ No customer data confidentiality concerns were identified. ✅ No unauthorized access occurred. ✅ No customer records were lost, altered, or corrupted. ✅ Post-incident corrective and preventive actions have been established and tracked. This post-incident review is part of Brillium's continuous improvement process and commitment to transparency with customers and partners. ## Frequently Asked Questions ### Was customer data compromised? No. Customer data remained secure throughout the event. The issue affected application availability only and did not impact data confidentiality, integrity, or security. ### Did assessments or results get lost? No. Assessment content, candidate information, and reporting data were preserved and remained intact. ### Has the problem been fixed? Yes. A corrective solution has been implemented, tested, validated, and deployed. Continuous monitoring confirms normal platform operation. ### Could this happen again? The immediate issue has been resolved. In addition, Brillium is undertaking a strategic architectural upgrade to remove the legacy session-management dependency entirely, significantly reducing the likelihood of similar issues in the future. ### What is Brillium doing differently going forward? Brillium is accelerating modernization efforts focused on: * Stateless application architecture * Increased scalability * Improved resilience during peak usage * Enhanced operational monitoring * Continuous performance testing under high-load conditions ## Closing Statement Brillium recognizes the importance of platform reliability to our customers' business operations and assessment programs. We sincerely apologize for the disruption experienced by affected users. Our teams responded quickly, identified the root cause, implemented a validated solution, and have initiated long-term architectural improvements designed to further strengthen platform performance and scalability. We remain committed to transparency, operational excellence, and the secure delivery of our services. **Brillium Operations & Engineering Team** **September 2026**

May 21, 2026 · resolved May 25

**Executive Summary** Brillium recently experienced a temporary service disruption affecting the AI Essay Grading capability within Assessment Builder. This disruption occurred during a required upgrade to our underlying AI model after the previous model was deprecated by our cloud provider. The issue has been fully resolved, services have been restored, and there was no impact to customer data. We take full responsibility for the disruption and have implemented additional safeguards to strengthen our change management and service reliability processes. ‌ **Impact Overview** * **Service Affected:** AI Essay Grading \(Assessment Builder\) * **Customer Impact:** Temporary unavailability of automated grading * **Workaround Provided:** Temporary routing to manual grading * **Data Integrity:** No loss, corruption, or unauthorized access to customer data All candidate submissions and assessment results remained secure, complete, and unchanged throughout the incident. ‌ **Root Cause** The disruption was the result of an external dependency change. The Large Language Model \(LLM\) previously used by Brillium for AI Essay Grading was deprecated by AWS, requiring an accelerated transition to a supported next-generation model. During this transition: * Automated grading was temporarily paused to ensure a controlled and secure upgrade * Additional validation was required to confirm grading accuracy, consistency, and fairness * Safeguards were applied to protect processing integrity and prevent inaccurate scoring While this action was necessary to maintain platform stability and vendor support compliance, it introduced a temporary service interruption while validation and stabilization were completed. ‌ **Resolution** Our engineering team has successfully: * Transitioned the AI Essay Grading engine to a supported next-generation LLM * Completed comprehensive regression testing and quality assurance * Validated grading precision, consistency, and fairness across all scenarios * Fully restored automated scoring for all assessments Manual grading processes introduced during the incident have now been discontinued. ‌ **Current Status** * AI Essay Grading is fully operational * All assessments are processing normally * No further action is required ‌ **What We Are Doing to Prevent Recurrence** We are strengthening our platform and processes to reduce the likelihood and impact of similar events: * **Enhanced Third-Party Dependency Monitoring** Improved tracking of vendor lifecycle changes, including deprecations and end-of-support timelines * **Proactive Upgrade Planning** Earlier adoption cycles to reduce the need for accelerated transitions * **Expanded Pre-Deployment Testing** Increased simulation of production scenarios prior to release ‌ **Customer Assurance** We recognize how critical reliable scoring is to your operations. This upgrade ensures: * Improved grading accuracy and consistency * Greater long-term system stability and vendor alignment * Continued protection of all customer data Brillium remains committed to delivering secure, high-performance, and future-ready assessment solutions. ‌ **Support** If you have any questions or need assistance, our support team is here to help.

Mar 26, 2026 · resolved Mar 26

Select customers experienced a brief service interruption due to abnormal external activity. The team addressed the issue promptly, and normal service was restored. We are continuing to strengthen our monitoring and protective controls to further improve platform resilience.

Mar 10, 2026 · resolved Mar 12

# **Brillium Platform Upgrade Incident – Post Mortem** **Incident Summary:** On March 10, 2026, Brillium experienced an unplanned service disruption during a scheduled platform upgrade. While Brillium upgrades are typically completed without customer impact and undergo extensive testing, this release resulted in unexpected performance issues that temporarily affected platform availability for our customers. Our engineering team responded immediately, worked continuously to restore service, and progressively brought customers back online while stabilizing platform performance. The platform is now fully available and operating as expected for all customers. **Customer Impact:** During the incident, customers may have experienced: * Temporary inability to access the Brillium platform * Slower performance while services were being restored * Intermittent access during stabilization efforts We recognize the importance of platform availability to our customers’ assessment and testing operations and regret the disruption this incident caused. **Root Cause \(High Level\):** This release introduced new features that required updates to the platform’s underlying data structure, including initializing certain data values as part of the upgrade process. While the upgrade was aggressively tested prior to deployment, the testing did not fully account for the impact of these changes on customers with very large data volumes. Under those conditions, the upgrade process placed significantly more load on the system than anticipated, which led to degraded performance and ultimately caused platform instability. **Resolution:** To resolve the issue, Brillium’s engineering team implemented targeted adjustments to support the upgrade process at scale, restored customer access in controlled phases, and increased monitoring to ensure platform stability. Once all customers were back online, the platform continued to be closely monitored to confirm normal operation and performance. **Preventative Measures and Improvements:** As a result of this incident, Brillium is implementing the following improvements: * Enhancements to pre upgrade testing to better simulate customers with large data volumes * Additional safeguards during upgrades that involve data structure changes * Improved monitoring and validation steps throughout the upgrade process These actions are intended to further reduce the risk of future upgrade related service disruptions. **Closing Statement:** We sincerely apologize for the disruption caused by this incident and appreciate the patience shown by our customers throughout the restoration process. Over the past 24 months, Brillium has successfully delivered more than 28 platform upgrades without service interruption through our zero downtime delivery process, which is designed to minimize customer impact. While we take extensive measures to ensure reliable and seamless upgrades, unplanned issues can still occur in complex technology environments. We take this incident seriously and are applying the lessons learned to further strengthen our upgrade and testing processes. Brillium remains fully committed to providing a stable, secure, and continuously improving platform, and we thank you for your continued trust.

Dec 10, 2025 · resolved Dec 11

During the investigation, the system operations team discovered that Assessment Builder was unable to establish a connection to the database systems. As a result, assessment authoring and delivery were impacted for approximately 1 hour and 15 minutes. No impact was observed on the Administration, Customer Management, or Talent applications. This issue appears to have been within the internal systems and the issue has been resolved.

Is Brillium down right now?

No — Brillium is up. All systems operational as of Oct 12, 5:46 PM UTC.

What is Brillium's current status?

Brillium: All Systems Operational. Alert24 checks Brillium's status page continuously and can notify you the moment it changes.

How do I get alerted when Brillium goes down?

Alert24 monitors Brillium and 3,700+ other cloud and SaaS providers. When an outage is detected it updates your status page automatically and pages your on-call team — no manual checks. Start free at alert24.net.