When Airtel Blocked File-Sharing Sites — and How to Tell if a Site Is Blocked

Years ago, broadband provider Airtel began blocking a batch of file-sharing sites — and, because of how the blocking was done, swept up a number of unrelated, perfectly ordinary websites along with them. It’s a small story that captures a question that has only grown more relevant: when does an internet provider get to decide which sites you can reach? Here’s what actually happened, why it mattered beyond the immediate annoyance, and a practical, evergreen guide to telling whether a site is genuinely blocked or simply down.

What happened

Under pressure from copyright holders, and trying to rein in peer-to-peer (P2P) traffic that consumed large amounts of bandwidth, the ISP started blocking access to file-sharing services. The problem was the method: the blocking was done bluntly, at the DNS or IP level, rather than surgically targeting specific infringing content. That distinction matters enormously. When you block by IP address, every other site that happens to share that address or sits on the same hosting infrastructure goes dark too — collateral damage by design. So alongside the intended file-sharing targets, a range of regular websites that had nothing to do with P2P suddenly stopped loading for that provider’s customers, with no explanation and no obvious way to tell why.

Why ISPs block, and why it’s blunt

Providers block sites for several reasons — court or regulator orders, copyright enforcement, bandwidth management, or content policy. The trouble is that the cheap, easy ways to block (refusing to resolve a domain in DNS, or null-routing an IP) are inherently imprecise. DNS blocking is trivial to set up and just as trivial to bypass; IP blocking is heavier-handed and routinely catches innocent neighbors sharing the same server. Precise, content-level blocking is expensive and complex, so providers reach for the blunt instruments — and ordinary sites pay the price.

The net-neutrality angle

This is the heart of the net-neutrality debate: the principle that an internet provider should carry all lawful traffic equally, rather than deciding what its customers can and can’t reach. Blocking a clearly-infringing service under a legal order is one thing; collateral blocking of lawful, unrelated sites is another entirely, and it’s exactly the kind of overreach net-neutrality rules are designed to prevent. The episode became a small but clear case study in why network-level blocking is so controversial — it’s difficult to do narrowly, easy to do badly, and it casts the provider as a gatekeeper deciding what the open web looks like for everyone on its network. It also sets a precedent: once the machinery to block lawful sites exists, it tends to get used again — for other content, under other pressures — which is why digital-rights groups push back on collateral blocking even when the original target was legitimate.

Is the site blocked, or is it just down?

If a site won’t load today, a block is only one possibility — and usually not the most likely one. Here’s how to work out which it is, in order:

Check if it’s down for everyone. A “down detector” service, or simply asking someone on a different network to try the site, tells you immediately whether the problem is the site itself or your connection. If it’s down for everyone, there’s nothing to fix on your end — wait it out.
Try another network. Switch from Wi-Fi to mobile data, or vice versa. If the site loads on one network but not the other, that points to network-level blocking or a routing problem on the first network — not the site being offline.
Change your DNS. Many ISP blocks happen at the DNS level — your provider simply refuses to translate the site’s name into its address. Switching to a public resolver such as Cloudflare’s 1.1.1.1 or Google’s 8.8.8.8 often restores access in seconds, with no software to install. If a DNS change fixes it, you were looking at a DNS-level block.
See what your connection reveals. Knowing your current public IP, location and provider helps you reason about what’s happening and on which network. Our What’s My IP tool shows all of that in one place.
A VPN as a route-around. For a genuine network-level block of a lawful site, a reputable VPN encrypts your connection and routes it through another location, bypassing the block. Use it to reach legitimately-available sites your network has restricted — not to break local law, and bear in mind that a few countries restrict VPN use entirely.

One practical tell that helps you diagnose the cause: a DNS-level block usually fails fast with a “server not found” or “can’t find the address” error, and a resolver change fixes it instantly — whereas an IP-level block tends to hang and time out, and a DNS change won’t help (a VPN will). A site that’s genuinely down, by contrast, behaves the same on every network and DNS you try. Matching the symptom to the cause saves you from “fixing” a problem that was never on your end.

In practice, most “this site is blocked!” panics turn out to be a DNS-level block (fixed in seconds with a resolver change) or the site simply being down (fixed by waiting). The Airtel episode is a useful reminder of why the distinction matters: blunt blocking catches innocent sites in the same net as its targets, which is exactly why how — and whether — providers block traffic remains worth paying attention to. For more on the technology and policy behind internet access, see our tech coverage.