Authentication (OAuth 2.0 / JWT)Box SignLogin/SSOBox AILogin/SSOUploads/DownloadsContent API
investigating
Our team is investigating an issue affecting multiple Box services. Users may experience errors or failures when using multiple Box services. We will provide additional information as it becomes available.
investigating
Our team is continuing to investigate the issue. We will provide additional information as it becomes available.
investigating
Our team is continuing to investigate the underlying issue. There is no current ongoing impact. We will provide additional information as it becomes available.
investigating
Our team is working with our cloud hosting provider to continue to investigate the issue. There is no current ongoing impact. We will provide additional information as it becomes available.
resolved
Our team has taken steps to remediate this issue and the Box service has returned to full functionality. If you continue to experience any issues, please contact Box Support at https://support.box.com.
postmortem
_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 Aug 6, 2026 between 6:42 PM PDT and 6:48 PM PDT and again between 7:27 PM to 7:33 PM PDT, some customers may have experienced intermittent failures affecting login, uploads/downloads, Notes, Box AI, and API access in Box. The disruptions were caused by a temporary resource exhaustion on our frontโend infrastructure.
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
[Critical] Issues with Multiple Box Services
์์ 2026๋ 8์ 7์ผ AM 2:06 UTC ยท 0m
Outage์ฌ๊ฐํ ์ธ์๋ํธ
resolved
From approximately 6:42 PM to 6:48 PM PDT, we observed an issue impacting multiple Box services. Users may have experienced errors or been unable to complete actions during that time. There is no current impact and no further updates will be provided here. If you continue to experience any issues, please contact Support at https://support.box.com.
We recently addressed issues affecting file uploads and edits that create new file versions. We want to explain what happened and what we have done to prevent it from happening again.
Between Jul 26, 2026 4:38 PM PDT and Jul 28, 2026 10:34 AM PDT, some users may have experienced delays or failures when uploading files or saving edits that create new file versions. The impact was limited to cases with a high number of concurrent uploads or edits on the same file.
During this period, concurrent upload and edit traffic contended on shared database locks while creating new file versions. Under load, an overly conservative insert locking strategy acquired locks, creating a bottleneck in the database. The contention was amplified by background processes that post-process the uploaded file and attach additional information to every new version, competing for the same locks.
# Analysis
This incident highlighted several opportunities for improvement:
* Lock-wait failures do not appear in our usual change-stream / mutation telemetry, which delayed our investigation.
* Background processes can contend with upload and edit paths that create new versions. Our development environments did not fully test this particular interaction under load.
Remediation combined an immediate reduction in non-essential background scan load with a code change that relaxed the overly conservative locking behavior, while preserving the intended isolation guarantees.
# Corrective Actions
Box has initiated the following corrective actions:
* Deploy and validate the insert-behavior fix across all live clusters \(completed and confirmed\).
* Improve observability for lock-wait and timeout-driven load so contention sources are visible.
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