Meta No Kings Instagram suspension: Meta says traffic from 'a Claude tool' set off its bot defenses

Meta took the No Kings Coalition's Instagram account offline on Saturday, October 17, 2026, in the middle of the coalition's national day of action ahead of the November 3 midterm elections. On Sunday, October 18, Meta gave a new explanation for the Meta No Kings Instagram suspension. It said engineers had traced it to "the use of a Claude tool" reading the account's profiles, posts and hashtags in bursts that looked like bot traffic. That's different from what many headlines implied. Meta didn't say it uses a Claude-based moderation tool. It said its own automated protections reacted to traffic from a tool built on Anthropic's Claude, and that the reaction was wrong.

This story is based on reporting by Bloomberg (October 18), Reuters (October 19) and The Next Web (October 19), which quote Meta spokesperson Andy Stone's posts on X and the coalition's statements, checked October 20, 2026. The clash fits a wider pattern of sites treating AI agents as bots, covered in our analysis of websites blocking AI agents.

The short version

• What happened: the No Kings Coalition's Instagram account went offline on October 17, during what the coalition said were nearly 3,000 events in all 50 states and Washington, D.C.
• How long: about 90 minutes for the public page, the coalition said. Organizers said full admin access came back at 5:33 p.m. ET.
• Meta's first explanation (October 17): high rates of posting, sharing or commenting triggered its systems, and the suspension was "clearly" an error, Bloomberg reported.
• Meta's second explanation (October 18): a spike in "reading" activity from "a Claude tool," about four times normal, in intense bursts.
• Still unknown: which Claude tool, who was running it, and why its activity counted against the No Kings account.

What did Meta say caused the suspension?

Meta said its systems mistook automated reading for an attack. According to Bloomberg and Reuters, Stone, Meta's vice president of communications, wrote on X on October 18 that Instagram engineers found the spike was mainly in the account's "reading" behavior. Network security systems detected "the use of a Claude tool reading profiles, posts, and hashtags," with activity up roughly 4x in intense bursts on October 17.

Stone wrote that the "abrupt, high-volume, sequential requests in a short period resembled automated bot traffic rather than an ordinary human browsing our systems." He added: "This activity caused our automated protections to incorrectly take the No Kings Instagram account offline." And: "We want to reiterate our sincere apology for the error."

So the system that removed the account was Meta's own automated protection, which Meta hasn't named or described further. The Claude tool, in Meta's account, was the traffic that set it off.

What's the timeline?

Last verified: October 20, 2026

Reports describe the outage slightly differently. Bloomberg, citing the coalition, said the page was down for about 90 minutes. Reuters said it was offline for "more than an hour" and that restoring organizers' access took longer. MediaNama reported that organizers said admins couldn't reach the account's back end for about four hours. These accounts can all be true at once, since the public page and admin access came back at different times.

What does the No Kings Coalition say?

It doesn't accept Meta's account. In a Bluesky post quoted by Reuters on October 19, the coalition wrote: "Meta's explanation still doesn't add up." It said "NoKings and early voting content was inaccessible, restricted, or seemed suppressed across Meta platforms," and added: "Weeks before an election, an apology isn't enough. The public needs answers, accountability, and concrete safeguards." Late on October 19, MS NOW reported that the coalition had sent Meta a letter seeking answers before Election Day. Organizers told Bloomberg that Instagram is crucial for reaching supporters. Meta hasn't addressed the wider claim that other No Kings content was restricted.

Senator Chris Murphy (D-Conn.) responded on X on October 18, in a post embedded by IBTimes UK: "Let's assume this is true. It's still a total indictment of Meta's outsized influence on our culture and politics."

Has Anthropic responded?

Not publicly, as far as reporting shows. Bloomberg, Reuters and The Next Web carried no statement from Anthropic, and none had been reported as of October 20. Meta's explanation doesn't say Anthropic did anything. It describes someone using a Claude-based tool to read Instagram content quickly. That could have been the coalition's own staff, a supporter, a researcher or an unrelated third party. Meta hasn't said which.

Anthropic does publish how its own fetchers identify themselves. Its Claude-User agent fetches pages when a Claude user asks, as covered in our guide to detecting AI agents. Meta hasn't said whether the traffic it saw carried that identifier or came from a browser-driving tool.

Why does this matter beyond one account?

It's the agent-versus-website problem again, this time at the worst possible moment. Websites have spent 2026 tightening defenses against automated visitors. Bloomberg reported on September 21 that Amazon had begun blocking Meta's own personal agent, Muse, as our analysis of sites blocking agents notes. Now Meta's defenses have treated an AI tool's reading pattern as an attack and penalized an account during a political event.

Meta is also on both sides of the crawling debate. Its own commercial terms, which take effect October 30, still let it crawl sites linked to business accounts (our report on Meta's terms), and its Muse Spark models power agents that browse on users' behalf.

What's confirmed, reported and uncertain

• Confirmed (Meta, via Stone's X posts as quoted by Bloomberg and Reuters): the account was taken offline in error by Meta's automated protections; Meta attributes the trigger to "a Claude tool" reading content at about 4x normal; Meta apologized.
• Reported (coalition, via Bloomberg and Reuters): about 90 minutes of downtime for the page, full access at 5:33 p.m. ET, and claims of wider restrictions on No Kings content.
• Conflict: Meta's two explanations differ. On October 17 it blamed posting, sharing or commenting rates; on October 18, reading activity. Meta hasn't explained the change.
• Uncertain: which Claude tool, who ran it, whether it was tied to the coalition, and what Meta's automated protections are. Anthropic hasn't commented publicly.