Notion Agent requests started stopping before completion from 11:54 UTC, lasting 4h 0m. The fault sat on Notion's side, in the Agent feature itself, not in your own setup.
Started
11:54 UTC
Duration
Lasted 4h 0m
Source
IsDown
Next time
Notion 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?
Notion opened a single incident at 11:54 UTC titled "Some Notion Agent requests may stop before completion." The only update filed is the initial investigating note, posted at 11:54, saying Notion was looking into reports that some Agent requests stop before finishing and would share more once the scope was understood. No further update followed, and the incident's listed duration is 4h 0m, so the page closes without a resolution message explaining what was fixed or why. No components are listed as affected on Notion's own status breakdown for this incident. No user reports were filed during the window on this page, so the only account of what happened comes from Notion's single filing. Notion's status page does not say what caused requests to stop early, nor whether it affected all Agent users or a subset. Over the past 90 days Notion has logged 29 incidents with a median duration of 2 hours 28 minutes, so a four hour incident sits above that typical length. Across all time Notion averages 4.3 incidents a month, putting this one in line with a service that files outages fairly often. One filing with no closing update is thin, but it is what Notion has published, and the page reflects that rather than filling in gaps.
Learning
This incident sat specifically in the Agent request pipeline, a feature layer that runs on Notion's infrastructure once a request leaves your browser or app, so there is nothing on your end that would have shown this stalling. If you only watch your own product's endpoints, a failure like this, where Notion accepts a request and then drops it partway through, stays invisible to you until users start complaining. Your UptimeRobot checks against your own service can stay green the whole time, correctly, because your side kept working. The problem lived entirely in Notion's Agent feature, and only a check against Notion's own availability would have caught it when it started at 11:54. Notion's 90 day history shows this kind of incident is routine for them, not exceptional, with 29 filed in that span. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.