Back to the trend of the day: Microsoft's AI helper, email and chat went dark worldwide for over a day
Poly Rating · from the trend of the day

Is ChatGPT down? Work AIs in the Microsoft outage, Nov 2026

Microsoft 365 Copilot went dark with Outlook because it reads the same mail servers. ChatGPT's chat never logged an incident and lost only its window into Microsoft 365, for 29 hours 49 minutes.

  • No. 1: Google Gemini
  • 10 places

01Final list

The leading AIs each built their own list of ten independently. Here is one result that is easy to check: every place has a reason, a source, and the list of AIs that included it.

Order: from most to least AI agreement.

A bright badge means this AI put the entry on its list. A dim badge means it did not.

  1. 1

    Google Gemini

    Nothing to break: its work data sits in Google Workspace, not Exchange. Google's status board shows 0 incidents for 9–15 November.

    Included it: Claude, ChatGPT, Meta, Gemini, Nova, DeepSeek, Wenxin, Qwen. Did not include: MiMo, Kimi.

    In their lists: Claude: 3 · ChatGPT: 2 · Meta: 1 · Gemini: 1 · Nova: 3 · DeepSeek: 1 · Wenxin: 3 · Qwen: 1

    What each AI noted 8
    • Claudeplace 3

      Google's own mail and files are outside Microsoft's incident, but I found no Gemini data for these days.

    • ChatGPTplace 2

      A separate productivity ecosystem offered a practical escape route, although it could not magically restore inaccessible Outlook mail.

    • Metaplace 1

      Answered 72 of 72 outage questions during the outage itself — the only engine to name EX1550543 in 20 answers.

      Source ↗
    • Geminiplace 1

      Operating entirely outside Microsoft's infrastructure, its chat and workspace integration suffered zero minutes of downtime while Outlook and Teams were down.

    • Novaplace 3

      Core service up; Microsoft connector failed for 36 hours

    • DeepSeekplace 1

      The one major assistant with no Microsoft 365 dependency to break: its app and API stayed out of the outage path.

      Source ↗
    • Wenxinplace 3

      No reported core disruption, zero native dependency on Microsoft 365 infrastructure

    • Qwenplace 1

      Zero M365 blast radius because it lives entirely inside Google Workspace.

    8 AIs put it here
  2. 2

    ChatGPT

    Chat logged no incident during the window. Its Microsoft 365 connector failed for 29h 49m (18:29 UTC 12 Nov to 00:18 UTC 14 Nov), longer than Claude's 24h 37m.

    Included it: Claude, ChatGPT, Meta, Gemini, Nova, DeepSeek, Wenxin, Qwen. Did not include: MiMo, Kimi.

    In their lists: Claude: 1 · ChatGPT: 1 · Meta: 7 · Gemini: 7 · Nova: 5 · DeepSeek: 2 · Wenxin: 1 · Qwen: 6

    What each AI noted 8
    • Claudeplace 1

      Chat itself was not reported as down in what I found, and the connector claim rests on one unconfirmed source.

      Source ↗
    • ChatGPTplace 1

      The chat and the office connection were separate failure domains: Microsoft's documents could disappear without ChatGPT itself being declared down.

      Source ↗
    • Metaplace 7

      Chat kept answering while its Microsoft 365 connector was broken for 29 hours 49 minutes — talk, but no mail.

      Source ↗
    • Geminiplace 7

      Conversations remained fluid on OpenAI's own servers, but users querying their company mailboxes were blocked until OpenAI resolved its connector on 14 November.

    • Novaplace 5

      Chat functional; Microsoft connector degraded 48 hours

    • DeepSeekplace 2

      It could still talk all day; what it lost was the ability to open Outlook mail and files, and that link came back on 14 November.

    • Wenxinplace 1

      Core chat service fully operational through the entire Microsoft 365 global outage

    • Qwenplace 6

      The chatbot never blinked, but its eyes (the M365 connector) stayed shut until 14 November.

    8 AIs put it here
  3. 3

    Claude

    Its connector failed for 24h 37m, shorter than ChatGPT's. But Claude's own chat also went down twice on 13 Nov, for about 2h and 2h 29m.

    Included it: Claude, ChatGPT, Meta, Gemini, Nova, DeepSeek, Wenxin, Qwen. Did not include: MiMo, Kimi.

    In their lists: Claude: 2 · ChatGPT: 3 · Meta: 8 · Gemini: 6 · Nova: 4 · DeepSeek: 3 · Wenxin: 2 · Qwen: 5

    What each AI noted 8
    • Claudeplace 2

      Claude's chat had a login outage on 13 November, and its Microsoft 365 link also failed.

      Source ↗
    • ChatGPTplace 3

      Its Microsoft connection recovered after 24 hours 37 minutes, but Claude also suffered separate chat, API and coding disruptions on November 13.

      Source ↗
    • Metaplace 8

      Worse than ChatGPT: its connector failed for a day, then Claude itself had two more outages on 13 November.

      Source ↗
    • Geminiplace 6

      Claude's direct chat never blinked, and Anthropic marked its Microsoft connector patched on the afternoon of 13 November—nearly a full day before Microsoft resolved its own incident.

    • Novaplace 4

      Core operational; Microsoft connector down 48 hours

      Source ↗
    • DeepSeekplace 3

      Its Microsoft link was down for 24 hours and 37 minutes, but Anthropic restored it before Microsoft restored the suite.

      Source ↗
    • Wenxinplace 2

      Core LLM service never went down, only the M365 file/mail link broke for ~21 hours

    • Qwenplace 5

      Chat stayed up and Anthropic rebuilt its M365 connector faster than Microsoft fixed its own mail.

    8 AIs put it here
  4. 4

    GitHub Copilot

    Its work data is code repositories, not Exchange, and GitHub was not on Microsoft's incident list. It had only a model slowdown on 13 Nov, timed at 1h 14m by one tracker and 2h 22m by another.

    Included it: ChatGPT, Meta, Gemini, Nova, Kimi, DeepSeek, Wenxin, Qwen. Did not include: Claude, MiMo.

    In their lists: ChatGPT: 8 · Meta: 9 · Gemini: 9 · Nova: 1 · Kimi: 4 · DeepSeek: 6 · Wenxin: 5 · Qwen: 7

    What each AI noted 8
    • ChatGPTplace 8

      Coding work and office productivity are different dependencies: an Outlook outage does not establish that code completion stopped.

    • Metaplace 9

      Not a Microsoft 365 connector story — a coding assistant that still degraded for 1 hour 14 minutes on 13 November.

    • Geminiplace 9

      Code completions in the IDE held on for cached tokens, but repository indexing and PR summaries broke under Azure AD and Microsoft 365 authentication cascades.

    • Novaplace 1

      Unaffected by Microsoft outage — built on GitHub infrastructure

    • Kimiplace 4

      While Outlook burned, the copilot that reads Git repos instead of Exchange inboxes never lost its data source - Azure showed no active events and GitHub was never in MO1550821.

      Source ↗
    • DeepSeekplace 6

      It stayed inside the IDE, where code and repos do not need Exchange Online — a different work graph from Outlook and Teams.

      Source ↗
    • Wenxinplace 5

      Code editor assistant stayed up, separated from the broken Microsoft 365 enterprise stack

      Source ↗
    • Qwenplace 7

      Kept suggesting code even while the corporate mail server was down.

    8 AIs put it here
  5. 5

    Microsoft 365 Copilot

    The only assistant that lost both its chat and its work data. Copilot drew about 6,000 Downdetector reports at peak, against roughly 130,000–140,000 for Outlook.

    Included it: Claude, ChatGPT, Meta, Gemini, Nova, DeepSeek, Wenxin, Qwen. Did not include: MiMo, Kimi.

    In their lists: Claude: 4 · ChatGPT: 10 · Meta: 10 · Gemini: 10 · Nova: 6 · DeepSeek: 10 · Wenxin: 6 · Qwen: 10

    What each AI noted 8
    • Claudeplace 4

      It went down with the suite it reads from; Copilot reports peaked near 6,000 against about 140,000 for Outlook.

      Source ↗
    • ChatGPTplace 10

      The most deeply integrated assistant faced the central failure of the event: its workplace context depended on the same degraded services.

      Source ↗
    • Metaplace 10

      The only assistant that lost both its chat and its work: Copilot reports peaked near 6,000 while Outlook peaked near 140,000.

      Source ↗
    • Geminiplace 10

      Anchored directly inside Outlook and Teams, the flagship assistant vanished alongside the office suite, logging over 6,000 direct complaints while Outlook passed 140,000.

      Source ↗
    • Novaplace 6

      Fully down with Microsoft 365 services

    • DeepSeekplace 10

      The native assistant did not just lose your mail — it lost its own chat, and Microsoft was still reporting Copilot for Microsoft 365 affected on 13 November.

      Source ↗
    • Wenxinplace 6

      Fell over together with Outlook, Teams and Exchange in the global 74-country outage

      Source ↗
    • Qwenplace 10

      The AI went completely dark with the office suite, peaking at 6,000 complaints.

    8 AIs put it here
  6. 6

    Grok

    Grok has no Microsoft 365 link, so the outage did not touch it. Trackers disagree on 12 Nov: IncidentHub logs about 1 hour of Grok Bot errors, UptimeRankings logs nothing.

    Included it: ChatGPT, Meta, Nova, MiMo, Kimi, DeepSeek, Wenxin. Did not include: Claude, Gemini, Qwen.

    In their lists: ChatGPT: 5 · Meta: 6 · Nova: 7 · MiMo: 2 · Kimi: 5 · DeepSeek: 5 · Wenxin: 4

    What each AI noted 7
    • ChatGPTplace 5

      Its independent chat infrastructure was an alternative to Microsoft, but its own history contains complete model-service outages.

      Source ↗
    • Metaplace 6

      Chat survived Microsoft, but xAI's own Grok Bot had elevated errors for about an hour on 12 November.

      Source ↗
    • Novaplace 7

      Unaffected third-party AI with no Microsoft ties

    • MiMoplace 2

      Grok spent the blackout live-blogging the Microsoft meltdown on X while its own status page logged nothing at all.

      Source ↗
    • Kimiplace 5

      Fully conversational for all 30 hours - and equally unable to see your work mail before, during and after the outage, since it has no Microsoft 365 link at all.

      Source ↗
    • DeepSeekplace 5

      It had its own brief spike — 445 reports an hour on 12 November — but recovered within about an hour.

    • Wenxinplace 4

      Core inference stayed online, no deep integration with Microsoft 365 enterprise stack

    7 AIs put it here
  7. 7

    Perplexity

    Its Outlook, Teams and SharePoint connectors query Microsoft Graph live, yet its status page posted 0 incidents in November. That makes it the outage's quietest blind spot.

    Included it: ChatGPT, Meta, Gemini, Nova, MiMo, Kimi, DeepSeek. Did not include: Claude, Wenxin, Qwen.

    In their lists: ChatGPT: 4 · Meta: 2 · Gemini: 4 · Nova: 8 · MiMo: 8 · Kimi: 6 · DeepSeek: 4

    What each AI noted 7
    • ChatGPTplace 4

      Useful as an independent research route when enterprise mail and document search cannot be trusted.

    • Metaplace 2

      No Microsoft 365 connector to fail, and no incident in the last 7 days covering 12–14 November.

      Source ↗
    • Geminiplace 4

      Live web index search and enterprise collections answered queries continuously, unaffected by Microsoft's directory blackout.

    • Novaplace 8

      Web-focused; minimal Microsoft dependency

    • MiMoplace 8

      Its Outlook, Teams and SharePoint connectors query Microsoft Graph live — and its status page said nothing all week: the blackout's quietest blind spot.

    • Kimiplace 6

      No incident page and no connector apology - when Graph failed, a search-index assistant had nothing to lose.

    • DeepSeekplace 4

      Its Microsoft connector covers SharePoint and OneDrive, not Outlook or Teams — so the part of the work graph it could reach was narrower.

      Source ↗
    7 AIs put it here
  8. 8

    DeepSeek

    No Microsoft link to lose. One tracker logs a 22-minute web/chat slowdown on 14 Nov, another shows nothing on 12–14 Nov.

    Included it: ChatGPT, Meta, Nova, MiMo, DeepSeek. Did not include: Claude, Gemini, Kimi, Wenxin, Qwen.

    In their lists: ChatGPT: 6 · Meta: 4 · Nova: 9 · MiMo: 3 · DeepSeek: 9

    What each AI noted 5
    • ChatGPTplace 6

      A separate model ecosystem can preserve general reasoning work, but independent hosting alone does not prove continuous availability.

    • Metaplace 4

      Stayed up through the Microsoft outage, then logged a 22-minute Web/Chat degradation on 14 November.

      Source ↗
    • Novaplace 9

      Limited Microsoft integration; core stable

    • MiMoplace 3

      Its two November majors lasted under a minute each — and both landed outside the Microsoft week entirely.

      Source ↗
    • DeepSeekplace 9

      It had no Microsoft 365 link to break, but it also had seven status-page outages in October alone.

    5 AIs put it here
  9. 9

    Mistral Le Chat

    It came into the outage with no open incidents (its last one was 11 Nov) and has no Microsoft 365 connector. It was up, but it was never reading your Outlook.

    Included it: ChatGPT, Meta, Nova, DeepSeek. Did not include: Claude, Gemini, MiMo, Kimi, Wenxin, Qwen.

    In their lists: ChatGPT: 7 · Meta: 5 · Nova: 2 · DeepSeek: 7

    What each AI noted 4
    • ChatGPTplace 7

      Another independent conversational route, with too little comparable incident evidence to award it a higher place.

    • Metaplace 5

      Its last incident was 11 November — it entered the Microsoft outage clean, unlike the two connector assistants.

      Source ↗
    • Novaplace 2

      European alternative with independent infrastructure

    • DeepSeekplace 7

      A quieter work assistant with no Microsoft 365 connector in the blast radius, and 100% Completion API uptime from late April to late July.

    4 AIs put it here
  10. 10

    Meta AI

    No Microsoft dependency and no recorded incident, but Meta publishes no status feed. So "still up" here comes from reachability checks, not an auditable record.

    Included it: Meta, DeepSeek. Did not include: Claude, ChatGPT, Gemini, Nova, MiMo, Kimi, Wenxin, Qwen.

    In their lists: Meta: 3 · DeepSeek: 8

    What each AI noted 2
    • Metaplace 3

      The quiet one: no recorded incident in the last 30 days — but also no readable status page to prove it.

      Source ↗
    • DeepSeekplace 8

      It kept answering, but Meta publishes no incident feed, so “still up” is a reachability check rather than an auditable status history.

      Source ↗
    2 AIs put it here

