Live

Elevated errors affecting the Google Calendar connector

The issue affecting the Google Calendar connector on claude.ai, Claude Code, and Claude Cowork has been resolved. Impact occurred from 04:07 PT / 11:07 UTC on October 26 to 11:52 PT / 18:52 UTC on October 28.

The latest update from Anthropic.

State

Resolved

Started

4 d ago

2026-10-28 16:19 UTC

Lasted

3 h 46 min

until 2026-10-28 20:05 UTC

Worst impact

Degraded

Timeline

4 updates
16:1917:1518:1219:0820:05
DegradedUpdate postedTimes in UTC

Investigating

3 h 28 min 92%

Monitoring

18 min 8%

Updates

Times in UTC

As posted by Anthropic

Resolved2026-10-28 20:05 UTC

The issue affecting the Google Calendar connector on claude.ai, Claude Code, and Claude Cowork has been resolved. Impact occurred from 04:07 PT / 11:07 UTC on October 26 to 11:52 PT / 18:52 UTC on October 28.

Monitoring2026-10-28 19:47 UTC

We are seeing recovery for errors affecting the Google Calendar connector, and error rates have returned to normal levels. We are continuing to monitor with our upstream provider.

Investigating2026-10-28 17:59 UTC

We are continuing to investigate elevated errors affecting the Google Calendar connector, and are working with our upstream provider. We will provide another update as soon as we have more information.

Investigating2026-10-28 16:19 UTC

We are investigating elevated errors affecting the Google Calendar connector. Some requests to list or search calendar events have been failing since October 26. We will provide an update as soon as possible.

Affected components

3
claude.aiClaude CodeClaude Cowork

Anthropic in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

50

Days with an incident

42

Median duration

1 h 8 min

This incident

3.3× the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

6 days
median 1 h 8 min
90 days agoToday

Other Anthropic incidents

All incidents

Follow Anthropic

Your coding agent knows when Anthropic is down, and tells you when a failure is theirs, not yours. You can also get Anthropic incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "anthropic" and tell me if Anthropic has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.cc/feed.xml?providers=anthropic
Slack
/feed subscribe https://outages.cc/feed.xml?providers=anthropic

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane