Summary: On December 10, several customers observed that portions of their branded web experience appeared in red, instead of using the customer-selected accent color. An incident was declared after it was determined the issue affected multiple customers.
The engineering team found that a prior internal update to a shared user-interface component had unintentionally removed color-related code that was still in use in production. When the web experience began using the updated version of this component after the December release cycle, this change caused the incorrect accent color to appear.
A hotfix was issued the same day to restore the correct behavior and normal functionality was fully recovered for all customers approximately one hour after the incident was declared.
Impact:
Affected elements included:
No functionality was hindered; the issue was visual only.
Root Cause: In early October, an update was made to an internal user-interface component. This update removed color-related code under the assumption that it was unused. However, parts of the web experience still depended on this code to correctly apply customer-selected accent colors.
When the December release updated the web experience to use the latest version of this component, the unintended removal of that code introduced a visual regression. As a result, certain UI elements defaulted to red instead of the correct customer-specific color.Mitigation: Once the incident was declared, engineers quickly identified the regression and traced it to the internal component update. A targeted hotfix was prepared and deployed to restore correct color functionality across all affected elements. The incident was fully resolved approximately one hour after formal declaration.
Recurrence Prevention: To minimize the likelihood of similar issues in the future, Firstup will take the following actions: