MOUNTAIN VIEW, Calif. – Users attempting to access content on YouTube encountered temporary disruptions Thursday morning, with Google reporting unusual traffic originating from multiple IP addresses, including 107.175.119.245, triggering automated security measures. The issue, first noted around 04:33 UTC on March 28, 2026, highlights the ongoing challenges tech companies face in balancing open access with protection against malicious activity and automated bot traffic.
The disruptions manifested as a block page informing users that their network’s requests appeared to violate Google’s Terms of Service. Google’s system detected activity potentially stemming from malicious software, browser plugins, or automated scripts. The company indicated the block would expire once the suspicious traffic ceased. This isn’t an uncommon occurrence, as Google routinely monitors for and mitigates automated requests designed to scrape data or overload systems.
While the specific YouTube video URL – https://www.youtube.com/watch%3Fv%3DwLT-c9Ie8NA – was flagged in this instance, the issue isn’t isolated to a single video. The automated systems are designed to identify patterns of abuse, not specific content. The incident underscores the complexities of maintaining a platform accessible to billions while simultaneously safeguarding against malicious actors.
Google’s Terms of Service, last updated May 22, 2024, explicitly address this type of situation. According to the terms, users are expected to adhere to rules that “keep the internet safe and open,” and those who violate these terms may face consequences, including temporary access restrictions. The terms state that Google may seek indemnification from users for legal proceedings arising from unlawful leverage of its services. [1], [2]
The incident comes as Google continues to expand its infrastructure and services. Notably, Google Fiber is preparing to launch internet service in Summerlin, Nevada, demonstrating the company’s continued investment in expanding its reach beyond its core search and advertising businesses. [3] However, maintaining the integrity and security of these services requires constant vigilance against evolving threats.
It’s important to understand that these automated blocks are not necessarily indicative of a user’s malicious intent. As Google’s support documentation explains, legitimate users can sometimes trigger these systems by using advanced search terms or making requests very quickly. If a user encounters this block, Google recommends checking for potentially malicious software or contacting their network administrator. [1]
For Google Fiber customers, the company’s Residential Terms of Service, last modified January 15, 2026, outline specific provisions regarding emergency services. Notably, the Google Voice app is not capable of placing or receiving emergency calls on devices without a SIM card, and users who are deaf, hard of hearing, or speech impaired are advised to use TTY or a telecommunications relay service to contact 911. [4] While seemingly unrelated to the YouTube disruption, this highlights Google’s broader commitment to addressing accessibility and safety concerns across its various platforms.
The incident serves as a reminder of the delicate balance tech companies must strike between providing open access to information and protecting their platforms from abuse. While frustrating for users temporarily blocked from accessing content, these automated security measures are essential for maintaining the integrity and reliability of online services. Google’s ongoing efforts to refine these systems will be crucial in mitigating future disruptions and ensuring a safe and secure online experience for all.
Google has not yet provided a specific timeline for resolving the issue, but the company stated the block would expire once the unusual traffic subsided. Users experiencing continued difficulties accessing YouTube are advised to check Google’s support resources or contact their internet service provider. The next update from Google regarding this matter is expected within 24 hours.
Keep reading