Box AI was unavailable for some users for 3 hours and 21 minutes on 4 November 2026. Box's own status page attributes the fault to its AI feature, not to the wider platform, and confirms the fix came from its side.
Started
05:48 UTC
Duration
Lasted 3h 21m
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 opened an incident at 05:48 UTC titled "[Minor] Issue with Box AI", stating that some users may be unable to use Box AI. At 06:18 UTC it posted a brief update saying the investigation was continuing, with no new detail on scope or cause. The incident was marked resolved at 09:07 UTC, a total of 3 hours and 21 minutes after it started, with Box stating that services had been restored to full functionality "after further monitoring". No components are listed as affected in Box's own breakdown for this incident, and no user reports were logged in UptimeRobot's window for this day. Box labelled the incident "Minor" itself, but that label reflects Box's own grading, not a measurement of how long or how widely the AI feature was unreachable. Three updates in total were published across the 3 hour 21 minute window, which is thin for an incident of that length: an opening note, one holding message 30 minutes later, and the resolution almost three hours after that. Box's status page does not explain what caused the Box AI issue, only that it occurred and was later resolved. Over the past 90 days Box has logged 17 incidents with a median duration of 1 hour 32 minutes, meaning this one ran longer than half of its recent incidents. Over its full history Box has filed 261 incidents, averaging 3.3 per month.
Learning
UptimeRobot's own 30-day data for Box shows 6 incidents, all resolved, with a median duration of 2 hours 45 minutes, which lines up with the kind of outage seen here rather than contradicting it. Box AI sits on top of core file storage and sharing, so a fault confined to that feature can leave the rest of Box functioning normally while anyone relying on AI summarisation or search gets nothing. This is the shape to recognise: a named sub-feature breaks while the base product and any simple uptime check against Box's main endpoints would still read green, because the fault lives in the AI service layer, not in the layer most external checks probe. Box's own wording, "some users may be unable to use Box AI", is a Box-side admission of partial, feature-specific impact rather than a platform-wide failure, and that distinction matters when you are trying to work out whether your integration or Box itself is at fault. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.