Box — status

Status verification pending

The latest official observation is not fresh enough to confirm current service health.

Official incident resolved

[Medium] Issue with multiple Box Services — _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 Team

Official incident resolved

[Critical] Issues with All Files Page, Box Notes, API calls, logins and downloads — 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, several VMs within a single availability zone were attached to a shared network device prior to the incident. When that device experienced a brief interruption, multiple database instances simultaneously became unavailable. Our systems retain warmed copies of the database instances to take over in the event of a hardware failure, and continuously monitor the health of the service. Within minutes of the impact start, this system correctly detected the issue and successfully remediated the problem by redirecting traffic from the unhealthy instance to a healthy copy. At this point, customers using Box saw errors subside and service return to normal. # Corrective Actions Box has initiated the following corrective actions: * Analyzing and optimizing the response time for our health checking services to more quickly remediate similar issues. * Ensuring that our health checking services are resilient to potentially larger, concurrent failures across our database fleet. ‌ 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