LRDF INTERNET SERVICE PRIVATE LIMITED makes Serchhip broadband depend on one visible upstream and local repair

Summary

• Public evidence identifies the company behind the abbreviated name as LRDF INTERNET SERVICE PRIVATE LIMITED. India's Department of Telecommunications lists it as a Category B ISP for the North East service area, with an effective date of 11 September 2025, while APNIC records connect it to AS154468 and the portable IPv4 block 144.79.204.0/23.
• AS154468 is active and widely visible, but route collectors show one immediate neighbouring network, CtrlS AS18229. PeeringDB shows no disclosed exchange or facility presence, and LRDF's own website remains an under-construction holding page. The evidence therefore supports a live regional network edge, not a verified resilient regional access system.
• LRDF's address block contains 512 IPv4 addresses and has a valid route-origin authorization. Those facts improve routing hygiene, but they do not measure subscribers, backhaul headroom, last-mile reach, pole or duct ownership, backup runtime, spare stock, or the time required to reach a failed link in Mizoram's hilly terrain.
• A customer's real service depends on a chain: premises equipment, local drop, neighbourhood distribution, powered aggregation, transport out of Serchhip, the CtrlS-facing handoff and onward carriers. The public record does not show a physically independent second route, so an upstream or transport failure may remain a shared point of interruption even when the local access cable is intact.
• The "Global" label should be corrected. The licence, registration address, routing records and operating signals point to a North East India regional ISP, specifically a Serchhip-linked operator in Mizoram. The stronger editorial category is Asia-Pacific regional ISP, while operating resilience should remain explicitly unverified.

The name is abbreviated, but the network is identifiable

A broadband bill is a compact object. It turns a month of connectivity into an account number, a due date and a price. None of those fields tells a household whether its fibre leaves the street in two directions, whether the powered cabinet has batteries, whether the upstream handoff is duplicated, or how many technicians can splice a cable during heavy rain. LRDF INTERNET SERVICE PRIVATE LIMITED is a useful case because the visible network is new enough, small enough and geographically specific enough to expose that gap between a commercial service and the infrastructure that must keep it working.

The first task is identity. The entity name presented here, INTERNET SERVICE PRIVATE LIMITED, is too generic to distinguish one Indian operator from many companies whose legal names contain the same words. The associated autonomous system resolves the ambiguity. APNIC's registration for AS154468 names IRINN-LDRF-AS-IN and describes the holder as LRDF INTERNET SERVICE PRIVATE LIMITED. The same record gives India as the country and places administrative and technical contacts at Dinthar Veng in Serchhip, Mizoram. IRINN's current-affiliate list also lists LRDF INTERNET SERVICE PRIVATE LIMITED in Mizoram. Those two records make "LRDF" the missing, identity-bearing part of the name.

Licensing evidence places the company more precisely. In the Department of Telecommunications' UL ISP and UL ISP VNO list as of 28 February 2026, LRDF appears under licence number DS-11/63/2025-DS-III, Category B, service area North East. The listed authorized person is Lalruatdika Fanchun, the registered office is in Serchhip, and both the signing and effective dates are 11 September 2025. This is materially stronger evidence than a commercial company listing or a payment page: it establishes a current public authorization record for a defined telecom service area.

It also contradicts the Global geography label. Category B "North East" is not a global operating footprint, and Serchhip is not an incidental contact when the internet-number records use essentially the same locality. The sensible interpretation is a regional ISP whose publicly attributable centre of gravity is Serchhip, within the North East service area. That does not prove every district served, and it should not be expanded into a coverage map. A licence defines where service may be offered; it does not prove where cable has been built, where customers are active, or which roads carry the transport route.

The distinction matters because a generic company name can tempt an equally generic story. This is not evidence of a borderless ISP selling abstract bandwidth. It is evidence of a young Mizoram-based operator with a narrow pool of internet addresses, a new autonomous system, one visible external neighbour and a regulatory scope tied to North East India. Its most important operating constraints are likely to be local: the route from Serchhip to a larger interconnection point, the condition and ownership of the access plant, power at aggregation sites, and the ability of a small team to find and repair faults.

