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: Uploads/Downloads
| Clock | Started | Running |
|---|---|---|
| Vendor clock when the vendor's open incident started | 88 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 Uploads”. 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 Uploads
major postmortem · started · resolved
7 updates
- investigating
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.
- identified
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.
- identified
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.
- monitoring
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.
- monitoring
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.
- resolved
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.
- postmortem
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, 2026, some users may have experienced difficulties while working in Box. During this time, users saw elevated error rates and reduced availability for uploads and other write-oriented actions. The issue occurred when a background user-cleanup process generated a sudden surge of database update activity that was amplified by an unbounded retry loop, which overloaded a database shard and exhausted connection capacity. We restored normal service by applying a rate limit to the cleanup traffic and stopping the offending cleanup workload. After traffic subsided, we removed the temporary limits once systems were stable
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.