For more information about our Incident Response and Communications please read this support article.

We also maintain a list of Known Product Issues separate from this site here.

[Critical] Issue with Box Shuttle

Incident Report for Box

Postmortem

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

Posted Jul 29, 2026 - 15:34 PDT

Resolved

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.
Posted Mar 25, 2026 - 10:00 PDT

Monitoring

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.
Posted Mar 25, 2026 - 09:26 PDT

Update

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.
Posted Mar 25, 2026 - 07:54 PDT

Identified

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.
Posted Mar 25, 2026 - 07:23 PDT

Update

We are continuing to investigate this issue. We will provide additional updates as they become available.
Posted Mar 25, 2026 - 06:24 PDT

Update

We are continuing to investigate this issue. We will provide additional updates as they become available.
Posted Mar 25, 2026 - 05:43 PDT

Update

We are continuing to investigate this issue.
Posted Mar 25, 2026 - 05:07 PDT

Update

We are continuing to investigate this issue.
Posted Mar 25, 2026 - 04:21 PDT

Update

We are continuing to investigate this issue.
Posted Mar 25, 2026 - 03:44 PDT

Update

We are continuing to investigate this issue.
Posted Mar 25, 2026 - 03:11 PDT

Update

We are continuing to investigate this issue.
Posted Mar 25, 2026 - 02:40 PDT

Update

We are continuing to investigate this issue.
Posted Mar 25, 2026 - 02:07 PDT

Update

We are continuing to investigate this issue.
Posted Mar 25, 2026 - 01:33 PDT

Update

We are continuing to investigate this issue.
Posted Mar 25, 2026 - 00:59 PDT

Update

We are continuing to investigate this issue.
Posted Mar 25, 2026 - 00:31 PDT

Update

We are continuing to investigate this issue.
Posted Mar 25, 2026 - 00:01 PDT

Update

We are continuing to investigate this issue.
Posted Mar 24, 2026 - 23:32 PDT

Investigating

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.
Posted Mar 24, 2026 - 22:52 PDT
This incident affected: Box Web Application (Box Shuttle).