- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Box Drive
- Down Index
- 31of 100
What to do
Check whether you use Box Box Drive. 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 4h 11m it lasted.
Anything that failed between 2026-10-15 08:30 UTC and 2026-10-15 12:41 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.
Root cause
The incident was caused by an unexpected workload surge.Read the postmortem
Updates from Box 7
- investigating
We are investigating latency with syncing from the Box Web Application to Box Applications: Box Drive Some Users may see delayed updates synchronizing items from the Box Web App to Box Drive desktop clients.
provider
- identified
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.
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 the Box Drive service. We are continuing to monitor for any additional impact.
provider
- resolved
After further monitoring, this incident is now considered resolved. The Box Drive service has been restored to full functionality. If you continue to experience any issues, please contact Box Support at https://support.box.com.
provider
- postmortem
We recently addressed issues affecting Events and Box Drive. We would like to take the opportunity to further explain these issues and the steps we have taken to prevent recurrence. Between October 14, 2026 at 3:00 PM PDT and October 15, 2026 at 5:10 AM PDT, some customers may have experienced delayed Events delivery and Box Drive synchronization. # Analysis The incident was caused by an unexpected workload surge. We remediated the issue by deploying a targeted filter for the workload and adding capacity. During the mitigation, some Events and Drive synchronizations may have been delayed. # Corrective Actions Box has initiated the following corrective actions: * Adding monitoring and improved workload filtering tools to respond to future incidents quicker. * Exploring ways to automatically handle unexpected workload changes across our event processing systems. 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-4efb3b1b8f
Is Box still down?
No, this incident was resolved 2026-10-15 12:41 UTC. For Box's live state, see https://down.guide/box.
How long did it last?
4h 11m, from 2026-10-15 08:30 UTC to 2026-10-15 12:41 UTC, by the times Box posted.
What was affected?
Box named Box Drive.
What caused it?
Box wrote: "The incident was caused by an unexpected workload surge." The postmortem: https://stspg.io/2z5s2yy8rp7n
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.