PCMag editors select and review products independently. If you buy through affiliate links, we may earn commissions, which help support our testing.

Why Facebook's AI Failed to Detect Video of New Zealand Shooting

Last Friday's shooting slipped past Facebook's system because it didn't have data to train its AI on live-streamed mass shootings. The incident also resembled first-person shooter video game footage, which is common on the platform.

 & Michael Kan Principal Reporter

Our team tests, rates, and reviews more than 1,500 products each year to help you make better buying decisions and get more from technology.

Our Expert
LOOK INSIDE PC LABS HOW WE TEST
65 EXPERTS
43 YEARS
41,500+ REVIEWS

Facebook's AI failed to detect live video of last Friday's New Zealand mosque attack because the system simply isn't smart enough to recognise a mass shooting filmed by the attacker, the social network says.

In a Wednesday blog post, Facebook offered a detailed rundown of how it responded to video of the terrorist attack, which was live streamed on the platform.

Facebook has been using AI-powered algorithms to automatically take down videos and images containing pornography and terrorist-sponsored content. The algorithms can do this because they've been fed a large number of real-world examples of the offending content.

Last Friday's shooting slipped past the system because Facebook doesn't possess training data depicting live-streamed mass shootings. The events are thankfully rare, wrote Facebook VP Guy Rosen.

Complicating the matter is the prevalence of videos on Facebook depicting video game footage from first-person shooters. "Another challenge is to automatically discern this content from visually similar, innocuous content—for example if thousands of videos from live-streamed video games are flagged by our systems, our reviewers could miss the important real-world videos where we could alert first responders to get help on the ground," Rosen added.

Facebook Live Video

As a result, the company had to depend on users to learn about the shooting footage. However, during the live broadcast, the video was only viewed 200 times, none of which generated a single user report. It was only 12 minutes after the live stream ended when a Facebook user finally reported the content.

Before the original video was taken down on Facebook, it had been viewed 4,000 times. But eventually more users began to share and post new copies of the video on Facebook.

Rosen blamed the video's circulation on three groups: bad actors who were deliberately trying to keep the footage up; media outlets covering the incident; and regular users curious about the event. Not helping the matter was how new copies of the videos were being shared in different formats, making it harder for Facebook's automated systems to detect and pull it down.

"In total, we found and blocked over 800 visually distinct variants of the video that were circulating," Rosen said. Facebook's systems eventually became smart enough to automatically remove more than 1.2 million videos of the attack during the upload process. However, about 300,000 additional copies were only taken down after they were posted.

So how might Facebook prevent another shooting from going viral? The company didn't offer any clear solutions. "Some have asked whether we should add a time delay to Facebook Live, similar to the broadcast delay sometimes used by TV stations. [But] there are millions of Live broadcasts daily, which means a delay would not help address the problem due to the sheer number of videos," Rosen said.

However, the company does plan on improving its AI systems to quickly detect and prevent problematic videos from going viral. One experiment involves using audio-based technology to identify different formats of the same video.

About Our Expert

Michael Kan

Michael Kan

Principal Reporter

My Experience

I've been a journalist for over 15 years. I got my start as a schools and cities reporter in Kansas City and joined PCMag in 2017, where I cover satellite internet services, cybersecurity, PC hardware, and more. I'm currently based in San Francisco, but previously spent over five years in China, covering the country's technology sector.

Since 2020, I've covered the launch and explosive growth of SpaceX's Starlink satellite internet service, writing 600+ stories on availability and feature launches, but also the regulatory battles over the expansion of satellite constellations, fights with rival providers like AST SpaceMobile and Amazon, and the effort to expand into satellite-based mobile service. I've combed through FCC filings for the latest news and driven to remote corners of California to test Starlink's cellular service.

I also cover cyber threats, from ransomware gangs to the emergence of AI-based malware. In 2024 and 2025, the FTC forced Avast to pay consumers $16.5 million for secretly harvesting and selling their personal information to third-party clients, as revealed in my joint investigation with Motherboard.

I also cover the PC graphics card market. Pandemic-era shortages led me to camp out in front of a Best Buy to get an RTX 3000. I'm now following how the AI-driven memory shortage is impacting the entire consumer electronics market. I'm always eager to learn more, so please jump in the comments with feedback and send me tips.

The Best Tech I've Had:

  • My first video game console: a Nintendo Famicom
  • I loved my Sega Saturn despite PlayStation's popularity.
  • The iPod Video I received as a gift in college
  • Xbox 360 FTW
  • The Galaxy Nexus was the first smartphone I was proud to own.
  • The PC desktop I built in 2013, which still works to this day.

Read full bio