Box

_Notice and disclaimer: Box is providing this preliminary information subject to further review and analysis. To the best of our knowledge, this is the current state and we may update as more information is confirmed._ On October 19, 2026 between 6:44 PM and 8:32 PM PDT, some customers may have experienced degradation when interacting with our Public API, Downloads, and Box Sign. The impact was caused by a focused traffic spike that resulted in increased latencies when accessing some data assets. We mitigated the impact by enabling additional targeted caching to relieve the stress on our datastores. Performance of our services returned to normal levels by 8:32 PM PDT. We are conducting a full engineering postmortem and our overview is subject to change with further analysis and findings. In the event our continuing investigation yields further substantive findings, we may publish additional analysis after the conclusion of the full engineering postmortem. Sincerely, The Box Teamstatus.box.com

We recently addressed issues affecting Events and Box Drive. We would like to take the opportunity to further explain these issues and the steps we have taken to prevent recurrence. ‌ Between October 14, 2026 at 3:00 PM PDT and October 15, 2026 at 5:10 AM PDT, some customers may have experienced delayed Events delivery and Box Drive synchronization. ‌ # Analysis The incident was caused by an unexpected workload surge. We remediated the issue by deploying a targeted filter for the workload and adding capacity. During the mitigation, some Events and Drive synchronizations may have been delayed. ‌ # Corrective Actions Box has initiated the following corrective actions: ‌ * Adding monitoring and improved workload filtering tools to respond to future incidents quicker. * Exploring ways to automatically handle unexpected workload changes across our event processing systems. ‌ We are continuously working to improve Box and want to make sure we are delivering the best product and user experienstatus.box.com

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.status.box.com

After further monitoring, this incident is now considered resolved. Event-based reports and Insights in the Admin Console, results from the Enterprise Events API, and Box AI unit usage have been restored to full functionality and are showing up-to-date information. If you continue to experience any issues, please contact Support at https://support.box.com.status.box.com

After further monitoring, this incident is now considered resolved. The Report Service has been restored to full functionality. If you continue to experience any issues, please contact Box Support at https://support.box.com.status.box.com

We recently addressed an issue that briefly affected the All Files page, Box Notes, API traffic, logins, and downloads in Box. We would like to take the opportunity to further explain this issue and the steps we have taken to keep it from happening in the future. On Tuesday, September 29, 2026 between approximately 6:39 AM PDT and 6:44 AM PDT, some customers may have experienced errors when using Box. The issue occurred when several database instances simultaneously became unavailable due to a disruption in our cloud-managed infrastructure. Our internal systems detected the unhealthy instances and automatically rerouted traffic to a healthy copy, which fully restored service availability. # Analysis Our database service is generally deployed evenly across multiple availability zones in order to reduce coupling to a single failure domain within our cloud infrastructure. However, VM scheduling within a given availability zone is managed by the compute service itself. In this instance, sestatus.box.com

We recently addressed issues affecting Box Notes in Box. 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. On September 28, 2026, beginning at 2:35 AM PDT, during a routine maintenance operation, some Box Notes users who had the app open in a background browser tab may have seen a brief "Reconnecting" message and a short delay when they returned to the tab. No data was lost, users who were actively editing were not prevented from working, and we received no widespread customer reports. The cause was a recent change to how Box Notes reconnects background tabs. We have since fixed the reconnection behavior and verified the fix. # Analysis The cause was a recent change to how Box Notes reconnects browser tabs that are open in the background. After an infrastructure switch during a release, those tabs did not reconnect on their own and instead reconnected when customers returned to them. The release status.box.com

We recently addressed issues affecting Admin Reports on AI usage reporting. 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 3:30 PM PDT and 7:59 PM PDT on September 3, 2026, ~~—~~ some users may have experienced difficulties while working in Box. During this time, AI Unit usage reports may have shown missing, empty, or otherwise incomplete AI-usage data and related insights. The issue occurred because a third‑party data ingestion service experienced elevated error rates that interrupted ingestion into our reporting pipeline. We were able to resolve the issue after the provider deployed a mitigation, and our teams re-ran previously failing ingestion jobs and rebuilt reporting tables to backfill missing data, restoring report availability. In addition, we will pursue follow-up with the provider and take steps to reduce the likelihood of recurrence. # Analysis Upon learning of the incidentstatus.box.com

