[Critical] Issue with Box API

Final update

_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 February 24, 2026 between 1:15 PM PST and 3:59 PM PST, some users may have experienced difficulties while working in Box. The most significant impact occurred from 1:42 PM PST to 1:59 PM PST, when Uploads, Downloads, Logins, APIs, and Notes saw elevated latency and errors. A small subset of functionality continued to experience some degradation through 3:59 PM PST. The issue occurred due to our cache cluster becoming temporarily overloaded due to a traffic spike concentrated on a single hot key. We were able to resolve the majority of the impact by rate limiting peripheral workloads and fully resolve the issue by stopping the offending traffic source. We are now implementing automated hot key detection and introducing dynamic rate limiting at the caching layer to prevent similar issues from occurring in the future. ‌ We are conducting a full engineering postmortem and our overview is subject to change with further analysis and findings. In the event our continuing

1. Postmortem · Mar 5, 22:31 UTC
   _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 February 24, 2026 between 1:15 PM PST and 3:59 PM PST, some users may have experienced difficulties while working in Box. The most significant impact occurred from 1:42 PM PST to 1:59 PM PST, when Uploads, Downloads, Logins, APIs, and Notes saw elevated latency and errors. A small subset of functionality continued to experience some degradation through 3:59 PM PST. The issue occurred due to our cache cluster becoming temporarily overloaded due to a traffic spike concentrated on a single hot key. We were able to resolve the majority of the impact by rate limiting peripheral workloads and fully resolve the issue by stopping the offending traffic source. We are now implementing automated hot key detection and introducing dynamic rate limiting at the caching layer to prevent similar issues from occurring in the future. ‌ 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 som
2. Resolved · Feb 25, 00:15 UTC
   After further monitoring, this incident is now considered resolved. Box API has been restored to full functionality. If you continue to experience any issues, please contact Box Support at https://support.box.com.
3. Monitoring · Feb 25, 00:02 UTC
   Our team has taken steps to remediate this issue and is seeing improvement for Box API. We are continuing to monitor for any additional impact.
4. Identified · Feb 24, 23:42 UTC
   We are continuing to work on a fix for this issue.
5. Identified · Feb 24, 23:32 UTC
   We are continuing to work on a fix for this issue.
6. Identified · Feb 24, 23:32 UTC
   Our team is investigating an issue with Box API 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.