Box Notes broke for 30 minutes on 28 September 2026, with users seeing errors or slowness when creating or updating notes. The fault sat with Box's Web Application component, not with anything on your side.
Started
10:04 UTC
Duration
Lasted 30m
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.
Affected components: Web Application
What happened?
Box opened the incident at 10:04 UTC, titled "[Medium] Issues with Box Notes". The update said users might see errors or slowness when creating or updating Box Notes, and that more information would follow. Box's own component list named a single affected component, Web Application. No further updates were posted between the opening notice and the resolution. At 10:31 UTC, 27 minutes later, Box marked the incident resolved, stating that after further monitoring the Box Notes service had been restored to full functionality. That gives a total window of 30 minutes for the day. Box filed exactly two updates for this incident: the opening and the resolution, with nothing in between describing a cause. No root cause has been published. No user reports were filed in this window, so there is no independent account of what people actually experienced beyond Box's own description. This was the only incident logged against Box on 28 September 2026. Box's own severity label was "Medium", but that is Box's internal grading, not a measure of how disruptive the outage was for you. Over the last 90 days, Box has logged 19 incidents with a median duration of 53 minutes, so this one resolved faster than the typical recent incident.
Learning
This incident sat inside Box Notes, a specific feature of the Web Application component, rather than the authentication or storage layers that most uptime checks are built to watch. If your own monitoring pings Box's base URL or login endpoint, it can stay green through an outage like this because those endpoints were never the ones failing. Box's own status page is the only record of what happened here, and a two-update filing with no root cause means you are trusting their word for both the start and the end of the problem. UptimeRobot's 30 day data for Box shows 4 incidents with a median duration of 30.2 minutes, a pattern consistent with short, narrow failures that land on specific features rather than the whole product going dark. The general shape to watch for is a feature going soft, slow saves, errors on specific actions, while the service as a whole still answers normally. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.