We recently addressed issues affecting Hubs shared-link access in Box. 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 August 27, 2026 at 11:18 PM PDT and August 28, 2026 at 2:48 AM PDT, some customers may have been unable to access Box Hubs using shared links. Other Box functionality, such as file and folder access, was not broadly affected. ‌ The issue occurred as a result of a recent code change in our ongoing effort to improve performance. We were able to resolve the issue by rolling back the change, and traffic returned to the previous behavior. ‌ # Analysis During a routine deployment, a configuration change intended exclusively for a pre-production environment was inadvertently applied to the production environment. The incident highlighted opportunities to strengthen deployment-time configuration validation and pre-deployment checks designed to catch environment-specific confistatus.box.com

We recently addressed issues affecting Downloads \(including ZIP downloads\) in Box. 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 August 24, 2026 at 11:25 PM PDT and August 25, 2026 at 12:05 AM PDT, some Box Zones Japan users may have had a degraded download experience. The disruption was caused by an unusual traffic pattern that placed unexpected strain on capacity in the region. Once the impact was identified we restored service by directing download traffic to another region and adding capacity. Downloads returned to normal by 12:05 AM PDT. Once confirming that the issue had been addressed, we returned traffic to the original region. Of note, even during the period of temporary traffic redirection, all Box Zones customer content was stored in the correct Box Zones region. # Analysis This incident highlighted opportunities to make our systems more resilient to unusual traffic pattestatus.box.com

We recently addressed issues affecting file uploads and other write operations within Box. 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 02:03 PM and 02:24 PM PDT on August 24, 2026, some users may have experienced difficulties while working in Box. During this time, users saw elevated error rates and reduced availability for uploads and other write-oriented actions. The issue occurred when a background user-cleanup process generated a sudden surge of database update activity that was amplified by an unbounded retry loop, which overloaded a database shard and exhausted connection capacity. We restored normal service by applying a rate limit to the cleanup traffic and stopping the offending cleanup workload. After traffic subsided, we removed the temporary limits once systems were stable. In addition, we are making changes to limit background cleanup traffic and improve retry behavior status.box.com

Between 3:44 PM and 4:27 PM PDT on August 19, 2026 and 10:28 AM and 11:21 AM PDT on August 24, 2026, some users may have experienced intermittent errors with some Box features, including Logins, Uploads, Downloads, and Box Sign. The issues occurred after a rapid surge of external Box client connections overwhelmed front-end capacity in the affected region, which caused an increase in server-side error rates and prevented some requests from reaching our back-end services. We restored service by working with our cloud provider and applying operational mitigations until front-end error rates returned to normal and user requests succeeded again. # Analysis This incident highlighted opportunities to improve our detection and correlation of frontend/load balancer health signals with our application telemetry and to strengthen joint monitoring and mitigation processes with our cloud provider during large-scale client connection events. It also underscored the importance of clearer detection tstatus.box.com

We recently addressed issues affecting Box Edit, Microsoft Office Online, iWork, and other integrations in Box. 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 04:17 PM PDT and 6:30 PM PDT on August 19, 2026 some users may have experienced difficulties while working in Box. During this time, impacted users were unable to open files in Box Edit, Microsoft Office Online, iWork, and other integrations. Additionally, some users saw errors, timeouts, or slow responses while working in other areas of Box. ‌ The issue occurred after a deployment of a backend service that provides integration and platform functionality. The deployment introduced a regression that caused the service’s performance to degrade under peak load, which led to client timeouts and errors. We restored functionality by reverting the deployment to a previous version. We are taking steps to reduce recurrence by improving status.box.com

_Notice and disclaimer: Box is providing this preliminary information subject to further review and analysis. To the best of our knowledge, this is the current state and we may update as more information is confirmed._ On August 19, 2026 between 3:44pm PDT to 3:49pm PDT, some users may have experienced difficulties while working in Box. When attempting to access Box during this time, some users may have seen an error message. Preview, and Box Notes functionalities were impacted. This occurred because of an issue affecting Box’s critical third party cloud ingress services. We are conducting a full engineering postmortem in conjunction with our cloud provider, and our overview is subject to change with further analysis and findings. In the event our continuing investigation yields further substantive findings, we may publish additional analysis after the conclusion of the full engineering postmortem. We are continuously working to improve Box and want to make sure we are delivering the bstatus.box.com

After further monitoring, this incident is now considered resolved. 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.status.box.com