Box

Affected: Content API, Uploads/Downloads, Box Sign, Box Sign

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-20 02:19 UTC

   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. investigating 2026-10-20 02:33 UTC

   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. identified 2026-10-20 03:11 UTC

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

4. resolved 2026-10-20 03:47 UTC

   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.

Excerpts are shortened. Read the full incident on Box's status page.

Affected: Box Drive

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-15 08:30 UTC

   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. identified 2026-10-15 09:10 UTC

   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. identified 2026-10-15 10:10 UTC

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

4. identified 2026-10-15 11:15 UTC

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

5. monitoring 2026-10-15 12:13 UTC

   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.

6. resolved 2026-10-15 12:41 UTC

   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.

Excerpts are shortened. Read the full incident on Box's status page.

Affected: Content API, Login/SSO, Web Application, Content Preview, Uploads/Downloads, Authentication (OAuth 2.0 / JWT), Search, Uploads/Downloads, Webhooks, Box Embed Widget, Box Sign, Box Canvas, Workflows and Automations, Box Shuttle, Accessible Site (a.box.com), Box AI, Box Sign, Box Doc Gen, Box Apps, Box Extract, Events API, Box AI, Files Page

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-08 09:27 UTC

   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. resolved 2026-10-08 09:33 UTC

   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.

Excerpts are shortened. Read the full incident on Box's status page.

Affected: Events API, Enterprise Reports

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-08 01:48 UTC

   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....

2. identified 2026-10-08 02:21 UTC

   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...

3. identified 2026-10-08 02:53 UTC

   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...

4. identified 2026-10-08 03:19 UTC

   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...

5. monitoring 2026-10-08 03:38 UTC

   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...

6. resolved 2026-10-08 03:54 UTC

   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...

Excerpts are shortened. Read the full incident on Box's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-10-01 10:00 UTC

   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.

Excerpts are shortened. Read the full incident on Box's status page.

Affected: Enterprise Reports

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-09-30 18:08 UTC

   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. monitoring 2026-09-30 18:53 UTC

   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. monitoring 2026-09-30 19:51 UTC

   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. monitoring 2026-09-30 20:47 UTC

   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.

5. monitoring 2026-09-30 21:23 UTC

   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.

6. monitoring 2026-09-30 22:17 UTC

   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.

7. monitoring 2026-10-01 00:02 UTC

   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.

8. monitoring 2026-10-01 04:03 UTC

   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.

9. monitoring 2026-10-01 07:11 UTC

   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.

10. monitoring 2026-10-01 09:11 UTC

    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.

11. monitoring 2026-10-01 11:13 UTC

    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.

12. monitoring 2026-10-01 13:26 UTC

    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.

13. identified 2026-10-01 14:44 UTC

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

14. identified 2026-10-01 21:28 UTC

    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.

15. monitoring 2026-10-02 10:03 UTC

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

16. identified 2026-10-02 16:58 UTC

    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...

17. resolved 2026-10-05 14:09 UTC

    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.

Excerpts are shortened. Read the full incident on Box's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-09-29 15:30 UTC

   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...

Excerpts are shortened. Read the full incident on Box's status page.

Affected: Web Application

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-28 10:04 UTC

   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. resolved 2026-09-28 10:31 UTC

   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.

Excerpts are shortened. Read the full incident on Box's status page.

Affected: Enterprise Reports

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-09-04 02:10 UTC

   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. identified 2026-09-04 02:16 UTC

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

3. resolved 2026-09-04 03:03 UTC

   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. postmortem 2026-09-15 21:26 UTC

   _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,...

Excerpts are shortened. Read the full incident on Box's status page.

Affected: Box Hubs

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-08-28 08:20 UTC

   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. identified 2026-08-28 09:44 UTC

   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. resolved 2026-08-28 10:00 UTC

   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. postmortem 2026-09-06 22:49 UTC

   _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...

Excerpts are shortened. Read the full incident on Box's status page.

Affected: Uploads/Downloads, Uploads/Downloads, Japan, Japan/Singapore, Singapore

