Claude's Connectors feature threw elevated errors for 4h 17m on 22 October, starting at 03:50 UTC, with claude.ai and Claude Cowork caught up in the same fault. Anthropic has confirmed the issue and its own fix, and it sits on their side of the line.
Started
03:50 UTC
Duration
Lasted 4h 17m
Source
IsDown
Next time
Anthropic 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: claude.ai
What happened?
Anthropic's status page shows one incident on 22 October, opened at 03:50 UTC as "Elevated errors affecting Connectors." The component listed is claude.ai, and Anthropic's updates also name Claude Cowork as affected by the same fault. The first update said only that Anthropic was investigating elevated errors affecting connectors, with no detail on cause or scope beyond that line. At 07:28 UTC, over three and a half hours later, Anthropic posted that a fix had been deployed and they were monitoring for recovery. The incident was marked resolved at 08:07 UTC, putting the total duration at 4 hours 17 minutes. That is three updates across the whole window: investigating, monitoring, resolved. No further detail was published on what caused the elevated errors, and Anthropic's status page does not say why connectors failed in the first place. There were no user reports filed in this window on record, so the only account of what happened comes from Anthropic itself. For context, Anthropic has logged 54 incidents in the past 90 days with a median duration of 1 hour 6 minutes, so this one ran well past that typical length. Across all time Anthropic has filed 838 incidents, averaging 29.9 a month, which is a high rate for a single provider.
Learning
Anthropic's own status page is the only record here, and it placed the fault specifically in Connectors, a feature layer that sits behind claude.ai's front door rather than at the network edge. A failure there can degrade functionality for people actively using connectors while leaving the base service reachable to a simple uptime check, which is why this kind of incident is easy for an external monitor to miss entirely even when it is real and lasts over four hours. Watching your own endpoints only tells you whether your product can reach Anthropic at all, not whether a specific feature like Connectors is throwing errors upstream. In UptimeRobot's own 30 day window, 8 incidents were recorded against this provider, all resolved, with a median duration of 1h 42m, which is the kind of pattern you only see by checking the provider's side directly rather than your own. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.
