Major incident

Box: [Medium] Issues with Box Shuttle Standalone

Affected: Box Shuttle

Current status of Box: Operational — live Box status

Timeline

1. Jul 31, 2026, 11:09 UTC
   investigating
   Our team is investigating an issue with Box Shuttle Standalone. Users may have issues to access, configure or create new Shuttle job details. We will provide additional information as it becomes available.
2. Jul 31, 2026, 11:16 UTC
   monitoring
   Our team has taken steps to remediate this issue and is seeing improvement for the Box Shuttle service (Standalone). We are continuing to monitor for any additional impact.
3. Jul 31, 2026, 11:30 UTC
   resolved
   After further monitoring, this incident is now considered resolved. Box Shuttle Service has been restored to full functionality. If you continue to experience any issues, please contact Box Support at https://support.box.com.
4. Aug 19, 2026, 00:19 UTC
   postmortem
   We recently addressed issues affecting Shuttle standalone jobs. 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:41 AM and 3:57 AM PDT on July 31, 2026, some customers using Shuttle Standalone could sign in to their Shuttle Standalone accounts and view their dashboards, but could not view job details, change job settings, or create new standalone jobs. The Shuttle native experience was not affected. After we restored service, we confirmed that customers could access existing jobs and create new ones. # Analysis A misconfiguration in Shuttle resulted in depleted resources that accessed job history. This caused Shuttle pages that load job history to time out. We restored access by restarting the affected services at 3:57 AM PDT. Job management returned to normal, with no recurrence. This briefly blocked the standalone experience for affected customers, even though sign-in and the Shuttle native experience continued to work. # Corrective Actions Box has initiated the following corrective actions: * Updating the capacity allocation to avoid the recurrence of this issue * Adding monitoring to better preempt the issue from occurring 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

Updates as published by Box (original).