- Level
- confirmed
- Worst impact
- Major outage
- Components
- Box Shuttle
- Down Index
- 45of 100
What to do
Check whether you use Box Box Shuttle. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 11h 8m it lasted.
Anything that failed between 2026-03-25 05:52 UTC and 2026-03-25 17:00 UTC may need a replay.Subscribe to Box's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=box works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Box 19
- 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.
provider
- investigating
We are continuing to investigate this issue.
provider
- investigating
We are continuing to investigate this issue.
provider
- investigating
We are continuing to investigate this issue.
provider
- investigating
We are continuing to investigate this issue.
provider
- investigating
We are continuing to investigate this issue.
provider
- investigating
We are continuing to investigate this issue.
provider
- investigating
We are continuing to investigate this issue.
provider
- investigating
We are continuing to investigate this issue.
provider
- investigating
We are continuing to investigate this issue.
provider
- investigating
We are continuing to investigate this issue.
provider
- investigating
We are continuing to investigate this issue.
provider
- investigating
We are continuing to investigate this issue. We will provide additional updates as they become available.
provider
- investigating
We are continuing to investigate this issue. We will provide additional updates as they become available.
provider
- 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.
provider
- 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.
provider
- 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.
provider
- 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.
provider
- 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
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-52ddd77c2c
Is Box still down?
No, this incident was resolved 2026-03-25 17:00 UTC. For Box's live state, see https://down.guide/box.
How long did it last?
11h 8m, from 2026-03-25 05:52 UTC to 2026-03-25 17:00 UTC, by the times Box posted.
What was affected?
Box named Box Shuttle.
What caused it?
Box hasn't published a root cause. If it does, it shows here.
Where does this come from?
Box's official status page, https://status.box.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.