Box logged a brief fault on 29 September 2026 affecting the All Files Page, Box Notes, API calls, logins and downloads. The disruption was short and resolved on Box's own systems before most people would have noticed.
Started
14:15 UTC
Duration
Lasted ~5m
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 history shows a single incident on 29 September 2026, posted directly as resolved rather than opened and updated over time. The one update filed says the issue ran from approximately 06:39 AM to 06:44 AM US Pacific time, and lists five things it touched: the All Files Page, Box Notes, API calls, logins and downloads. That spread suggests a shared backend component rather than one isolated feature, since logins and file access rarely fail together unless something underneath both is affected. Box says its own systems automatically detected and corrected the underlying issue, and that no further updates would be posted. No cause is given beyond that, and no post-mortem has been published, so why the fault occurred is not on the record. There were no user reports filed during this window, which is consistent with a fix landing inside the five-minute Pacific time span before it spread widely. Box lists no affected components on its status page for this entry and the incident record shows a duration of 0 minutes, which reflects how it was logged rather than a claim that nothing happened. Over the last 90 days Box has logged 19 incidents with a median duration of 53 minutes, so this one sits well under what's typical for the service. Across all time, Box has recorded 256 incidents, averaging 3.3 per month, which gives useful context for how often short faults like this one surface and clear.
Learning
UptimeRobot's own 30 day checks on Box recorded 4 incidents with a median duration of 30.2 minutes, and this one does not line up with Box's own five minute window in a way that lets you draw a direct comparison, because the two are measuring different things. An external monitor watches whether a request to Box actually succeeds from outside, while Box's own status page reflects what its internal systems detected and corrected on their own infrastructure. Both can be accurate at once: a backend fault can resolve itself quickly on Box's side while still producing failed logins or stalled downloads for people hitting it during that window. This is the shape to watch for generally, a provider-side fault that clears before you'd think to check your own stack, leaving you with user complaints and no clear culprit in your own logs. Monitoring your own endpoints tells you your product responded, it doesn't tell you whether the provider underneath it was healthy at that moment. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.
