Zendesk's Support component threw "Access temporarily restricted" errors for 1h 27m on 13 November 2026, starting at 18:46 UTC. The fault sat on Zendesk's side, not yours.
Started
18:46 UTC
Duration
Lasted 1h 27m
Source
IsDown
Next time
Zendesk 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: Support
What happened?
Zendesk logged a single incident on this date, titled "Access temporarily restricted errors", affecting the Support component. It began at 18:46 UTC and ran for 1h 27m before resolving. Zendesk did not publish any updates against this incident, so there is no record of what caused the restriction or which accounts it hit hardest. No user reports were filed during the window, which means whatever you may have seen at your desk that day went unlogged here. A single incident with zero updates still counts as a filing from Zendesk, but it carries less weight than a fully narrated one: you get a start time, a duration and a title, and nothing else. Over the past 90 days Zendesk has logged 11 incidents on Support-related issues, with a median duration of 1 hour 39 minutes, so this one ran shorter than typical. Across its full history, Zendesk has filed 511 incidents at a rate of roughly 7.7 per month, which puts this one inside a long pattern rather than an isolated event. There is no longest-incident figure separate from this one, since it was the only incident of the day. Nothing in Zendesk's own status history explains the specific trigger behind "Access temporarily restricted", and no post-mortem has been published.
Learning
Over the last 30 days, UptimeRobot's own checks against Zendesk recorded 7 incidents, all resolved, with a median duration of 5h 8m, noticeably longer than the 1h 27m Zendesk logged for this one. That gap is not a contradiction. Zendesk's status page reflects what its own engineers see and choose to file, while an external probe measures whether the service actually answers requests from outside its walls, and those two views can diverge by hours depending on how a fault spreads. An "access restricted" error is the kind of failure that can resolve for some accounts or regions well before it clears everywhere, so a short vendor-logged window and a longer externally measured one are both accurate descriptions of the same event seen from different sides. If your own uptime checks only watch your own endpoints, this kind of fault never shows up there at all, because the problem sits inside Zendesk's authentication or access layer, not in anything you control. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.