Failure mode: Traffic surge or denial-of-service attack. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-08-25 06:53 UTC

   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. identified 2026-08-25 07:07 UTC

   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. monitoring 2026-08-25 07:13 UTC

   We are continuing to monitor for any additional impact.

4. resolved 2026-08-25 07:37 UTC

   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. postmortem 2026-09-16 23:01 UTC

   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...

Excerpts are shortened. Read the full incident on Box's status page.

Affected: Uploads/Downloads, Uploads/Downloads

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-08-24 21:21 UTC

   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. identified 2026-08-24 21:26 UTC

   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. identified 2026-08-24 21:29 UTC

   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. monitoring 2026-08-24 21:29 UTC

   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. monitoring 2026-08-24 21:29 UTC

   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. resolved 2026-08-24 22:03 UTC

   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. postmortem 2026-08-30 22:37 UTC

   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,...

Excerpts are shortened. Read the full incident on Box's status page.

Failure mode: Traffic surge or denial-of-service attack. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-08-24 17:30 UTC

   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...

2. postmortem 2026-08-30 22:39 UTC

   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...

Excerpts are shortened. Read the full incident on Box's status page.

Affected: Microsoft Office Integration, Box Edit / Tools

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-08-20 00:31 UTC

   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. investigating 2026-08-20 00:44 UTC

   We are continuing to investigate this issue.

3. monitoring 2026-08-20 01:30 UTC

   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. resolved 2026-08-20 01:44 UTC

   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. postmortem 2026-08-24 00:53 UTC

   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...

Excerpts are shortened. Read the full incident on Box's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2026-08-19 22:00 UTC

   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...

2. postmortem 2026-08-21 18:09 UTC

   _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...

Excerpts are shortened. Read the full incident on Box's status page.

Affected: Files Page

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-19 11:38 UTC

   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. monitoring 2026-08-19 11:57 UTC

   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. resolved 2026-08-19 12:03 UTC

   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.

Excerpts are shortened. Read the full incident on Box's status page.

Affected: Content API, Login/SSO, Login/SSO, Uploads/Downloads, Authentication (OAuth 2.0 / JWT), Box Sign, Box AI

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-08-07 02:37 UTC

   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. investigating 2026-08-07 03:34 UTC

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

3. investigating 2026-08-07 04:06 UTC

   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. investigating 2026-08-07 05:02 UTC

   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. resolved 2026-08-07 05:16 UTC

   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. postmortem 2026-08-11 02:52 UTC

   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...

Excerpts are shortened. Read the full incident on Box's status page.

Affected: Uploads/Downloads, Uploads/Downloads

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: Network or DNS. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-04 20:23 UTC

   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. resolved 2026-08-04 20:44 UTC

   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. postmortem 2026-08-11 02:54 UTC

   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...

Excerpts are shortened. Read the full incident on Box's status page.

Affected: Box Shuttle

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-07-31 11:09 UTC

   Our team is investigating an issue with Box Shuttle Standalone. Users may have issues to access, configure or create new Shuttle job details. We will provide additional information as it becomes available.

2. monitoring 2026-07-31 11:16 UTC

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

3. resolved 2026-07-31 11:30 UTC

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

4. postmortem 2026-08-19 00:19 UTC

   We 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...

Excerpts are shortened. Read the full incident on Box's status page.

Affected: Uploads/Downloads

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-28 02:58 UTC

   We are investigating an ongoing issue affecting uploads. We will provide more information as soon as it is available.

2. identified 2026-07-28 03:08 UTC

   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. identified 2026-07-28 04:02 UTC

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

4. monitoring 2026-07-28 04:22 UTC

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

5. resolved 2026-07-28 04:57 UTC

   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.

6. postmortem 2026-08-04 04:09 UTC

   We 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...

Excerpts are shortened. Read the full incident on Box's status page.

Affected: Box Hubs

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-07-23 14:14 UTC

   We are investigating an ongoing issue affecting Box Hubs. We will provide more information as soon as it is available.

