Who is down right now

20 down now · 248 this week

Box · Apps and SaaSNov 11, 2025, 01:00 UTC 12 months ago

[Critical] Issues with Multiple Box Services

CriticalCapacityUpdated 13d ago
Nov 11, 01:00 UTCNov 11, 01:00 UTC
Duration
0m
Impact
Critical
Root cause
Capacity
Box, 90 days
17 incidents
Affected
Not listed by the vendor.
Status page

Final update

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 November 10, 2025 between 5:00 pm PST and 5:26 pm PST, some users may have experienced slowness or temporary unavailability while working in Box. The issue occurred due to a sudden, large traffic spike on one database, which caused connection saturation on other databases, making them temporarily inaccessible. The issue was automatically resolved as our middleware service detected the problem and backed off. We are working on ways to prevent sudden traffic spikes from cascading to other systems and accelerating our middleware service’s auto-remediation process 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

Timeline

  1. Postmortem · Nov 19, 23:44 UTC
    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 November 10, 2025 between 5:00 pm PST and 5:26 pm PST, some users may have experienced slowness or temporary unavailability while working in Box. The issue occurred due to a sudden, large traffic spike on one database, which caused connection saturation on other databases, making them temporarily inaccessible. The issue was automatically resolved as our middleware service detected the problem and backed off. We are working on ways to prevent sudden traffic spikes from cascading to other systems and accelerating our middleware service’s auto-remediation process 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
  2. Resolved · Nov 11, 01:00 UTC
    From approximately 5:00 PM to 5:14 PM US Pacific time, we observed an issue impacting Box Web Application and Public APIs. 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.

More from Box

Full history

Also caused by capacity and load

All