More about the top three ↓

02More about the top three

The ranking is above. Here is more about the three places at the top: what they are, why they are here, and what is worth knowing.

Gemini has no Microsoft link to lose, so its measure is Google's incident count. ChatGPT and Claude are measured by how long their Microsoft 365 connector failed, and Claude's chat also had separate outages.

1Google Gemini

No. 1 — Google Gemini. On the lists of 8 of 10 AIs; median place there: 1.5. It keeps work data in Google Workspace, not Microsoft's mail servers, so the outage had nothing to break and nothing stopped working.

Gemini multimodal reasoning based on visual cues
Authors of the preprint: Gemini Team Google: Rohan Anil, Sebastian Borgeaud, Yonghui Wu, Jean-Baptiste Alayrac, Jiahui Y · CC BY 4.0 · Wikimedia Commons

Did you know

  • Google's help page says Gemini Apps activity older than 18 months is deleted by default. You can change that to 3 or 36 months, or turn auto-delete off.

What it is
Google's AI assistant, built into Google Workspace.
Its edge
Zero downtime, because it never depended on Microsoft's mail system.
Who it suits
Suits Google Workspace teams; it can't open Outlook mail.
  • Microsoft 365 link downtime0 incidents, 9–15 Nov

Wikipedia · Wikidata