2. identified 2026-07-23 14:26 UTC

   Box continues remediation efforts to restore full functionality to Box Hubs. The underlying cause of the issue has been identified and efforts are underway to restore usability.

3. resolved 2026-07-23 14:30 UTC

   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. postmortem 2026-07-31 01:27 UTC

   We 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...

Excerpts are shortened. Read the full incident on Box's status page.

Affected: Sharing (Shared Links)

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-23 09:45 UTC

   We are investigating an ongoing issue affecting metadata updates using File Request. We will provide more information as soon as it is available. Users of this service may face delays in metadata updates while attempting to upload files using File Request.

2. identified 2026-07-23 11:05 UTC

   The underlying cause of the issue has been identified and efforts are underway to restore stability. Box continues remediation efforts to fully restore the metadata functionality of File Requests.

3. resolved 2026-07-23 11:42 UTC

   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. postmortem 2026-08-05 02:03 UTC

   We 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...

Excerpts are shortened. Read the full incident on Box's status page.

Affected: Microsoft Office Integration, Box Edit / Tools

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-07-16 21:30 UTC

   Box is investigating reports of a momentary issue with Box Edit / Microsoft Office Online. Affected services are subject to change as the investigation continues.

2. investigating 2026-07-16 21:30 UTC

   We are continuing to investigate this issue.

3. identified 2026-07-16 21:45 UTC

   Our team has identified the underlying cause of this issue and is working to take remediating steps.

4. monitoring 2026-07-16 21:47 UTC

   Our team has taken steps to remediate this issue and is seeing improvement for the Microsoft Online service and Box Edit.

5. resolved 2026-07-16 21:48 UTC

   After further monitoring, this incident is now considered resolved. Microsoft Office Online and Box Edit has been restored to full functionality.

6. postmortem 2026-07-31 01:21 UTC

   We 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...

Excerpts are shortened. Read the full incident on Box's status page.

Affected: Box Relay

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-07-15 04:14 UTC

   We are investigating an ongoing issue affecting Box Relay. We will provide additional information as it becomes available.

2. identified 2026-07-15 04:50 UTC

   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. identified 2026-07-15 06:00 UTC

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

4. monitoring 2026-07-15 06:32 UTC

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

5. resolved 2026-07-15 06:43 UTC

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

6. postmortem 2026-07-19 23:53 UTC

   We 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...

Excerpts are shortened. Read the full incident on Box's status page.

Affected: Search, Search, Box Sign

Failure mode: Traffic surge or denial-of-service attack. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-07 14:11 UTC

   Our team is investigating an issue with the Search service and Metadata queries. Users may see errors or slowness when attempting to search items in Box and / or using Metadata queries. We will provide additional information as it becomes available.

2. investigating 2026-07-07 14:42 UTC

   Our team is investigating an issue with the Search service, Box Sign Templates and Metadata queries. Users may see errors or slowness when attempting to search items in Box and / or using Metadata queries. We will provide additional information as it becomes available.

3. identified 2026-07-07 15:07 UTC

   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.

4. identified 2026-07-07 16:01 UTC

   Our team continues remediation efforts to restore full functionality to the Search service, Box Sign Templates and Metadata queries. We will provide additional updates as they become available.

5. monitoring 2026-07-07 16:12 UTC

   Our team has taken steps to remediate this issue and is seeing improvement for the Search service, Box Sign Templates and Metadata queries. We are continuing to monitor for any additional impact.

6. resolved 2026-07-07 16:19 UTC

   After further monitoring, this incident is now considered resolved. Search service, Box Sign Templates and Metadata queries have been restored to full functionality. If you continue to experience any issues, please contact Box Support at https://support.box.com.

7. postmortem 2026-07-31 21:02 UTC

   We 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...

Excerpts are shortened. Read the full incident on Box's status page.

Affected: Uploads/Downloads

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-25 19:29 UTC

   Our team is investigating an issue with Zip Downloads in the Box Web Application. Users may see errors or slowness when attempting to download folders from Box. We will provide additional information as it becomes available.

