Let’s assume this is true. It’s still a total indictment of Meta’s outsized influence on our culture and politics.
How were they not ready for the biggest day of anti-Trump protest of the campaign? If it wasn’t malevolence, it was likely a natural consequence of a company that is desperate to get as close to Trump as possible (and thus has a disincentive to do the basic, proactive work to be ready to support users on No Kings Day).
Further, Meta desires to have a monstrously large market share of political communications. They resist attempts to shrink their reach. What comes with that market power is a responsibility to see major moments of political action coming (and how could they not see it this one coming!?) and be ready. The No Kings IG was down for 4 hours.
An investigation is warranted, at the very least, to understand why Meta (which effectively functions these days as a private government) was unable to protect protest against Trump, while it spends so much time trying to get close to Trump.
We have continued to dig into the root cause here and would like to offer an update.
Our engineering team discovered that the spike that triggered the incorrect enforcement was primarily in the account’s “reading” behavior. 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.
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. An automated re-review of the removal action an hour later recognized that shouldn’t have happened and restored the account. It unfortunately took additional time for us to straighten out the situation with admin access to the IG account.
We want to reiterate our sincere apology for the error.