A live route is strong operating evidence, but only for the routed edge

LRDF's network identity became concrete in late 2025. APNIC's ASN record gives 24 December 2025 as the registration date for AS154468. The corresponding address record assigns 144.79.204.0 through 144.79.205.255 to LRDF as portable IPv4 space, also registered on 24 December 2025. A /23 contains 512 addresses. The "portable" designation means the allocation is registered to LRDF rather than merely being a slice of an upstream provider's larger customer block, although practical reachability still depends on other networks carrying LRDF's route.

The route is not dormant. RIPEstat's AS overview showed AS154468 announced on 10 July 2026, and its routing-status view reported 512 IPv4 addresses visible through three announcements. The first observed route was 144.79.204.0/24 on 8 January 2026. By 10 July, the aggregate /23 and both component /24s were visible. The collector view saw the IPv4 route from 326 of 327 RIS peers, which is strong evidence that the origin was globally reachable rather than appearing at only one obscure observation point.

That is the cleanest reason to reject an overly severe "paper company" conclusion. A current telecom licence, current IRINN affiliation, allocated portable address space and a broadly visible route are mutually reinforcing. Cloudflare Radar's AS154468 overview also observes traffic and publishes an estimated user population. The estimate has recently appeared around 13,000 to 14,000 users. It should not be converted into a subscriber count: Cloudflare explains it as an estimated population informed by APNIC measurements, and people, devices, addresses and paid subscriptions are not interchangeable units. Still, observed traffic adds another signal that packets are moving through the network.

The limit is equally important. BGP proves that LRDF can originate addresses into the global routing system. It does not prove that LRDF owns a fibre distribution network, that every routed address belongs to a retail customer, or that the path from a Serchhip home to the border router has redundancy. A route collector sees control-plane announcements. It cannot see an unlit spare fibre, a diesel tank, a depleted battery, a damaged pole, an unpaid wayleave, a missing optical module or a technician travelling along a blocked road.

The 512-address pool is also not a direct capacity meter. Carrier-grade network address translation can place many customers behind relatively few public addresses, while business customers may receive several addresses each. Infrastructure devices, point-to-point links and internal services consume some of the pool. Conversely, a network can advertise an entire /23 while using only a small fraction of it. The address count therefore establishes administrative scale and routing independence, not take-up, line speed or simultaneous throughput.

One visible upstream is the central resilience fact

The most consequential public routing result is not the number of prefixes but the number of neighbours. RIPEstat's ASN-neighbours view showed one unique adjacent autonomous system on 10 July 2026: AS18229. APNIC identifies AS18229 as CtrlS. BGP.tools' AS154468 view independently classifies LRDF as an active eyeball network, lists three IPv4 announcements representing two /24s of address space, and shows CtrlS as its one upstream. Across sampled public paths, LRDF sits behind CtrlS, with Bharti Airtel AS9498 often appearing farther upstream.

This does not prove that LRDF has exactly one physical circuit. An operator can run two links to the same provider, use separate ports, buy protected transport, or maintain a backup that is not active in normal BGP observations. A second provider may be contracted but not visible, or may carry private traffic rather than LRDF's public prefixes. The defensible statement is narrower: public route observations expose one immediate external autonomous-system neighbour, and no current evidence demonstrates an independently routed second upstream.

That is enough to make single-route exposure a serious question. Two circuits to one upstream may protect against an optic failure or a local port fault but still share the upstream's network, building, fibre corridor or maintenance domain. Two logical BGP sessions over the same physical cable are not route diversity. Even two named carriers can converge into the same duct or leave a hill town along the same road. Resilience requires independence at several layers: separate border equipment, separate power, separate building entries, separate transport paths and preferably separate upstream administrative domains.

