Operational Box status
box.com · Official status page (Statuspage-compatible JSON)
FROM ALL SOURCES
No sign of a widespread Box problem right now; every source we read is quiet.
confidence: medium Vendor: operational · users: normal · routing: no data.
- Vendor status page Operational · 1 open incident
- User reports 0 in 15 min vs ~0 typical
- Routing / BGP no ASN mapped, so no routing view
- News & network weather no recent mentions
- Providers it may run on (inferred) Google Cloud: no issues
- CISA KEV (context) no recent entries for this vendor
Regions mentioned: Enterprise Reports
| Clock | Started | Running |
|---|---|---|
| Vendor clock when the vendor's open incident started | 51 days | |
| Crowd clock when user reports began rising above normal | not seen | n/a |
| Network clock when routing anomaly data first flagged it | not seen | n/a |
| ORBIT clock when our checker first recorded the change | not seen | n/a |
Evidence
- Official page: Operational (“All Systems Operational”). evidence confidence: high
- Vendor stage: postmortem on “[Medium] Issue with multiple reports”. evidence confidence: high
- User reports are within normal range (0 in 15 min). evidence confidence: low
What we don't know: what is happening inside Box's own systems, how many users are actually affected (reports are self-selected and unverified), and anything from routing / bgp. Routing data shows reachability, not whether the app works.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Generated .
Cloudy_Day's take
Stage vs. health
The vendor's stage is “postmortem”. Stage tells you where they are in their process; health is what users experience. Right now vendor: operational · users: normal · routing: no data. Vendor status and outside signals roughly agree.
Who depends on whom
Box may run on Google Cloud (inferred). We don't map other services that depend on Box. Dependency chains are where single points of failure hide.
Identity & trust lens
Even without an identity system involved, outages push people toward workarounds: password resets, unofficial apps and “status” links in DMs. Each one is a trust decision. Use official channels.
For users
Nothing points to a broad problem. If it's broken for you, try “Is it just me?” and check your own network first.
For security teams
Treat this as an availability event unless an official source says otherwise. Check which of your systems sit on Box or its upstream providers, watch for outage-themed phishing aimed at your users, and log what you see with timestamps (all four clocks).
What to watch next
Any new vendor incident, a jump in user reports above baseline, or trouble at the providers Box may depend on.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Independent researcher; not affiliated with Box. No blame or attack claims without an official source. Generated .
INCIDENT REPLAY
[Medium] Issue with multiple reports
major postmortem · started · resolved
18 updates
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- identified
The issue has been identified and a fix is being implemented.
- 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.
- monitoring
Recovery work remains in progress. We will provide our next update when the status changes.
- 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.
- 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.
- 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
Community comments (0)
Comments are opinions of visitors, not statements by Cloudy_Day. Every comment is held for review before it appears. Links are removed, and personal data is redacted. Community guidelines.
No approved comments yet.
How to read this: official status comes from each provider's own public status page. User reports are unverified visitor reports. Things that happen at the same time are coincidence, not causation. Cloudy_Day is independent and not an official status source for any company listed.