Updated 37 minutes ago
Claude Calendar and Gmail connector incidents resolved: impact windows and notice times

Claude Calendar and Gmail connector incidents resolved: impact windows and notice times

Anthropic marked two connector incidents resolved on October 28. Calendar list/search and Gmail search/read had different reported impact windows, which ended before their resolution notices were posted.

Two connector incidents, with different affected operations

Anthropic marked its Google Calendar connector incident resolved on October 28, following a separate Gmail connector resolution earlier that day. The notices identify claude.ai, Claude Code and Claude Cowork as the affected Claude surfaces.

The Calendar investigation concerned some requests to list or search calendar events. Gmail’s notice concerned searching and reading email. Those are useful distinctions for someone matching a failed task to the incident record: a calendar lookup and an email read depend on different connector operations, even when they are attempted from the same Claude product.

The notices do not say every request failed. They also do not establish a blanket failure of Claude models, the Claude API or all connectors. Gmail’s investigation specifically said the issue did not affect other connectors. Its scope should not be expanded to explain an unrelated failure.

Reported impact windows differ from resolution‑post times

The Calendar and Gmail resolution notices report the following impact endpoints. Every time in this table is UTC in 2026, at the minute precision displayed by Anthropic.

Connector Reported impact window (UTC, 2026) Resolved notice (UTC, 2026)
Google Calendar Oct 26 11:07 to Oct 28 18:52 Oct 28 20:05
Gmail Oct 27 23:00 to Oct 28 05:29 Oct 28 05:48

The Calendar notice reports impact starting October 26 at 11:07 UTC and ending October 28 at 18:52 UTC. Its resolved post appeared at 20:05 UTC on October 28. Gmail’s reported window began October 27 at 23:00 UTC and ended October 28 at 05:29 UTC; its resolved post appeared at 05:48 UTC that day.

These are two kinds of time, rather than competing estimates of one event. An impact endpoint describes when the provider says the affected period ended. A resolution‑post timestamp describes when that status update was published. Neither is an independently measured uptime result, and the intervals should not be added together as a single Claude outage.

The first notice is not necessarily the start of impact

The Calendar incident record first displayed an investigating update at 16:19 UTC on October 28, saying some list or search requests had been failing since October 26. The later resolution supplied the more precise impact endpoints. Gmail’s first displayed investigating update was at 03:59 UTC on October 28, after the start time subsequently given in its resolution.

That distinction matters when reading an incident timeline retrospectively. Counting from the first visible post would not reproduce the impact window the provider ultimately reported. Conversely, the reported window does not mean each user experienced a continuous failure throughout it. The notices provide no per‑account failure rate or request denominator.

Calendar updates mention work with an upstream provider. They do not establish a root cause or assign fault to Google. Neither record establishes data loss or supplies evidence that changing credentials or permissions was required.

A resolved record is a dated observation, not a health guarantee

In the [status‑page snapshot captured at 21:08 UTC on October 28](https://anthropic.statuspage.io/), both connector incidents were marked resolved. This report describes those completed incident records; it is not a live health monitor or a guarantee that a particular subsequent request will succeed. OpenTools previously covered [Anthropic’s October 27 Sonnet model incidents and their separate impact and notice clocks](https://opentools.ai/news/claude‑sonnet‑5‑5‑october‑27‑incidents‑impact‑notice‑times). Those model‑related records answer a different question from the Calendar and Gmail connector operations described here. Their timestamps should not be substituted into this connector timeline. Anthropic co‑founder and CEO Dario Amodei at TechCrunch Disrupt in San Francisco on September 20, 2023. “TechCrunch Disrupt 2023 - Day 2.” Photo: Kimberly White/Getty Images for TechCrunch, ©2023 Getty Images; [TechCrunch](https://www.flickr.com/photos/techcrunch/53201932199/), via [Wikimedia Commons](https://commons.wikimedia.org/wiki/File:Dario_Amodei_at_TechCrunch_Disrupt_2023_04.jpg). [CC BY 2.0](https://creativecommons.org/licenses/by/2.0/). Resized and cropped for display. Archive company‑leadership context; not the Calendar or Gmail incidents, their resolution or an engineering response.

Share this article

PostShare

Related News