Why it is here
  • Microsoft's outage was the problem, and Gemini's work data is not in Microsoft's mail system. Reuters-sourced reports say Downdetector logged over 130,000 Outlook reports, the scale of the failure Gemini users avoided.

Did you know
  • Deleting your Gemini activity may not remove everything. Reports say chats that human reviewers have looked at can be kept for up to three years, even after you delete your activity.

History
  • In February 2024, Google renamed Bard to Gemini and introduced a Gemini mobile app and a paid Advanced plan powered by Ultra 1.0. The rebrand tied the assistant’s name to Google’s family of AI models. — Google

Keep in mind
  • Even with activity turned off, Google keeps a short-term buffer of up to 72 hours for safety. Your data might also be reviewed by human annotators, though Google says it's anonymized.

What people say
  • Like a drop of dye mixed into a gallon of water, you can't reach in and pick out the dye molecules. — Ben Khalesi (Android Police)

Where to go further
  • Read Google's help page on Gemini Apps Activity to see the auto-delete choices. Then find the Activity setting in Gemini and pick the period you want.

Video: Gemini 4 Argon explained in 5min.. · Caleb Writes Code

Compare the top three ↓

2ChatGPT

No. 2 — ChatGPT. On the lists of 8 of 10 AIs; median place there: 3.5. Its chat never had an incident, but its Microsoft 365 link stayed broken longest, nearly 30 hours, so it loses points.

