Meta’s Spokesman Ties the No Kings
“Error” to “Reading.”

Meta’s spokesman, Andy Stone, wrote on October 17, 2026 that the automated action on the No Kings account “was clearly taken in error,” and on October 18, about 22½ hours later, that the spike behind the “incorrect enforcement” was “primarily in the account’s ‘reading’ behavior.” Stone’s two posts name different behaviors: posting, sharing or commenting “at very high frequencies,” and “reading.”

By William Douglas Baker

Founding Editor

How this was sourced: Meta’s explanation of what triggered the removal rests on its spokesman’s two X posts, read through a mirror of X, not on x.com; as of October 19, 2026, no source this edition read names who ran the tool that the second post describes. On October 17, 2026, Meta’s spokesman, Andy Stone, wrote on X that an automated action on the No Kings Instagram account “was clearly taken in error.”

The No Kings Coalition, The Next Web reports, “comprises hundreds of groups, including Indivisible, Common Cause, and the ACLU.” Stone’s first post says: “When accounts post, share or comment at very high frequencies it can trigger automated systems. That’s what happened with the No Kings IG account in the lead up to today’s day of action.” His update, posted on October 18, 2026, 22 hours 33 minutes 52 seconds later, says the spike that triggered what it calls the “incorrect enforcement” was “primarily in the account’s ‘reading’ behavior.” The two posts name different behaviors: posting, sharing or commenting in the first, “reading” in the second, and the update says “primarily.” Stone posted the update as a quote of his first post; the update’s own text names “reading” and does not repeat the posting sentence.

What Stone’s first post says

Mediaite, which calls him “Meta’s communications officer,” writes that Stone responded to its request for comment “by deferring to its X account,” and prints his post of October 17, 2026. Stone’s X profile bio, as mirrored on October 19, 2026, reads “Communications, @Meta.” The rest of his post, which he wrote for Meta in the first person plural, says: “Unfortunately, that automated action was clearly taken in error. Everything is now working as it should and we sincerely apologize.”

What the update says

Stone’s update opens: “We have continued to dig into the root cause here and would like to offer an update.” The sentence after the spike line, written for Meta, reads: “Specifically, our network security systems detected the use of a Claude tool reading profiles, posts, and hashtags, the rate of which sharply increased (~4x volume) in intense bursts on October 17.” Stone’s post does not say four times what.

Stone’s third paragraph goes on, for Meta: “These abrupt, high-volume, sequential requests in a short period resembled automated bot traffic rather than an ordinary human browsing our systems. This activity caused our automated protections to incorrectly take the No Kings Instagram account offline.” Both words, “resembled” and “caused,” are Meta’s, in its spokesman’s post of October 18, 2026. The same update calls the action “incorrect enforcement.”

Stone’s update then turns to the restoration, which it attributes to an “automated re-review of the removal action an hour later.” Stone’s next sentence in that paragraph reads: “It unfortunately took additional time for us to straighten out the situation with admin access to the IG account.” The update credits the later root-cause finding to “Our engineering team” and puts the admin-access delay on Meta (“us”); as of October 19, 2026, his post gives no duration for that time and names no individual. The update closes: “We want to reiterate our sincere apology for the error.”

The times each speaker gives

Ezra Levin, described in a Meidas Touch post that Mediaite embeds as a “No Kings organizer,” posted on Bluesky about the lockout. Five of his Bluesky posts, quoted below, are stamped in UTC on October 17, 2026. At 20:51 UTC Levin posted that the account was “Not restored - it’s now publicly accessible but we still have no backend access and can’t post!” At 21:29 UTC he posted: “Update: about 4 hours later and we still don’t have admin access so we still can’t post to the No Kings instagram account.” He does not say from when. At 21:52 UTC he posted: “Update: WE ARE BACK IN! We can post again.”

At 21:55 UTC, twelve minutes before Stone’s first post, Levin posted: “We have no explanation for why we were locked out for 4 hours today. We will be seeking answers.” At 23:49 UTC, replying to another user, he posted: “Unclear, the original message was ‘We’re sorry we got this wrong...Sometimes we need to take action to help keep our community safe.’” His post does not name who sent that message, and this edition does not say who did. All five posts predate Stone’s update.

Stone’s first post is stamped 22:07 UTC on October 17, 2026, and his update 20:41 UTC on October 18, 2026. Mediaite reports that MS NOW’s Antonia Hylton “reported Saturday afternoon”: “A spokesperson for No Kings says the main accounts for the coalition on Instagram were frozen and pulled down ... They say this happened at about 1:30 p.m. Eastern.” Mediaite also reports that Levin told Meidas Touch the page was suspended “for about an hour-and-a-half, during the height of the mobilization.” The Next Web reports that the coalition “stated that its page was down for approximately 90 minutes” and that “The coalition said that full access was restored at 17:33 ET.” The figures matter because Stone’s update times only the re-review, “an hour later,” and, in the October 19, 2026 pull, gives no figure for the admin-access delay. This edition does not reconcile these figures, and does not say that any of them is wrong.

What the sources read do not say

In the sources this edition read, as of October 19, 2026, neither Stone post cites a rule, policy or Terms clause, and no source names who ran the tool: not Stone’s posts, nor the reports of Mediaite, The Next Web or MediaNama. As pulled on October 19, 2026, neither post says whether any person took part in the removal, the “automated re-review” or the restoration. In the same pull, neither post says whether Meta’s “automated protections” or its “automated re-review” use an AI model. Not covered: the x.com originals, replies or threads under either post, other Meta statements, enforcement pages, or notices sent to the coalition.

Levin’s posts are quoted from his Bluesky feed as pulled at 20:42 UTC on October 19, 2026; his posts elsewhere were not read, and his interviews were not heard. The MS NOW and Meidas Touch clips were not watched, and the Bloomberg report that The Next Web cites was not read. In the sources read through October 19, 2026, none carries a statement from Anthropic about the No Kings suspension, and the first page of Anthropic’s newsroom listing, fetched October 19, 2026 (ten dated items, October 1 to October 18, 2026, plus five featured items), shows no item whose title or summary concerns No Kings, Instagram or Meta; article bodies were not opened, and Anthropic’s own accounts and press line were not searched.

What Stone’s posts are made of

On our reading, Stone’s two posts put three things side by side that a reader can take for one: a spike, a verdict and a reason.

Where the record stops

This edition states no cause or motive. Both posts were read through a mirror of X, and how x.com renders the quoted post was not seen. No statement issued in the No Kings Coalition’s own name was read; Levin posts on his Bluesky account. Declassified is researched and drafted with AI tools, including Anthropic’s Claude models, and an OpenAI model gave this edition an outside read. Agentics builds AI agents for its clients.

Editor’s note: Edition No. 096 examined a similar case; this one adds a platform spokesman’s own account, in two posts, of what its systems detected.

We map the record, not any person or company, to Digital Derangement Syndrome™ (DDS™). On our reading, Meta’s two posts are consistent with Contextual Ambiguity (a specific answer produced before the context determining its applicability had been established): Stone’s first post said “That’s what happened with the No Kings IG account in the lead up to today’s day of action,” and his update of the next day says Meta had “continued to dig into the root cause.” That mapping is editorial, not any source’s finding.