The 70-Day AirFiber Hostage Crisis: Paid For 100 Mbps, Got 8–11 Mbps, Now Barred at 0 Mbps

1. THE 100 MBPS PLAN & THE 90% DEFICIT: Subscriber enrolled and paid full subscription charges for an Airtel 100 Mbps AirFiber plan. However, from 19 July 2026 onwards, maximum throughput never exceeded 8 to 11 Mbps—representing an ~90% speed shortfall accompanied by extreme packet loss, high latency, and constant connection drops. As a technology founder working in cloud infrastructure and cybersecurity, this chronic throttle severely crippled daily operations and client meetings. 2. THE 20+ FAKE "RESOLVED" TICKETS: Over the span of more than two months, over 20 complaints were officially logged through the 121 IVR and the Airtel Thanks app detailing the crippling 8–11 Mbps speed degradation. Within 24 to 48 hours, every single complaint was systematically marked "Resolved" by automated backend metrics. Not a single technician arrived at the premises to test RF levels, inspect alignment, or replace the faulty receiver. 3. THE SEPTEMBER 27 COMPLETE BLACKOUT & BUCK-PASSING: On 27 September 2026, the connection failed completely, collapsing from 8–11 Mbps to 0.00 Mbps (total blackout). When physical hardware replacement was urgently requested, Airtel local support initiated a recursive blame game: the Dhubri AirFiber team directed the customer to Bilasipara, while the Bilasipara team insisted it was Dhubri's jurisdiction—despite the Dhubri team having successfully replaced the hardware at this exact location in April 2025! 4. THE BILLING HOSTAGE PROTOCOL: During an earlier escalation, a senior Airtel customer care representative explicitly instructed: "Sir, please do not pay your bill until we permanently resolve your connection." Following those exact instructions, the customer withheld payment for unrendered service. Airtel's automated billing barred the service, and on LinkedIn, @AirtelCares delivered the ultimate Catch-22: "We kindly request you to clear the outstanding amount... Once the services are active, we will coordinate with the concerned team."