Box Outage History

Started Jul 15, 2026, 04:14 AM UTC· resolved Jul 15, 2026, 06:43 AM UTC

1. investigating Jul 15, 2026, 04:14 AM UTC

   We are investigating an ongoing issue affecting Box Relay. We will provide additional information as it becomes available.

2. identified Jul 15, 2026, 04:50 AM 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.

3. identified Jul 15, 2026, 06:00 AM UTC

   We are continuing to work on a fix for this issue.

4. monitoring Jul 15, 2026, 06:32 AM UTC

   A fix has been implemented and we are monitoring the results.

5. resolved Jul 15, 2026, 06:43 AM UTC

   After further monitoring, this incident is now considered resolved. Box Relay has been restored to full functionality. If you continue to experience any issues, please contact Box Support at https://support.box.com.

6. postmortem Jul 19, 2026, 11:53 PM UTC

   We recently addressed issues affecting Relay. We would like to take the opportunity to further explain these issues and the steps we have taken to address them. Between July 14, 2026 at 2:21 AM PDT and July 14, 2026 at 11:55 PM PDT, some users may have experienced difficulties while working in Box. A recent code change in Relay introduced stricter error handling for collaboration failures, which caused the task outcome to not work in some cases. The issue was resolved by rolling back the Relay service to the previous version, after which point task outcome errors returned to baseline. 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

Read the full incident report →

Started Jul 07, 2026, 02:11 PM UTC· resolved Jul 07, 2026, 04:19 PM UTC

1. investigating Jul 07, 2026, 02:11 PM UTC

   Our team is investigating an issue with the Search service and Metadata queries. Users may see errors or slowness when attempting to search items in Box and / or using Metadata queries. We will provide additional information as it becomes available.

2. investigating Jul 07, 2026, 02:42 PM UTC

   Our team is investigating an issue with the Search service, Box Sign Templates and Metadata queries. Users may see errors or slowness when attempting to search items in Box and / or using Metadata queries. We will provide additional information as it becomes available.

3. identified Jul 07, 2026, 03:07 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.

4. identified Jul 07, 2026, 04:01 PM UTC

   Our team continues remediation efforts to restore full functionality to the Search service, Box Sign Templates and Metadata queries. We will provide additional updates as they become available.

5. monitoring Jul 07, 2026, 04:12 PM UTC

   Our team has taken steps to remediate this issue and is seeing improvement for the Search service, Box Sign Templates and Metadata queries. We are continuing to monitor for any additional impact.

6. resolved Jul 07, 2026, 04:19 PM UTC

   After further monitoring, this incident is now considered resolved. Search service, Box Sign Templates and Metadata queries have been restored to full functionality. If you continue to experience any issues, please contact Box Support at https://support.box.com.

7. postmortem Jul 31, 2026, 09:02 PM UTC

   We recently addressed an issue that affected Box Search and related Query functionality, including the Public APIs and Box Apps features that rely on them. We would like to take the opportunity to explain what happened and the steps we have taken to prevent it from happening again. On July 7, 2026 between 06:22 AM and 08:53 AM PT, some customers may have experienced elevated latencies and intermittent errors when using the Box Search and Query functionality. Public APIs for these features, Box Apps, Web App Search, and other functionalities that depends on Search and Query APIs were also impacted. This incident was caused by a sudden surge in indexing traffic that overwhelmed services in one of our subsystems, before they could be scaled up or rate limiting could kick in. We were able to remediate the issue by isolating the offending traffic and allowing the surge of indexing work to finish processing and drain. Regular traffic routing was restored once the affected infrastructure was healthy again. # **Analysis** This incident revealed an opportunity to improve how we protect our search indexing subsystem from sudden~~,~~ and concentrated surges of load. While our stateless services can quickly autoscale horizontally, our stateful systems cannot be scaled as quickly to handle sudden surges in load. We’ve historically focused on query traffic driven load and over-provisioned to handle any increases in internally generated indexing load. This incident revealed that sudden and large indexing surges can impact stability more than we anticipated. Our safeguards did not sufficiently slow or throttle a large burst of re-indexing traffic, and a temporary configuration change in place at the time of this incident caused files to be re-indexed in full even when only non-content attributes had changed, amplifying the load. # **Corrective Actions** Box has initiated the following corrective actions: * Add per source rate limiting to the indexing pipeline so a large burst of work cannot overwhelm the subsystem. * Optimize indexing load, so files are only re-indexed when their content has actually changed. * Set safer limits on how much work the pipeline will accept at once. * Improve monitoring and alerting to detect unusual spikes in processing earlier and respond before customers are impacted. ‌ 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 this provides clarity on what occurred and the steps we are taking. We would be happy to answer any questions you may still have regarding this matter. Sincerely, The Box Team

Read the full incident report →

Started Jun 25, 2026, 07:29 PM UTC· resolved Jun 25, 2026, 09:47 PM UTC

1. investigating Jun 25, 2026, 07:29 PM UTC

   Our team is investigating an issue with Zip Downloads in the Box Web Application. Users may see errors or slowness when attempting to download folders from Box. We will provide additional information as it becomes available.

2. identified Jun 25, 2026, 07:50 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.

3. identified Jun 25, 2026, 07:59 PM UTC

   We are continuing to work on a fix for this issue.

4. monitoring Jun 25, 2026, 08:29 PM UTC

   Our team has taken steps to remediate this issue and is seeing improvement for the Zip Downloads service. We are continuing to monitor for any additional impact.

