Box incident
[Minor] Customers may be experiencing issues with uploads and downloads
Box experienced a minor incident on March 21, 2025 affecting Uploads/Downloads, lasting 1h 17m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Mar 21, 2025, 04:50 PM UTC
We are investigating an ongoing issue affecting uploads and downloads. We will provide more information as soon as it is available.
- investigating Mar 21, 2025, 04:50 PM UTC
We are continuing to investigate this issue.
- investigating Mar 21, 2025, 04:53 PM UTC
We are continuing to investigate this issue.
- identified Mar 21, 2025, 05:21 PM UTC
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.
- monitoring Mar 21, 2025, 05:40 PM UTC
Our team has taken steps to remediate this issue and is seeing improvement for uploads and downloads. We are continuing to monitor for any additional impact.
- resolved Mar 21, 2025, 06:07 PM UTC
After further monitoring, this incident is now considered resolved. Our Service has been restored to full functionality. If you continue to experience any issues, please contact Box Support at https://support.box.com.
- postmortem Mar 27, 2025, 03:34 PM UTC
We recently addressed issues affecting Box Zones Germany and Box Zones France. 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. Between 9:04am and 10:32am PDT on March 21, 2025, some Box Zones users in Germany and France may have experienced difficulties while working in Box. During this time, some servers became unresponsive, causing connections to time out for some users in these Box Zones regions. The issue occurred due to a configuration change made as part of a software upgrade, which resulted in some servers losing memory. We were able to resolve the issue by temporarily redirecting some processing activity until the configuration change was fixed. Throughout the duration of the incident, all content continued to be stored in the correct Zones region. We are also implementing additional monitoring and alerting to catch this type of issue sooner to prevent similar issues from occurring in the future. **Analysis** The issue occurred due to a configuration change which was made as part of upgrading some software to use the latest Long Term Supported \(LTS\) version of Java. The change inadvertently resulted in some servers running out of Java heap memory. We were able to resolve the issue by temporarily processing some European customer traffic using servers in the US until the European servers were back to normal. At no time during the issue was content moved or stored in a different region than the appropriate Box Zones region. **Corrective Actions** Box has initiated the following corrective actions: * Additional monitoring and alerting is being put into place to catch this type of issue sooner to prevent similar issues from occurring in the future. * We are making improvements to reduce the amount of time taken to switch to alternative servers for processing in these and similar issues. 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