Box incident
[Major] Some Users May See Errors Accessing The All Files Page
Box experienced a major incident on October 17, 2025 affecting Accessible Site (a.box.com), lasting 1h 31m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Oct 17, 2025, 01:36 PM UTC
Our team is investigating an issue with Box All Files page. Users may see 500 HTTP errors while accessing the All Files page. We have identified the underlying cause of this issue and are working to take remediating steps. We will provide additional updates as they become available.
- monitoring Oct 17, 2025, 01:55 PM UTC
Our team has taken steps to remediate this issue and is seeing improvement for All Files experience. We are continuing to monitor for any additional impact.
- monitoring Oct 17, 2025, 02:37 PM UTC
Our team has taken steps to remediate this issue and is seeing improvement for All Files experience. We are continuing to monitor for any additional impact.
- resolved Oct 17, 2025, 03:07 PM UTC
After further monitoring, this incident is now considered resolved. The All Files page service has been restored to full functionality. If you continue to experience any issues, please contact Box Support at https://support.box.com.
- postmortem Oct 22, 2025, 07:47 PM UTC
We recently addressed issues affecting availability of the Box All Files page. We would like to take the opportunity to further explain these issues and the steps we have taken to keep them from happening in the future. Between 5:42 AM PDT and 6:30 AM PDT on October 17th, some users may have experienced difficulties while working in Box. During this time, there was a degradation in availability of the All Files page. The issue occurred due to a bug in our code promotion pipeline, which promoted a disruptive change beyond the canary stage, causing wider impact. We were able to resolve the issue by rolling back the change. In addition, we are working to improve our release strategy and testing processes to prevent similar issues from occurring in the future. **Analysis** The code that was promoted beyond the canary stage introduced an unintended change in the behavior of our feature flagging mechanism. The code change was intended to improve application performance by implementing a filtering-based approach. However, the feature flagging system was not yet fully compatible with this implementation, which resulted in a malfunction on the All Files page. **Corrective Actions** Box has initiated the following corrective actions: * Strengthened the canary deployment validation criteria in our release strategy. * Updated internal documentation to reflect feature-flag system dependencies and operational constraints. * Provided engineers clear guidance for safely integrating changes with the feature-flag system. We are continuously working to improve Box and want to make sure we are delivering the best product and user experience we can. We hope we have provided some clarity here and we would be happy to answer any questions you may still have regarding this matter. Sincerely, The Box Team