The story of our small arts collective is, in many ways, the story of modern Mumbai—a tale of raw ambition, digital threads, and a sudden, chilling silence. Our idea wasn’t to challenge a government; it was to build a community. Yet, on a humid Tuesday afternoon, we were collectively labeled “unstable” by powers we never saw, marking the beginning of what I can only describe as a silent coup against a narrative they couldn’t control. This is the day they declared us unstable, and what happened after.

The Andheri Loft: Where Our Idea Began

Tucked away above a bustling bakery in Andheri West, our loft was less a physical space and more a state of mind. We were a fluid group: independent documentary filmmakers, poets writing in a mix of Marathi and code, visual artists digitizing traditional Warli art, and musicians sampling the city’s soundscape. Our common thread was a simple, powerful idea: to use digital storytelling to archive the voices that Mumbai’s glossy development narratives often erased.

• We hosted weekly “Upload Sessions” where people could share unfiltered stories.
• We launched a community-funded mesh network project to create small, local internet pockets in dense, underserved housing societies.
• Our primary platform was a self-hosted blog and a low-bandwidth podcast series called City of Whispers.

The air was always thick with chai, debate, and the hum of old laptops. We felt autonomous, believing the digital realm was our democratized canvas. We were, it turns out, profoundly naive.

An Unexpected Verdict: The ‘Unstable’ Label

It began with a single, frustratingly polite email on June 12th. Our internet service provider, one of Mumbai’s largest, notified us of “scheduled network optimizations” that might affect our “high-uptime commercial service.” We were on a residential plan; this was odd. Then, the cascade:

• Our website, hosted on a local server, became intermittently inaccessible outside our immediate area.
• Contributors from Navi Mumbai and Thane reported being unable to upload files or even load our site’s homepage.
• Our domain registrar flagged our account for a “manual review” citing “potential stability and content integrity issues.”

The official verdict, delivered in a sterile follow-up call, was the pivotal moment. The representative, reading from a script, stated: “Due to patterns consistent with unstable data propagation and network volatility, your nodal activity has been categorized as unstable. Service will be maintained at optimal levels for standard use.” We were baffled. “Unstable.” It was a technical-sounding word weaponized to mean “dissenting.” It wasn’t a takedown notice; it was a diagnosis designed to discredit our very existence.

> Tip: When authority uses ambiguous technical jargon to describe your activity, it’s often the first sign of a delegitimization strategy. Always ask for specific, written criteria.

Protocol of a Silent Crackdown: ISP Throttling

What followed was a masterclass in invisible suppression—a silent crackdown. There were no police raids, no sealed orders. Instead, a perfect, deniable technological stranglehold was implemented:

• Selective Throttling: Our specific IP addresses and domain were subjected to severe bandwidth throttling between 6 PM and midnight, precisely when our traffic peaked.
• Packet Shaping: Data packets for our uploads were deliberately delayed and deprioritized, making audio and video transfers impossible.
• DNS Poisoning: For certain users, especially on major ISP networks, our domain name simply stopped resolving to the correct server IP address for hours at a time.

The brilliance—and horror—of the method was its plausibility. The ISP could blame “local cable faults” or “network congestion.” The state could point to private companies managing their networks. We were left screaming into a void, our digital voices choked not by a hand over the mouth, but by a meticulously engineered atmosphere that lacked oxygen.

Connecting Digital Dots: This Was No Accident

At first, we thought it was a glitch. Then, coordination. Through our fraying digital connections, we reached out to other collectives. A Dalit rights video channel in Dharavi reported identical “instability” flags. A heritage conservation group mapping colonial-era land deeds in Fort faced sudden “server incompatibility.” The pattern was undeniable.

This was systemic marginalization of digital assemblies. The “unstable” label was a standardized protocol, a tag in a system designed to identify and isolate nodes of independent narrative-building without the messiness of legal charges. The tools were not censorship bills, but terms of service agreements and network management protocols.

• Key Identifier: Sites facilitating user-generated content focused on local, granular realities.
• Trigger Action: Surging, organic traffic from diverse, non-institutional IP clusters.
• Automated Response: Flagging for “anomalous behavior” leading to human-reviewed throttling.

The coup was not against servers, but against synapses—the connections between people. The goal was not to delete the information, but to make its distribution so laborious and unreliable that the community itself would dissipate in frustration.

Beyond the Silence: A Community in Resistance

We did not dissipate. The silence, ironically, amplified our resolve. If digital centralization was our weakness, we would return to analog roots and decentralized digital tactics.

• We created physical “data rickshaws”—USB drives with our entire archive, passed hand-to-hand in local trains and markets.
• We migrated to a decentralized hosting platform resistant to single-point throttling.
• Our podcast episodes were distributed as audio files via Bluetooth at chai stalls, rebranded as “Mumbai Memory Share.”
• Crucially, we documented every “service disruption,” every error message, creating a public ledger of the silent intervention.

> “A narrative they must throttle is a narrative they fear. Our instability is their metric for our impact.” — Note from our collective’s wall.

We learned that resistance in the age of silent coups is about protocol literacy. Understanding how data moves is as important as the story it carries. The label “unstable” has become our badge of honor, a反向 indicator that we are resonating.

The silent coup in Mumbai did not install a new leader. It installed a new filter—one that sorts citizens by algorithmic risk scores and network “stability.” But from the Andheri loft to the data rickshaws of Churchgate, a counter-protocol is being written. It is written in the stubborn persistence of shared files, in the whisper networks that bypass throttled bandwidth, and in the simple, enduring act of telling a true story about our city, no matter how “unstable” they declare it to be.