PeeringDB's record for AS154468 sharpens the question. LRDF self-describes there as a regional cable, DSL or ISP network with mostly inbound traffic, an open peering policy and traffic in the 1-5Gbps band. It reports two IPv4 prefixes, no IPv6, and no exchange or facility presence. Self-reported traffic bands are useful orientation, not audited capacity. "No exchange" means no exchange connection is disclosed in PeeringDB; it does not prove that no private interconnection exists. But in combination with the one observed upstream, it provides no public basis for claiming local peering diversity or direct cache access.

The economic effect of a single visible upstream can be larger than the engineering diagram suggests. If most traffic enters through one paid path, LRDF's retail cost and congestion risk are shaped by the price and capacity of that handoff. Popular video traffic may be cached closer to users if the network has private content caches, but no such deployment is public. Without local exchange participation or disclosed caches, evening demand can concentrate on the same upstream interface. An operator can purchase more capacity, but usable customer performance still depends on the slowest shared segment between household and interconnection.

The immediate recovery question is therefore concrete: if CtrlS reachability or the transport path to the CtrlS handoff fails, what alternate route originates 144.79.204.0/23? Public routing does not answer. A strong resilience claim would show a second upstream ASN appearing in normal or test announcements, documented failover drills, physically diverse transport and a route policy that prevents the backup from becoming stale. In their absence, the route should be treated as operational but externally concentrated.

The route begins in Serchhip, not at the BGP table

Internet routing abstracts geography, while local broadband is made of geography. LRDF's registration and licence both point to Serchhip. The Serchhip district disaster-management plan treats landslides, road disruption, power and communications as practical district hazards. That context does not prove an LRDF outage, but it explains why a fibre route in the district cannot be assessed as though it crossed a flat urban grid with numerous alternative streets.

For a Serchhip customer, the path likely begins with an optical network terminal or router at the premises. From there it may use an aerial drop on poles, a building riser, buried conduit, or a wireless link. It then reaches a splitter, switch, optical line terminal or aggregation point before entering longer-haul transport. The public record does not identify which of those technologies LRDF uses. The broad description of last-mile, fixed-wireless, fibre or broadband infrastructure must therefore remain a set of possibilities, not an asserted architecture.

The distinction affects failure behaviour. Passive optical fibre can carry high capacity without electrical power at every splitter, but the customer terminal and central optical equipment still require power. Active Ethernet may place powered switches closer to customers. Fixed wireless avoids some trenching but introduces tower power, line-of-sight, radio interference and mast access. A hybrid network can inherit all of these dependencies. Until LRDF publishes an access design or credible site evidence appears, it is not sound to depict the operator as purely fibre or purely wireless.

The national infrastructure around LRDF creates options without proving that LRDF uses them. Digital Bharat Nidhi's North East OFC implementation description says RailTel was tasked with augmenting and managing intra-district optical fibre between state and district headquarters in Meghalaya, Mizoram and Tripura, with subsidized capacity intended for sharing with licensed providers. BharatNet's project description likewise explains that public-sector fibre and incremental fibre connect block headquarters and gram panchayats, with bandwidth, dark fibre, Wi-Fi and FTTH available as utilisation models. Those programmes make shared transport conceivable. They do not show an LRDF lease, handoff, route or service order.

This ownership boundary is fundamental. LRDF can be the retail operator and BGP origin while leasing poles, ducts, dark fibre, wavelengths or managed bandwidth from others. A local cable operator can own the final drop while LRDF supplies authentication and internet transit. A government-backed fibre segment can sit in the middle. Each arrangement changes who detects faults, who holds spares, who has access permission and who controls restoration priority. The customer sees one bill, but repair may cross several organizations.

An evidence-based profile should therefore separate four claims. LRDF is authorized to operate in the North East. LRDF holds and originates its own IP resources. LRDF appears to carry active traffic. The ownership and topology of its physical access and transport network are not publicly established. The first three claims support an operating ISP classification; the fourth prevents claims of route diversity, fibre reach or restoration readiness.

Installed capacity is not usable capacity