5. resolved Jun 25, 2026, 09:47 PM UTC

   After further monitoring, this incident is now considered resolved. The Zip Downloads service has been restored to full functionality. If you continue to experience any issues, please contact Box Support at https://support.box.com.

6. postmortem Aug 04, 2026, 11:04 PM UTC

   Between 10:40 AM PDT and 12:33 PM PDT on June 25, 2026, some users may have experienced difficulties while working in Box. During this time, users routed through one particular US region may have seen failures or delays when attempting to download folders as ZIP files. The issue occurred after a recent network component update impacted a backend service in that region. We restored the feature availability by reverting the change. In addition, we are updating configuration and monitoring practices for such changes to reduce the likelihood of recurrence. # Analysis As part of our continuous and ongoing service improvement efforts, we recently rolled out a change to our internal compute platform. In one of our US regions, this change resulted in a resource problem within our service mesh layers. This incident highlighted opportunities to improve how platform updates and service configuration changes are propogated across Box compute regions. # Corrective Actions Box has initiated the following corrective actions: * Improved our multi-region roll out monitoring and alerting * Audited resource configurations for multi-region services * Improved ongoing monitoring and alerting of multi-region services 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

7. postmortem Aug 06, 2026, 04:17 PM UTC

   Between 10:40 AM PDT and 12:33 PM PDT on June 25, 2026, some users may have experienced difficulties while working in Box. During this time, users routed through one particular US region may have seen failures or delays when attempting to download folders as ZIP files. The issue occurred after a recent network component update impacted a backend service in that region. We restored the feature availability by reverting the change. In addition, we are updating configuration and monitoring practices for such changes to reduce the likelihood of recurrence. # Analysis As part of our continuous and ongoing service improvement efforts, we recently rolled out a change to our internal compute platform. In one of our US regions, this change resulted in a resource problem within our service mesh layers. This incident highlighted opportunities to improve how platform updates and service configuration changes are propogated across Box compute regions. # Corrective Actions Box has initiated the following corrective actions: * Improved our multi-region roll out monitoring and alerting * Audited resource configurations for multi-region services * Improved ongoing monitoring and alerting of multi-region services ‌ 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

Read the full incident report →

Started Jun 17, 2026, 07:34 PM UTC· resolved Jun 17, 2026, 08:28 PM UTC

1. investigating Jun 17, 2026, 07:34 PM UTC

   Our team is investigating an issue with Box Webapp. Users may experience intermittent failures when loading the "All files" page and subfolders. We will provide additional information as it becomes available.

2. monitoring Jun 17, 2026, 07:44 PM UTC

   Our team has taken steps to remediate this issue and is seeing improvement for Box Webapp service. We are continuing to monitor for any additional impact.

3. resolved Jun 17, 2026, 08:28 PM UTC

   After further monitoring, this incident is now considered resolved. Box Webapp services have been restored to full functionality. Please contact Box Support at https://support.box.com/ if you continue to experience any issues.

4. postmortem Jun 18, 2026, 08:26 PM 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 June 17th 2026 between 12:06pm PST and 12:39pm PST, some users may have experienced difficulties while working in Box. During this time, some customers were unable to browse folders in the web application. The issue occurred because folder browsing traffic was directed to a new implementation, as part of an ongoing effort to improve performance and stability. We were able to resolve the issue through targeted traffic adjustments and capacity mitigations. We are improving our deployment, capacity, and observability practices to prevent recurrence and detect future issues more quickly. 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

Read the full incident report →

Started Jun 16, 2026, 11:00 PM UTC· resolved Jun 16, 2026, 11:00 PM UTC

1. resolved Jun 16, 2026, 11:16 PM UTC

   From approximately 3:40PM and 3:50 PM PDT, we observed an issue impacting downloads. 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.

Read the full incident report →

Started Jun 01, 2026, 12:58 AM UTC· resolved Jun 01, 2026, 02:25 AM UTC

1. investigating Jun 01, 2026, 12:58 AM UTC

   We are investigating an ongoing issue affecting Box AI. We will provide more information as soon as it is available.

2. identified Jun 01, 2026, 01:16 AM 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.

3. monitoring Jun 01, 2026, 01:49 AM UTC

   Our team has taken steps to remediate this issue and is seeing improvement for Box AI. We are continuing to monitor for any additional impact.

4. resolved Jun 01, 2026, 02:25 AM UTC

   After further monitoring, this incident is now considered resolved. Box services have been restored to full functionality. Please contact Box Support at https://support.box.com/ if you continue to experience any issues.

5. postmortem Aug 07, 2026, 12:00 AM 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 May 31, 2026 between 5:00pm PDT and 6:41pm PDT, some customers may have experienced errors or degraded performance when using Box AI features, including failures to generate AI responses or slower-than-expected behavior. The issue affected only AI-related capabilities and did not impact general file access. The disruption was caused by an outage with a third-party AI provider that led to failed AI requests. Service was restored once the provider issue was resolved and normal AI request processing resumed. We are reviewing our third-party dependencies and operational practices to reduce the risk of similar interruptions 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

Read the full incident report →

Started May 22, 2026, 08:46 AM UTC· resolved May 22, 2026, 09:18 AM UTC

1. investigating May 22, 2026, 08:46 AM UTC

   Our team is investigating an issue with Logins for Box Drive. Users attempting to log in to Box Drive may see errors or timeouts. Users encountering this issue can log in to the Box Web Application as a temporary workaround. We will provide additional information as it becomes available.

