Changes / Box / [Critical] Issues with Multiple Box Services
Box: Critical incident: [Critical] Issues with Multiple Box Services
Summary
Box reported a critical outage affecting Login, All Files, Notes, Uploads and Box API. It started and was marked resolved at 2026-06-03 17:53 UTC (computed duration: 0 min). Box said its systems automatically detected and corrected the underlying issue, with no current impact.
Machine-written from the diff below (Sol; type: incident outage). Check the diff before relying on it.
What changed
Before: not present
After: [Critical] Issues with Multiple Box Services
Before: not present
After: critical
Before: not present
After: postmortem
Before: not present
After: 2026-06-03 17:53 UTC
Before: not present
After: 2026-06-03 17:53 UTC
Before: not present
After: From approximately 10:53 PM to 10:58 PM PDT, we observed an issue impacting Login, All Files, Notes, Uploads and Box API. Our systems automatically detected and corrected the underlying issue. There is no current impact and no further updates will be provided here. If you continue to experience any issues, please contact Box Support at https://support.box.com.
Before: not present
After: We recently addressed issues affecting Authentication, File Access, Notes, Uploads, and Public API. We would like to take the opportunity to further explain these issues and the steps we have taken to keep them from happening in the future.
On June 3, 2026 between 10:53 PM and 10:58 PM PDT, some customers may have experienced issues when attempting to sign in to Box and when accessing files, notes, uploads, and our public API. The issue was caused by a temporary fluctuation in a database shard due to elevated disk activity, which led to connection saturation and service errors for a subset of users. Service returned to normal by 10:58 PM PDT and monitoring remains in place to watch for recurrence.
# Analysis
As part of our routine system maintenance, we deployed standard software updates to our infrastructure. Following these updates, a scheduled background system scan processed a larger-than-normal volume of files. This background activity led to temporary resource contention on the database tier, resulting in brief latency and connection saturation for a subset of users.
While Box utilizes redundant database replicas to ensure high availability, our automated monitoring and failover systems did not immediately redirect traffic because the database remained partially responsive.
# Corrective Actions
Box has initiated the following corrective actions:
* Implemented strict I/O resource limits on background maintenance processes to ensure they cannot impact active user traffic.
* Upgraded our database monitoring and health checks to immediately detect and alert on localized resource contention, ensuring faster automated failover response.
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.
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Critical incident: [Critical] Issues with Multiple Box Services (this change) Box reported a critical outage affecting Login, All Files, Notes, Uploads and Box API. It started and was marked resolved at 2026-06-03 17:53 UTC (computed duration: 0 min). Box said its systems automatically detected and corrected the underlying issue, with no current impact. | Major incident |