Struck in red is what Box removed; blue is what they added. Muted text is unchanged context.
BeforeAfter
ChangedStatus#1
Before: resolved
After: postmortem
AddedUpdatepostmortem#2
Before: not present
After: We recently addressed an issue that affected several Box services. We would like to take the opportunity to further explain what happened and the steps we have taken to keep it from happening in the future.
On Thursday, October 8, 2026, between 1:48 AM and 2:08 AM PDT, some customers may have experienced high error rates, slowness, and intermittent service unavailability across several Box capabilities, including All Files, API integrations, Web and SSO logins, Box Sign, Uploads, and Downloads.
A deployment initiated by our cloud provider resulted in latency across several of our database volumes causing database requests to stall. The incident was resolved after our cloud provider identified the performance regression and rolled back the offending change.
Analysis
Our database service is deployed across multiple availability zones to provide high availability and redundancy. Typically, our systems detect if an active database instance fails or becomes unreachable and redirect traffic away from the impacted instance to replicas in alternate zones.
During this incident, our cloud provider was deploying an update to a single availability zone that inadvertently caused severe disk read latency without failing explicitly or timing out, which caused pending storage operations and database queries to hang. This incident impacted several of our databases in the affected availability zone which led to widespread slowness and timeouts. However, automated health-checking systems did not detect failure because database instances remained responsive to health checks. Consequently, traffic was not automatically redirected and the degraded instances continued to receive requests that they could not process.
Once our cloud provider detected the degradation, they immediately paused and rolled back the change, at which point our database performance returned to baseline and all degraded services recovered.
Corrective Actions
Box is taking the following actions to improve system resilience:
Upgrading health checks to perform more comprehensive system health evaluation and validate end-to-end query responsiveness.
Ensuring health-checking and remediation services perform effectively under concurrent, multi-instance failures during widespread zonal degradation.
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
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 these records existed by then and have not been changed since, by anyone, Rewindex included.
Box reported a critical outage affecting the All Files page, API, uploads, downloads, Box Sign and Notes, starting 2026-10-08 09:27 UTC and resolved at 2026-10-08 09:33 UTC (computed duration: 5 min). Box confirmed services were restored to full functionality; no cause was stated.
Cite this
Incident updated: [Critical] Issues with Multiple Box Services on Box’s status page, changed 2026-11-09 08:13 UTC (change 2 of 2).
Title
Incident updated: [Critical] Issues with Multiple Box Services