PeeringDB's 1-5Gbps traffic band is the only public numerical indication of network traffic scale, and even that is a broad, self-reported range. It should not be mistaken for a 5 Gbps upstream port, customer capacity or guaranteed throughput. A network with two 10 Gbps interfaces can carry less than 1 Gbps; a network with a single 1 Gbps bottleneck can sell plans whose advertised rates add up to many times that amount. Broadband economics relies on customers not using peak speed simultaneously, but the oversubscription ratio and demand shape determine when that assumption fails.

TRAI's January-March 2026 performance-indicator report provides national market context and lists reported providers with more than 10,000 internet subscribers, but LRDF is not identifiable in that table. That absence does not prove fewer than 10,000 customers: reporting timing, naming, thresholds and the company's recent launch all complicate the inference. It does mean there is no public regulator table that can safely turn Cloudflare's estimated user population into LRDF retail subscriptions.

The same report shows why national totals do not solve the local question. India had more than a billion broadband subscriptions by March 2026, but a national growth rate says nothing about the capacity of one Serchhip aggregation link. A small ISP can matter greatly to a community while being invisible in national market-share tables. Its risk is concentrated rather than systemic: a fault may affect a limited number of people, yet those people can lose their principal route for work, education, payments, communications and public services.

Usable capacity has at least five layers. The customer package sets a commercial ceiling. The access medium sets a physical ceiling shared by a splitter, radio sector or switch. Aggregation links combine neighbourhood demand. Long-haul transport carries that demand out of the district. Upstream transit and interconnection deliver it to the wider internet. Headroom at one layer cannot compensate for congestion at another. The lack of published LRDF speed tiers, contention policy, fair-use terms, utilisation graphs or latency measurements leaves every layer beyond the routed edge unquantified.

TRAI's 2024 Quality of Service regulations identify the measurements that matter to a broadband user: service provisioning, fault repair, speed, latency, packet loss, jitter and network availability. The March 2026 broadband performance-monitoring index shows the regulator collecting provider performance, but no LRDF-specific public row was found. A route can remain visible while customer sessions fail, DNS becomes unreachable, a congested link drops packets or an access splitter goes dark. BGP availability is only the outside edge of service availability.

The two /24 more-specific routes deserve care as well. LRDF announces the covering /23 and both /24s. More specifics can support traffic engineering, because different routes can be given different preferences or carried over different paths. Here, however, all three announcements lead to the same origin and the public neighbour set still contains only CtrlS. The route pattern demonstrates control over the address block; it does not demonstrate two exits. Treating two prefixes as two physical routes would confuse address segmentation with transport diversity.

Routing hygiene is better documented than physical resilience

LRDF has taken one meaningful step that is visible from outside: its route-origin authorization is valid. RIPEstat's RPKI validation shows a valid authorization for AS154468 to originate 144.79.204.0/23, with a maximum length of /24. That covers the aggregate and permits the two more-specific announcements. Networks enforcing route-origin validation can reject a conflicting unauthorized origin, reducing one class of accidental leak or hijack.

RPKI is not an availability system. A valid route can lead to an overloaded link, a powered-off router or a cut cable. It does not authenticate the full AS path, and it does not reveal whether the origin router is in Serchhip, Aizawl, Guwahati, Hyderabad or another interconnection location. It is best understood as sound routing administration for the addresses LRDF holds, not proof that the underlying service is redundant.

IPv6 is the more visible omission. APNIC and routing summaries show no IPv6 allocation or announcement attributable to AS154468, and PeeringDB marks IPv6 false. That does not prevent customers from reaching IPv6 services through translation or an upstream arrangement, but no public evidence shows native LRDF IPv6. For a newly established network, the absence matters because adding IPv6 later can require customer-premises support, address planning, security policies, monitoring and staff knowledge. It is a capability gap, not necessarily an immediate outage risk.