Did you know

  • A UBS analyst note estimated ChatGPT reached about 100 million monthly users in January 2023, roughly two months after launch. Sensor Tower data in the same coverage put TikTok at about nine months and Instagram at two and a half years.

What it is
OpenAI's chatbot, which can connect to Microsoft 365.
Its edge
Chat stayed up all through the outage, though its Microsoft link was down longest.
Who it suits
Suits general chat; not reliable for Outlook mail during an outage.
  • Microsoft 365 link downtime29h 49m connector outage

Wikipedia · Wikidata

Why it is here
  • ChatGPT's Microsoft 365 link depends on Microsoft's mail system, which failed first. That is the outage Downdetector put at over 130,000 Outlook reports, so ChatGPT's work link was exposed in a way Gemini's was not.

History
  • In December 2025, OpenAI declared a "code red" that put all company resources into improving ChatGPT and delayed its ads. In January 2026 it announced ads, clearly labeled as sponsored and kept apart from answers.

Keep in mind
  • ChatGPT can now check out purchases inside the chat. The Walrus says OpenAI and Stripe built the Agentic Commerce Protocol so people can buy directly in ChatGPT. Check each price and seller before you pay.

Claude, ChatGPT, Wenxin put it first. What they saw in it
  • Claude: Chat itself was not reported as down in what I found, and the connector claim rests on one unconfirmed source.

  • ChatGPT: The chat and the office connection were separate failure domains: Microsoft's documents could disappear without ChatGPT itself being declared down.

  • Wenxin: Core chat service fully operational through the entire Microsoft 365 global outage

Compare the top three ↓

3Claude

No. 3 — Claude. On the lists of 8 of 10 AIs; median place there: 3.5. Its Microsoft link came back sooner than ChatGPT's, but Claude's own chat also went down twice on 13 November.

Did you know

  • Claude can take in what a rival has learned about you. You export your saved memory from ChatGPT's settings, paste it into a new Claude chat, and ask Claude to store it. It's a similar picture of you, not an exact copy.

What it is
Anthropic's AI assistant, with project-based memory.
Its edge
Its Microsoft link recovered about five hours sooner than ChatGPT's.
Who it suits
Suits people who want memory by project; chat had two outages.
  • Microsoft 365 link downtime24h 37m connector outage

Wikipedia · Wikidata

Did you know
  • Claude's memory is split by project. Each project gets its own memory space, so notes from one project don't have to mix with another. You can also delete single memories or use incognito mode.

    Source ↗ ✓ confirmed by several AIs
History
  • In 2022, Anthropic trained its first Claude model but chose to use it for safety research instead of releasing it. Claude became available more broadly in March 2023, after a closed test with partners. — Anthropic

Keep in mind
  • A Reddit user says Claude Code saved a memory containing a patch instead of fixing the code, so they turned memory off for their whole account. It shows saved notes can be wrong.

