Changes / Box / [Critical] Issue with Box API
Box: Critical incident: [Critical] Issue with Box API
Summary
Box reported a critical degradation affecting Box Platform / API - Content API, starting 2026-02-24 23:32 UTC and resolved 2026-02-25 00:15 UTC (43 min). Box said remediation steps improved the API and confirmed full functionality after monitoring; no specific cause or fix was disclosed.
Machine-written from the diff below (Sol; type: incident degradation). Check the diff before relying on it.
Major incidentLabel: degradation (model (Jev), 50%)Changed Detected Source: stspg.io (opens in new tab)
What changed
Before: not present
After: [Critical] Issue with Box API
Before: not present
After: critical
Before: not present
After: postmortem
Before: not present
After: 2026-02-24 23:32 UTC
Before: not present
After: 2026-02-25 00:15 UTC
Before: not present
After: Box Platform / API - Content API, Content API
Before: not present
After: 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.
Before: not present
After: We are continuing to work on a fix for this issue.
Before: not present
After: We are continuing to work on a fix for this issue.
Before: not present
After: 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.
Before: not present
After: 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.
Before: not present
After: _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 some clarity here and we would be happy to answer any questions you may still have regarding this matter.
Sincerely,
The Box Team
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Critical incident: [Critical] Issue with Box API (this change) Box reported a critical degradation affecting Box Platform / API - Content API, starting 2026-02-24 23:32 UTC and resolved 2026-02-25 00:15 UTC (43 min). Box said remediation steps improved the API and confirmed full functionality after monitoring; no specific cause or fix was disclosed. | Major incident |