2. monitoring May 22, 2026, 09:15 AM UTC

   We have resolved the issue impacting Box Drive. We are continuing to monitor to ensure no further impact is observed

3. resolved May 22, 2026, 09:18 AM UTC

   After further monitoring, this incident is now considered resolved. Box services have been restored to full functionality. Please contact Box Support at https://support.box.com/ if you continue to experience any issues.

4. postmortem May 29, 2026, 12:41 AM 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._ Between May 21, 2026 at 10:56 PM and May 22, 2026 at 2:07 AM PDT, some customers attempting to sign into Box Drive may have experienced errors or been unable to complete the login process. The issue affected a subset of customers who use a particular Mobile Application Management \(MAM\) service that was not universal across all users. The problem was caused by a change to our single sign-on configuration that prevented certain Box Drive logins from completing. Service was restored after we reverted the configuration and validated successful logins for impacted users. We are reviewing our deployment and administrative procedures to reduce the risk of this type of issue recurring. 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

Read the full incident report →

Started May 14, 2026, 09:31 AM UTC· resolved May 14, 2026, 09:03 PM UTC

1. resolved May 29, 2026, 07:25 PM UTC

   Between 2:31am and 4:45pm PDT on May 14, 2026 we observed an issue impacting streaming Enterprise Events API . Our systems 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.

2. postmortem May 29, 2026, 07:26 PM UTC

   We recently addressed issues affecting **Enterprise Events 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. ‌ Between 2:31am and 4:45pm PDT on May 14, 2026, some users may have experienced difficulties while working in Box. During this time, customers using the streaming Enterprise Events API experienced delivery delays of up to 6.5 hours. The issue occurred when an internal indexing service unexpectedly generated events at an unconstrained rate, which caused a significant concentrated spike in the total events volume. We were able to resolve the issue by redirecting those events from our streaming enterprise events pipeline for later processing. In addition, we will exclude events originating from internal services from our enterprise events processing pipelines and proactively deprioritize unexpected surges in events to prevent similar issues from occurring in the future. ‌ **Analysis** ‌ There were a number of contributing factors leading to this incident: ‌ Our internal search indexing service produced events, which should not have been created, at a rate significantly exceeding enterprise usage. These events were published to a queue to be written to the persistent datastore. Also, these events were concentrated in certain access patterns causing hot spotting in some database partitions. The significantly reduced throughput of these partitions caused the subscriber to fall behind. Once these access patterns were identified and the corresponding events removed, service was resolved promptly. Moving forward, these events will not be published. ‌ **Corrective Actions** ‌ The following corrective actions have been completed or are planned: ‌ * **Disable Event Publishing for Search Services** - We are disabling enterprise events from being produced and processed from Box internal services. * **Deprioritize Surge Workloads** - We will monitor for workloads generating significant volumes of event data and deprioritize those events from the primary pipeline. * **Update Incident Response Procedures** - We are updating our runbooks to account for these conditions and related actions. ‌ 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

Read the full incident report →

Started Apr 27, 2026, 05:36 PM UTC· resolved Apr 27, 2026, 07:11 PM UTC

1. investigating Apr 27, 2026, 05:36 PM UTC

   Our team is investigating an issue with Search by metadata in the Box Web Application. Users may see search results not return. We will provide additional information as it becomes available.

2. investigating Apr 27, 2026, 05:37 PM UTC

   We are continuing to investigate this issue.

3. investigating Apr 27, 2026, 05:51 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.

4. identified Apr 27, 2026, 05:52 PM UTC

   The issue has been identified and a fix is being implemented.

5. monitoring Apr 27, 2026, 06:17 PM UTC

   Our team has taken steps to remediate this issue and is seeing improvement for the search with metadata service. We are continuing to monitor for any additional impact.

6. resolved Apr 27, 2026, 07:11 PM UTC

   After further monitoring, this incident is now considered resolved. Search with metadata has been restored to full functionality. If you continue to experience any issues, please contact Box Support at https://support.box.com.

Read the full incident report →

Started Apr 07, 2026, 12:00 AM UTC· resolved Apr 07, 2026, 12:00 AM UTC

1. resolved Apr 07, 2026, 12:36 AM UTC

   Between 4:57 and 5:05 PM PST, some users may have experienced difficulties using Public API. No further impact has been observed and we are considering this issue to be resolved. If you are still experiencing any issues, please let us know at https://support.box.com.

Read the full incident report →

Started Apr 03, 2026, 04:04 AM UTC· resolved Apr 03, 2026, 08:09 AM UTC

1. investigating Apr 03, 2026, 04:04 AM UTC

   We are investigating an ongoing issue affecting Box Sign. We will provide more information as soon as it is available.

2. identified Apr 03, 2026, 06:27 AM 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.

3. resolved Apr 03, 2026, 08:09 AM UTC

   After further monitoring, this incident is now considered resolved. Box Sign services have been restored to full functionality. Please contact Box Support at https://support.box.com/ if you continue to experience any issues.

4. postmortem Apr 10, 2026, 04:36 PM UTC

   On April 2, 2026 between 8:19 PM PDT and 11:56 PM PDT, some users may have experienced difficulties while working in Box. During this time, Box Sign users might have experienced errors while creating new signature requests, accessing existing signature requests, or attempting ~~been unable~~ to access the service. The issue occurred as a result of an erroneous change made by a third-party infrastructure provider. We were able to resolve the issue by escalating it to the provider. In addition, we are working to improve the reliability of the Box Sign service by enhancing our disaster recovery processes 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

Read the full incident report →