2. identified 2026-06-25 19:50 UTC

   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. identified 2026-06-25 19:59 UTC

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

4. monitoring 2026-06-25 20:29 UTC

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

5. resolved 2026-06-25 21:47 UTC

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

6. postmortem 2026-08-06 16:17 UTC

   Between 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...

Excerpts are shortened. Read the full incident on Box's status page.

Affected: Uploads/Downloads

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-24 12:18 UTC

   We are investigating an ongoing issue affecting uploads. We will provide more information as soon as it is available.

2. resolved 2026-06-24 12:33 UTC

   This incident is now considered resolved. Box uploads have been restored to full functionality. Please contact Box Support at https://support.box.com/ if you continue to experience any issues.

3. postmortem 2026-06-29 18:26 UTC

   We 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...

Excerpts are shortened. Read the full incident on Box's status page.

Affected: Workflows and Automations, Box Extract, Box Automate, Files Page

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-06-17 19:34 UTC

   Our team is investigating an issue with Box Webapp. Users may experience intermittent failures when loading the "All files" page and subfolders. We will provide additional information as it becomes available.

2. monitoring 2026-06-17 19:44 UTC

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

3. resolved 2026-06-17 20:28 UTC

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

4. postmortem 2026-06-18 20:26 UTC

   We 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...

Excerpts are shortened. Read the full incident on Box's status page.

Affected: Login/SSO, Authentication (OAuth 2.0 / JWT), Box Edit / Tools, Box Sign

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-06-11 00:34 UTC

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

2. monitoring 2026-06-11 01:41 UTC

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

3. resolved 2026-06-11 02:01 UTC

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

4. postmortem 2026-06-24 22:02 UTC

   We 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...

Excerpts are shortened. Read the full incident on Box's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2026-06-03 17:53 UTC

   From approximately 10:53 PM to 10:58 PM PDT, we observed an issue impacting Login, All Files, Notes, Uploads and Box API. Our systems automatically detected and corrected the underlying issue. There is no current impact and no further updates will be provided here. If you...

2. postmortem 2026-06-10 02:48 UTC

   We 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...

Excerpts are shortened. Read the full incident on Box's status page.

Affected: Box AI

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-06-01 00:58 UTC

   We are investigating an ongoing issue affecting Box AI. We will provide more information as soon as it is available.

2. identified 2026-06-01 01:16 UTC

   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. monitoring 2026-06-01 01:49 UTC

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

4. resolved 2026-06-01 02:25 UTC

   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. postmortem 2026-08-07 00:00 UTC

   _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...

Excerpts are shortened. Read the full incident on Box's status page.

Affected: Box Drive

Failure mode: A configuration change caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-05-22 08:46 UTC

   Our team is investigating an issue with Logins for Box Drive. Users attempting to log in to Box Drive may see errors or timeouts. Users encountering this issue can log in to the Box Web Application as a temporary workaround. We will provide additional information as it becomes...

2. monitoring 2026-05-22 09:15 UTC

   We have resolved the issue impacting Box Drive. We are continuing to monitor to ensure no further impact is observed

3. resolved 2026-05-22 09:18 UTC

   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. postmortem 2026-05-29 00:41 UTC

   We 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...

Excerpts are shortened. Read the full incident on Box's status page.

Failure mode: Traffic surge or denial-of-service attack. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-05-14 19:30 UTC

   Between 2:31am and 4:45pm PDT on May 14, 2026 we observed an issue impacting streaming Enterprise Events API . Our systems 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...

2. postmortem 2026-05-29 19:26 UTC

   We 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...

Excerpts are shortened. Read the full incident on Box's status page.

Affected: Box Shield (Auto Classification), Box Hubs, Box AI

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-05-07 01:20 UTC

   We are investigating an ongoing issue affecting browsing folders, collections, Box AI, Classifications, and Hubs. Customers may experience seeing errors when loading folders, collections, Box AI and Hubs. We will provide more information as soon as it is available.

