Notion's Public API returned 500 errors for 16 minutes on 1 October 2026, starting at 12:18 UTC. The fault sat on Notion's side, in the API layer rather than anything you control.
Started
12:18 UTC
Duration
Lasted 16m
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.
Affected components: Notion API
What happened?
Notion logged one incident on this day, affecting the Notion API component only. It opened at 12:18 UTC with a single update: Notion said it was aware of an issue affecting Public API requests returning 500 errors and was investigating. No further update was filed after that, and the incident's listed duration is 16 minutes. There is no post-mortem and no explanation of what caused the 500 errors. No user reports were filed during the window, so there is no independent account of what this looked like from outside Notion's own status page. One filing from a vendor, with no resolution update attached, is thin evidence on its own, but a 16 minute window matching the stated duration is consistent with a short-lived server-side fault rather than a prolonged one. For context, Notion has logged 27 incidents in the past 90 days with a median duration of 1 hour 56 minutes, and 318 incidents all time at a rate of about 4.2 per month. Against that backdrop, a 16 minute API blip is on the short end of what Notion typically reports.
Learning
If you build on top of Notion's Public API, your own endpoint monitoring will not catch a fault like this, because the break happened inside Notion's infrastructure before any request reached a server you control. Over the same 30 days, UptimeRobot's own checks recorded 12 incidents against Notion, all resolved, with a median duration of 2 hours 37 minutes, a different shape from the 16 minute incident Notion itself logged for this day. Both readings can be correct at once: your integration can look healthy because your own code and servers are fine, while a specific call like the Public API returns 500s underneath it. The pattern to watch for is a spike in 500 responses from one specific API surface rather than a wider platform failure, since that's what Notion's component list and update describe here. Treat a single investigating update with no resolution as a limited claim, not a full account of impact. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.
