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: Box Hubs
| Clock | Started | Running |
|---|---|---|
| Vendor clock when the vendor's open incident started | 84 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] Issues with Box Hubs Shared Links”. 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] Issues with Box Hubs Shared Links
major postmortem · started · resolved
4 updates
- investigating
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.
- identified
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.
- resolved
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.
- postmortem
We recently addressed issues affecting Hubs shared-link access in Box. We would like to take the opportunity to further explain these issues and the steps we have taken to keep them from happening in the future. Between August 27, 2026 at 11:18 PM PDT and August 28, 2026 at 2:48 AM PDT, some customers may have been unable to access Box Hubs using shared links. Other Box functionality, such as file and folder access, was not broadly affected. The issue occurred as a result of a recent code change in our ongoing effort to improve performance. We were able to resolve the issue by rolling back the change, and traffic returned to the previous behavior. # Analysis During a routine deployment, a configuration change intended exclusively for a pre-production environment was inadvertently applied to the production environment. The incident highlighted opportunities to strengthen deployment-
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.