2. identified 2026-05-07 01:52 UTC

   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. identified 2026-05-07 02:12 UTC

   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.

4. monitoring 2026-05-07 02:32 UTC

   Our team has taken steps to remediate this issue and is seeing improvement in Box Folder, Collections, Box AI, Hubs, and Classification. We are continuing to monitor for any additional impact.

5. resolved 2026-05-07 03:07 UTC

   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.

6. postmortem 2026-05-15 17:48 UTC

   We 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,...

Excerpts are shortened. Read the full incident on Box's status page.

Affected: Search

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-27 17:36 UTC

   Our team is investigating an issue with Search by metadata in the Box Web Application. Users may see search results not return. We will provide additional information as it becomes available.

2. investigating 2026-04-27 17:37 UTC

   We are continuing to investigate this issue.

3. investigating 2026-04-27 17:51 UTC

   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.

4. identified 2026-04-27 17:52 UTC

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

5. monitoring 2026-04-27 18:17 UTC

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

6. resolved 2026-04-27 19:11 UTC

   After 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.

Excerpts are shortened. Read the full incident on Box's status page.

Affected: Box Sign

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-04-03 04:04 UTC

   We are investigating an ongoing issue affecting Box Sign. We will provide more information as soon as it is available.

2. identified 2026-04-03 06:27 UTC

   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. resolved 2026-04-03 08:09 UTC

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

4. postmortem 2026-04-10 16:36 UTC

   On 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...

Excerpts are shortened. Read the full incident on Box's status page.

Affected: Admin Console & Functionality

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-25 11:44 UTC

   Our team is investigating an issue with the Admin Conssole dashboard. Users may experience slowness when attempting to access the Admin Console. We will provide additional information as it becomes available.

2. identified 2026-03-25 12:23 UTC

   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. monitoring 2026-03-25 13:36 UTC

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

4. resolved 2026-03-25 14:03 UTC

   After 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.

Excerpts are shortened. Read the full incident on Box's status page.

Affected: Box Shuttle

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-25 05:52 UTC

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

2. investigating 2026-03-25 06:32 UTC

   We are continuing to investigate this issue.

3. investigating 2026-03-25 07:01 UTC

   We are continuing to investigate this issue.

4. investigating 2026-03-25 07:31 UTC

   We are continuing to investigate this issue.

5. investigating 2026-03-25 07:59 UTC

   We are continuing to investigate this issue.

6. investigating 2026-03-25 08:33 UTC

   We are continuing to investigate this issue.

7. investigating 2026-03-25 09:07 UTC

   We are continuing to investigate this issue.

8. investigating 2026-03-25 09:40 UTC

   We are continuing to investigate this issue.

9. investigating 2026-03-25 10:11 UTC

   We are continuing to investigate this issue.

10. investigating 2026-03-25 10:44 UTC

    We are continuing to investigate this issue.

11. investigating 2026-03-25 11:21 UTC

    We are continuing to investigate this issue.

12. investigating 2026-03-25 12:07 UTC

    We are continuing to investigate this issue.

13. investigating 2026-03-25 12:43 UTC

    We are continuing to investigate this issue. We will provide additional updates as they become available.

14. investigating 2026-03-25 13:24 UTC

    We are continuing to investigate this issue. We will provide additional updates as they become available.

15. identified 2026-03-25 14:23 UTC

    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.

16. identified 2026-03-25 14:54 UTC

    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.

17. monitoring 2026-03-25 16:26 UTC

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

18. resolved 2026-03-25 17:00 UTC

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