Started Mar 25, 2026, 11:44 AM UTC· resolved Mar 25, 2026, 02:03 PM UTC

1. investigating Mar 25, 2026, 11:44 AM UTC

   Our team is investigating an issue with the Admin Conssole dashboard. Users may experience slowness when attempting to access the Admin Console. We will provide additional information as it becomes available.

2. identified Mar 25, 2026, 12:23 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.

3. monitoring Mar 25, 2026, 01:36 PM UTC

   Our team has taken steps to remediate this issue and is seeing improvement to access the Box Admin console. We are continuing to monitor for any additional impact.

4. resolved Mar 25, 2026, 02:03 PM UTC

   After further monitoring, this incident is now considered resolved. The Admin console service has been restored to full functionality. If you continue to experience any issues, please contact Box Support at https://support.box.com.

Read the full incident report →

Started Mar 25, 2026, 05:52 AM UTC· resolved Mar 25, 2026, 05:00 PM UTC

1. investigating Mar 25, 2026, 05:52 AM UTC

   Our team is investigating an issue with Box Shuttle and has identified the underlying cause of this issue and is working to take remediating steps. We will provide additional updates as they become available.

2. investigating Mar 25, 2026, 06:32 AM UTC

   We are continuing to investigate this issue.

3. investigating Mar 25, 2026, 07:01 AM UTC

   We are continuing to investigate this issue.

4. investigating Mar 25, 2026, 07:31 AM UTC

   We are continuing to investigate this issue.

5. investigating Mar 25, 2026, 07:59 AM UTC

   We are continuing to investigate this issue.

6. investigating Mar 25, 2026, 08:33 AM UTC

   We are continuing to investigate this issue.

7. investigating Mar 25, 2026, 09:07 AM UTC

   We are continuing to investigate this issue.

8. investigating Mar 25, 2026, 09:40 AM UTC

   We are continuing to investigate this issue.

9. investigating Mar 25, 2026, 10:11 AM UTC

   We are continuing to investigate this issue.

10. investigating Mar 25, 2026, 10:44 AM UTC

    We are continuing to investigate this issue.

11. investigating Mar 25, 2026, 11:21 AM UTC

    We are continuing to investigate this issue.

12. investigating Mar 25, 2026, 12:07 PM UTC

    We are continuing to investigate this issue.

13. investigating Mar 25, 2026, 12:43 PM UTC

    We are continuing to investigate this issue. We will provide additional updates as they become available.

14. investigating Mar 25, 2026, 01:24 PM UTC

    We are continuing to investigate this issue. We will provide additional updates as they become available.

15. identified Mar 25, 2026, 02:23 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.

16. identified Mar 25, 2026, 02:54 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.

17. monitoring Mar 25, 2026, 04:26 PM UTC

    Our team has taken steps to remediate this issue and is seeing improvement for the Box Shuttle service. We are continuing to monitor for any additional impact.

18. resolved Mar 25, 2026, 05:00 PM UTC

    After further monitoring, this incident is now considered resolved. Box Shuttle has been restored to full functionality. If you continue to experience any issues, please contact Box Support at https://support.box.com.

19. postmortem Jul 29, 2026, 10:33 PM UTC

    We recently addressed issues affecting Shuttle \(migration service\). 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 03/24/2026 08:00 PM PDT and 03/25/2026 11:40 AM PDT on Mar 24–25, 2026 — some users may have experienced difficulties while working in Box. During this time, users reported blank pages, timeouts, and failures when configuring or running migration jobs in the Shuttle interface. ‌ The issue occurred after a vendor-managed database maintenance update that included an operating system and security library change, which caused the affected database clusters to enter a read-only or degraded state and prevented normal job configuration and history access. We were able to resolve the issue after the vendor reverted the change on the affected clusters and our teams restarted the dependent services, after which we verified normal operation. In addition, we will take steps to reduce the likelihood of recurrence by improving coordination and testing for vendor-managed upgrades and strengthening our operational safeguards. ‌ # Analysis ‌ This incident highlighted risks in relying on vendor-managed platform updates without staged validation across environments, and showed gaps in how quickly we could detect and isolate read-only database states. Response required close vendor collaboration to identify and revert the change; internal mitigations \(service restarts and connection management\) were insufficient until the vendor rollback completed. We will improve pre-upgrade controls, monitoring for early signs of degraded database state, and runbook guidance for faster mitigation. ‌ # Corrective Actions Box has initiated the following corrective actions: ‌ * Require staged validation of vendor-managed platform upgrades \(dev → staging → production\) before production rollout. * Establish a coordinated upgrade/runbook with the vendor that defines pre-checks, rollback steps, and escalation pathways. * Enhance monitoring and alerts for read-only database states, failed elections, and connection saturation to detect similar issues earlier. ‌ 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

Read the full incident report →

Started Mar 20, 2026, 03:37 AM UTC· resolved Mar 20, 2026, 05:08 AM UTC

1. investigating Mar 20, 2026, 03:37 AM UTC

   We are investigating an ongoing issue affecting folder and file preview. Customers may experience a white or blank page when loading subfolders and accessing shared links. We will provide more information as soon as it is available.

2. identified Mar 20, 2026, 03:59 AM UTC

   The issue has been identified and a fix is being implemented.

3. investigating Mar 20, 2026, 04:13 AM UTC

   We are continuing to investigate this issue.

4. investigating Mar 20, 2026, 04:14 AM UTC

   We are continuing to investigate this issue.

5. monitoring Mar 20, 2026, 04:44 AM UTC

   A fix has been implemented and we are monitoring the results.

