https://approjects-vendor-status-watch.static.hf.space/v/box.htmlIncidents from Box's public status page, polled daily.Wed, 16 Sep 2026 12:28:20 +0000https://stspg.io/jpryz8xs8k4rbox:2026-09-03T19:10:06.402-07:00Fri, 04 Sep 2026 02:10:06 +0000_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 September 3, 2026 between 3:30 PM PDT and 7:12 PM PDT, some customers may have experienced missing, delayed, or inaccurate results within admin reporting features, including AI usage reports, in Box. Reports may have shown empty fields or data that did not reflect recent activity. The issue was caused by an outage in a third‑party data service that interrupted our data ingestion pipelines. Service availability was restored after the provider mitigated the problem. We are conducting a full engineering postmortem and our overview is subject to change with further analysihttps://stspg.io/st2mtmmbkz5cbox:2026-08-28T01:20:35.272-07:00Fri, 28 Aug 2026 08:20:35 +0000_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 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 so traffic returned to the previous behavior. We are conducting a full engineering postmortem, including a review of our deployment and configuration practices, to reduce the chancehttps://stspg.io/wyyrssnxky67box:2026-08-24T23:53:37.438-07:00Tue, 25 Aug 2026 06:53:37 +0000After further monitoring, this incident is now considered resolved. If you continue to experience any issues, please contact Box Support at https://support.box.com.https://stspg.io/jlrhnrtb4pnfbox:2026-08-24T14:21:52.400-07:00Mon, 24 Aug 2026 21:21:52 +0000We 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 offendhttps://stspg.io/ptjpkj753hy3box:2026-08-24T08:30:00.000-07:00Mon, 24 Aug 2026 15:30:00 +0000Between 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 applihttps://stspg.io/fjshz04251vsbox:2026-08-20T15:00:00.000-07:00Thu, 20 Aug 2026 22:00:00 +0000From 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.https://stspg.io/ybdp1knrj9qtbox:2026-08-19T17:31:23.000-07:00Thu, 20 Aug 2026 00:31:23 +0000We 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 performahttps://stspg.io/xslc1vyl1t88box:2026-08-19T15:00:00.000-07:00Wed, 19 Aug 2026 22:00:00 +0000_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 https://stspg.io/s2cb5jfx5gj3box:2026-08-19T04:38:19.903-07:00Wed, 19 Aug 2026 11:38:19 +0000After 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.https://stspg.io/ybhf2bqz17mfbox:2026-08-06T19:37:34.595-07:00Fri, 07 Aug 2026 02:37:34 +0000_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 Aug 6, 2026 between 6:42 PM PDT and 6:48 PM PDT and again between 7:27 PM to 7:33 PM PDT, some customers may have experienced intermittent failures affecting login, uploads/downloads, Notes, Box AI, and API access in Box. The disruptions were caused by a temporary resource exhaustion on our front‑end infrastructure. 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 conclusionhttps://stspg.io/ldkcrysdxtkdbox:2026-08-04T13:23:03.393-07:00Tue, 04 Aug 2026 20:23:03 +0000On 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 mhttps://stspg.io/vyz7j1dv5zqjbox:2026-07-31T04:09:34.000-07:00Fri, 31 Jul 2026 11:09:34 +0000We 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 restarhttps://stspg.io/p6nj49jzsjbsbox:2026-07-27T19:58:26.496-07:00Tue, 28 Jul 2026 02:58:26 +0000We recently addressed issues affecting file uploads and edits that create new file versions. We want to explain what happened and what we have done to prevent it from happening again. Between Jul 26, 2026 4:38 PM PDT and Jul 28, 2026 10:34 AM PDT, some users may have experienced delays or failures when uploading files or saving edits that create new file versions. The impact was limited to cases with a high number of concurrent uploads or edits on the same file. During this period, concurrent upload and edit traffic contended on shared database locks while creating new file versions. Under load, an overly conservative insert locking strategy acquired locks, creating a bottleneck in the database. The contention was amplified by background processes that post-process the uploaded file andhttps://stspg.io/vh4zgdtq8z4xbox:2026-07-23T07:14:47.603-07:00Thu, 23 Jul 2026 14:14:47 +0000We recently addressed an issue affecting Box Hubs. We’d like to take this opportunity to explain what happened and the steps we’ve taken to prevent it from happening again. Between 06:50 AM PDT to 07:26 AM PDT on July 23, 2026, some users may have experienced difficulties while working in Box. During this time, users attempting to access Box Hubs were unable to load the Hubs gallery and instead encountered a "Not Found" page. The issue occurred as a result of a recent frontend dependency update, which introduced a package version conflict that prevented the Hubs module from loading correctly. We were able to resolve the issue by rolling back the frontend application to the previous stable version, which fully restored access to Box Hubs. In addition, we are working to improve our automathttps://stspg.io/tt41whfy05bcbox:2026-07-23T02:45:51.100-07:00Thu, 23 Jul 2026 09:45:51 +0000We recently addressed an issue affecting metadata updates using File Request in Box. We would like to take the opportunity to further explain the issue and the steps we have taken to keep similar issues from happening in the future. Between 09:10 AM PDT on July 22, 2026 and 03:36 PM PDT on July 23, 2026, some users may have experienced delays in metadata updates while uploading files using File Request. The issue occurred when repeated attempts to process a subset of unsuccessful metadata events reduced available processing capacity and delayed other events. We restored the metadata functionality of File Requests by limiting unnecessary retries, reducing processing idle time, and improving the handling of failures that would not succeed when retried. In addition, we are improving retry behttps://stspg.io/kltqnqmpzbh9box:2026-07-16T14:30:27.000-07:00Thu, 16 Jul 2026 21:30:27 +0000We recently addressed issues affecting Open With integrations within Box. We would like to take this opportunity to further explain these issues and the steps we have taken to prevent them from reoccurring. Between 1:00 PM PDT and 2:40 PM PDT on July 16, 2026, some customers may have been unable to open or edit files using any Open With integration in the Box web application. During this period, affected files may have appeared unavailable or grayed out, and users may have encountered permission-related errors when launching an integration. Microsoft Office workflows, including Office Online in the browser and desktop editing through Box Edit, were among those impacted. The issue occurred after a recent service update unintentionally changed how integration workflows were handled, causinhttps://stspg.io/dskd65lxnyh9box:2026-07-14T21:14:09.557-07:00Wed, 15 Jul 2026 04:14:09 +0000We recently addressed issues affecting Box Relay. 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 1:10 AM and 11:33 PM PT on July 14, 2026, some users may have experienced difficulties while working in Box. During this time, some users may have experienced degradation of Box Relay workflows that include a task outcome. The issue occurred as a result of a recent code change intended to improve how task assignments are handled in workflows. We were able to resolve the issue by reverting that change and restoring the previous behavior. In addition, we are improving our automated testing, monitoring, and deployment safeguards to prevent similar issues from occurring in the future.  ‌ **Analyhttps://stspg.io/q6y0bmwy00qqbox:2026-07-07T07:11:14.153-07:00Tue, 07 Jul 2026 14:11:14 +0000We recently addressed an issue that affected Box Search and related Query functionality, including the Public APIs and Box Apps features that rely on them. We would like to take the opportunity to explain what happened and the steps we have taken to prevent it from happening again. On July 7, 2026 between 06:22 AM and 08:53 AM PT, some customers may have experienced elevated latencies and intermittent errors when using the Box Search and Query functionality. Public APIs for these features, Box Apps, Web App Search, and other functionalities that depends on Search and Query APIs were also impacted. This incident was caused by a sudden surge in indexing traffic that overwhelmed services in one of our subsystems, before they could be scaled up or rate limiting could kick in. We were able to https://stspg.io/gr2zt4rcp4c5box:2026-06-25T12:29:04.063-07:00Thu, 25 Jun 2026 19:29:04 +0000Between 10:40 AM PDT and 12:33 PM PDT on June 25, 2026, some users may have experienced difficulties while working in Box. During this time, users routed through one particular US region may have seen failures or delays when attempting to download folders as ZIP files. The issue occurred after a recent network component update impacted a backend service in that region. We restored the feature availability by reverting the change. In addition, we are updating configuration and monitoring practices for such changes to reduce the likelihood of recurrence. # Analysis As part of our continuous and ongoing service improvement efforts, we recently rolled out a change to our internal compute platform. In one of our US regions, this change resulted in a resource problem within our service mesh lhttps://stspg.io/75fz2vnd0czqbox:2026-06-24T05:18:40.053-07:00Wed, 24 Jun 2026 12:18:40 +0000We recently addressed issues affecting file uploads 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 4:47 AM PDT and 5:28 AM PDT on June 24, 2026, some users may have experienced difficulties uploading larger files to Box. During this time, chunked uploads of large files may have failed or timed out, while smaller file uploads continued to work normally. The issue occurred when an internal system that temporarily tracks the progress of large, chunked uploads experienced an unexpected failover and lost the in-progress upload information it was holding. The issue resolved once those connections were reset. In addition, we are hardening how our upload service detects and recovers from https://stspg.io/xq7198krgbqdbox:2026-06-17T12:34:08.934-07:00Wed, 17 Jun 2026 19:34:08 +0000We recently addressed issues affecting the Box API, All Files, and Box AI. We would like to take the opportunity to further explain what happened and the steps we have taken to prevent reoccurrence. Between 12:06 PM PDT and 12:39 PM PDT on June 17, 2026, some users may have experienced difficulties while working in Box. During this time, some customers were unable to access content, browse folders, or complete uploads and other file operations, and error rates for affected features were elevated. **What Happened** The issue occurred after a recent rollout of a new traffic-routing change for the All Files experience reached full traffic volume. This routing change directed file-browsing requests through a newer service path that, under full production load, generated a significantly highhttps://stspg.io/w10c0j6bntt4box:2026-06-10T17:34:13.920-07:00Thu, 11 Jun 2026 00:34:13 +0000We recently addressed issues affecting Box Public API. 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 5:10 PM PDT and 6:40 PM PDT on June 10, 2026, some users may have experienced difficulties accessing or working within Box. During this period, there was a noticeable degradation affecting Public API request processing. This issue occurred as a result of a recent software change to our authentication infrastructure in our ongoing effort to improve performance and stability of Public API service. We were able to resolve the issue by scaling up the service, correcting its resource allocation, and rolling back the change. In addition, we are working to improve our resource provisioning to phttps://stspg.io/kj8bsh076nb0box:2026-06-03T10:30:00.000-07:00Wed, 03 Jun 2026 17:30:00 +0000We recently addressed issues affecting Authentication, File Access, Notes, Uploads, and Public API. 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 June 3, 2026 between 10:53 PM and 10:58 PM PDT, some customers may have experienced issues when attempting to sign in to Box and when accessing files, notes, uploads, and our public API. The issue was caused by a temporary fluctuation in a database shard due to elevated disk activity, which led to connection saturation and service errors for a subset of users. Service returned to normal by 10:58 PM PDT and monitoring remains in place to watch for recurrence. # Analysis As part of our routine system maintenance, we deployed standard software updathttps://stspg.io/xdf1rh8zpqpjbox:2026-05-31T17:58:40.111-07:00Mon, 01 Jun 2026 00:58:40 +0000_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 May 31, 2026 between 5:00pm PDT and 6:41pm PDT, some customers may have experienced errors or degraded performance when using Box AI features, including failures to generate AI responses or slower-than-expected behavior. The issue affected only AI-related capabilities and did not impact general file access. The disruption was caused by an outage with a third-party AI provider that led to failed AI requests. Service was restored once the provider issue was resolved and normal AI request processing resumed. We are reviewing our third-party dependencies and operational phttps://stspg.io/xgwnfbj03kd9box:2026-05-22T01:46:15.327-07:00Fri, 22 May 2026 08:46:15 +0000We recently addressed issues affecting Box Drive login and Single Sign-On \(SSO\) configuration. 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 10:56 PM PDT on May 21, 2026 and 2:07 AM PDT on May 22, 2026, some users may have experienced difficulties while working in Box. During this time, enterprise customers with Intune Mobile Application Management \(MAM\) enabled experienced SSO login failures when attempting to access Box Drive, and administrators were unable to view, update, or manage SSO configurations in the Admin Console. The issue occurred as a result of an unintended configuration change where our primary, active identity provider administration console region was inadvertentlyhttps://stspg.io/w68h5wm82kllbox:2026-05-14T12:30:00.000-07:00Thu, 14 May 2026 19:30:00 +0000We recently addressed issues affecting **Enterprise Events API**. 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 2:31am and 4:45pm PDT on May 14, 2026, some users may have experienced difficulties while working in Box. During this time, customers using the streaming Enterprise Events API experienced delivery delays of up to 6.5 hours. The issue occurred when an internal indexing service unexpectedly generated events at an unconstrained rate, which caused a significant concentrated spike in the total events volume. We were able to resolve the issue by redirecting those events from our streaming enterprise events pipeline for later processing. In addition, we will exclude events originathttps://stspg.io/3zrg1zp5fdvwbox:2026-05-06T18:20:15.000-07:00Thu, 07 May 2026 01:20:15 +0000We recently addressed issues affecting folder and collection browsing, and related APIs. 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 05:22 PM PDT and 07:04 PM PDT on May 6, 2026, some users may have experienced difficulties while working in Box. During this time, users reported failures and elevated errors when loading folders and collections, intermittent service errors, and degraded AI-related functionality. The issue was caused by runtime saturation in a backend API service that had been gradually approaching its capacity limits over several weeks. During peak traffic hours, multiple service instances simultaneously became unable to respond to internal health checks within the confhttps://stspg.io/h03kn85y4kf3box:2026-04-27T10:36:40.630-07:00Mon, 27 Apr 2026 17:36:40 +0000After further monitoring, this incident is now considered resolved. Search with metadata has been restored to full functionality. If you continue to experience any issues, please contact Box Support at https://support.box.com.https://stspg.io/48gkty34w2x0box:2026-04-02T21:04:31.122-07:00Fri, 03 Apr 2026 04:04:31 +0000On April 2, 2026 between 8:19 PM PDT and 11:56 PM PDT, some users may have experienced difficulties while working in Box. During this time, Box Sign users might have experienced errors while creating new signature requests, accessing existing signature requests, or attempting ~~been unable~~ to access the service. The issue occurred as a result of an erroneous change made by a third-party infrastructure provider. We were able to resolve the issue by escalating it to the provider. In addition, we are working to improve the reliability of the Box Sign service by enhancing our disaster recovery processes 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 ehttps://stspg.io/wb4z37ykflcqbox:2026-03-25T04:44:45.799-07:00Wed, 25 Mar 2026 11:44:45 +0000After further monitoring, this incident is now considered resolved. The Admin console service has been restored to full functionality. If you continue to experience any issues, please contact Box Support at https://support.box.com.