Skip to content
OutageDeck

Incident detail

[Medium] Issues with Box Shuttle Standalone

Resolved incidentMajor1 affected service

Timeline window

to

Get alerted the next time Box breaks

Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Set up free alertsHow Box alerts work

Timeline

Incident updates

Every update on the official status source, oldest to newest, exactly as it appeared there.

  1. 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. 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. 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. Resolved

    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

Keep exploring

More from Box

Neighboring incidents on Box's timeline and the rest of their record on OutageDeck.

All Box incidentsBox live status