6. resolved Mar 20, 2026, 05:08 AM UTC

   After further monitoring, this incident is now considered resolved. Our teams have validated that all affected services are restored to full functionality. Please contact Box Support at https://support.box.com/ if you continue to experience any issues.

7. postmortem Apr 15, 2026, 09:10 PM UTC

   We recently addressed issues affecting the “All Files” page in Box. 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 **3:00 PM PDT** and **9:34 PM PDT** on **March 19, 2026**, some users may have experienced difficulties while working in Box. During this time, users accessing Box through the web application may have encountered blank pages when navigating into folders on the “All Files” page or when opening certain shared links. The issue occurred as a result of a recent code change, made in our ongoing effort to improve performance and stability. We were able to resolve the issue by reverting the web application to the previous stable version. In addition, we are strengthening safeguards in our deployment and rollback processes to prevent similar issues from occurring in the future. **Analysis** The incident revealed areas for improvement in automation reliability, validation controls, and the consistency of rollout and rollback mechanisms, which contributed to an unintended artifact version being promoted to the production environment. **Corrective Actions** Box has initiated the following corrective actions: * **Strengthen deployment validation and gating mechanisms**: We are implementing stricter automated checks to verify artifact integrity, version correctness, and configuration alignment at each stage of the pipeline, ensuring only validated and approved builds can be promoted to production. * **Standardize and reinforce rollout and rollback procedures**: We are establishing consistent, well-documented deployment and rollback workflows with automated safeguards and audit trails to ensure reliable reversibility and prevent incorrect artifact promotion during release operations. 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

Read the full incident report →

Started Mar 18, 2026, 04:00 PM UTC· resolved Mar 18, 2026, 06:00 PM UTC

1. resolved Mar 18, 2026, 06:49 PM UTC

   Between 10:56am PST to 11:42am PST on March 18th, 2026 some users may have experienced difficulties previewing files. No further impact has been observed and we are considering this issue to be resolved. If you are still experiencing any issues, please let us know at https://support.box.com.

Read the full incident report →

Started Mar 10, 2026, 12:30 AM UTC· resolved Mar 10, 2026, 01:14 AM UTC

1. investigating Mar 10, 2026, 12:30 AM UTC

   Our team is investigating reports of issues affecting Logins. Some customers may be experiencing errors or delays when attempting to log in to their Box accounts. We are working to identify the cause and will provide another update as soon as more information is available.

2. identified Mar 10, 2026, 12:34 AM UTC

   We have identified the cause of the issue. Our team is now actively working on implementing a solution.

3. monitoring Mar 10, 2026, 01:05 AM UTC

   A fix has been implemented to address the issue, and we are observing recovery. Customers should now be seeing improvement when attempting to log in. Our team will continue to monitor the service to ensure full stability is restored. We will provide another update once the incident is resolved or if the status changes.

4. monitoring Mar 10, 2026, 01:13 AM UTC

   After a period of monitoring, we have confirmed that the issues affecting Login are now resolved. Service has been restored to full functionality. If you continue to experience any issues, please contact Box Support at https://support.box.com.

5. resolved Mar 10, 2026, 01:14 AM UTC

   This incident has been resolved.

6. postmortem Mar 22, 2026, 08:47 PM 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 March 9th 2026, between 3:46 PM PST and 4:32 PM PST, some users may have experienced difficulties while while attempting to log in to Box. Users already logged to Box were not impacted by this issue. The issue occurred due to a overloading and insufficient resources assigned to one of the services used during login process, responsible for ensuring maximum device security of users using Box. The issue was resolved by assigning more resources to the service, sufficient for current and future traffic. ‌ We are conducting a full engineering postmortem to identify gaps in our processes that allowed the service to experience excessive load without more resources being assigned in advance automatically. 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

Read the full incident report →

Started Feb 27, 2026, 08:02 PM UTC· resolved Feb 27, 2026, 11:51 PM UTC

1. investigating Feb 27, 2026, 08:02 PM UTC

   We are investigating an ongoing issue affecting FTP and SFTP logins. We will provide more information as soon as it is available.

2. investigating Feb 27, 2026, 09:15 PM UTC

   Box continues to investigate reports of Captcha errors issues with FTP and SFTP logins.

3. monitoring Feb 27, 2026, 09:58 PM UTC

   A fix has been implemented and we are monitoring the results.

4. monitoring Feb 27, 2026, 10:58 PM UTC

   We are continuing to monitor for any further issues.

5. resolved Feb 27, 2026, 11:51 PM UTC

   After further monitoring, this incident is now considered resolved. FTP and SFTP service has been restored to full functionality. If you continue to experience any issues, please contact Box Support at https://support.box.com.