The public website offers little operational help. LRDF's website resolves and is served by Squarespace, but it displays only an under-construction notice. It has no service-area map, tariff sheet, network-status page, fault telephone, escalation path, planned-maintenance notice or resilience claim. The domain's mail routing points to Google, which at least suggests an established communications setup, but a parked website cannot tell a customer whom to call when the optical alarm turns red.

This is where operational transparency and resilience meet. A small provider does not need to publish sensitive diagrams. It can publish support hours, outage notices, realistic restoration targets, covered localities, a maintenance calendar and an explanation of when premises power is the customer's responsibility. None of those disclosures would reveal a fibre route. Their absence increases uncertainty about how the service behaves when it fails.

Six failure paths test the real network

The first failure path is a customer drop or neighbourhood access cut. A truck, construction crew, falling branch, landslip, damaged pole, rodent or building work can sever fibre or copper. If LRDF uses fixed wireless, antenna movement, radio failure or loss of line-of-sight can create the same customer outcome. The blast radius depends on where the fault sits: one drop may affect one premises, while a feeder cut ahead of a splitter or switch can disconnect a whole area. Public records do not reveal feeder routes, spare fibres, pole agreements or whether access cables approach neighbourhoods from more than one direction.

Recovery begins before the cut. The operator needs accurate route records, labelled joints, optical test equipment, compatible connectors, spare cable, closures and trained staff. A technician must distinguish a customer-equipment fault from a feeder problem, locate the loss, obtain physical access and make a durable repair. If another company owns the pole or transport segment, LRDF must also open and escalate a ticket across the ownership boundary. A promise of local support has economic value only when staff, stock and authority are available at the time of failure.

The second path is loss of power. Customer equipment needs electricity, as do central switches, routers, optical line terminals, radios and monitoring systems. Mizoram's Power and Electricity Department maintains a Serchhip division and publicly posts planned work, including a shutdown of the 132 kV Zuangtui-Serchhip line. Planned shutdowns are not evidence of poor service; they are evidence that the power path is a real maintenance dependency. A broadband site can bridge an interruption with batteries or a generator, but LRDF publishes no site list, backup runtime or refuelling plan.

Power redundancy is often overstated. A battery that supports a router for four hours does not protect the customer if the neighbourhood switch lasts one hour. A generator does not help if fuel cannot reach a site or if the automatic transfer switch fails. Two utility feeds may share a substation. For LRDF, the test is end-to-end: how long can each powered point from customer aggregation to border routing operate, and which point expires first? No public answer is available.

The third path is long-haul transport failure. Serchhip traffic must reach a location where CtrlS can carry it onward. Public BGP paths identify the administrative neighbour but not the physical handoff. The path could be leased fibre, a managed circuit, microwave, public-sector transport or a chain of providers. A cut between Serchhip and that handoff can isolate LRDF while AS154468 remains visible briefly from a remote router, or it can withdraw the routes entirely. The distinction matters for diagnosis but not for a customer whose applications stop working.

Mizoram's terrain makes route independence a physical question. A second circuit following the same road shoulder can fail in the same landslide or excavation. A ring is valuable only if its two arcs are separated far enough to avoid common hazards and if both arcs are actually lit, monitored and sized for failover load. Digital Bharat Nidhi's North East fibre programme describes ring and shared-capacity ambitions at the public-network layer, but it does not establish LRDF's topology. The evidence needed is an LRDF-specific route-diversity statement bounded by named handoff areas and common-cause risks.

The fourth path is upstream loss. CtrlS may have a robust national network, but LRDF's observed adjacency still concentrates the boundary in one external autonomous system. A configuration error, suspended session, interface failure, maintenance window or upstream routing incident can remove reachability. The clean resilience test is a controlled withdrawal of the primary session while monitoring whether the /23 remains reachable through a different provider and physical path. No such result is public.

The fifth path is congestion. Unlike a cut, congestion may leave the route and link up while making service frustrating or unusable. Evening video demand, software updates or a traffic surge can fill access, aggregation or transit capacity. Packet loss and latency then rise, and advertised speed becomes a poor description of experience. PeeringDB's traffic band offers no utilisation percentage, and no public LRDF status or measurement page shows peak-hour headroom. Capacity should therefore be described as unknown, not as 1-5 Gbps of customer service.