19. postmortem 2026-07-29 22:33 UTC

    We recently addressed issues affecting Shuttle \(migration 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 03/24/2026 08:00 PM PDT and 03/25/2026 11:40 AM PDT on Mar...

Excerpts are shortened. Read the full incident on Box's status page.

Affected: Login/SSO, Preview, Sharing (Shared Links)

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-03-20 03:37 UTC

   We are investigating an ongoing issue affecting folder and file preview. Customers may experience a white or blank page when loading subfolders and accessing shared links. We will provide more information as soon as it is available.

2. identified 2026-03-20 03:59 UTC

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

3. investigating 2026-03-20 04:13 UTC

   We are continuing to investigate this issue.

4. investigating 2026-03-20 04:14 UTC

   We are continuing to investigate this issue.

5. monitoring 2026-03-20 04:44 UTC

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

6. resolved 2026-03-20 05:08 UTC

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

7. postmortem 2026-04-15 21:10 UTC

   We recently addressed issues affecting the “All Files” page 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 **3:00 PM PDT** and **9:34 PM PDT** on **March 19, 2026**,...

Excerpts are shortened. Read the full incident on Box's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-03-18 18:00 UTC

   Between 10:56am PST to 11:42am PST on March 18th, 2026 some users may have experienced difficulties previewing files. 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...

Excerpts are shortened. Read the full incident on Box's status page.

Affected: Login/SSO

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-03-10 00:30 UTC

   Our team is investigating reports of issues affecting Logins. Some customers may be experiencing errors or delays when attempting to log in to their Box accounts. We are working to identify the cause and will provide another update as soon as more information is available.

2. identified 2026-03-10 00:34 UTC

   We have identified the cause of the issue. Our team is now actively working on implementing a solution.

3. monitoring 2026-03-10 01:05 UTC

   A fix has been implemented to address the issue, and we are observing recovery. Customers should now be seeing improvement when attempting to log in. Our team will continue to monitor the service to ensure full stability is restored. We will provide another update once the...

4. monitoring 2026-03-10 01:13 UTC

   After a period of monitoring, we have confirmed that the issues affecting Login are now resolved. Service has been restored to full functionality. If you continue to experience any issues, please contact Box Support at https://support.box.com.

5. resolved 2026-03-10 01:14 UTC

   This incident has been resolved.

6. postmortem 2026-03-22 20:47 UTC

   We recently addressed an issue affecting logins to Box. We would like to take the opportunity to further explain this issue and the steps we have taken to keep it from happening in the future. Between **4:46 PM PDT** and **5:32 PM PDT** on **March 9, 2026**, some users may have...

Excerpts are shortened. Read the full incident on Box's status page.

Affected: FTP

Failure mode: A configuration change caused the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-27 20:02 UTC

   We are investigating an ongoing issue affecting FTP and SFTP logins. We will provide more information as soon as it is available.

2. investigating 2026-02-27 21:15 UTC

   Box continues to investigate reports of Captcha errors issues with FTP and SFTP logins.

3. monitoring 2026-02-27 21:58 UTC

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

4. monitoring 2026-02-27 22:58 UTC

   We are continuing to monitor for any further issues.

5. resolved 2026-02-27 23:51 UTC

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

6. postmortem 2026-03-05 22:43 UTC

   We recently addressed issues affecting Box FTP and SFTP services. 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. From February 25th, 2026 at 9:20 AM PST to February 27th at 4:10 PM PST,...

Excerpts are shortened. Read the full incident on Box's status page.

Affected: Uploads/Downloads

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-02-25 13:00 UTC

   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.

2. monitoring 2026-02-25 13:45 UTC

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

3. monitoring 2026-02-25 13:58 UTC

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

4. resolved 2026-02-25 14:16 UTC

   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. postmortem 2026-03-05 22:49 UTC

   _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 February 25, 2026 between 4:45 am PST and 5:40 am PST,...

Excerpts are shortened. Read the full incident on Box's status page.

Affected: Content API

Failure mode: Traffic surge or denial-of-service attack. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-02-24 23:32 UTC

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

2. identified 2026-02-24 23:32 UTC

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

3. identified 2026-02-24 23:42 UTC

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

4. monitoring 2026-02-25 00:02 UTC

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

5. resolved 2026-02-25 00:15 UTC

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

6. postmortem 2026-03-05 22:31 UTC

   _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 February 24, 2026 between 1:15 PM PST and 3:59 PM PST,...

Excerpts are shortened. Read the full incident on Box's status page.

Affected: Login/SSO, Uploads/Downloads, Box Sign

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2026-02-24 14:59 UTC

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

2. resolved 2026-02-24 16:07 UTC

   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.

3. postmortem 2026-03-10 17:54 UTC

   _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 February 24th, 2026 between 6:11 AM PST and 6:40 AM...

Excerpts are shortened. Read the full incident on Box's status page.

Affected: Login/SSO, Box.com Marketing Website

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Cloudflare.

1. investigating 2026-02-20 19:11 UTC

   Our team is investigating an issue with the marketing site box.com. Users may see errors when attempting to access Box.

2. identified 2026-02-20 19:14 UTC

   Our team has identified the underlying cause of this issue and is working to take remediating steps. The issue is due to an outage within Cloudflare at this time: https://www.cloudflarestatus.com/incidents/kwy3dt82bwbt As we work on remediation steps users can workaround this...

3. monitoring 2026-02-20 19:30 UTC

   Our team has taken steps to remediate this issue and is seeing improvement for our marketing page box.com. We are continuing to monitor for any additional impact.

4. resolved 2026-02-20 20:37 UTC

   This incident has now been resolved. Box will continue to monitor CloudFlare: https://www.cloudflarestatus.com/incidents/kwy3dt82bwbt

5. postmortem 2026-07-09 19:16 UTC

   We recently addressed issues affecting Box web access. 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:50 AM PST and 11:25 AM PST on February 20, 2026, some users may have...

Excerpts are shortened. Read the full incident on Box's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-01-09 06:00 UTC

   From approximately 9:52 PM to 10:00 PM US Pacific time, we observed an issue impacting Logins, Notes and API. 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.

Excerpts are shortened. Read the full incident on Box's status page.

Affected: Content API, Login/SSO, Web Application, Content Preview, Uploads/Downloads, Authentication (OAuth 2.0 / JWT), Search, Uploads/Downloads, Webhooks, Box Embed Widget, Box Sign, Box Canvas, Workflows and Automations, Box Shuttle, Box AI, Box Doc Gen, Box Apps

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-01-08 01:39 UTC

   We are investigating an ongoing issue affecting Login, Public API, Uploads, Downloads and Box Notes. We will provide more information as soon as it is available.

2. investigating 2026-01-08 01:58 UTC

   We are continuing to investigate this issue.

3. identified 2026-01-08 02:05 UTC

   The problem has been identified, and we are observing a trend towards recovery.

4. monitoring 2026-01-08 02:13 UTC

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

5. resolved 2026-01-08 02:37 UTC

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

6. postmortem 2026-01-08 23:59 UTC

   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 January 7th, 2026 between 5:10 PM and 5:50 PM PST, some customers experienced elevated...

Excerpts are shortened. Read the full incident on Box's status page.

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-01-02 13:30 UTC

   From approximately 05:30 AM to 02:30 PM US Pacific time, we observed an issue impacting Enterprise Reporting. Customers that attempted to run a report or had a scheduled report during this window may not have the report generated. Reports run during this window should be run...

2. postmortem 2026-01-14 12:40 UTC

   We recently addressed issues affecting the Enterprise Report feature. 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 January 2, 2026 between 5:30 AM and 2:33 PM PST, some users may...

Excerpts are shortened. Read the full incident on Box's status page.

Affected: Box Sign

Failure mode: A schema or data migration caused the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-12-18 00:21 UTC

   We are investigating an ongoing issue affecting Box Sign. We will provide more information as soon as it is available.

2. identified 2025-12-18 00:39 UTC

   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. resolved 2025-12-18 00:45 UTC

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

4. postmortem 2026-02-24 01:10 UTC

   We recently addressed issues affecting several features of 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 December 17, 2025, from 11:15 AM PST to 4:46 PM PST, some users may...

Excerpts are shortened. Read the full incident on Box's status page.