6. postmortem Mar 05, 2026, 10:43 PM UTC

   We recently addressed issues affecting Box FTP and SFTP services. 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. From February 25th, 2026 at 9:20 AM PST to February 27th at 4:10 PM PST, some users may have experienced difficulties while working in Box. During this time, Box FTP and SFTP users may have seen CAPTCHA messages while logging in through FTP. The issue occurred due to a change in internal traffic routing which affected the Box FTP and SFTP services. We were able to resolve the issue by reverting the internal routing change and clearing CAPTCHAs for affected users. We are now working to harden the system against internal rate limiting going forward to prevent similar issues from occurring in the future. ‌ **Analysis** On February 23rd at 8:20 AM PST, a change was made to send a subset of login traffic through a new route. After this change, no issues were observed and no customer issues were reported. On February 25th at 8:20 AM PST, a subsequent change was made to send more of the same login traffic through the new route. Roughly one hour after this change was completed, the Box FTP service started to receive an increased rate of CAPTCHA failures, blocking users from logging in. The second routing change was identified as the root cause and reverted on February 27th at 12:49 PM PST. After revert, a number of Box FTP users needed to clear an additional CAPTCHA. Box Support assisted in clearing the CAPTCHAs manually and by 4:10 PM PST, all Box FTP and SFTP login errors were resolved. ‌ Our analysis determined that the root cause of this issue was a service that was added to the call stack in the new route. The service in question did not properly communicate rate limiting information sent by the Box FTP service. This led to Box FTP being internally rate limited, which prompted users to improperly complete a CAPTCHA when logging in to Box FTP. ‌ **Corrective Actions** Box has initiated the following corrective actions: * The service in question has been fixed to properly forward required rate limiting information. * We are implementing enhanced monitoring to enable faster responses in the case of similar occurrences. * A comprehensive review is being performed to find any instances of missing rate limiting information within the stack. ‌ 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

Read the full incident report →

Started Feb 25, 2026, 01:00 PM UTC· resolved Feb 25, 2026, 02:16 PM UTC

1. identified Feb 25, 2026, 01:43 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.

2. monitoring Feb 25, 2026, 01:54 PM UTC

   Our team has taken steps to remediate this issue and is seeing improvement for the impacted services. We are continuing to monitor for any additional impact.

3. monitoring Feb 25, 2026, 01:58 PM UTC

   Our team has taken steps to remediate this issue and is seeing improvement for the impacted services. We are continuing to monitor for any additional impact.

4. resolved Feb 25, 2026, 02:16 PM UTC

   After further monitoring, this incident is now considered resolved. Box services have been restored to full functionality. Please contact Box Support at https://support.box.com/ if you continue to experience any issues.

5. postmortem Mar 05, 2026, 10:49 PM 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 February 25, 2026 between 4:45 am PST and 5:40 am PST, some users may have experienced difficulties while working in Box. During this time, customers of Box Zones UK may have had issues with uploading, downloading, and previewing files. ‌ The issue occurred when some instances of a backend service in the impacted region ran into memory pressure. We resolved the issue by temporarily redirecting certain compute processes from the impacted region to the US region. Of note, even during the period of temporary traffic redirection, all Box Zones customer content continued to be stored in the correct Box Zones region. ‌ We are conducting a full engineering postmortem and our overview is subject to change with further analysis. 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

Read the full incident report →

Started Feb 24, 2026, 11:32 PM UTC· resolved Feb 25, 2026, 12:15 AM UTC

1. identified Feb 24, 2026, 11:32 PM UTC

   Our team is investigating an issue with Box API and has identified the underlying cause of this issue and is working to take remediating steps. We will provide additional updates as they become available.

2. identified Feb 24, 2026, 11:32 PM UTC

   We are continuing to work on a fix for this issue.

3. identified Feb 24, 2026, 11:42 PM UTC

   We are continuing to work on a fix for this issue.

4. monitoring Feb 25, 2026, 12:02 AM UTC

   Our team has taken steps to remediate this issue and is seeing improvement for Box API. We are continuing to monitor for any additional impact.

5. resolved Feb 25, 2026, 12:15 AM UTC

   After further monitoring, this incident is now considered resolved. Box API has been restored to full functionality. If you continue to experience any issues, please contact Box Support at https://support.box.com.

6. postmortem Mar 05, 2026, 10:31 PM 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 February 24, 2026 between 1:15 PM PST and 3:59 PM PST, some users may have experienced difficulties while working in Box. The most significant impact occurred from 1:42 PM PST to 1:59 PM PST, when Uploads, Downloads, Logins, APIs, and Notes saw elevated latency and errors. A small subset of functionality continued to experience some degradation through 3:59 PM PST. The issue occurred due to our cache cluster becoming temporarily overloaded due to a traffic spike concentrated on a single hot key. We were able to resolve the majority of the impact by rate limiting peripheral workloads and fully resolve the issue by stopping the offending traffic source. We are now implementing automated hot key detection and introducing dynamic rate limiting at the caching layer 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

Read the full incident report →

Started Feb 20, 2026, 07:11 PM UTC· resolved Feb 20, 2026, 08:37 PM UTC

1. investigating Feb 20, 2026, 07:11 PM UTC

   Our team is investigating an issue with the marketing site box.com. Users may see errors when attempting to access Box.

2. identified Feb 20, 2026, 07:14 PM UTC

   Our team has identified the underlying cause of this issue and is working to take remediating steps. The issue is due to an outage within Cloudflare at this time: https://www.cloudflarestatus.com/incidents/kwy3dt82bwbt As we work on remediation steps users can workaround this issue by access box through app.box.com instead of box.com

3. monitoring Feb 20, 2026, 07:30 PM UTC

   Our team has taken steps to remediate this issue and is seeing improvement for our marketing page box.com. We are continuing to monitor for any additional impact.

4. resolved Feb 20, 2026, 08:37 PM UTC

   This incident has now been resolved. Box will continue to monitor CloudFlare: https://www.cloudflarestatus.com/incidents/kwy3dt82bwbt

