[Medium] Issues with Box Hubs

Final update

We recently addressed an issue affecting Box Hubs. We’d like to take this opportunity to explain what happened and the steps we’ve taken to prevent it from happening again. Between 06:50 AM PDT to 07:26 AM PDT on July 23, 2026, some users may have experienced difficulties while working in Box. During this time, users attempting to access Box Hubs were unable to load the Hubs gallery and instead encountered a "Not Found" page. The issue occurred as a result of a recent frontend dependency update, which introduced a package version conflict that prevented the Hubs module from loading correctly. We were able to resolve the issue by rolling back the frontend application to the previous stable version, which fully restored access to Box Hubs. In addition, we are working to improve our automated pre-release testing processes to ensure that dependency updates are validated across all affected modules before reaching production, and we are enhancing our monitoring and alerting capabilities to detect and surface similar issues more quickly, to prevent similar issues from occurring in the future. # **Analysis** At the technical level, a shared package used by the core web application and t

1. Postmortem · Jul 31, 01:27 UTC
   We recently addressed an issue affecting Box Hubs. We’d like to take this opportunity to explain what happened and the steps we’ve taken to prevent it from happening again. Between 06:50 AM PDT to 07:26 AM PDT on July 23, 2026, some users may have experienced difficulties while working in Box. During this time, users attempting to access Box Hubs were unable to load the Hubs gallery and instead encountered a "Not Found" page. The issue occurred as a result of a recent frontend dependency update, which introduced a package version conflict that prevented the Hubs module from loading correctly. We were able to resolve the issue by rolling back the frontend application to the previous stable version, which fully restored access to Box Hubs. In addition, we are working to improve our automated pre-release testing processes to ensure that dependency updates are validated across all affected modules before reaching production, and we are enhancing our monitoring and alerting capabilities to detect and surface similar issues more quickly, to prevent similar issues from occurring in the future. # **Analysis** At the technical level, a shared package used by the core web application and the Hubs page module fell out of version alignment when the core application upgraded the dependency without a corresponding update in the Hubs module. This caused the Hubs page to crash at load time. The regression was not caught before reaching production because pre-release automated tests were sc
2. Resolved · Jul 23, 14:30 UTC
   After further monitoring, this incident is now considered resolved. Box services have been restored to full functionality. Please contact Box Support at https://support.box.com/ if you continue to experience any issues.
3. Identified · Jul 23, 14:26 UTC
   Box continues remediation efforts to restore full functionality to Box Hubs. The underlying cause of the issue has been identified and efforts are underway to restore usability.
4. Investigating · Jul 23, 14:14 UTC
   We are investigating an ongoing issue affecting Box Hubs. We will provide more information as soon as it is available.