Box Outage History

Box carried out a scheduled resiliency test maintenance from Nov 23, 2025 7:30 AM UTC to Nov 23, 2025 10:30 AM UTC. During this window, 16 components across Box Web Application, API, Desktop, Mobile, and Notes were placed into maintenance and then returned to normal. The affected areas included Box Web Application / Collaboration, Uploads/Downloads, Box Platform / API / Content API, Content Preview, Search, Uploads/Downloads, Desktop Applications / Box Sync, Desktop Applications / Box Drive, Mobile Applications / Preview, Mobile Applications / Search, Mobile Applications / Uploads/Downloads, Box Notes / Web Application, Box Web Application / Admin Console & Functionality, Box Web Application / Preview, Box Web Application / Sharing (Shared Links), and Box Web Application / Search.

Box performed a scheduled SSO maintenance window affecting the Box Web Application / Admin Console & Functionality from 2:00 AM UTC to 5:00 AM UTC. During this period, some users reported login issues; a login issue was first observed around 2:44 AM UTC. The maintenance was communicated via the status page, with updates issued at the start and end of the window. The maintenance lasted about 3 hours and the Box Web Application / Admin Console & Functionality returned to up at 5:00 AM UTC. The incident involved a single component and was tracked through two official status updates.

Box experienced a brief partial outage affecting multiple web applications, including Downloads, Box Sign, and Box Notes, with the Preview component also impacted during part of the incident. Users may have encountered difficulty accessing content, uploading or downloading files, and using Box Notes features. The issue began around 5:30 AM UTC when Box's status page flagged degraded service, spanning four components: Box Web Application / Uploads/Downloads, Box Web Application / Preview, Box Web Application / Box Sign, and Box Notes / Web Application.

Box users attempting to sign in with SMS-based MFA experienced delays and failures, affecting login/SSO across Box Web Application, Desktop Applications, and Mobile Applications. The incident began at Oct 20, 2025 6:00 PM UTC with the team investigating SMS MFA code delivery and verification, and was resolved about Oct 20, 2025 6:50 PM UTC after approximately 50 minutes. The provider issued two status updates during the outage, communicating the investigation and subsequent resolution.

Box Web Application / Login/SSO experienced an SMS delivery issue that prevented verification codes from arriving, causing login delays for users attempting to sign in. The SMS-based verification flow was affected from Oct 20, 2025 9:04 AM UTC to Oct 20, 2025 10:10 AM UTC, lasting about 1 hour and 6 minutes. Box's status page documented two updates: an initial investigation noting that users may not receive SMS when attempting to login, and a follow-up confirming the SMS service had recovered and the login flow returned to normal.

Box Web Application / Box Hubs and Box Web Application / Box AI experienced a brief degradation affecting Box AI features within Box Hubs. The incident lasted about 50 minutes, during which Box AI within Box Hubs was temporarily unavailable.

The provider logged two status updates during the incident, first noting an investigation and later confirming restoration of services. The outage began at 4:45 AM UTC and was resolved by 5:35 AM UTC.

An outage started with Admin Console report generation issues at 3:50 PM UTC before evolving into a broader Box services disruption. By 8:50 PM UTC a wide portion of Box Web Applications and Platform APIs were affected, with users seeing errors and degraded performance across report generation, access, and collaboration features. The incident lasted about 3 hours and 25 minutes, with recovery completed by 12:15 AM UTC as services returned to an up state. The Box status page issued 6 updates during the event, detailing investigations, underlying cause, and progress toward restoration. Affected components included more than 20 Box Web Application components and API services such as Collaboration, Enterprise Reports, Login/SSO, Box AI, Box Shield, Email Notifications, and Content APIs.

Box experienced a brief API outage affecting the Box Platform API and Content API, with callers seeing 502 errors or a generic Server Error. The incident began at Sep 18, 2025 8:50 AM UTC and lasted for about 2 hours and 25 minutes, ending at Sep 18, 2025 11:15 AM UTC. No user reports were recorded during the event, indicating the impact was primarily on API usage rather than end-user services.

Box issued two official status updates during the incident: the first acknowledged an active investigation and the second confirmed that services had been restored. The issue was confined to the Box Platform / API and Content API, with no broader regional impact noted.

Box experienced a partial outage impacting the All Files Page, API calls, user logins, and Box Notes. Users may have seen errors, slow responses, or failed actions across Box features, with Box Sign also affected during the incident. The issue impacted four components: Box Platform / API / Content API, Box Notes / Web Application, Box Web Application / Login/SSO, and Box Web Application / Box Sign. The outage began at Sep 15, 2025 9:55 AM UTC and was resolved by Sep 15, 2025 11:50 AM UTC, lasting approximately 1 hour 55 minutes.

On Sep 4, 2025 6:25 PM UTC, Box Web Application components began failing, causing login issues, inability to share or preview content, and missing email notifications. The disruption affected dozens of Box Web Application and Box Platform API components, including Admin Console & Functionality, Box Sign, Box Canvas, Email Notifications, and Governance features. Users across Box reported problems accessing services and links, and the issue appeared to be widespread across Box services. The outage lasted about 50 minutes and was resolved by Sep 4, 2025 7:15 PM UTC.

Box issued four official status updates during the incident. The updates documented the timeline: initial investigation at Sep 4, 2025 6:25 PM UTC, a follow-up at Sep 4, 2025 6:30 PM UTC and another at Sep 4, 2025 6:35 PM UTC indicating a fix was being implemented, and a recovery update at Sep 4, 2025 7:15 PM UTC when the majority of components returned to normal. A surge in user reports around Sep 4, 2025 6:00 PM UTC signaled broad impact across users and regions, with restoration progressing as communications updated across Web App and Platform APIs.