The Pulse
Meta Says a Claude Tool Triggered No Kings’ Instagram Suspension
Meta says bursts of reading activity by a tool linked to Claude triggered Instagram’s mistaken suspension of the No Kings Coalition’s account on October 17. The account became publicly available again after about 90 minutes, but organizers
AI.info Team · Written with AI · fact-checked ·
Meta says activity by a tool linked to Claude triggered Instagram’s automated systems before the platform took the No Kings Coalition’s account offline during a nationwide early-voting push. The suspension began on Saturday, October 17, as organizers held events ahead of the November 3 midterm elections. Meta later apologized, but its account of what happened shifted between Saturday and Sunday, and the company has not identified the tool or who was operating it.
Meta’s explanation changed from posting to reading
Meta’s first explanation focused on activity visible to other users: high rates of posting, sharing or commenting can trigger automated systems, the company said. Andy Stone, Meta’s vice president of communications, called the action an error and apologized. The coalition disputed that explanation, saying it had posted only a handful of times while livestreaming to thousands, according to The Guardian.
On Sunday, Meta offered a different account of the trigger. Its engineers, the company said, found that the spike was primarily in the account’s “reading” activity: a Claude tool was accessing Instagram profiles, posts and hashtags in intense bursts. Meta said the volume rose to about four times the normal level, and that the sequential requests looked to its security systems like automated bot traffic rather than ordinary browsing.
“This activity caused our automated protections to incorrectly take the No Kings Instagram account offline.”
— Andy Stone, Meta’s vice president of communications
Stone’s post also said an automated re-review restored the account about an hour after its removal, but that administrative access took longer to resolve. “We have regained access to our accounts, but Meta still owes us an explanation,” the No Kings Coalition said in a statement published Sunday, according to The Guardian. The coalition said restricting communications about voting during an election was unacceptable.
The account returned before its admins did
The account went offline at roughly 1:30 p.m. Eastern, and the coalition said it was unavailable for about 90 minutes. Meta said an automated re-review roughly an hour after the removal recognized that the account should not have been taken down and restored it. Full administrative access took longer: The Next Web reported that the coalition regained it at 5:33 p.m. Eastern.
That gap mattered on a day when the coalition and its partners were coordinating nearly 3,000 events across the United States to encourage early voting. The account’s public return did not immediately give organizers control over it. Meta apologized again for the mistake but has not said which specific Claude tool its systems detected, who ran it or what the tool was being used to do.
A political account caught in an automated security check
The suspension drew scrutiny because it happened during a large political mobilization focused on voting. No Kings organizers feared censorship after losing access, while Meta attributed the incident to an automated security system misreading high-volume activity. The available explanation identifies the pattern Meta says its systems detected; it does not establish who was behind the activity or why it was happening.
Meta’s two explanations also leave a basic discrepancy unresolved. Saturday’s account pointed to frequent posting, sharing or commenting; Sunday’s account centered on reading activity by a Claude tool. Meta has not publicly explained why its first description differed from its later technical account.
The operator remains unidentified
Meta has not named the Claude-based tool, its operator or whether it was being used by the coalition, a service provider or someone else. The company’s explanation links the detected activity to the suspension, but offers no public detail that would let outside observers determine who initiated the requests.
The account was restored and organizers regained administrative access, but the attribution remains Meta’s. The unanswered question is concrete: who was using the tool that generated the reading activity Meta says triggered the suspension?