Is Box down?

Our team is investigating an issue with Box API authentication and has identified the underlying cause of this issue and is working to take remediating steps. We will provide additional updates as they become available.

Our team has taken steps to remediate this issue and is seeing improvement. We are continuing to monitor for any additional impact.

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

From approximately 10:53 PM to 10:58 PM PDT, we observed an issue impacting Login, All Files, Notes, Uploads and Box API. Our systems automatically detected and corrected the underlying issue. There is no current impact and no further updates will be provided here. If you continue to experience any issues, please contact Box Support at https://support.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 June 3, 2026 between 10:53 PM and 10:58 PM PDT, some customers may have experienced issues when attempting to sign in to Box and when accessing files, notes, uploads, and our public API. ‌ The issue was caused by a temporary fluctuation in a database shard due to elevated disk activity, which led to connection saturation and service errors for a subset of users. Service returned to normal by 10:58 PM PDT and monitoring remains in place to watch for recurrence. We are also reviewing our deployment and operational practices to reduce the risk of similar incidents in the future. ‌ We are conducting a full engineering postmortem. 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 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

We are investigating an ongoing issue affecting Box AI. We will provide more information as soon as it is available.

Our team has identified the underlying cause of this issue and is working to take remediating steps. We will provide additional updates as they become available.

Our team has taken steps to remediate this issue and is seeing improvement for Box AI. We are continuing to monitor for any additional impact.

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.

Our team is investigating an issue with Logins for Box Drive. Users attempting to log in to Box Drive may see errors or timeouts. Users encountering this issue can log in to the Box Web Application as a temporary workaround. We will provide additional information as it becomes available.

We have resolved the issue impacting Box Drive. We are continuing to monitor to ensure no further impact is observed

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.

_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._ Between May 21, 2026 at 10:56 PM and May 22, 2026 at 2:07 AM PDT, some customers attempting to sign into Box Drive may have experienced errors or been unable to complete the login process. The issue affected a subset of customers who use a particular Mobile Application Management \(MAM\) service that was not universal across all users. The problem was caused by a change to our single sign-on configuration that prevented certain Box Drive logins from completing. Service was restored after we reverted the configuration and validated successful logins for impacted users. We are reviewing our deployment and administrative procedures to reduce the risk of this type of issue recurring. 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. 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

Between 2:31am and 4:45pm PDT on May 14, 2026 we observed an issue impacting streaming Enterprise Events API . Our systems detected and corrected the underlying issue. There is no current impact and no further updates will be provided here. If you continue to experience any issues, please contact Box Support at https://support.box.com.

We recently addressed issues affecting **Enterprise Events API**. 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 2:31am and 4:45pm PDT on May 14, 2026, some users may have experienced difficulties while working in Box. During this time, customers using the streaming Enterprise Events API experienced delivery delays of up to 6.5 hours. The issue occurred when an internal indexing service unexpectedly generated events at an unconstrained rate, which caused a significant concentrated spike in the total events volume. We were able to resolve the issue by redirecting those events from our streaming enterprise events pipeline for later processing. In addition, we will exclude events originating from internal services from our enterprise events processing pipelines and proactively deprioritize unexpected surges in events to prevent similar issues from occurring in the future. ‌ **Analysis** ‌ There were a number of contributing factors leading to this incident: ‌ Our internal search indexing service produced events, which should not have been created, at a rate significantly exceeding enterprise usage. These events were published to a queue to be written to the persistent datastore. Also, these events were concentrated in certain access patterns causing hot spotting in some database partitions. The significantly reduced throughput of these partitions caused the subscriber to fall behind. Once these access patterns were identified and the corresponding events removed, service was resolved promptly. Moving forward, these events will not be published. ‌ **Corrective Actions** ‌ The following corrective actions have been completed or are planned: ‌ * **Disable Event Publishing for Search Services** - We are disabling enterprise events from being produced and processed from Box internal services. * **Deprioritize Surge Workloads** - We will monitor for workloads generating significant volumes of event data and deprioritize those events from the primary pipeline. * **Update Incident Response Procedures** - We are updating our runbooks to account for these conditions and related actions. ‌ 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