- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Enterprise Reports
- Down Index
- 33of 100
What to do
Check whether you use Box Enterprise Reports. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 4d 20h it lasted.
Anything that failed between 2026-09-30 18:08 UTC and 2026-10-05 14:09 UTC may need a replay.Subscribe to Box's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=box works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Root cause
One of these jobs experienced substantially increased latency due to a performance regression introduced within our cloud-managed data warehouse.Read the postmortem
Updates from Box 18
- monitoring
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.
provider
- monitoring
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.
provider
- monitoring
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.
provider
- monitoring
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.
provider
- monitoring
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.
provider
- monitoring
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.
provider
- monitoring
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.
provider
- monitoring
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.
provider
- monitoring
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.
provider
- monitoring
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.
provider
- monitoring
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.
provider
- monitoring
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.
provider
- identified
The issue has been identified and a fix is being implemented.
provider
- identified
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.
provider
- monitoring
Recovery work remains in progress. We will provide our next update when the status changes.
provider
- identified
We continue working to restore current data across affected reports and Admin Console insights. Currently identified affected reports include Bandwidth Usage by Files and Folders, Classification, Collaborations, Disposition, Folders & Files, Legal Hold Content, Legal Hold Custodians, Outbound Collaboration, Retention, Shared Links, User Engagement, Folder Collaborations, and Folder Shared Links. Storage and Content Growth insights are also affected. These reports and insights may show missing or outdated values. User Engagement Reports may show values of zero.
provider
- resolved
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.
provider
- postmortem
We recently addressed issues that affected reporting and Admin Console insights 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. From September 29, 2026 to October 3, 2026, customers may have experienced outdated or unavailable data across select reports and Admin Console insights. A performance regression in our cloud-managed data warehouse introduced timeouts in our analytics data pipeline, which impacted data freshness until the provider resolved the underlying issue. # Analysis Our analytics data pipeline is comprised of several scheduled jobs which maintain data freshness and accuracy. One of these jobs experienced substantially increased latency due to a performance regression introduced within our cloud-managed data warehouse. This led to the job exceeding timeout thresholds and failing to update the latest analytics data. Reporting and Admin Insights thereby became unable to serve this data, and temporarily displayed zeroed, delayed, or partially missing data in customer reports. On-call engineers manually mitigated these jobs by backfilling data in batches, while we simultaneously partnered with our cloud provider to identify a root cause. The issue was remediated when our cloud provider deployed a performance optimization addressing the underlying issue. Automated jobs resumed processing without timing out, completing a full backfill of all delayed analytics data and continually updating reporting data within typical freshness. # Corrective Actions Box has initiated the following corrective actions: * Designing and implementing a more scalable data model for our analytics pipeline to improve its overall performance and resilience to regressions in our cloud data warehouse. * Enhancing observability for data analytics jobs and query performance to improve detection and diagnosis of similar incidents in the future. * Partnering with our cloud provider to improve proactive detection and prevention of performance regressions. We are continuously working to improve Box and want to make sure we are delivering the best product and user experience we can. We hope we have provided some clarity here and we would be happy to answer any questions you may still have regarding this matter. Sincerely, The Box Team
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-d3ed332e3e
Is Box still down?
No, this incident was resolved 2026-10-05 14:09 UTC. For Box's live state, see https://down.guide/box.
How long did it last?
4d 20h, from 2026-09-30 18:08 UTC to 2026-10-05 14:09 UTC, by the times Box posted.
What was affected?
Box named Enterprise Reports.
What caused it?
Box wrote: "One of these jobs experienced substantially increased latency due to a performance regression introduced within our cloud-managed data warehouse." The postmortem: https://stspg.io/jttbktzfwt3s
Where does this come from?
Box's official status page, https://status.box.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.