Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    Box outage history

    82 recorded Box incidents since March 2025, with official updates, affected components, duration and resolution information.

    Back to current status

    [Medium] Issue with multiple Box Services

    Started October 20, 2026 at 2:19 AM UTC · 1h 29m

    OutageMajor incident
    Affected components
    Box SignBox SignUploads/DownloadsContent API
    1. October 20, 2026 at 2:19 AM UTCinvestigating

      Our team is investigating an issue with the Public API and Box Sign. Users may see errors or timeouts when attempting to use the Public API or Box Sign. We will provide additional information as it becomes available.

    2. October 20, 2026 at 2:33 AM UTCinvestigating

      Our team is continuing to investigate an issue with the Public API, Box Sign, and Downloads. We will provide additional information as it becomes available.

    3. October 20, 2026 at 3:11 AM UTCidentified

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

    4. October 20, 2026 at 3:47 AM UTCresolved

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

    [Major] Issue with Box Drive

    Started October 15, 2026 at 8:30 AM UTC · 4h 11m

    OutageMajor incident
    Affected components
    Box SyncBox Drive
    1. October 15, 2026 at 8:30 AM UTCinvestigating

      We are investigating latency with syncing from the Box Web Application to Box Applications: Box Drive Some Users may see delayed updates synchronizing items from the Box Web App to Box Drive desktop clients.

    2. October 15, 2026 at 9:10 AM UTCidentified

      Our team has identified the underlying cause of this issue and is working to take remediating steps. We will provide additional updates as they become available.

    3. October 15, 2026 at 11:15 AM UTCidentified

      We are continuing to work on a fix for this issue.

    4. October 15, 2026 at 12:13 PM UTCmonitoring

      Our team has taken steps to remediate this issue and is seeing improvement for the Box Drive service. We are continuing to monitor for any additional impact.

    5. October 15, 2026 at 12:41 PM UTCresolved

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

    6. October 26, 2026 at 7:23 PM UTCpostmortem

      _Notice and disclaimer: Box is providing this preliminary information subject to further review and analysis. To the best of our knowledge, this is the current state and we may update as more information is confirmed._ ‌ Between October 14, 2026 at 3:00 PM PDT and October 15, 2026 at 5:10 PM PDT, some customers may have experienced delays in receiving User Events while using Box Drive. ‌ The issue occurred due to a workload increase impacting some backend services. We were able to resolve the issue by rate limiting the internal workload. In addition, we are looking at ways to detect and respond to workload changes more quickly, and ways to further isolate workloads on shared infrastructure in order to prevent similar issues from occurring in the future.  ‌ We are conducting a full engineering postmortem and our overview is subject to change with further analysis and findings. In the event our continuing investigation yields further substantive findings, we may publish additional analysis after the conclusion of the full engineering postmortem. ‌ 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

    [Critical] Issues with Multiple Box Services

    Started October 8, 2026 at 9:27 AM UTC · 5m

    OutageCritical incident
    Affected components
    Authentication (OAuth 2.0 / JWT)Web ApplicationBox SignBox AppsBox ExtractBox SignLogin/SSOEvents APIUploads/DownloadsSearchBox AIContent PreviewBox Embed WidgetWebhooksBox ShuttleBox Doc GenAccessible Site (a.box.com)Workflows and AutomationsBox AIUploads/DownloadsBox CanvasContent APIFiles Page
    1. October 8, 2026 at 9:27 AM UTCinvestigating

      We are investigating an ongoing issue affecting All Files page, API, uploads, downloads, Box Sign and Notes. We will provide more information as soon as it is available.

    2. October 8, 2026 at 9:33 AM UTCresolved

      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.

    [Medium] Issue with Enterprise Event Reports

    Started October 8, 2026 at 1:48 AM UTC · 2h 6m

    OutageMajor incident
    Affected components
    Enterprise ReportsEvents API
    1. October 8, 2026 at 1:48 AM UTCinvestigating

      Our team is investigating an issue affecting enterprise event data. Admins may see missing or outdated information in event-based reports and Insights in the Admin Console, as well as in results from the Enterprise Events API. Box AI users may also see inaccurate AI unit usage. We will provide additional information as it becomes available.

    2. October 8, 2026 at 2:21 AM UTCidentified

      Our team continues remediation efforts for enterprise event data. New events are now being processed, and we are working through the delayed data. Event-based reports and Insights in the Admin Console, results from the Enterprise Events API, and Box AI unit usage may continue to show missing or outdated information until processing is complete. We will provide additional updates as they become available.

    3. October 8, 2026 at 2:53 AM UTCidentified

      Our team continues to process the delayed enterprise event data. Event-based reports and Insights in the Admin Console, the Enterprise Events API, and Box AI unit usage may continue to show outdated information while this work is underway. We will provide additional updates as they become available.

    4. October 8, 2026 at 3:19 AM UTCidentified

      Our team has finished processing the delayed enterprise event data. Event-based reports and Insights in the Admin Console, and results from the Enterprise Events API, should now show up-to-date information. Box AI unit usage may continue to show outdated information while our team completes additional processing. We will provide additional updates as they become available.

    5. October 8, 2026 at 3:38 AM UTCmonitoring

      Our team has completed processing the delayed enterprise event data and is seeing improvement. Event-based reports and Insights in the Admin Console, results from the Enterprise Events API, and Box AI unit usage are now showing up-to-date information. We are continuing to monitor for any additional impact.

    6. October 8, 2026 at 3:54 AM UTCresolved

      After further monitoring, this incident is now considered resolved. Event-based reports and Insights in the Admin Console, results from the Enterprise Events API, and Box AI unit usage have been restored to full functionality and are showing up-to-date information. If you continue to experience any issues, please contact Support at https://support.box.com.

    [Medium] Issue with File Requests

    Started October 1, 2026 at 10:00 AM UTC · 0m

    OutageMajor incident
    1. October 2, 2026 at 3:43 AM UTCresolved

      From approximately 2:50 AM to 3:30 AM PDT on Oct 01, 2026, we observed an issue impacting File Requests. There is no current impact and no further updates will be provided here. If you continue to experience any issues, please contact Box Support at https://support.box.com.

    2. October 21, 2026 at 7:01 PM UTCpostmortem

      We recently addressed issues affecting File Requests in 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 October 1, 2026 between 2:50 AM and 3:30 AM PT, some customers may have experienced File Requests upload pages rendering as garbled text and unavailable File Request links, preventing users from accessing File Requests upload pages and File Request links. Service was restored at 3:30 AM PT. # Analysis The issue was caused by a change to how File Requests upload pages are packaged for production, which made them incompatible with the service that delivers them. As a result, the pages displayed as garbled text. Rolling back to the previous release restored the pages, and we have since configured our deployments to keep using the compatible format. # Corrective Actions Box has initiated the following corrective actions: * Correcting the deployment configuration for File Requests upload pages so they are always packaged in a format the delivering service can read. * Adding a mandatory pre-release check that automatically stops a rollout if File Requests and Forms pages fail validation in production. * Strengthening monitoring of File Requests upload pages so rendering issues are detected and addressed before customers are affected. ‌ 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

    [Medium] Issue with multiple reports

    Started September 30, 2026 at 6:08 PM UTC · 4d 20h

    OutageMajor incident
    Affected components
    Enterprise Reports
    1. September 30, 2026 at 6:08 PM UTCmonitoring

      We are monitoring an issue affecting User Engagement Reports and collaboration-related insights in the Admin Console. Some data may be missing or out of date. We have taken steps to restore data processing and are validating recovery.

    2. September 30, 2026 at 6:53 PM UTCmonitoring

      Data recovery is progressing. User Engagement Reports and collaboration-related insights may continue to contain missing or outdated data while processing catches up. We are continuing to monitor recovery.

    3. October 1, 2026 at 11:13 AM UTCmonitoring

      Data recovery continues to progress. User Engagement Reports and collaboration-related insights may continue to contain missing or outdated data while processing catches up. We are continuing to monitor recovery.

    4. October 1, 2026 at 1:26 PM UTCmonitoring

      Many report types (including User Engagement and Folders & Files reports) and collaboration-related insights may continue to contain missing or outdated data while processing catches up. We will provide our next update when the status changes.

    5. October 1, 2026 at 2:44 PM UTCidentified

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

    6. October 1, 2026 at 9:28 PM UTCidentified

      We continue working to restore current data across affected reports and collaboration-related insights. Some customers may see missing or outdated values in their reporting. Recovery work remains in progress.

    7. October 2, 2026 at 10:03 AM UTCmonitoring

      Recovery work remains in progress. We will provide our next update when the status changes.

    8. October 2, 2026 at 4:58 PM UTCidentified

      We continue working to restore current data across affected reports and Admin Console insights. Currently identified affected reports include Bandwidth Usage by Files and Folders, Classification, Collaborations, Disposition, Folders & Files, Legal Hold Content, Legal Hold Custodians, Outbound Collaboration, Retention, Shared Links, User Engagement, Folder Collaborations, and Folder Shared Links. Storage and Content Growth insights are also affected. These reports and insights may show missing or outdated values. User Engagement Reports may show values of zero.

    9. October 5, 2026 at 2:09 PM UTCresolved

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

    [Critical] Issues with All Files Page, Box Notes, API calls, logins and downloads

    Started September 29, 2026 at 2:15 PM UTC · 1h 14m

    OutageCritical incident
    1. September 29, 2026 at 2:15 PM UTCresolved

      From approximately 06.39 AM to 06:44 AM US Pacific time, we observed an issue impacting All Files Page, Box Notes, API calls, logins and downloads. Our systems automatically detected and corrected the underlying issue. There is no current impact and no further updates will be provided here. If you continue to experience any issues, please contact Box Support at https://support.box.com.

    [Medium] Issues with Box Notes

    Started September 28, 2026 at 10:04 AM UTC · 28m

    OutageMajor incident
    Affected components
    Web Application
    1. September 28, 2026 at 10:04 AM UTCinvestigating

      Our team is investigating an issue with Box Notes. Users may see errors or slowness when creating or updating Box Notes. We will provide additional information as it becomes available.

    2. September 28, 2026 at 10:31 AM UTCresolved

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

    3. October 21, 2026 at 7:02 PM UTCpostmortem

      We recently addressed issues affecting Box Notes in 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 28, 2026, beginning at 2:35 AM PDT, during a routine maintenance operation, some Box Notes users who had the app open in a background browser tab may have seen a brief "Reconnecting" message and a short delay when they returned to the tab. No data was lost, users who were actively editing were not prevented from working, and we received no widespread customer reports. The cause was a recent change to how Box Notes reconnects background tabs. We have since fixed the reconnection behavior and verified the fix. # Analysis The cause was a recent change to how Box Notes reconnects browser tabs that are open in the background. After an infrastructure switch during a release, those tabs did not reconnect on their own and instead reconnected when customers returned to them. The release and infrastructure switch completed successfully, and background tabs reconnected gradually as customers came back to them. Normal connection levels returned by 3:33 AM PDT. # Corrective Actions Box has initiated the following corrective actions: * Fixing the reconnection behavior for background tabs so they reconnect automatically after an infrastructure switch, and verifying the fix with a controlled switch. * Adding an automated test that reproduces this scenario, to catch any regression before release in the future. * Scheduling a further review of reconnection logic with the team, paired with metrics analysis. ‌ 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

    [Minor] Issue with Admin Reporting

    Started September 4, 2026 at 2:10 AM UTC · 53m

    IssuesMinor incident
    Affected components
    Enterprise Reports
    1. September 4, 2026 at 2:10 AM UTCinvestigating

      Our team is investigating an issue with Admin Reporting. Users may experience inconsistent data in reports generated after approximately 3:30 PM Pacific Time. We will provide additional information as it becomes available.

    2. September 4, 2026 at 2:16 AM UTCidentified

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

    3. September 4, 2026 at 3:03 AM UTCresolved

      This incident is now resolved and Box services have been restored to full functionality. If you generated reports during the impacted period, please re-run those reports. Please contact Box Support at https://support.box.com/ if you continue to experience any issues.

    4. September 15, 2026 at 9:26 PM UTCpostmortem

      We recently addressed issues affecting Admin Reports on AI usage reporting. 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:30 PM PDT and 7:59 PM PDT on September 3, 2026, ~~—~~ some users may have experienced difficulties while working in Box. During this time, AI Unit usage reports may have shown missing, empty, or otherwise incomplete AI-usage data and related insights. The issue occurred because a third‑party data ingestion service experienced elevated error rates that interrupted ingestion into our reporting pipeline. We were able to resolve the issue after the provider deployed a mitigation, and our teams re-ran previously failing ingestion jobs and rebuilt reporting tables to backfill missing data, restoring report availability. In addition, we will pursue follow-up with the provider and take steps to reduce the likelihood of recurrence. # Analysis Upon learning of the incident, coordination with our third‑party provider was required to restore capacity. # Corrective Actions Box has initiated the following corrective actions: * Obtaining the provider's formal root‑cause analysis. * Enhancing re-try mechanisms to recover from failures. * Enhancing alerting mechanisms for failed ingestion jobs error rates and observable signs of data‑quality degradation. 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

    [Medium] Issues with Box Hubs Shared Links

    Started August 28, 2026 at 8:20 AM UTC · 1h 40m

    OutageMajor incident
    Affected components
    Box Hubs
    1. August 28, 2026 at 8:20 AM UTCinvestigating

      We are investigating an ongoing issue affecting Box Hubs shared links. Users may face issues with accessing Box Hubs using Shared Links. We will provide more information as soon as it is available.

    2. August 28, 2026 at 9:44 AM UTCidentified

      Box continues remediation efforts to restore full functionality to Box Hubs access via Shared Link. The underlying cause of the issue has been identified and efforts are underway to restore stability.

    3. August 28, 2026 at 10:00 AM UTCresolved

      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.

    4. September 6, 2026 at 10:49 PM UTCpostmortem

      We recently addressed issues affecting Hubs shared-link access in 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. ‌ Between August 27, 2026 at 11:18 PM PDT and August 28, 2026 at 2:48 AM PDT, some customers may have been unable to access Box Hubs using shared links. Other Box functionality, such as file and folder access, was not broadly affected. ‌ The issue occurred as a result of a recent code change in our ongoing effort to improve performance. We were able to resolve the issue by rolling back the change, and traffic returned to the previous behavior. ‌ # Analysis During a routine deployment, a configuration change intended exclusively for a pre-production environment was inadvertently applied to the production environment. The incident highlighted opportunities to strengthen deployment-time configuration validation and pre-deployment checks designed to catch environment-specific configuration differences. # Corrective Actions Box has initiated the following corrective actions: * Improving deployment validation to ensure required environment-specific configuration blocks are present before release. * Adding end-to-end checks for shared-link resolution that run as part of pre-release and rollout verification. * Enhancing production monitoring and alerts for shared-link failures so regressions are detected and triaged faster. ‌ 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

    [Critical] Issue with Downloads

    Started August 25, 2026 at 6:53 AM UTC · 44m

    OutageCritical incident
    Affected components
    SingaporeUploads/DownloadsJapan/SingaporeJapanUploads/Downloads
    1. August 25, 2026 at 6:53 AM UTCinvestigating

      Our team is investigating an issue with Downloads. Users of Box Zones in Asian region may be unable to download files from Box. We will provide additional information as it becomes available.

    2. August 25, 2026 at 7:07 AM UTCidentified

      Our team has taken steps to remediate this issue and is seeing improvement for Downloads for users of Box Zones in the Asian region. We are continuing to monitor for any additional impact.

    3. August 25, 2026 at 7:13 AM UTCmonitoring

      We are continuing to monitor for any additional impact.

    4. August 25, 2026 at 7:37 AM UTCresolved

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

    5. September 16, 2026 at 11:01 PM UTCpostmortem

      We recently addressed issues affecting Downloads \(including ZIP downloads\) in 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. Between August 24, 2026 at 11:25 PM PDT and August 25, 2026 at 12:05 AM PDT, some Box Zones Japan users may have had a degraded download experience. The disruption was caused by an unusual traffic pattern that placed unexpected strain on capacity in the region. Once the impact was identified we restored service by directing download traffic to another region and adding capacity. Downloads returned to normal by 12:05 AM PDT. Once confirming that the issue had been addressed, we returned traffic to the original region. Of note, even during the period of temporary traffic redirection, all Box Zones customer content was stored in the correct Box Zones region. # Analysis This incident highlighted opportunities to make our systems more resilient to unusual traffic patterns, to strengthen regional capacity safeguards, and to further improve monitoring so that conditions like these are detected and addressed before affecting customers. # Corrective Actions Box has initiated the following corrective actions: * Improving safeguards so that unusual activity in one part of the system cannot affect unrelated services. * Strengthening regional capacity protections and automated recovery. * Enhancing monitoring and alerting so we detect and resolve similar conditions faster. 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

    [Medium] Issue with Uploads

    Started August 24, 2026 at 9:21 PM UTC · 41m

    OutageMajor incident
    Affected components
    Uploads/DownloadsUploads/Downloads
    1. August 24, 2026 at 9:21 PM UTCinvestigating

      Our team is investigating an issue with Uploads. Users may see errors or slowness when attempting to upload items to Box. We will provide additional information as it becomes available.

    2. August 24, 2026 at 9:26 PM UTCidentified

      Our team has identified the underlying cause of this issue and is working to take remediating steps. We will provide additional updates as they become available.

    3. August 24, 2026 at 9:29 PM UTCidentified

      Our team has taken steps to remediate this issue and is seeing improvement for the Upload service. We are continuing to monitor for any additional impact.

    4. August 24, 2026 at 9:29 PM UTCmonitoring

      Our team is investigating an issue with Uploads. Users may see errors or slowness when attempting to upload items to Box. We will provide additional information as it becomes available.

    5. August 24, 2026 at 9:29 PM UTCmonitoring

      Our team has taken steps to remediate this issue and is seeing improvement for the Upload service. We are continuing to monitor for any additional impact.

    6. August 24, 2026 at 10:03 PM UTCresolved

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

    7. August 30, 2026 at 10:37 PM UTCpostmortem

      We recently addressed issues affecting file uploads and other write operations within 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. Between 02:03 PM and 02:24 PM PDT on August 24, 2026, some users may have experienced difficulties while working in Box. During this time, users saw elevated error rates and reduced availability for uploads and other write-oriented actions. The issue occurred when a background user-cleanup process generated a sudden surge of database update activity that was amplified by an unbounded retry loop, which overloaded a database shard and exhausted connection capacity. We restored normal service by applying a rate limit to the cleanup traffic and stopping the offending cleanup workload. After traffic subsided, we removed the temporary limits once systems were stable. In addition, we are making changes to limit background cleanup traffic and improve retry behavior to reduce the chance of recurrence. # Analysis Following this incident, we are now improving how similar types of background jobs are managed and retried, and making adjustments to better prioritize customer-facing operations over these tasks. Specifically, during this issue, rapid retry cycles amplified service friction, highlighting areas where additional safeguards can further protect against similar issues occurring again in the future. We are also reviewing rollout and feature-flag practices to avoid accidental large-scale job generation. # Corrective Actions Box has initiated the following corrective actions: * Implementing bounded exponential-backoff retries for background cleanup jobs. * Enforcing throttling and monitoring on background cleanup traffic so it cannot overwhelm write-path resources. * Introducing priority-aware protections so low-priority background work is shed before it affects customer-facing operations. 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

    [Minor] Issue with Logins & Files Page

    Started August 24, 2026 at 3:30 PM UTC · 2h 0m

    IssuesMinor incident
    1. August 25, 2026 at 8:13 PM UTCresolved

      From approximately 10:28 AM to 10:35 AM US Pacific time, we observed an issue intermittently impacting some Logins and the Files page view. Our systems automatically detected and corrected the underlying issue. There is no current impact and no further updates will be provided here. If you continue to experience any issues, please contact Box Support at https://support.box.com.

    2. August 30, 2026 at 10:39 PM UTCpostmortem

      Between 3:44 PM and 4:27 PM PDT on August 19, 2026 and 10:28 AM and 11:21 AM PDT on August 24, 2026, some users may have experienced intermittent errors with some Box features, including Logins, Uploads, Downloads, and Box Sign. The issues occurred after a rapid surge of external Box client connections overwhelmed front-end capacity in the affected region, which caused an increase in server-side error rates and prevented some requests from reaching our back-end services. We restored service by working with our cloud provider and applying operational mitigations until front-end error rates returned to normal and user requests succeeded again. # Analysis This incident highlighted opportunities to improve our detection and correlation of frontend/load balancer health signals with our application telemetry and to strengthen joint monitoring and mitigation processes with our cloud provider during large-scale client connection events. It also underscored the importance of clearer detection thresholds and runbook steps for frontend degradations, so we can escalate and remediate faster without over or under communicating impact to customers. # Corrective Actions Box has initiated the following corrective actions: * Improving monitoring and observability for large-scale client connection events and working with our cloud provider on coordinated mitigation strategies. * Coordinating with our cloud provider to ensure connection rates are within expected thresholds. 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

    [Minor] Issues with Box Notes

    Started August 20, 2026 at 10:00 PM UTC · 11h 45m

    Pending
    1. August 21, 2026 at 11:08 AM UTCresolved

      From approximately 2:42 AM to 2:45 AM PDT (US Pacific Time), we observed an issue impacting Box Notes. Our systems automatically detected and corrected the underlying issue. There is no current impact and no further updates will be provided here. If you continue to experience any issues, please contact Box Support at https://support.box.com.

    [Medium] Issue with Microsoft Office Integration and Box Edit

    Started August 20, 2026 at 12:31 AM UTC · 1h 13m

    OutageMajor incident
    Affected components
    Box Edit / ToolsMicrosoft Office Integration
    1. August 20, 2026 at 12:31 AM UTCinvestigating

      Our team is investigating an issue with Microsoft Office Integration and Box Edit. Users may see errors or slowness when attempting to access Microsoft Office via Box, and using Box Edit. We will provide additional information as it becomes available.

    2. August 20, 2026 at 12:44 AM UTCinvestigating

      We are continuing to investigate this issue.

    3. August 20, 2026 at 1:30 AM UTCmonitoring

      Our team has taken steps to remediate this issue and is seeing improvement on Microsoft Office Integration and Box Edit service. We are continuing to monitor for any additional impact.

    4. August 20, 2026 at 1:44 AM UTCresolved

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

    5. August 24, 2026 at 12:53 AM UTCpostmortem

      We recently addressed issues affecting Box Edit, Microsoft Office Online, iWork, and other integrations in 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. ‌ Between 04:17 PM PDT and 6:30 PM PDT on August 19, 2026 some users may have experienced difficulties while working in Box. During this time, impacted users were unable to open files in Box Edit, Microsoft Office Online, iWork, and other integrations. Additionally, some users saw errors, timeouts, or slow responses while working in other areas of Box. ‌ The issue occurred after a deployment of a backend service that provides integration and platform functionality. The deployment introduced a regression that caused the service’s performance to degrade under peak load, which led to client timeouts and errors. We restored functionality by reverting the deployment to a previous version. We are taking steps to reduce recurrence by improving our pre-release validation and deployment safeguards, including validating the performance of the service under load, improving observability, and making defensive changes to the affected service. ‌ # Analysis ‌ This incident highlighted opportunities for improving our pre-release validation to test how a change behaves under peak traffic. In this situation, a change in a backend service which handles integration and platform functionality modified its scalability characteristics under load. The service operated normally during non-peak traffic but was not able to keep up with peak traffic demand. Under peak load, the service’s thread pool became saturated, causing requests to queue while waiting for an available worker and increasing latency. # Corrective Actions Box has initiated the following corrective actions: * Strengthening pre-release validation to include tests that better simulate peak traffic and scaling behavior for the affected service. * Improving observability so that scaling issues are more readily detected. * Implementing defensive changes in the affected service to reduce impact if a similar performance degradation were to 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

    [Medium] Issues with Multiple Box Services

    Started August 19, 2026 at 10:00 PM UTC · 0m

    OutageMajor incident
    1. August 20, 2026 at 1:15 AM UTCresolved

      Between 3:44pm PDT to 3:49pm PDT on August 19th 2026,we observed an issue impacting Login, All Files, Uploads, Downloads and Box API. No further impact has been observed and we are considering this issue to be resolved. If you are still experiencing any issues, please let us know at https://support.box.com.

    2. August 21, 2026 at 6:09 PM UTCpostmortem

      _Notice and disclaimer: Box is providing this preliminary information subject to further review and analysis. To the best of our knowledge, this is the current state and we may update as more information is confirmed._ On August 19, 2026 between 3:44pm PDT to 3:49pm PDT, some users may have experienced difficulties while working in Box. When attempting to access Box during this time, some users may have seen an error message. Preview, and Box Notes functionalities were impacted. This occurred because of an issue affecting Box’s critical third party cloud ingress services. We are conducting a full engineering postmortem in conjunction with our cloud provider, and our overview is subject to change with further analysis and findings. In the event our continuing investigation yields further substantive findings, we may publish additional analysis after the conclusion of the full engineering postmortem. 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

    [Minor] Issues with All Files Page

    Started August 19, 2026 at 11:38 AM UTC · 25m

    IssuesMinor incident
    Affected components
    Files Page
    1. August 19, 2026 at 11:38 AM UTCinvestigating

      Our team is investigating an issue on All Files page, in the WebApp. Users may see errors or slowness when attempting to access files or folders. We will provide additional information as it becomes available.

    2. August 19, 2026 at 11:57 AM UTCmonitoring

      Our team has taken steps to remediate this issue and is seeing improvement on the All Files page service. We are continuing to monitor for any additional impact.

    3. August 19, 2026 at 12:03 PM UTCresolved

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

    [Medium] Issues affecting multiple Box services

    Started August 7, 2026 at 2:37 AM UTC · 2h 39m

    OutageMajor incident
    Affected components
    Authentication (OAuth 2.0 / JWT)Box SignLogin/SSOBox AILogin/SSOUploads/DownloadsContent API
    1. August 7, 2026 at 2:37 AM UTCinvestigating

      Our team is investigating an issue affecting multiple Box services. Users may experience errors or failures when using multiple Box services. We will provide additional information as it becomes available.

    2. August 7, 2026 at 3:34 AM UTCinvestigating

      Our team is continuing to investigate the issue. We will provide additional information as it becomes available.

    3. August 7, 2026 at 4:06 AM UTCinvestigating

      Our team is continuing to investigate the underlying issue. There is no current ongoing impact. We will provide additional information as it becomes available.

    4. August 7, 2026 at 5:02 AM UTCinvestigating

      Our team is working with our cloud hosting provider to continue to investigate the issue. There is no current ongoing impact. We will provide additional information as it becomes available.

    5. August 7, 2026 at 5:16 AM UTCresolved

      Our team has taken steps to remediate this issue and the Box service has returned to full functionality. If you continue to experience any issues, please contact Box Support at https://support.box.com.

    6. August 11, 2026 at 2:52 AM UTCpostmortem

      We recently addressed issues affecting some customers at Box. We would like to take this opportunity to explain what happened and the steps we have taken to prevent them from occurring again. ‌ On August 6, 2026, between 6:42 PM PDT and 6:48 PM PDT, and again between 7:27 PM PDT and 7:33 PM PDT, some customers may have experienced intermittent disruptions affecting login, uploads/downloads, Notes, Box AI, and API access in Box. The disruptions were a symptom of a temporary capacity issue in the infrastructure that managed incoming traffic to Box. We restored service by increasing capacity and adjusting our systems to better handle traffic under load. # Analysis We recently introduced automatic capacity scaling to help Box respond more efficiently to changes in customer traffic. However, a configuration error caused our systems to release capacity too quickly, leading to repeated cycles of scaling up and scaling down. These rapid fluctuations disrupted active customer sessions and contributed to the issues described above. # Corrective Actions Box has initiated the following corrective actions: ‌ * Restoring and increasing front-end capacity, and updating our scaling configuration to prevent capacity from being reduced during periods of high traffic. * Updating our internal procedures to roll out capacity changes gradually, so that any impact is limited to a small portion of our infrastructure and broader customer impact is avoided. * Adding alerts for connection failures and capacity thresholds to our critical escalation processes, enabling our teams to respond to similar issues more quickly in the future. ‌ 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 this provides clarity and we would be happy to answer any remaining questions you may have regarding this matter. ‌ Sincerely, ‌ The Box Team

    [Critical] Issues with Multiple Box Services

    Started August 7, 2026 at 2:06 AM UTC · 0m

    OutageCritical incident
    1. August 7, 2026 at 2:06 AM UTCresolved

      From approximately 6:42 PM to 6:48 PM PDT, we observed an issue impacting multiple Box services. Users may have experienced errors or been unable to complete actions during that time. There is no current impact and no further updates will be provided here. If you continue to experience any issues, please contact Support at https://support.box.com.

    [Medium] Issues with Uploads and Downloads

    Started August 4, 2026 at 8:23 PM UTC · 22m

    OutageMajor incident
    Affected components
    Uploads/DownloadsUploads/Downloads
    1. August 4, 2026 at 8:23 PM UTCinvestigating

      Our team is investigating an issue with Uploads and Downloads in Box. Users may see errors or slowness when attempting to upload or download items. We will provide additional information as it becomes available.

    2. August 4, 2026 at 8:44 PM UTCresolved

      Our team has taken steps to remediate this issue and the uploads and downloads service has returned to full functionality. If you continue to experience any issues, please contact Box Support at https://support.box.com.

    3. August 11, 2026 at 2:54 AM UTCpostmortem

      On August 4, 2026 between 12:10 PM PDT and 1:20 PM PDT, some customers experienced failures and delays when uploading files to Box. The problem was caused by a routing issue on our frontend load balancers. We restored service by rerouting upload traffic and provisioning additional capacity. # Analysis A temporary network connectivity disruption impacted a small part of our load balancing fleet, causing a spike of TCP retransmit errors. Our engineering team mitigated the impact by redirecting traffic away from the affected region, which restored normal upload operations and resolved the errors. This incident highlighted opportunities to improve observable signals and alerting for TCP retransmit errors. # Corrective Actions Box has initiated the following corrective actions: * Improve monitoring and alerting for the isolated TCP retransmit issues. * Review and update operational runbooks for isolating problematic instances and for capacity management to shorten time to mitigation. ‌ 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