5. postmortem Jul 09, 2026, 07:16 PM UTC

   We recently addressed issues affecting Box web access. 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 10:50 AM PST and 11:25 AM PST on February 20, 2026, some users may have experienced difficulties accessing Box via web browser, including failed page loads and intermittent connectivity. During this time, requests to our site that relied on a third-party network service did not route reliably for affected networks, causing DNS resolution and connectivity failures for that hostname. We were able to restore service after the third-party re-advertised the affected network prefixes, at which point we safely re-enabled the dependent routing configuration, restoring normal service behavior. In addition, we are working with the third-party provider and updating our procedures and monitoring to reduce the risk of recurrence and improve detection and recovery. # Analysis This incident highlighted a dependency risk on third-party network prefix advertisement and revealed opportunities to improve early detection and customer-facing communication. It also reinforced the importance of clear playbooks for safely changing routing configurations during third-party outages and ensuring monitoring captures customer-impacting DNS and connectivity failures quickly. # Corrective Actions Box has initiated the following corrective actions: * Work with the third-party provider to complete follow-up and incorporate their post-incident findings * Update our routing and operational runbooks to clarify safe, pre-approved steps for toggling routing configurations during third-party network incidents * Enhance external-facing monitoring and alert thresholds for DNS and site availability to detect and communicate customer impact more quickly ‌ 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

Read the full incident report →

Started Jan 09, 2026, 06:00 AM UTC· resolved Jan 09, 2026, 06:00 AM UTC

1. resolved Jan 09, 2026, 07:14 AM UTC

   From approximately 9:52 PM to 10:00 PM US Pacific time, we observed an issue impacting Logins, Notes and API. 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.

Read the full incident report →

Started Jan 02, 2026, 01:30 PM UTC· resolved Jan 02, 2026, 10:33 PM UTC

1. resolved Jan 03, 2026, 12:16 AM UTC

   From approximately 05:30 AM to 02:30 PM US Pacific time, we observed an issue impacting Enterprise Reporting. Customers that attempted to run a report or had a scheduled report during this window may not have the report generated. Reports run during this window should be run again if they have not appeared as expected. 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.

2. postmortem Jan 14, 2026, 12:40 PM UTC

   We recently addressed issues affecting the Enterprise Report feature. 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 January 2, 2026 between 5:30 AM and 2:33 PM PST, some users may have experienced difficulties while working in Box. During this time, users were unable to generate some types of Enterprise Reports, and Enterprise Reports scheduled during this time interval may have failed. We were able to resolve the issue by rolling back a configuration change that caused the issues for the reporting engine. ‌ **Analysis** Box Enterprise Reports relies on a definition of the schemas that describe the underlying database tables that the engine will consume to generate the reports. As we deliver new products, these schemas may occasionally need to be updated, and we have a standard process and pipeline to deploy these schema. As part of a project to upgrade our pipeline infrastructure, the schema deployment pipeline migrated to a new infrastructure. During the migration process, an external library version upgrade introduced a new default behavior that was not compatible with the existing pipeline. As a result, the Enterprise Reports service could not access the underlying tables in some cases, resulting in a temporary degradation of the service. Additionally, the migration process exposed some observability and guardrails gaps in the pipeline that would have prevented this issue from happening and that extended the impact for a longer period of time. ‌ Once identified, the incompatible library was reverted to the previous version and the system went back to normal. ‌ **Corrective Actions** Box has initiated the following corrective actions: * Introduce a schema validation step in the deployment pipeline so that incompatible schemas cannot be deployed * Enforce the environment promotion process as part of the schema deployment pipeline * Uplift the observability of the pipeline to enable more visibility around the different phases of the deployment process ‌ 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

Read the full incident report →

Started Dec 18, 2025, 12:21 AM UTC· resolved Dec 18, 2025, 12:45 AM UTC

1. investigating Dec 18, 2025, 12:21 AM UTC

   We are investigating an ongoing issue affecting Box Sign. We will provide more information as soon as it is available.

2. identified Dec 18, 2025, 12:39 AM 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.

3. resolved Dec 18, 2025, 12:45 AM UTC

   After further monitoring, this incident is now considered resolved. The affected services have been restored to full functionality. If you continue to experience any issues, please contact Box Support at https://support.box.com.

4. postmortem Feb 24, 2026, 01:10 AM UTC

   We recently addressed issues affecting several features of Box. 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 December 17, 2025, from 11:15 AM PST to 4:46 PM PST, some users may have experienced difficulties while working in Box Sign, Box AI, and Box Doc Gen. During this time, users may have noticed service degradation and delayed email delivery. The issue was caused by a missing schema, which was itself caused by a corrupted schema deployment. We were able to resolve the issue by rolling back the change that temporarily created issues. ‌ **Analysis** Box Sign, Box AI, and Box Doc Gen rely on a definition of the schemas that describe the events that they need to process. As we deliver new products, these schemas may occasionally need to be updated, and we have a standard process and pipeline to deploy these schema. As part of a project to upgrade our pipeline infrastructure, the schema deployment pipeline migrated to a new infrastructure. During the migration process, an external library version upgrade introduced a new default behavior that was not compatible with the existing pipeline. This resulted in a temporary degradation of the service. Additionally, the migration process exposed some observability and guardrail gaps in the pipeline that would have prevented this issue from happening and that extended the impact for a longer period of time. Once identified, the incompatible library was reverted to the previous version and the system resumed to normal. ‌ **Corrective Actions** Box has initiated the following corrective actions: * Introduce a schema validation step in the deployment pipeline so that incompatible schemas cannot be deployed * Enforce the environment promotion process as part of the schema deployment pipeline * Uplift the observability of the pipeline to enable more visibility around the different phases of the deployment process ‌ 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

Read the full incident report →

