- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Box Shuttle
- Down Index
- 25of 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 21m it lasted.
Anything that failed between 2026-07-31 11:09 UTC and 2026-07-31 11:30 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 4
- 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.
provider
- 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.
provider
- 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.
provider
- 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
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-ccc06c01d1
Is Box still down?
No, this incident was resolved 2026-07-31 11:30 UTC. For Box's live state, see https://down.guide/box.
How long did it last?
21m, from 2026-07-31 11:09 UTC to 2026-07-31 11:30 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.