What people say
  • I honestly don’t like the half-baked memory features because that’s what this is — u/Primary_Bee_43 (r/ClaudeAI, on Claude Code's new auto-memory)

Where to go further
  • Read Anthropic's help page on how Claude's memory works. Then open Settings, look at the memory list, and try editing or deleting one entry.

Compare the top three ↓

The top three side by side

Google GeminiChatGPTClaude
In the AIs' lists8 / 108 / 108 / 10
Microsoft 365 link downtime0 incidents, 9–15 Nov29h 49m connector outage24h 37m connector outage
Put first byMeta, Gemini, DeepSeek, QwenClaude, ChatGPT, Wenxin—

Places with the same number of AIs are ordered by their average place in the AIs' own lists.

03Worth knowing

What the AIs noticed while building the list.

"The AI answered" and "the AI could open your mail" split apart. ChatGPT's chat logged no incident while its Microsoft 365 link was down 29h 49m. Copilot could not even load its chat.

Noticed by:
Included it: ChatGPT, Meta, MiMo, Kimi, DeepSeek. Did not include: Claude, Gemini, Nova, Wenxin, Qwen.
Source ↗

Microsoft's outage length depends on which clock you use. It gives the end of impact as 16:10 UTC on 13 Nov, about 24 hours, but its final restoration notice came at 06:09 UTC on 14 Nov, about 38 hours.

Noticed by:
Included it: Meta, MiMo, Kimi. Did not include: Claude, ChatGPT, Gemini, Nova, DeepSeek, Wenxin, Qwen.
Source ↗

The Outlook peak is quoted as about 130,000 (CRN, AP) and about 140,000 (BBC), and the Microsoft total as 7 million or 7.4 million. These are different cut-offs and regions, and they count complaints, not people.

Noticed by:
Included it: Claude, ChatGPT, MiMo, Kimi, DeepSeek. Did not include: Meta, Gemini, Nova, Wenxin, Qwen.
Source ↗

The blackout also hit Microsoft's own AI products: Dynamics 365 Contact Center went down for just under 8 hours under CR1550885. When your agents and your AI share one cloud, the second system is just another way to fail.

Noticed by:
Included it: Kimi. Did not include: Claude, ChatGPT, Meta, Gemini, Nova, MiMo, DeepSeek, Wenxin, Qwen.
Source ↗

04Questions people ask

is chatgpt down

No. ChatGPT's chat logged no incident during the 12–14 November Microsoft outage. Only its Microsoft 365 connector failed, for 29h 49m, and it was resolved at 00:18 UTC on 14 November.

Source ↗
is chatgpt down right now

Trackers on 15 November showed ChatGPT operational and the connector incident closed. For the live state, check OpenAI's component status page.

Source ↗
is chatgpt down today

No new incident was posted after the connector fix at 00:18 UTC on 14 November. The 7 million-plus Downdetector reports that week were about Microsoft, not ChatGPT.

Source ↗
is chatgpt down rn

If ChatGPT answers but cannot open Outlook mail or calendar, the problem is the Microsoft 365 connector, not the chat. That connector was the only part that broke, for 29h 49m in November.

05How we counted

In plain words, no formulas.

1The question

Top 10 work AIs ranked by what still worked when Outlook and Teams went dark

2Why this topic

It splits 'the AI answered' from 'the AI could still reach your work' across several companies for the same two days, something no status page or complaint chart shows on its own.

3Where it applies

global, AI assistants used at work (Microsoft 365 Copilot, ChatGPT, Claude, Gemini and others), 12–14 November 2026

4What we looked at

  • Whether the assistant's own chat stayed up on 12–14 November 2026, according to each company's status history
  • Whether its link into company mail, calendar and files stayed up, according to the same status history
  • How many problem reports each product drew on Downdetector, compared with what the company says actually failed
  • How long the link into Microsoft 365 was broken, from the company's start and end times compared with Microsoft's own incident window
  • Ookla Downdetector — Microsoft 365 outage, November 2026 — Problem reports sent in by users, by service and time. More than 7 million Microsoft reports by 16:00 UTC on 13 Nov; Outlook near 130,000–140
  • Microsoft 365 Service Health (EX1550543, MO1550821) — Services Microsoft marked as degraded: Exchange Online, Teams, SharePoint Online, Microsoft 365 Copilot and Defender XDR. Exchange incident opened
  • OpenAI status — ChatGPT's own incidents, kept apart from the Microsoft 365 connector incident (Connectors/Apps)
  • Anthropic status — Claude's own chat, API and Claude Code incidents, kept apart from the Microsoft 365 connector and Claude for Outlook

5Who ranked

The leading AIs, each building its own list of ten independently and naming a source for every place: Claude, ChatGPT, Meta, Gemini, Nova, MiMo, Kimi, DeepSeek, Wenxin, Qwen.

6How the places were set

The same entry written differently by different AIs was counted as one. The more AIs put an entry on their list, and the higher they put it, the higher its place. "AI agreement" shows how many of the AIs had it on their own list. Sources are only those the AIs found themselves; nothing was added by hand.

06Each AI's own list

🇺🇸 Claude4 places · 2 notes

The same question, answered by Claude alone. The final list above combines all the AIs.

  1. 1
    ChatGPT (chat only, November 2026)

    Chat itself was not reported as down in what I found, and the connector claim rests on one unconfirmed source.

    Source ↗
  2. 2
    Claude (chat and Claude Code, November 2026)

    Claude's chat had a login outage on 13 November, and its Microsoft 365 link also failed.

    Source ↗
  3. 3
    Gemini (November 2026)

    Google's own mail and files are outside Microsoft's incident, but I found no Gemini data for these days.

  4. 4
    Microsoft 365 Copilot (November 2026)

    It went down with the suite it reads from; Copilot reports peaked near 6,000 against about 140,000 for Outlook.

    Source ↗

What Claude noticed

Claude's Microsoft 365 connector was marked resolved while Microsoft's own incident was still open, and later reports said errors persisted.

Teams core functions (calls, chat) were largely unaffected; calendars and invites failed because they read from Exchange.

🇺🇸 ChatGPT10 places · 3 notes

The same question, answered by ChatGPT alone. The final list above combines all the AIs.

  1. 1
    ChatGPT (OpenAI), 2026

    The chat and the office connection were separate failure domains: Microsoft's documents could disappear without ChatGPT itself being declared down.

    Source ↗
  2. 2
    Google Gemini, 2026

    A separate productivity ecosystem offered a practical escape route, although it could not magically restore inaccessible Outlook mail.

  3. 3
    Claude (Anthropic), 2026

    Its Microsoft connection recovered after 24 hours 37 minutes, but Claude also suffered separate chat, API and coding disruptions on November 13.

    Source ↗
  4. 4
    Perplexity AI, 2026

    Useful as an independent research route when enterprise mail and document search cannot be trusted.

  5. 5
    Grok (xAI), 2026

    Its independent chat infrastructure was an alternative to Microsoft, but its own history contains complete model-service outages.

    Source ↗
  6. 6
    DeepSeek AI, 2026

    A separate model ecosystem can preserve general reasoning work, but independent hosting alone does not prove continuous availability.

  7. 7
    Mistral Le Chat, 2026

    Another independent conversational route, with too little comparable incident evidence to award it a higher place.

  8. 8
    GitHub Copilot, 2026

    Coding work and office productivity are different dependencies: an Outlook outage does not establish that code completion stopped.

  9. 9
    Microsoft Copilot (consumer), 2026

    The Copilot name covered multiple products; consumer chat complaints cannot automatically be assigned to the Microsoft 365 enterprise incident.

    Source ↗
  10. 10
    Microsoft 365 Copilot, 2026

    The most deeply integrated assistant faced the central failure of the event: its workplace context depended on the same degraded services.

    Source ↗

What ChatGPT noticed

Claude's Microsoft 365 connector impact ended at 16:40 UTC on November 13, before its 21:49 UTC resolution announcement. Customer-impact time and incident-ticket duration are different measurements.

OpenAI's connector issue was marked resolved on November 13 at 19:18 ET, not November 14 in the displayed incident history. Confusing time zones or publication dates changes the comparison.

Teams meetings were reported as mostly functional while Outlook and Exchange remained uneven. A global incident was not equivalent to every Microsoft feature being completely unavailable.

🇺🇸 Meta10 places · 2 notes

The same question, answered by Meta alone. The final list above combines all the AIs.

  1. 1
    Google Gemini

    Answered 72 of 72 outage questions during the outage itself — the only engine to name EX1550543 in 20 answers.

    Source ↗
  2. 2
    Perplexity

    No Microsoft 365 connector to fail, and no incident in the last 7 days covering 12–14 November.

    Source ↗
  3. 3
    Meta AI

    The quiet one: no recorded incident in the last 30 days — but also no readable status page to prove it.

    Source ↗
  4. 4
    DeepSeek

    Stayed up through the Microsoft outage, then logged a 22-minute Web/Chat degradation on 14 November.

    Source ↗
  5. 5
    Mistral Le Chat

    Its last incident was 11 November — it entered the Microsoft outage clean, unlike the two connector assistants.

    Source ↗
  6. 6
    Grok

    Chat survived Microsoft, but xAI's own Grok Bot had elevated errors for about an hour on 12 November.

    Source ↗
  7. 7
    ChatGPT

    Chat kept answering while its Microsoft 365 connector was broken for 29 hours 49 minutes — talk, but no mail.

    Source ↗
  8. 8
    Claude

    Worse than ChatGPT: its connector failed for a day, then Claude itself had two more outages on 13 November.

    Source ↗
  9. 9
    GitHub Copilot

    Not a Microsoft 365 connector story — a coding assistant that still degraded for 1 hour 14 minutes on 13 November.

  10. 10
    Microsoft 365 Copilot

    The only assistant that lost both its chat and its work: Copilot reports peaked near 6,000 while Outlook peaked near 140,000.

    Source ↗

What Meta noticed

Outlook was the complaint magnet, not Copilot: Outlook peaked near 140,000 Downdetector reports, Copilot near 6,000, yet Copilot was unusable for work because it depends on the same Exchange Online data.

Anthropic closed its connector incident on 13 November while Microsoft was still restoring service — its 24h 37m impact window is shorter than OpenAI's 29h 49m ticket, even though Claude itself then failed twice more.

🇺🇸 Gemini10 places · 1 notes

The same question, answered by Gemini alone. The final list above combines all the AIs.

  1. 1
    Google Gemini for Google Workspace

    Operating entirely outside Microsoft's infrastructure, its chat and workspace integration suffered zero minutes of downtime while Outlook and Teams were down.

  2. 2
    Slack AI

    Salesforce's independent cloud kept conversation summaries and enterprise channels running without dropping a single native message thread.

  3. 3
    Notion AI

    Its internal knowledge graph and document synthesis stayed entirely online, even while third-party Outlook calendar sync lagged.

  4. 4
    Perplexity Enterprise

    Live web index search and enterprise collections answered queries continuously, unaffected by Microsoft's directory blackout.

  5. 5
    Glean Enterprise Search AI

    Its federated index kept Salesforce, Jira, and Google Drive queries alive, isolating Microsoft 365 downtime to an indexing pause rather than a system crash.

  6. 6
    Claude (Anthropic)

    Claude's direct chat never blinked, and Anthropic marked its Microsoft connector patched on the afternoon of 13 November—nearly a full day before Microsoft resolved its own incident.

  7. 7
    ChatGPT Enterprise (OpenAI)

    Conversations remained fluid on OpenAI's own servers, but users querying their company mailboxes were blocked until OpenAI resolved its connector on 14 November.

  8. 8
    Cursor Agentic Editor

    Local code intelligence and autonomous file edits worked without interruption, though developer teams using Microsoft Azure AD SSO suffered intermittent re-authentication freezes.

  9. 9
    GitHub Copilot

    Code completions in the IDE held on for cached tokens, but repository indexing and PR summaries broke under Azure AD and Microsoft 365 authentication cascades.

  10. 10
    Microsoft 365 Copilot

    Anchored directly inside Outlook and Teams, the flagship assistant vanished alongside the office suite, logging over 6,000 direct complaints while Outlook passed 140,000.

    Source ↗

What Gemini noticed

Ookla Downdetector gathered over 7 million problem reports across Microsoft services worldwide by 16:00 UTC on 13 November, showing that copilot disruptions generated user confusion between network failure and AI model failure.

🇺🇸 Nova10 places · 1 notes

The same question, answered by Nova alone. The final list above combines all the AIs.

  1. 1
    GitHub Copilot

    Unaffected by Microsoft outage — built on GitHub infrastructure

  2. 2
    Mistral Vibe

    European alternative with independent infrastructure

  3. 3
    Google Gemini

    Core service up; Microsoft connector failed for 36 hours

  4. 4
    Claude

    Core operational; Microsoft connector down 48 hours

    Source ↗
  5. 5
    ChatGPT

    Chat functional; Microsoft connector degraded 48 hours

  6. 6
    Microsoft Copilot

    Fully down with Microsoft 365 services

  7. 7
    Grok

    Unaffected third-party AI with no Microsoft ties

  8. 8
    Perplexity AI

    Web-focused; minimal Microsoft dependency

  9. 9
    DeepSeek

    Limited Microsoft integration; core stable

  10. 10
    Qwen

    China-focused; limited Microsoft exposure

What Nova noticed

Anthropic resolved Claude's Microsoft connector faster (13 Nov) than Microsoft's own services (14 Nov), highlighting third-party agility.

🇨🇳 MiMo10 places · 2 notes

The same question, answered by MiMo alone. The final list above combines all the AIs.

  1. 1
    Gemini

    The only major work AI whose board stayed green the entire Microsoft week — zero incidents 9–15 November — because its company mail is Gmail, not Exchange.

  2. 2
    Grok

    Grok spent the blackout live-blogging the Microsoft meltdown on X while its own status page logged nothing at all.

    Source ↗
  3. 3
    DeepSeek

    Its two November majors lasted under a minute each — and both landed outside the Microsoft week entirely.

    Source ↗
  4. 4
    You.com

    One incident in 90 days, closed in 34 minutes — and not a single post during the days Microsoft fell over.

    Source ↗
  5. 5
    Poe

    Perfectly boring, perfectly up: zero incidents on the tracker in the month Microsoft went dark for more than a day.

    Source ↗
  6. 6
    GitHub Copilot

    The only work AI whose status page hands you the escape hatch mid-incident: 'choose another model or select Auto' — and coding never stopped.

  7. 7
    ChatGPT

    It answered questions for 30 straight hours while its window into your mailbox sat broken: 29h 48m of 'can talk, cannot see the work'.

    Source ↗
  8. 8
    Perplexity

    Its Outlook, Teams and SharePoint connectors query Microsoft Graph live — and its status page said nothing all week: the blackout's quietest blind spot.

  9. 9
    Claude

    Anthropic marked its Microsoft link fixed at 21:49 UTC on 13 November — while Microsoft's incident was still open — and had two unrelated outages of its own that same day.

    Source ↗
  10. 10
    Microsoft 365 Copilot

    The assistant died with the inbox: chat refused to load, work data went dark for 20+ hours, and it drew 6,000 complaints against Outlook's 140,000 — a footnote in its own outage.

    Source ↗

What MiMo noticed

The AI was a side character in a mail outage: at peak, Outlook drew roughly 140,000 Downdetector reports while Copilot drew about 6,000 — a 23:1 ratio. The 7.4 million reports are complaints, not people.

The blackout leaked sideways within the hour: Veeam's M365 backups, ConnectWise PSA and KnowBe4 all opened incidents starting 18:28–19:38 UTC on 12 November — 'work AI' downtime is really 'everything that reads Exchange' downtime.

🇨🇳 Kimi10 places · 1 notes

The same question, answered by Kimi alone. The final list above combines all the AIs.

  1. 1
    Google Gemini

    The only big-four assistant with nothing to apologize for on Nov 13 - it sits on Google Cloud, not on Exchange or Graph, so there was no link to break.

  2. 2
    ChatGPT (OpenAI)

    It kept talking for the whole 30 hours - it just could not open your mail, calendar or files for 1 day 5 hours 48 minutes, the longest connector outage of the crisis.

    Source ↗
  3. 3
    Claude (Anthropic)

    Shorter connector outage than ChatGPT (24h37m vs 1d5h48m) - but claude.ai itself went dark twice on Nov 13, the only big assistant that could not even talk, while Claude on Bedrock, Google Cloud and Foundry kept working.

  4. 4
    GitHub Copilot

    While Outlook burned, the copilot that reads Git repos instead of Exchange inboxes never lost its data source - Azure showed no active events and GitHub was never in MO1550821.

    Source ↗
  5. 5
    Grok (xAI)

    Fully conversational for all 30 hours - and equally unable to see your work mail before, during and after the outage, since it has no Microsoft 365 link at all.

    Source ↗
  6. 6
    Perplexity

    No incident page and no connector apology - when Graph failed, a search-index assistant had nothing to lose.

  7. 7
    Notion AI

    Documents and AI stayed reachable for all 30 hours - but its brain is rented from model providers, and one of those providers was switched off for 18 days in June.

    Source ↗
  8. 8
    Microsoft 365 Copilot

    The only assistant that went down with the ship - about 6,000 complaint reports at peak and no mail, calendar or files left to read, because its eyes and its brain belong to the same company.

    Source ↗
  9. 9
    Microsoft Copilot Studio agents (Power Platform)

    Microsoft's own agent builder tripped over the same Graph cables - flows, apps and connectors failing intermittently under advisory PP1550869 while Copilot Studio saw connector failures.

    Source ↗
  10. 10
    Dynamics 365 Contact Center AI

    The clearest no-fallback case: the contact center went down just under 8 hours (CR1550885) - when your agents and your AI share one cloud, you do not have a backup, you have a second way to fail.

    Source ↗

What Kimi noticed

Every assistant plugged into Microsoft 365 failed together: 'If your overflow channel and your AI assistant share the same cloud as the contact center, you do not have a fallback. You have a second way to fail.'

🇨🇳 DeepSeek10 places · 3 notes

The same question, answered by DeepSeek alone. The final list above combines all the AIs.

  1. 1
    Gemini (2026 global work outage)

    The one major assistant with no Microsoft 365 dependency to break: its app and API stayed out of the outage path.

    Source ↗
  2. 2
    ChatGPT (2026 global work outage)

    It could still talk all day; what it lost was the ability to open Outlook mail and files, and that link came back on 14 November.

  3. 3
    Claude (2026 global work outage)

    Its Microsoft link was down for 24 hours and 37 minutes, but Anthropic restored it before Microsoft restored the suite.

    Source ↗
  4. 4
    Perplexity (2026 global work outage)

    Its Microsoft connector covers SharePoint and OneDrive, not Outlook or Teams — so the part of the work graph it could reach was narrower.

    Source ↗
  5. 5
    Grok (2026 global work outage)

    It had its own brief spike — 445 reports an hour on 12 November — but recovered within about an hour.

  6. 6
    GitHub Copilot (2026 global work outage)

    It stayed inside the IDE, where code and repos do not need Exchange Online — a different work graph from Outlook and Teams.

    Source ↗
  7. 7
    Mistral Le Chat (2026 global work outage)

    A quieter work assistant with no Microsoft 365 connector in the blast radius, and 100% Completion API uptime from late April to late July.

  8. 8
    Meta AI (2026 global work outage)

    It kept answering, but Meta publishes no incident feed, so “still up” is a reachability check rather than an auditable status history.

    Source ↗
  9. 9
    DeepSeek (2026 global work outage)

    It had no Microsoft 365 link to break, but it also had seven status-page outages in October alone.

  10. 10
    Microsoft Copilot (2026 global work outage)

    The native assistant did not just lose your mail — it lost its own chat, and Microsoft was still reporting Copilot for Microsoft 365 affected on 13 November.

    Source ↗

What DeepSeek noticed

Copilot drew a small fraction of Outlook’s complaint volume — Copilot peaked near 6,000 Downdetector reports while Outlook peaked near 140,000 — which says as much about installed base and habit as about relative reliability.

Anthropic restored its connector at 16:40 UTC on 13 November, hours before Microsoft declared full restoration on 14 November; OpenAI’s connector was marked resolved at 00:18 UTC on 14 November. Third-party AI links came back before the suite did.

Microsoft said the failure came from a network capacity upgrade, not a cyberattack or an AI/agent fault — the assistants were collateral damage in the office suite, not the cause.

🇨🇳 Wenxin10 places · 2 notes

The same question, answered by Wenxin alone. The final list above combines all the AIs.

  1. 1
    ChatGPT (OpenAI, 2026)

    Core chat service fully operational through the entire Microsoft 365 global outage

  2. 2
    Claude (Anthropic, 2026)

    Core LLM service never went down, only the M365 file/mail link broke for ~21 hours

  3. 3
    Gemini (Google, 2026)

    No reported core disruption, zero native dependency on Microsoft 365 infrastructure

  4. 4
    Grok 4.5 (SpaceXAI / xAI, 2026)

    Core inference stayed online, no deep integration with Microsoft 365 enterprise stack

  5. 5
    GitHub Copilot (Microsoft, 2026)

    Code editor assistant stayed up, separated from the broken Microsoft 365 enterprise stack

    Source ↗
  6. 6
    Microsoft 365 Copilot (2026)

    Fell over together with Outlook, Teams and Exchange in the global 74-country outage

    Source ↗
  7. 7
    Microsoft Copilot (public web, 2026)

    Partially degraded; many features that pulled from M365 went dark while basic chat survived

  8. 8
    Copilot in Teams (embedded, 2026)

    Unusable for almost the full outage, because Teams itself could not load reliably

    Source ↗
  9. 9
    Copilot in Outlook (embedded, 2026)

    Could not run at all while Exchange Online and Outlook were offline globally

    Source ↗
  10. 10
    Copilot in SharePoint / OneDrive (2026)

    Failed completely when SharePoint and OneDrive lost broad access across regions

    Source ↗

What Wenxin noticed

Almost none of the major AI assistants crashed their own chat engine; the real failure was the connector that reads your mail and files, not the model itself

Users who accessed ChatGPT directly via its official site saw almost no disruption, while users who reached it through Microsoft-linked enterprise routes often saw connection errors

🇨🇳 Qwen10 places

The same question, answered by Qwen alone. The final list above combines all the AIs.

  1. 1
    Google Gemini

    Zero M365 blast radius because it lives entirely inside Google Workspace.

  2. 2
    Slack AI

    Kept chatting while Teams was dead, proving the value of a second chat app.

  3. 3
    Zoom AI Companion

    Meeting summaries continued to flow even when Outlook mail stopped.

  4. 4
    Notion AI

    Docs stay up; the only thing broken were embedded Microsoft links.

  5. 5
    Claude

    Chat stayed up and Anthropic rebuilt its M365 connector faster than Microsoft fixed its own mail.

  6. 6
    ChatGPT

    The chatbot never blinked, but its eyes (the M365 connector) stayed shut until 14 November.

  7. 7
    GitHub Copilot

    Kept suggesting code even while the corporate mail server was down.

  8. 8
    Grammarly

    Still correcting emails in drafts, even though users couldn't send them.

  9. 9
    Microsoft Copilot (Consumer)

    The free web chat worked, but it had no idea what was happening in your work inbox.

  10. 10
    Microsoft 365 Copilot

    The AI went completely dark with the office suite, peaking at 6,000 complaints.