The sixth path is shortage of repair labour. This is often the decisive constraint for a regional ISP. A network can own spares and still wait if its only trained splicer is already on another fault. A field crew can be ready and still be blocked by weather, road access, site permission or an upstream provider's dispatch queue. The public contact records identify administrative and technical roles, but they do not establish the number, location, shift coverage or qualifications of field technicians. One telephone number in a registry is not a 24-hour operations centre.

Local support labour is part of the product

For a large national provider, fault handling can be divided among a call centre, network operations centre, warehouse, contractor and local field team. A young regional operator may compress those roles into a handful of people. That can produce excellent service when staff know every route and customer. It can also create key-person risk: one absence, vehicle failure or simultaneous storm event can stretch restoration far beyond normal expectations.

LRDF's public footprint does not permit a judgment either way. The company has named regulatory and internet-resource contacts, and an active network needs someone to configure and maintain it. But there is no public careers page, team description, local support address, service-level agreement, fault-repair report or contractor disclosure. The right conclusion is not that crews do not exist. It is that crew depth and restoration coverage are unverified.

The economic test is simple. A provider collects recurring revenue because it accepts continuing obligations: keeping equipment powered, buying upstream capacity, monitoring faults, answering customers and replacing failed plant. The less dense the customer base, the farther each rupee of revenue must stretch across route kilometres, travel time and spare inventory. Serchhip's dispersed and hilly operating context can raise the cost per repair even if wages are lower than in a major city. That makes local knowledge valuable but also makes staffing a fixed cost that cannot be deferred indefinitely.

Customers should ask questions that produce operational answers rather than slogans. Is support answered locally? What hours are covered by staff rather than voicemail? Is there an after-hours number for a multi-customer outage? Are spare optical terminals and power supplies held in Serchhip? Does the company own a fusion splicer and optical time-domain reflectometer, or wait for a contractor? What is the escalation route when a leased backhaul circuit fails? How are customers informed during a long outage? None of these questions requires LRDF to publish confidential topology.

A useful restoration target also separates fault classes. A premises-router problem, local drop cut, feeder break, power outage and upstream failure have different owners and repair times. One blanket "best effort" promise hides that difference. A mature local operator can state what it controls, what it leases and when the clock depends on a third party. LRDF's unfinished website currently provides none of that public operating contract.

Regional ISP economics reward concentration and punish fragility

Small ISPs exist because local demand and local execution do not always fit the priorities of national carriers. A regional operator can build to overlooked streets, understand local rights of way, collect payments through familiar channels and send a technician who knows the terrain. It can combine wholesale capacity with local access and support. That proximity is a genuine competitive advantage, especially when customers value restoration and human contact more than a marginal increase in headline speed.

The same model carries structural risks. Upstream transit is purchased at wholesale while retail prices face competition from mobile data and larger fixed networks. New fibre requires upfront capital, but revenue arrives monthly. Spare capacity protects service but sits unused in normal conditions. A second route can be expensive relative to a small customer base. The operator may therefore be tempted to postpone redundancy until growth pays for it, even though a prolonged outage can stop that growth.

LRDF's own resources offer some bargaining independence. Holding AS154468 and portable IPv4 space allows the company to maintain a consistent network identity when changing or adding upstreams. A provider using only upstream-assigned addresses can face customer renumbering and operational disruption when it switches. LRDF's valid RPKI authorization also reduces friction in carrying its prefixes through a new provider. These are useful foundations for multi-homing, but the current public routing view does not show that multi-homing has been completed.

The address pool may also encourage network address translation. With 512 public addresses and an estimated user population much larger than that, sharing is plausible, although it is not directly proven. Carrier-grade NAT can conserve IPv4 space and reduce address costs, but it adds stateful infrastructure and can complicate inbound services, abuse attribution and troubleshooting. Native IPv6 would relieve some pressure, yet no LRDF IPv6 route is visible. Address architecture is therefore another area where administrative readiness is ahead of disclosed service design.

