rewindex

ChangesBox[Major] Issue with Box Drive

Box: Incident silently edited: [Major] Issue with Box Drive

Silent editNot classified yetChanged stspg.io (opens in new tab)
Summary

Summary pending. The diff below shows exactly what changed.

Incident page: the full timeline of updates

What changed

Struck in red is what Box removed; blue is what they added. Muted text is unchanged context.

ChangedUpdatepostmortem#1
Before: 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. ‌ Between October 14, 2026 at 3:00 PM…
After: 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…
Before: …PM PDT and October 15, 2026 at 5:10 PM PDT, some customers may have experienced delayed Events…
After: …PM PDT and October 15, 2026 at 5:10 AM PDT, some customers may have experienced delayed Events…
Before: …5:10 AM PDT, some customers may have experienced delays in receiving User Events while using Box Drive. ‌ The issue occurred due to a workload increase impacting some backend services. We were able to resolve the issue by rate limiting the internal workload. In addition, we are looking at ways to detect and respond to workload changes more quickly, and ways to further isolate workloads on shared infrastructure in order 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…
After: …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…

Compared with the previous archived version of this incident (10 to 30-minute polling). View the live incident (opens in new tab).

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

Rewindex captured a newer version after the last checkpoint; the next run () commits it.

History of this incident

TodayThursday, October 29Thu, Oct 29

1 rewrite

Monday, October 26

1 incident change

Thursday, October 15

1 incident change

All Box changesBox profileMarkdownJSON