The Telecom Regulatory Authority of India (TRAI) Launches Network Anubhav Platform

1. At a Glance

• Network Anubhav is a geospatial and analytical dashboard that the Telecom Regulatory Authority of India (TRAI) launched on 04 Nov 2026. On one map it shows consumers' own speed and call tests alongside TRAI's Independent Drive Tests (IDTs) [1].
• It also gives web access to DND (Do Not Disturb) services: setting preferences, filing complaints about spam, tracking complaints, and viewing complaint data by service provider [1].
• Why it matters for UPSC: it brings together quality-of-service (QoS) regulation, consumer protection against spam, open data and evidence-based regulation. It ties to TRAI's statutory mandate under the TRAI Act, 1997 [1][4].

2. Why in the News

• TRAI launched the Network Anubhav Platform on 04 Nov 2026 [1].
• This follows the revamp of the MySpeed and DND apps in Feb 2026 [2] and the TCCCPR (Third Amendment) Regulations, 2026 on unsolicited commercial communication (UCC) [8].

3. Background & Evolution

• 1997: the TRAI Act, 1997 (Act No. 24 of 1997) sets up TRAI and the TDSAT. India Code records the Act's commencement as 25 Jan 1997 [4].
• 2000: an amendment sets up the TDSAT under Section 14 of the TRAI Act [4].
• Earlier MySpeed app: it sent coverage, speed, device and location data to the TRAI MySpeed portal [5].
• Jan 2024: TRAI publishes a report on drive tests at 20 locations. The KPIs included handover success, web browsing delay, video streaming delay and latency [6].
• 2018: the Telecom Commercial Communications Customer Preference Regulations (TCCCPR), 2018 become the anti-spam framework [7][10].
• Feb 2025: TRAI amends TCCCPR, 2018 to tighten UCC enforcement [7].
• Nov 2025: TRAI directs that variables in SMS templates (URLs, callback numbers) must be pre-tagged [11].
• 13 Feb 2026: TRAI revamps the DND and MySpeed apps. MySpeed adds video streaming and web browsing tests, latency, jitter and packet loss, scheduled and continuous testing, and geospatial history maps [2].
• 2026: the TCCCPR Third Amendment is notified after a draft consultation [8][9].
• 04 Nov 2026: the Network Anubhav Platform launches [1].

4. Core Static Facts

Item	Fact
Launching body	TRAI, a statutory body under the TRAI Act, 1997 [1][4]
Composition of TRAI	Chairperson + up to 2 whole-time + up to 2 part-time members, all appointed by the Centre; head office New Delhi [4]
Relevant TRAI function	Section 11: set QoS standards, ensure compliance with licence terms, ensure interconnection [4]
Powers	Sec 12: call for information and investigate; Sec 13: issue directions to service providers [4]
Appellate body	TDSAT, Sec 14, set up in 2000; hears appeals against TRAI directions [4]
Data sources	User test data from the MySpeed (internet speed) and MyCall (call quality) apps, plus IDT data [1]
Display filters	Cellular / Fixed broadband, service provider, technology; parameters such as download and upload speed [1]
Percentiles	P50 = median, for both categories; P80 = Mobile Broadband; P90 = Fixed Broadband [1]
TSP access	A secure interface shows call quality, coverage and internet tests, with location, date, time and technical values [1]
MySpeed SDK	Lets eligible third-party apps add connectivity measurement [1]
DND web functions	Set preferences, complain about UCC, track complaint status, view complaint data by provider [1]
Status of crowdsourced data	Indicative only. It is not an assessment under standard methodology [1]

5. Multi-Dimensional Analysis

Governance / Ethical

• Publishing performance by location reduces the information gap between telecom service providers (TSPs) and consumers, and lets consumers compare operators and areas [1].
• It moves TRAI toward evidence-based regulation: TRAI monitors aggregated insights, and TSPs get granular data to fix weak spots [1].
• TRAI already publishes QoS audit and drive-test results on its website. The platform adds a single interactive layer on top [3].

Scientific / Technological

