Skip to content

Incident detail

[Critical] Issue with Multiple Box Services

Resolved incidentCritical2 affected services

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

    Our team is investigating an issue with multiple Box Services. Users may see errors or slowness when attempting to access Box. 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 multiple Box Services. We are continuing to monitor for any additional impact.

  3. Monitoring

    We are continuing to monitor for any additional impact.

  4. Resolved

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

  5. Resolved

    We recently addressed issues affecting the Box 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 September 17, 2025 at 11:17 PM and September 18, 2025 at 2:21PM PDT, some users may have experienced difficulties while working in Box. During this time, when attempting to access Box, some users may have seen an unbranded error message which cleared after their browser established a new connection to Box. The issue occurred as a result of a change made by one of Box’s cloud infrastructure providers, and was resolved when the vendor reverted the change. In addition, Box is working closely with our vendor’s engineering team to minimize the likelihood of similar issues occurring in the future.

    ‌

    Analysis

    Box’s cloud provider experienced an issue that caused global load balancer services to incorrectly return HTTP 502 responses for a small percentage of user requests during the following three time periods:

    1. September 17, 2025 from 11:17 PM to 2025-09-18 1:30 AM Pacific

    2. September 18, 2025 from 8:50 AM to 2025-09-18 9:30 AM Pacific

    3. September 18, 2025 from 12:50 PM to 2025-09-18 2:21 PM Pacific

    These appear to have been linked to a load balancer software release. Upon discovery, the third-party vendor subsequently performed a rollback at 2:00 PM PT on September 18 to recover the issue. The provider has fixed the bug in their code and will include the fix in future builds.

    ‌

    Corrective Actions

    Box has initiated the following corrective actions:

    • Implementation of specific improvements to our alerting system for cloud provider load balancer errors
    • Improved observability to better enable correlation of cloud provider load balancer errors with other conditions
    • Added measures for these particular load balancer conditions as a new Service Level Indicator
    • Increased communication with the cloud provider to detect and resolve this class of issue more quickly

    ‌

    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.