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
| Clock | Started | Running |
|---|---|---|
| Vendor clock when the vendor's open incident started | 49 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 File Requests”. 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 File Requests
major postmortem · started · resolved
2 updates
- resolved
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.
- postmortem
We recently addressed issues affecting File Requests 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. On October 1, 2026 between 2:50 AM and 3:30 AM PT, some customers may have experienced File Requests upload pages rendering as garbled text and unavailable File Request links, preventing users from accessing File Requests upload pages and File Request links. Service was restored at 3:30 AM PT. # Analysis The issue was caused by a change to how File Requests upload pages are packaged for production, which made them incompatible with the service that delivers them. As a result, the pages displayed as garbled text. Rolling back to the previous release restored the pages, and we have since configured our deployments to keep using the compatible format. # Corrective Actions Box has initiated th
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.