Started Dec 17, 2025, 12:57 AM UTC· resolved Dec 17, 2025, 04:31 AM UTC

1. investigating Dec 17, 2025, 12:57 AM UTC

   We are investigating an ongoing issue affecting Logins/SSO, API and Box Notes. We will provide more information as soon as it is available.

2. identified Dec 17, 2025, 01:19 AM 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.

3. identified Dec 17, 2025, 01:42 AM UTC

   We are continuing to work on a fix for this issue.

4. identified Dec 17, 2025, 02:36 AM UTC

   We are continuing to work on a fix for this issue.

5. identified Dec 17, 2025, 03:17 AM UTC

   We are continuing to work on a fix for this issue.

6. monitoring Dec 17, 2025, 03:42 AM UTC

   Our team has taken steps to remediate this issue and is seeing improvement for multiple Box services. We are continuing to monitor for any additional impact.

7. resolved Dec 17, 2025, 04:31 AM UTC

   After further monitoring, this incident is now considered resolved. Our teams have validated that all affected services are restored to full functionality. Please contact Box Support at https://support.box.com/ if you continue to experience any issues.

8. postmortem Dec 18, 2025, 01:45 AM UTC

   We recently addressed issues affecting Box services**.** We would like to take the opportunity to further explain these issues and the steps we have taken to prevent them from happening in the future. On December 16, 2025 between 4:25 PM PST and 7:23 PM PST, some users may have experienced slowness and temporary unavailability while working in Box. The issue occurred when we attempted to roll back a diagnostic change that was suspected of causing a minor degradation. The rollback unintentionally resulted in decreased capacity in our middleware service, leading to a degraded site experience. It also introduced a distributed deadlock condition that prolonged our incident response and mitigation efforts. Ultimately, we were able to resolve the deadlock and return to normal operations by temporarily throttling inbound traffic. We have implemented measures to increase system capacity and minimize the possibility of a similar deadlock occurring in the future. We are also working on adding safeguards to avoid the rollback failure that served as the proximate cause of this incident. **Analysis** Between 11:11 AM PST and 1:38 PM PST, there was a production deployment of code that was aimed at gathering diagnostic information from our middleware service, in our ongoing efforts to improve system performance and resilience. At 3:30 PM PST, we observed a brief, mostly imperceptible degradation and decided to roll back the change as a precaution. Due to failure in the rollback procedure, we observed a significantly reduced capacity in our middleware service that eventually led to a distributed deadlock condition between critical databases. Box has made significant investments in reliability and mitigation measures. In this case, the issue was regional in scope and cross-region recovery capabilities are still in development. We therefore completed recovery by remediating the impacted region directly rather than executing a regional failover. We restored middleware service capacity by 5:21 PM PST, but the deadlock condition persisted. After several lower-impact attempts to dislodge the deadlock were unsuccessful, we took a broader mitigation step and throttled all traffic at 6:54 PM PST. This resulted in a 26-minute full outage, after which systems stabilized and gradually recovered, with the site returning to full functionality at 7:23 PM PST. **Corrective Actions** Box has initiated the following corrective actions: * Complete the planned capacity increase to reduce the chance of similar deadlocks and shorten recovery time if they occur * Strengthen rollback safeguards so changes can be safely and reliably reverted, preventing a repeat of the rollback failure that triggered this incident Thank you again for being a valued Box customer. We are continuously working to improve Box and want to make sure we are delivering the best in class product and user experience. Should you have any additional questions please do not hesitate to contact us. Sincerely, The Box Team

Read the full incident report →

Started Oct 30, 2025, 05:29 AM UTC· resolved Oct 30, 2025, 06:51 AM UTC

1. investigating Oct 30, 2025, 05:29 AM UTC

   We are investigating an ongoing issue affecting Downloads, Preview, Box Sign and Box Notes. We will provide more information as soon as it is available.

2. investigating Oct 30, 2025, 05:36 AM UTC

   We are continuing to investigate this issue.

3. identified Oct 30, 2025, 05:50 AM 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.

4. monitoring Oct 30, 2025, 06:16 AM UTC

   Our team has taken steps to remediate this issue and is seeing improvements. We are continuing to monitor for any additional impact.

5. resolved Oct 30, 2025, 06:51 AM UTC

   After further monitoring, this incident is now considered resolved. The affected services have been restored to full functionality. If you continue to experience any issues, please contact Box Support at https://support.box.com.

6. postmortem Nov 07, 2025, 01:59 AM UTC

   We recently addressed issues affecting downloads, preview, and Box Notes. 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 10:07 PM PDT and 11:16 PM PDT on October 29, 2025, some users may have experienced difficulties while working in Box. During this time, users may have encountered problems downloading or previewing files and using Box Notes. The issue was caused by a disruption with one of our third-party cloud partners. We resolved the issue by restarting and scaling up the impacted backend services. In addition, we are examining how to improve our resiliency in these scenarios to prevent similar issues from occurring in the future. ‌ **Analysis** This issue was triggered by a maintenance operation at one of our third-party cloud providers. During this operation, we encountered increased latency between several components in our US cloud regions. Because impact during this issue was limited to US cloud regions, Box Zones customers were not impacted. With the corrective actions outlined below, we strive to prevent or greatly minimize impact to customers from future similar incidents. ‌ **Corrective Actions** Box has initiated the following corrective actions: * Updated our client timeouts to be more fault-tolerant in the face of third party disruptions * Improved our regional resiliency through increased geo-redundancy for external dependencies * Updated our internal incident response processes to improve our response time ‌ 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

Read the full incident report →