• Geospatial analytics combines crowdsourced data and field data on one map [1].
• Percentile reporting (P80/P90) shows the speed most users actually get, not a mean that outliers can inflate [1].
• The MySpeed revamp added latency, jitter and packet loss as metrics, which matter more for real experience than raw throughput [2].

Legal / Regulatory

• The platform rests on TRAI's Sec 11 duty to set QoS standards and its Sec 12–13 powers [4].
• Web access to DND puts into practice the consumer-facing parts of TCCCPR, 2018, as amended [1][7].

Social / Consumer protection

• Under the 2025 amendment, consumers can complain about spam within 7 days of receiving it (previously 3) [7].
• Action against a sender is now triggered by 5 complaints in 10 days, down from 10 in 7 days. The penalty is a 15-day bar on outgoing services for a first violation and disconnection plus blacklisting for repeat violations [7].
• In Dec 2025, more than 7.5 crore calls and messages were blocked per day based on customer preferences, and about 21 lakh connections had been disconnected [10].

Administrative

• IDTs are run through TRAI's regional offices. For example, the Mumbai LSA test (Jan 2026) covered 214.8 km of city, hotspot, walk and coastal routes [12].
• Bottleneck: crowdsourced data has sampling bias, since people tend to run tests when the network is bad, and it is not standardised. That is why it is treated as indicative only [1].

6. Recent Developments (last 12–18 months)

• Nov 2025: direction to pre-tag variables in SMS templates [11].
• Dec 2025: more than 3 lakh senders and 21,000 telemarketers are registered on the DLT platform [10].
• 13 Feb 2026: MySpeed and DND apps revamped [2].
• 2026: IDT reports for Mumbai (Jan 2026 tests) [12], Ahmedabad–Gandhinagar–Vadodara highway [13] and Uttara Kannada, Karnataka [14].
• 2026: the TCCCPR Third Amendment brings AI/ML-based detection of suspected spam numbers (CLIs), mandatory pre-declaration of A2P calls, a consumer appeal mechanism and recognition of legacy consents [8][9].
• 04 Nov 2026: Network Anubhav Platform launched [1].

7. Prelims Hooks

• Network Anubhav was launched by TRAI, not DoT, on 04 Nov 2026 [1].
• It pairs crowdsourced user tests with TRAI's Independent Drive Tests on one map [1].
• User test data comes from the MySpeed (speed) and MyCall (call quality) apps [1].
• P80 is the benchmark for Mobile Broadband and P90 for Fixed Broadband [1].
• P50 = median: half the tests were at or above the value [1].
• The MySpeed SDK lets eligible third-party apps add measurement capability [1].
• The platform gives web-based DND access, including complaint data by service provider [1].
• TRAI Act = Act No. 24 of 1997; head office New Delhi [4].
• TRAI = Chairperson + ≤2 whole-time + ≤2 part-time members [4].
• TDSAT set up under Sec 14 of the TRAI Act, in 2000 [4].
• QoS standard-setting is a TRAI function under Sec 11 [4].
• Anti-spam framework: TCCCPR, 2018 [7].
• Number series: 140 for promotional calls, 1600 for transactional and service calls [7].
• Spam complaint window extended to 7 days (2025 amendment) [7].
• The revamped MySpeed app (Feb 2026) measures latency, jitter and packet loss [2].

8. Why 'All Benchmarks Met' and a Bad Local Network Can Both Be True

• The official answer and the ground reality do not match
• In 2026 the Minister told Parliament that all telecom service providers (TSPs) met the network QoS (quality of service) benchmarks in every licensed service area (LSA) for Jan–Feb 2026 [16].
• But TRAI's own drive test in Pune (Sep 2025) found BSNL's call drop rate was 8.68%. Other operators were below 0.4% [17].

• The Pune report does not say whether this broke a benchmark [17]. So the two facts do not contradict each other. They show that one result for a whole area can hide a very bad patch inside it.

• Why this happens: the benchmark is checked over a large area

• An LSA (the area covered by one telecom licence, usually a whole state or metro) is very large.

• When good towns and bad villages are added together, the average can still pass. A user in the bad patch gets no help from that average.

