YouTube apologizes for falsely banning channels for spam, canceling subscriptions

youtube-apologizes-for-falsely-banning-channels-for-spam,-canceling-subscriptions
YouTube apologizes for falsely banning channels for spam, canceling subscriptions

A misfire of YouTube’s systems led to the accidental banning of YouTube channels affecting numerous creators who were informed their channels were removed for “Spam & Deceptive Practices.” YouTube has now apologized for the problem and says it’s rectifying the situation, but did not comment on the cause of the bans, leading creators to wonder if the company’s automation is to blame.

Hi Creators – We’re aware of an issue causing some channels to be incorrectly flagged for Spam and removed. Our teams are looking into this and reinstating the channels right now – thanks so much for your patience.

More information: https://t.co/xQ9AFg0woc

— TeamYouTube (@TeamYouTube) October 3, 2024

On X, YouTube acknowledged the problem on Thursday night, saying it was aware of an issue “causing some channels to be incorrectly flagged for spam and removed.” The company said it was looking into this and working to reinstate the channels that were affected. Later in the evening, YouTube updated again to say that it was still working on the reinstatement and added that other content, like playlists, may still be delayed.

The company had not posted another update as of Friday morning, indicating the problem was not fully resolved at the time.

Update: our teams are still working on reinstating the incorrectly removed channels and access to subscriptions – we’re sorry for the trouble! Some content like playlists may be delayed, but it’s all coming back. Thanks for your patience while we work on this! https://t.co/YH9idZFuai

— TeamYouTube (@TeamYouTube) October 4, 2024

However, YouTube updated its X account on Friday afternoon, saying the problem is now fixed.

Happy to report that all channels and most videos incorrectly removed have been reinstated and subscriptions are restored (we’re still working on the last few, bear with us!!). We know this caused some disruption, and we so appreciate your patience while we sort this out ❤️‍🩹 https://t.co/8HbjnhJC4T

— TeamYouTube (@TeamYouTube) October 4, 2024

Missing in YouTube’s posts is any explanation as to how something like this could occur or an acknowledgment of the scale of the problem, though the last post suggests that YouTube itself knows the issue.

Social media reports from creators had indicated the problem was fairly serious and widespread. On YouTube’s X posts, for example, there were hundreds of replies from creators and their fans about channels they wanted to see restored. Some creators also noted that their files were missing, or complained that they tried to change their settings or reach out to support but received no assistance. YouTube’s updates on its Help site have hundreds of responses as well, but no further explanation.

While the issue affecting creators has been of greater concern, because channel removals have an impact on their livelihood, some YouTube Premium subscribers said they also lost access even though they don’t post videos or haven’t in years. As a result, they no longer had access to their Premium subscription, nor could they stream via YouTube Music.

The issue highlights the problems that can result when multiple services are tied together under one roof: publishing on YouTube, subscribing to Premium, and streaming via YouTube Music and YouTube TV. A false takedown over spam means people were losing access to not only their channels, which they may not have even utilized, but also their paid subscriptions.

YouTube’s announcement on its Help site said it was working on restoring access to subscriptions as well as the removed channels, adding, “We are very sorry for this error on our part and we’ll follow up here when it’s done.”

TechCrunch reached out to YouTube for comment on the situation, including the scale and the cause. As of Friday afternoon, the company only pointed us to its official X posts.

Originally published on 10/4/24 at 10:52 AM ET; updated with more recent context on 10/4/24 at 4:55 PM ET.