- Level
- confirmed
- Worst impact
- Major outage
- Components
- Content API
- Down Index
- 39of 100
What to do
Check whether you use Box Content API. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 43m it lasted.
Anything that failed between 2026-02-24 23:32 UTC and 2026-02-25 00:15 UTC may need a replay.Subscribe to Box's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=box works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Box 6
- identified
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.
provider
- identified
We are continuing to work on a fix for this issue.
provider
- identified
We are continuing to work on a fix for this issue.
provider
- monitoring
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.
provider
- resolved
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.
provider
- 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 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
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-455c06a4fa
Is Box still down?
No, this incident was resolved 2026-02-25 00:15 UTC. For Box's live state, see https://down.guide/box.
How long did it last?
43m, from 2026-02-24 23:32 UTC to 2026-02-25 00:15 UTC, by the times Box posted.
What was affected?
Box named Content API.
What caused it?
Box hasn't published a root cause. If it does, it shows here.
Where does this come from?
Box's official status page, https://status.box.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.