Skip to content

Incident detail

[Outage] Issues with Box Services

Resolved incidentCritical

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.

Timeline

Incident updates

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

  1. Investigating

    We are investigating an ongoing issue affecting Box. Users may experience errors or long load times using Box services. We will provide more information as soon as it is available.

  2. Investigating

    We are continuing to investigate this issue.

  3. Investigating

    We are continuing to investigate this issue.

  4. Identified

    The issue has been identified and a fix is being implemented.

  5. Monitoring

    A fix has been implemented and we are monitoring the results.

  6. Monitoring

    Box services have recovered. We're continuing to monitor and ensure full restoration.

  7. Resolved

    After further monitoring, this incident is now considered resolved. All services have been restored to full functionality. If you continue to experience any issues, please contact Box Support at https://support.box.com.

  8. Resolved

    We recently addressed issues affecting Box. 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.

    On September 4, 2025 between 11:03 AM and 11:24 AM PDT, Box was unavailable to users. The outage occurred when maintenance performed on our caching tier triggered a latent bug. We were able to remediate the issue by manually restoring the caching tier to its pre-maintenance state. After the initial issue was resolved, between 11:24 AM and 01:16 PM PDT, a limited number of users may have continued to experience slowness when interacting with some Box features.

    ‌

    Analysis

    The issue was caused during a maintenance event on our caching tier to remove a dependent component. Although the change had been successfully tested in pre-production, a configuration difference between environments meant the error path was never exercised and the issue went undetected. When the dependent component was removed in production during the maintenance, client instances encountered errors and were unable to correctly handle incoming requests. Restoring the dependent component to its previous state allowed normal operations to resume. A limited number of client instances remained degraded and were recreated to recover full performance.

    ‌

    Corrective Actions

    Box has initiated the following corrective actions:

    • Improve error handling within our caching client instances to reduce the impact of caching tier failures.
    • Add observability for configuration differences between our testing and production environments.
    • Enhance deployment procedure to deploy caching tier changes more incrementally.
    • Shorten the time taken to restore the caching tier when issues occur.

    ‌

    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.