Box's File Requests feature had a problem on 1 October 2026 that Box itself logged as lasting from roughly 2:50 AM to 3:30 AM PDT. The incident record on Box's status page shows a duration of 17h 43m from first posting to resolution, longer than the 40 minute window Box describes for the actual impact.
Started
10:00 UTC
Duration
Lasted 17h 43m
Source
IsDown
Next time
Box is degraded. Is your product working?
An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.
50 monitors for your own websites. No card.
What happened?
Box's status page lists one incident on 1 October 2026, titled "[Medium] Issue with File Requests", first started at 10:00 UTC. There is a single update on record, posted at 03:43 UTC and marked resolved from the start. That update states the actual problem ran "from approximately 2:50 AM to 3:30 AM PDT", a window of about 40 minutes, and says there is no current impact. No components are listed as affected in Box's own breakdown for this incident. Box closes the update by directing anyone still experiencing issues to contact Box Support directly, which is standard language rather than a sign of ongoing trouble. There is only one filing for the whole day, so everything you can read about this incident comes from that single resolved update. No cause is given anywhere in the text, so the reason File Requests broke is not on the record. No user reports were filed during the window covered by this page. Over the past 90 days Box has logged 20 incidents with a median duration of 58 minutes, so a short File Requests issue like this one fits the normal pattern for Box rather than standing out. Across all time Box's status page shows 256 incidents, averaging 3.3 per month.
Learning
File Requests is a specific Box feature sitting on top of the broader storage and sharing platform, and a fault there does not necessarily touch the parts of Box your own uptime checks are likely watching, such as login or general file access. That is the general shape of this kind of failure: a narrow feature regresses for a short window while the rest of the service answers normally, so an external check hitting a different endpoint can stay green the whole time without being wrong. Box's own update gives a tighter window, roughly 40 minutes, than the 17h 43m duration recorded between the incident being opened and formally closed on the status page, which is a reminder that status page timestamps reflect administrative handling as much as the live fault. With only one update and no root cause published, you are left taking Box's word for both the scope and the timing. If your product depends on File Requests specifically, a green dashboard on your side during this window would have been accurate for your own infrastructure and still missed the fault sitting upstream. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.