• Rural users have been flagged before

• A parliamentary Committee on Estimates report called quality of service in rural and remote areas "dismal" and asked for remedial action to meet TRAI benchmarks [20].

• Network Anubhav's map shows results by location [1]. For the first time, this kind of local gap is visible to the public, and not just inside TRAI's files.

• The catch: the map can show the problem but cannot punish it

• Crowdsourced data is officially "indicative only" (a hint, not legal proof) [1].
• So a red patch on the map cannot by itself trigger a penalty. Penalties still depend on the formal benchmark process [3].

9. Can Public Shaming Do What Small Fines Cannot?

• The fines for poor QoS are small
• When a TSP misses a benchmark, TRAI first asks it to explain. Then it may impose a financial disincentive (a fine) [3].
• The fine is up to ₹1 lakh per benchmark for a first breach, ₹2 lakh for a second breach in a row, and ₹3 lakh for each later breach in a row [3].

• For a large operator, this is a very small cost. It may be cheaper to pay than to build new towers.

• Network Anubhav adds a different kind of pressure

• It lets consumers compare operators area by area [1]. An operator that looks bad on a public map may lose customers.

• This is called reputational regulation (the regulator makes performance public and lets customers punish poor service by leaving).

• This works only if three things are true

• People must actually look at the map. The note gives no usage figures yet.
• People must be able to switch. In a village with only one working network, a bad rating changes nothing.
• The data must be trusted. Since it is "indicative only" [1], operators can dismiss a bad result as a sampling problem.

10. What Crowdsourced Speed Tests Can and Cannot Tell a Regulator

• Many things that affect a test are outside the network's control
• The OECD (Organisation for Economic Co-operation and Development, a group of rich countries) reviewed official speed tests in 2014.
• It found that many factors change a test result, and some of them only the user controls, such as the phone, the Wi-Fi and other apps running at the time [18].

• So a slow test may say more about the user's device than about the operator.

• Crowdsourced data may not answer the regulator's question

• The same OECD report warns that crowd-sourced tests may not always give the information needed for a specific policy or regulatory goal [18].

• It also notes that a regulator with its own measurement points depends less on voluntary user tests [18]. India's version of this is TRAI's Independent Drive Tests (IDTs).

• Advertised speed and real speed are different things

• A 2023 OECD paper notes that the speeds operators report to regulators can differ from what users actually get [19].

• This is the real value of Network Anubhav. It shows the speed people actually get, using P80/P90 percentiles (the speed that 80% or 90% of tests reach or beat) [1].

• How to use this in an answer: crowdsourced data is good at showing where to look. IDTs are needed to prove a problem. The two work as a team. Neither can replace the other.

11. Who Sees the Location Data That Users Hand Over

• Each test carries personal details
• The secure interface for TSPs shows each test with its location, date, time and technical values [1].

• A string of location-and-time records can show where a person lives, works and travels.

• The privacy rules are not stated

• The PIB release does not say how long this data is kept, whether it is anonymised (names and IDs removed) before TSPs see it, or what users agree to [1].

• The MySpeed SDK also lets eligible third-party apps add testing [1]. So data may now enter the system through apps that TRAI does not run.

• Why it matters for Mains: this links the topic to the Digital Personal Data Protection Act, 2023. A transparency tool for consumers should not become a tracking tool for companies.

12. What TRAI Should Do Next

• TRAI should use crowdsourced red spots to decide where to send drive tests
• Today, IDTs are planned city by city or highway by highway, as in Mumbai and Uttara Kannada [12][14].
• If the Network Anubhav map shows a cluster of poor tests, TRAI's regional office could send an IDT there next.

• This follows the OECD point that crowdsourced data is useful, but the regulator's own measurement is what it can rely on [18].

• TRAI should report benchmark results for smaller areas, not only whole LSAs

• An all-LSA "pass" [16] sat alongside an 8.68% call drop rate for one operator in one city [17].

• Publishing results by district would stop a good city average from hiding a bad rural patch. The Committee on Estimates asked for exactly this kind of rural focus [20].