The strongest commercial claim LRDF could make is not "fast internet." It would be a bounded reliability proposition: named covered localities, measured peak-hour performance, transparent maintenance, local spare stock, a second independent upstream or tested backup, and repair times by fault class. Those details would make a monthly bill legible as an infrastructure service rather than just a speed tier. At present, public evidence supports the existence of the billable network edge more strongly than the resilience behind it.

What would raise confidence

Confidence would rise first with corrected public identity. LRDF should use its full legal and operating name consistently across the company website, IRINN, PeeringDB, customer documents and support channels. The abbreviated entity name should be treated as a display error, not a separate operator. A clear service-area page should distinguish licensed North East scope from actually serviceable localities and should identify whether the retail product is fibre, fixed wireless or a mixture.

Second, routing diversity should be demonstrable. A second immediate upstream in independent route collectors would be a strong signal, especially if the company explained that the circuits use separate transport and entries. PeeringDB could list actual interconnection facilities or exchanges if disclosure is appropriate. A published IPv6 plan and live IPv6 prefix would show that the network is preparing beyond short-term IPv4 conservation. None of these changes would expose customer information.

Third, the physical recovery model should be bounded. LRDF could publish the operating hours of its support team, maintenance notifications, backup-power design targets, local spare categories and escalation times for leased transport. A high-level diagram could show customer access, Serchhip aggregation, diverse transport and upstreams without revealing precise routes. Independent evidence such as dated photographs of unbranded equipment rooms, licence-matched invoices or third-party facility confirmations would help establish location and ownership.

Fourth, performance should be measured rather than inferred. Peak-hour latency, packet loss, DNS response, throughput attainment and outage duration are more useful than an address count. Publication of rolling metrics or participation in regulator reporting would allow customers to distinguish installed ports from usable service. The company should also clarify whether Cloudflare's estimated population bears any relationship to active accounts; until then it remains an external model, not a commercial disclosure.

Finally, resilience should be tested under failure. A tabletop plan is weaker than a recorded failover. The most informative exercises would remove the primary upstream, isolate one transport arc, exhaust utility power at a representative node and simulate simultaneous access faults. The public result need not include sensitive details. It should state whether traffic failed over, how much capacity remained, which sites exhausted backup first and how long field dispatch took.

A live regional edge with an unproven recovery system

LRDF is not merely a generic name attached to an ASN. The Department of Telecommunications identifies a North East Category B ISP licence effective in September 2025. APNIC and IRINN identify the same Serchhip company. AS154468 has originated LRDF's /23 since January 2026, the routes are broadly visible, traffic is observed and the origin authorization is valid. That is enough to describe an operating regional network edge with medium confidence.

It is not enough to describe a resilient regional broadband system. Public observation shows one immediate upstream, no IPv6, no disclosed exchange or facility presence and no independent evidence of a second route. The company website is unfinished and provides no tariff, coverage, support or status information. No public material establishes the ownership of access fibre or towers, the location of aggregation sites, peak-hour headroom, backup runtime, spare inventory, field-crew depth or restoration targets.

The consequence for a Serchhip customer is straightforward. The bill may come from one company, but continuity depends on several layers that the bill does not name: customer power, local access plant, powered aggregation, road- or terrain-exposed transport, an upstream handoff and people able to repair each boundary. LRDF has built enough administrative and routing independence to be identifiable. Its next credibility test is whether it can show equivalent independence in transport and recovery.

Until that evidence appears, the fair verdict is neither dismissal nor promotion. LRDF should be treated as a young, active North East India ISP whose routing edge is real and whose resilience remains unverified. The Global category and abbreviated company name should be corrected. The network's public grade is Medium because authorization and current routing are strong, while the physical access, power, diversity and repair case is still thin.