• TRAI should review the size of QoS fines

• ₹1–3 lakh per benchmark [3] is unlikely to change an operator's investment plans.

• Public data from Network Anubhav works best when it is backed by a penalty that actually costs the operator something.

• TRAI should publish a data policy for the platform

• It should say what location data TSPs and SDK partners receive, in what form, and for how long [1].
• This would build user trust. More users testing means a better map.

13. Anchors for Answers

• Data: BSNL call drop rate of 8.68% vs below 0.4% for other operators, from TRAI's Pune drive test (Sep 2025) [17]
• Data: Minister's statement that all TSPs met network QoS benchmarks in all LSAs for Jan–Feb 2026 [16]
• Data: QoS fine of up to ₹1 lakh per benchmark for a first breach, rising to ₹3 lakh for repeated breaches [3]
• Report/Committee: Committee on Estimates (15th Lok Sabha) called rural QoS "dismal" [20]; OECD, Access Network Speed Tests (2014) [18]
• Law/Case: TRAI Act, 1997, Sec 11 (QoS standards), Secs 12–13 (powers) [4]; Standards of QoS for Access and Broadband Services Regulations, in force from 1 Oct 2024 [21]
• Comparison: OECD (2023) found that speeds reported to regulators can differ from what users actually get [19]
• Scheme: TCCCPR, 2018 and the DLT platform, the anti-spam regime behind the web DND service [7][10]

14. Mains Relevance

• GS-II: statutory, regulatory and quasi-judicial bodies; government policies and interventions; e-governance and transparency.
• GS-III: infrastructure (telecom and digital connectivity); science and technology in everyday life; cyber security (spam and fraud communications).
• Question stems: 1. "Crowdsourced data can complement but not replace standardised regulatory measurement." Examine with reference to TRAI's Network Anubhav Platform. 2. How far have TRAI's recent interventions protected consumers from unsolicited commercial communication? Suggest further measures. 3. Discuss the role of transparency tools in evidence-based regulation of India's telecom sector.

15. Related Topics to Study Next

• TRAI Act, 1997 and TDSAT: the statutory base and the appeals route.
• Telecommunications Act, 2023: the new overarching telecom law [15].
• TCCCPR, 2018 and the DLT platform: the anti-spam regime that DND access serves.
• Sanchar Saathi / Chakshu (DoT): parallel citizen-facing anti-fraud tools; contrast with TRAI.
• BharatNet and 5G rollout: coverage gaps that the platform makes visible.
• Digital Personal Data Protection Act, 2023: location and device data in crowdsourced testing.
• QoS regulations (call drops, network KPIs): the standards the IDTs measure.

16. NCERT Concepts to Revise

• Telecom Regulatory Authority of India (Polity): TRAI launched the platform; its Act and quality-of-service powers are the legal base of the whole note.
• Telecom Disputes Settlement and Appellate Tribunal (Polity): TDSAT, set up in 2000 under Section 14, hears appeals against TRAI directions; a common prelims trap.
• Percentiles (Economy): The platform reports P50, P80 and P90 speeds; knowing percentiles shows what these benchmarks mean.
• Sampling bias (Economy): Crowdsourced tests skew towards bad-network moments, which is why the data is only 'indicative'.
• Consumer protection (Economy): The platform and DND web access protect consumers from spam and poor service, and give them information.
• Digital Personal Data Protection Act 2023 (Polity): Test data carries user location, raising privacy questions that this Act's consent and data-handling rules address.

17. Common Errors / Trap Areas

• TRAI vs DoT: Network Anubhav, MySpeed, MyCall and DND belong to TRAI. Sanchar Saathi belongs to DoT.
• P80 vs P90: P80 is for Mobile, P90 is for Fixed broadband. Exam questions often swap them [1].
• Crowdsourced ≠ official assessment: user test data is indicative. It is not standard methodology [1].
• TDSAT was not created in 1997 with TRAI. It came through the 2000 amendment under Sec 14 [4].
• MySpeed vs MyCall: MySpeed tests speed, MyCall tests call quality [1].