Summary

  • HSB's operating identity can be joined with reasonable confidence across several records. APNIC assigns AS142444 and 103.170.66.0/23 to HSB INTERNET SERVICE at an Ulhasnagar address under Harshavardhan Suresh. The Department of Telecommunications lists HSB INTERNET (OPC) PRIVATE LIMITED at the same address under Harshavardhan Suresh Bagul, and the HSB customer app uses the licence contact number. The licensed company, trading brand and number-resource holder should still be distinguished rather than treated as interchangeable legal names.
  • TRAI attributed 39 broadband subscribers to HSB INTERNET (OPC) PRIVATE LIMITED at 30 June 2025, up from 15 in the two preceding quarterly reports. That is the latest company-specific public count. The March 2026 report publishes individual totals only for providers above 10,000 subscribers, so HSB's absence there cannot update the figure or prove closure. It does make the app's claim of thousands of clients impossible to accept without reconciliation.
  • On 10 July 2026, HSB's AS142444 originated 103.170.66.0/24 and 103.170.67.0/24, covering 512 IPv4 addresses, with valid route-origin authorisations. Public route collectors saw those announcements almost globally. This is strong evidence of a live internet edge, but address count and route visibility are not customer count, access coverage or usable capacity.
  • Every current observed path to HSB passed through Navkar Supertech's AS137127, the only visible neighbour of AS142444. The same two prefixes were originated by Navkar for much of May 2023 through early August 2024 before HSB resumed originating them. This establishes a persistent upstream boundary. It does not establish whether there are one or several circuits, whether they share a duct, whether failover exists privately, or whether HSB has any second carrier.
  • HSB says its Ulhasnagar service is delivered through selected entrepreneurs or cable operators. Indian licensing rules permit last mile over fibre, radio, copper or an authorised cable network and permit passive-infrastructure sharing. No public source says which option HSB uses, who owns the drops and distribution nodes, where its network room is, how it powers active equipment, how many technicians it can dispatch, or how long restoration takes.
  • The proper conclusion is a split grade: current routing and licensed identity support a small operating city ISP, while physical resilience remains weakly evidenced. A buyer can verify HSB by asking for a serviceable-address list, subscriber reconciliation, route and circuit inventory, busy-hour graphs, power-runtime tests, spare stock and repair records. Until those exist, the bill buys reachability, not demonstrated route diversity.

The number that shrinks the network is 39

The first task in understanding HSB is to put unlike measurements in separate columns. A licence measures permission. An autonomous system and address block measure control of internet-number resources. A visible route measures reachability from route collectors. An app download measures distribution of software. A subscriber return measures accounts reported to the regulator at a particular date. None can substitute for another.

For HSB, the subscriber return is unusually important because it is both small and attributable to the licensed company. The Telecom Regulatory Authority of India's report for April to June 2025 lists HSB INTERNET (OPC) PRIVATE LIMITED with 39 broadband subscribers and no narrowband subscribers at 30 June 2025. TRAI says the annexure is compiled from reports received from internet service providers. That makes 39 a provider-reported regulatory figure, not an outside estimate of households seen online.

The sequence before it is also revealing. TRAI's October to December 2024 report assigned the company 15 broadband subscribers. The January to March 2025 report again reported 15. The next quarter's 39 therefore represented an increase of 24 accounts, or 160 per cent, from a very low base. It was meaningful growth for the company, but not evidence of a city-wide mass market.

The series stops being individually legible after that. TRAI's latest available January to March 2026 report limits its named provider annexure to businesses with more than 10,000 internet subscribers. HSB is not named there. Its absence does not mean 39 became zero; it means the newer publication deliberately leaves small providers inside an aggregate. The June 2025 figure is consequently the latest public company-specific count, not a current census.

This is where the company's own language becomes difficult. HSB's Google Play listing says the ISP operates only in Ulhasnagar, delivers service through selected entrepreneurs or cable operators, and is trusted by thousands of clients. The app had more than 500 downloads when observed and was last updated on 12 March 2024. Downloads can include former customers, repeated devices, installers and people who never activated service. They are not subscriptions. More importantly, the thousands claim and the regulator's 39 do not describe the same apparent scale.

Several explanations are possible, but none is established. The app copy may be promotional exaggeration. It may count end users behind building, cable-operator or business accounts that TRAI counts differently. It may describe the earlier unincorporated HSB brand while the 39 figure covers only the later one-person company. It may be old. Some subscribers may be reported by a wholesale licensor rather than HSB. Any one of these could narrow the discrepancy. Public material does not say which one is true.

The correct analytical move is not to select the most flattering explanation. It is to retain both facts with their labels. HSB advertised thousands of clients. HSB INTERNET (OPC) PRIVATE LIMITED reported 39 broadband subscribers at the end of June 2025. A lender, landlord, supplier or enterprise buyer should ask for a reconciliation that maps retail accounts, bulk building accounts, cable-operator accounts, active sessions and regulator reporting. Until then, revenue and affected-customer estimates should be built around a broad range, not the marketing number.

That range changes the economics of resilience. At 39 subscribers, one lost account equals about 2.6 per cent of the reported base. A single apartment block or local business contract could create a large percentage change. A second upstream, duplicate optical line terminal, generator, large battery bank and round-the-clock field roster may be hard to finance from 39 ordinary household bills. If the true served population is in the thousands, those investments may be more affordable, but the company would then need to explain why the licensed subscriber return is so small.

HSB therefore belongs in the regional-ISP category only in the broad sense of a geographically bounded local connectivity provider. The record supports an ISP serving one city inside the Kalyan Secondary Switching Area. It does not support a regional backbone, a large retail base or infrastructure spread across Maharashtra.

The brand, the company and the licence form one operating story, with legal seams

The name on the assigned internet resources is HSB INTERNET SERVICE. APNIC's record for AS142444 uses that name, identifies the network as HSBINTER-AS-IN, and gives an Ulhasnagar address near Takshsheela Vidyalaya. It names Harshavardhan Suresh as the administrative and technical contact. APNIC's record for the IPv4 block repeats the address and contact. The ASN was registered in July 2021, before the later licensed company received its authorisation.

The licence sits under a longer legal name. The Department of Telecommunications' current ISP authorisation list includes HSB INTERNET (OPC) PRIVATE LIMITED under licence DS-11/293/2023-DS-III. It identifies Harshavardhan Suresh Bagul as director, gives the Vikramsheela Colony address near Takshsheela Vidyalaya in Ulhasnagar, and records a Category C authorisation for Maharashtra (Kalyan), effective 9 January 2024.

The contact surfaces bridge the names further. The Google Play app uses telephone number 7276664414, the same number in the earlier official licence list, and its support address contains the HSB name. HSB's customer payment page identifies HSB Internet, gives a Thane address, uses the same telephone number and directs payment issues to an HSB email address. The app says service is limited to Ulhasnagar. These repeated identifiers make it reasonable to analyse the brand, number resources and licensed company as parts of the same operating story.

That is not permission to erase the legal boundary. HSB INTERNET SERVICE may have begun as a trade name or proprietorship associated with the 2021 number resources. HSB INTERNET (OPC) PRIVATE LIMITED is a corporate person and the named licensee from January 2024. The public material does not include an asset-transfer agreement, brand licence, customer novation, APNIC transfer or corporate statement explaining how the earlier business moved into the company. The ASN remains registered under the shorter name.

This distinction matters during an outage or dispute. The party that sends a bill may be the licensed company; the party named in a route record is the shorter HSB name; a cable operator may own the final drop; Navkar may carry the route; and a software vendor hosts the payment service. Customers need one accountable counterparty, but physical and contractual responsibility can cross several organisations.

The bridge is strong enough to avoid a false conclusion that the names are unrelated. The same principal, street location, brand, customer phone and city make coincidence implausible. It is not strong enough to assume every asset registered to the 2021 name is on the 2024 company's balance sheet. A serious service contract should name the licensed company, identify the trading name, state who owns customer equipment and access plant, and specify who must restore each segment.

The licence is for Kalyan; the visible offer is for Ulhasnagar

Geography supplies another necessary boundary. The Department of Telecommunications' internet-service guidance says Category C authorisation covers one Secondary Switching Area. HSB's licence specifies Maharashtra (Kalyan). That is permission to provide service within the Kalyan SSA, not evidence that the company covers all of it. The app narrows its actual claim to Ulhasnagar alone.

Ulhasnagar is an unusually dense place in which to run a small access network. The municipal corporation's city location profile gives an area of 13.5 square kilometres and a 2011 population of 506,098. Those figures imply roughly 37,500 residents per square kilometre at the census date. The corporation's history page describes a compact city divided into camps and blocks, with the Waldhuni River through it and the Ulhas River along its north-eastern boundary. It also describes local manufacturing and a road network threaded through the built-up area.

Density can make local broadband attractive. A short feeder can pass many potential customers. One distribution point can serve several floors. Technicians can move between faults without covering rural distances. Customer acquisition by neighbourhood cable operators can be cheaper than a national campaign. A small provider can concentrate on buildings or lanes where incumbents offer poor installation or support.

Density also concentrates risk. A cable cut at a building entrance can disconnect many accounts at once. A failed switch or optical splitter can affect a large share of a tiny customer base. A street cabinet may face heat, dust, water ingress or unstable local power. Multiple logical customers can still share one physical feeder, one pole line, one conduit or one powered node. A city-scale map can look richly connected while every route converges at one room.

No public HSB map resolves this. There is no serviceable-address checker, pole or duct inventory, tower list, optical-line-terminal location, fibre-kilometre figure, building count or point-of-presence address. The registered office could contain network equipment, but it could also be purely administrative. The app's statement that HSB uses entrepreneurs or cable operators makes a distributed access arrangement plausible, yet it does not reveal whether those partners own coaxial cable, Ethernet, fibre drops, radio links or only the customer relationship.

Local construction adds a concrete reason to ask. The Mumbai Metropolitan Region Development Authority's Ulhasnagar road programme describes 7.73 kilometres of concrete-road work across three packages, including routes around Kurla Camp and Ulhasnagar 4. It identifies water-line shifting, sewer work and property connections among the obstacles. This is not evidence that an HSB cable has been cut. It shows the kind of crowded civil-work environment in which undocumented telecom lines can be exposed, moved or trapped beneath new surfaces.

India's Telecommunications Right of Way Rules framework distinguishes underground and overground networks, ducts, poles, towers and street furniture. The Department's Call Before u Dig service is intended to coordinate excavators with utility owners and reduce damage from unmonitored digging. Those systems work best when the facility owner knows the route, registers it accurately and can respond quickly. HSB publishes no evidence about any of those capabilities.

The physical service area should therefore be described at three levels. The legal ceiling is the Kalyan SSA. The marketed area is Ulhasnagar. The demonstrated footprint consists only of an Ulhasnagar identity, a small reported subscriber base, active internet routes and customer-facing surfaces. Anything more detailed would need an address list or plant map.

Two routed prefixes prove reachability, not scale

The strongest current operating evidence is at the internet edge. APNIC assigns HSB the IPv4 range 103.170.66.0 through 103.170.67.255, a /23 containing 512 addresses. On 10 July 2026, RIPE's public route collectors showed HSB announcing it as two more-specific routes: 103.170.66.0/24 and 103.170.67.0/24. Both were originated by AS142444.

The routing-status view recorded two IPv4 prefixes, 512 announced IPv4 addresses and visibility from 326 of 327 IPv4 collector peers. It showed no IPv6 announcement. The AS overview marked the network announced. The announced-prefixes view showed both /24s throughout its current two-week observation window.

This is real operational substance. A route visible to almost every collector is not a dormant registration. Remote networks have a current path toward HSB's addresses. The two /24s are also the conventional minimum-length IPv4 announcements accepted by much of the global internet, avoiding reliance on propagation of the covering /23 alone.

Route-origin security is in place. RIPE's validation for the lower /24 and upper /24 marks AS142444's origin valid under a route-origin authorisation covering the /23 with a maximum length of /24. That lets networks which enforce Resource Public Key Infrastructure origin validation reject unauthorised origins more confidently.

None of this says how much traffic HSB can carry. A /23 is an address holding, not a 512-customer limit and not a bandwidth measure. One household can use a private address behind carrier-grade translation; one business can use many public addresses; infrastructure consumes addresses; unused addresses may remain assigned. HSB could carry a gigabit, ten gigabits or far less behind the same two routes. Public BGP carries no circuit-capacity field.

The route also says nothing about access medium. Packets may reach customers over fibre to the home, Ethernet in buildings, coaxial cable, fixed wireless or a mixture. The licence permits several of these. The app does not name one. Geolocation services place some HSB addresses around Mumbai or Ambarnath, but IP geolocation is inferred and can lag actual network use. It cannot map cable routes or prove a point of presence.

The absence of IPv6 is a limitation, not proof of service failure. Customers can use IPv4 normally, especially behind translation. Over time, an IPv4-only edge can add translation cost and operational complexity and may make end-to-end inbound connectivity harder. HSB publishes no IPv6 plan, public-address policy or translation design. An enterprise buyer that needs globally reachable servers should ask explicitly rather than infer capability from the /23.

The correct statement is narrow and useful: HSB currently originates all 512 IPv4 addresses assigned in its /23 as two globally visible and RPKI-valid /24s. That establishes a live routing edge. It does not establish the number of customers, their location, installed access capacity or resilience.

One visible neighbour makes Navkar the central dependency

The route becomes more informative one step beyond the origin. RIPE's neighbour view for AS142444 showed exactly one observed neighbour on 10 July 2026: AS137127. APNIC's record for AS137127 identifies it as NAVKARS-AS, Navkar Supertech Pvt Ltd, at Bhiwandi in Thane district.

Sampled BGP paths to HSB's lower prefix end with AS137127 AS142444. Many then pass through Tata Teleservices Maharashtra's AS17439 and Tata Communications' AS9498 before reaching larger global carriers. The precise path varies by observer, but Navkar is consistently the last visible network before HSB.

This is enough to identify an operating boundary. HSB originates its own routes, while Navkar propagates them outward. If that adjacency disappears and no hidden alternative takes over, both HSB /24s can become unreachable from the global internet even if every local cable, router and customer device remains powered. A local customer might still reach an HSB portal or another local subscriber, but ordinary internet service would fail.

History makes the relationship more significant. RIPE's route history for 103.170.66.0/24 and history for 103.170.67.0/24 show HSB originating the prefixes after allocation in 2021, disappearing in July 2022, and Navkar originating them from May 2023 until early August 2024. HSB resumed as origin around the end of July and beginning of August 2024 and has remained visible into July 2026.

That history should not be turned into an acquisition story. It does not show a sale, outage, rescue or customer transfer. It does show that the same address space has depended on Navkar in two configurations: for a period Navkar was the public origin, and now HSB originates while Navkar is the sole observed neighbour. The commercial contract and physical handoff remain private.

One BGP neighbour does not always equal one fibre. HSB and Navkar could have two circuits at different sites under the same pair of AS numbers. They could use separate fibres in one cable, separate cables in one duct, or truly independent routes. Conversely, a diagram showing two circuits could conceal one common pole, bridge, power supply or Navkar router. Public route data cannot distinguish these designs.

Nor does Navkar's broader connectivity automatically protect HSB. The neighbour view for AS137127 shows several observed networks on Navkar's outer side. That may give Navkar choices beyond its edge. HSB still has one visible attachment to Navkar. A failure at the HSB handoff, a shared access tail, Navkar's customer-facing router or the contract between them could isolate HSB before Navkar's multiple upstreams help.

The redundancy question is therefore specific. Does HSB have two physical handoffs? Are they in different HSB rooms and different Navkar sites? Do they use independently powered equipment and separate street routes? Is there a second carrier with a tested route policy? How much spare capacity remains during failover? Does the backup accept both /24s with valid origin security? No public claim answers these questions.

The lack of a PeeringDB entry for AS142444 adds no proof either way. Participation is voluntary. HSB could buy private transit without listing itself, or could exchange local traffic through arrangements not recorded there. The absence simply removes one common place where networks publish interconnection sites, capacities and policies.

For a customer, the practical meaning is simple. HSB's autonomous system gives it control of route origin and addressing. Navkar remains the single visible doorway from that system to the rest of the internet. Autonomous does not mean independent.

The last mile may belong to a chain of local operators

HSB's app offers the clearest statement about access ownership, and it is still incomplete. It says service is delivered through selected entrepreneurs or cable operators who follow company standards. This suggests that HSB may combine a central internet edge with neighbourhood distribution run by local partners. That is a common way to reach dense urban blocks without owning every drop.

The legal framework allows several structures. The Unified Licence says an internet-service licensee may establish its own transmission and last-mile links within its service area using fibre, radio or underground copper. It may use an authorised cable operator's network for the last mile. It may also share passive infrastructure such as buildings, towers, dark fibre, ducts and rights of way with other licensees.

Permission is not a description of HSB's deployment. If a cable operator owns the building network, HSB may control authentication, addressing and upstream transit while the partner maintains splitters, switches, coaxial amplifiers, rooftop radios or fibre drops. Another arrangement could put the physical plant under HSB and leave the entrepreneur with sales and collections. A third could be wholesale resale over a larger provider's access network. The app does not choose among them.

Each structure moves the fault boundary. When one building loses service, the cause might be customer equipment, an in-building cable, a partner switch, a feeder, HSB's central router, the HSB-Navkar link or a wider upstream. A support representative must locate the failure before dispatching the right party. If monitoring ends at the HSB router, a partner access fault can look like silent customers rather than a clear alarm.

Local labour is therefore part of the product. A field technician needs permission to enter a building or roof, accurate cable records, a working optical power meter or cable tester, connectors and replacement devices, and a safe route to the fault. The technician also needs someone who can make a configuration change at HSB or escalate to Navkar. A promise of local support is valuable only when these responsibilities are assigned and measured.

HSB publishes no technician count, shift schedule, service-level objective, spare inventory, dispatch area or restoration history. The app's cable-operator language indicates a labour structure, but it does not prove that operators are available after hours or that their stocks are compatible. The payment portal provides a support contact; it does not provide an outage number, escalation ladder or status page.

This is a major weakness in a city where a small number of accounts can be physically clustered. Suppose 20 of the reported 39 subscriptions sit behind one partner switch. A single power adapter or fibre feeder then affects more than half the named base. If thousands of end users actually sit behind bulk accounts, the human impact could be much larger. Without a customer-to-node map, neither HSB nor a buyer can express concentration clearly.

The commercial contract should make the chain visible. It should name the access owner, define the demarcation point, state who supplies and replaces the customer device, set response and restoration targets, and require notice when a partner changes. For business service, it should include a route drawing and escalation contact for both HSB and the access partner. A low monthly fee can be rational, but only if the customer understands which risks have been removed and which have merely been transferred.

Installed capacity is not usable capacity

HSB publishes no current tariff or speed table on its main domain. The domain hsbnet.co.in resolves, but on 10 July 2026 it displayed a generic Hostinger page saying website files still needed to be uploaded. The official .in domain registration record shows the domain registered through February 2031 and updated in December 2025. Registration and DNS therefore remain active while the public content is not.

That condition prevents a reader from checking retail speeds, fair-usage terms, installation fees, serviceable locations or support promises. It does not stop packets on AS142444 from forwarding. Web hosting and internet access are separate systems. Yet a default page is still operationally relevant: prospective customers cannot use the stated domain to compare plans, and existing customers cannot rely on it for status information.

The payment portal remains identifiable as HSB, but its public TLS certificate was expired when checked on 10 July 2026. A security warning does not prove that billing accounts or network sessions are inactive. It does undermine the safety and usability of a page intended to take payments. Customers should not be expected to bypass a certificate warning to recharge service. The contrast is telling: BGP route-origin security is valid while a basic customer-facing certificate is not.

With no tariff and no engineering disclosure, capacity has to remain unknown. The two /24s reveal address quantity only. A route path reveals sequence of autonomous systems only. A responsive router reveals a reachable device only. None gives the committed information rate purchased from Navkar, the backhaul rate from each local operator, busy-hour demand, oversubscription ratio or headroom after failure.

TRAI's June 2025 report states broadband benchmarks that clarify what a proper measurement would look like. It lists latency of at most 50 milliseconds, packet loss of at most one per cent, jitter of at most 40 milliseconds, and maximum bandwidth utilisation of 80 per cent on a customer-serving node to the ISP gateway or internet exchange link. These are national benchmarks, not HSB-specific results. The report does not include a performance row proving that HSB met them.

Installed capacity is the nominal rate of ports, radios, fibre optics and upstream circuits. Usable capacity is what remains after protocol overhead, contention, failures and busy-hour demand. Resilient capacity is smaller again: what can be carried after the largest credible component fails. An ISP with two 1 Gbps links may have 2 Gbps in normal operation but only 1 Gbps after one failure; if normal traffic reaches 1.6 Gbps, the backup exists yet congestion is guaranteed.

For HSB, even the first figure is absent. A buyer should request at least 30 days of five-minute utilisation for every upstream and customer-serving node, with the maximum, 95th percentile and busy-hour period. The same evidence should be shown during a deliberate failover test. Aggregate traffic should be reconciled with active subscriber sessions so a quiet graph is not mistaken for spare capacity when it merely reflects disconnected users.

IPv4 capacity deserves separate treatment. HSB's 512 addresses could support 39 subscriptions comfortably, but a larger base may require translation or address sharing. That can work well, but it affects inbound services, abuse attribution, port availability and logging. HSB's public material does not say whether residential customers receive public, shared or static addresses. An enterprise customer should put the required addressing arrangement in the order rather than infer it from HSB's allocation.

The evidence supports connectivity, not a speed promise. Until HSB publishes plans or supplies a contract, no responsible account can describe its installed or usable capacity in megabits or gigabits.

Six failures define what the monthly bill is buying

The first failure is loss of the visible upstream. Every observed global path reaches AS142444 through Navkar's AS137127. If the HSB-Navkar adjacency, customer-facing circuit or relevant Navkar router fails, the two HSB prefixes can disappear together. Valid route-origin authorisations reduce one class of routing mistake; they do not create an alternate path. A second session over the same cable would improve device redundancy but not protect against a cable cut.

The second is a local access cut. Ulhasnagar's dense roads, building entries and active civil works create many points at which a cable can be moved or damaged. The national right-of-way framework and Call Before u Dig service can reduce risk, but only for accurately recorded assets and responsive owners. HSB does not publish route records, ring topology or participation in dig coordination. An aerial route can avoid excavation but add pole, clearance and weather exposure. An underground route can avoid pole damage but become slow to locate and repair.

The third is power. Customer routers and optical terminals need electricity. So do partner switches, rooftop radios, fibre amplifiers where used, HSB routers and the Navkar handoff. A battery at HSB's room does not keep an unprotected neighbourhood switch alive; a customer inverter does not help when the upstream room is dark. Public records identify no HSB network site, utility feed, uninterruptible power supply, generator, fuel contract or tested runtime. Backup power must be described node by node.

The fourth is equipment failure. A small network can depend on one router, one optical-line terminal, one switch chassis or one power supply even when spare ports exist. HSB publishes no device redundancy or spare list. Recovery depends on configuration backups, compatible optics, labelled fibres and a person authorised to change the network. A replacement on a shelf in another city is not the same as a tested local spare.

The fifth is field-repair shortage. HSB's distributed cable-operator approach can put knowledge close to customers, which is an advantage when the right person is available. It can also fragment records and spares. A partner may know an apartment cable but lack access to HSB's router; HSB may see a partner node fail but lack keys to the building. Night, rain, traffic and simultaneous faults can turn a short geographic distance into a long restoration.

The sixth is congestion. A route can remain fully visible while service becomes unusable. If many local accounts share one feeder or Navkar circuit, evening demand can fill it. Packet loss and latency then rise without a clean outage. HSB supplies no busy-hour data, customer-serving-node map or failover headroom. The app's low-price positioning, if still current, would make disciplined contention management especially important because revenue per account may be limited.

There are also customer-channel failures. A default public website and expired payment certificate do not prove an access outage, but they can prevent sign-up, secure recharge or support discovery. When connectivity is already down, customers may rely on mobile data to find a status page. HSB publishes no independent status site. A network can be technically repairable and still feel abandoned if the customer cannot learn what failed or when it will return.

These failures can combine. Civil work cuts a feeder, a technician discovers that the route drawing is old, rain slows splicing, a partner cabinet has no working battery, and customers cannot reach a secure recharge or status page. Alternatively, a Navkar handoff fails while every HSB access node remains healthy; local lights look normal but both public prefixes vanish. Resilience is the ability to separate these cases quickly and restore the affected layer.

Who is affected remains part of the uncertainty

The likely affected parties are households, small businesses and corporate users in Ulhasnagar because those are the groups named by the app. The city is dense, commercially active and integrated into the Mumbai Metropolitan Region. Connectivity loss can interrupt payments, remote work, cloud applications, education, entertainment and customer communications. HSB does not publish a customer list, so no hospital, school, government office or other critical site should be attributed to it.

The number affected by one failure cannot be read from the 39-subscriber return alone. A subscriber may be one household. It may be a business with many employees. It may be a cable-operator or building account serving multiple end users. Conversely, an app download may belong to someone who no longer subscribes. The public record lacks the mapping from billed accounts to active sessions and from sessions to physical nodes.

Concentration matters more than total count. If 39 accounts are spread across 39 independent building drops, a local cut may affect one or two. If 30 share one partner feeder, the same cut affects most of the base. If all HSB traffic reaches Navkar over one unprotected handoff, an upstream failure affects everyone regardless of access distribution. A useful resilience statement therefore needs both node-level customer counts and end-to-end dependency groups.

Local businesses face an additional distinction between restoration and continuity. HSB may restore a failed circuit within hours, but a shop whose payment system requires constant connectivity may need automatic mobile failover within seconds. A business buyer should ask whether HSB offers diverse access or only a second logical service over common plant. Buying two HSB lines does not create independence if both use the same partner switch and Navkar handoff.

Households may reasonably choose price and local support over full redundancy. The issue is disclosure. A low-cost city service can be valuable even with one upstream and best-effort repair. The bill becomes misleading only if ordinary reachability is presented as engineered diversity. HSB's public material does not make a current redundancy claim, which is better than an unsupported promise, but it also gives customers almost no basis for comparison.

What would turn the downgrade into a stronger case

The first missing item is a service and subscriber reconciliation. HSB should explain how the app's thousands claim relates to the 39 subscribers reported at June 2025 and provide a current count split among household, business, bulk-building and cable-operator accounts. It should identify which legal entity bills each class. This would establish scale without disclosing customer names.

The second is a physical network inventory. A useful summary would show points of presence, distribution nodes, access technologies, route kilometres, owned versus leased segments and the number of customers behind each failure domain. Sensitive street-level detail need not be public, but an enterprise buyer or auditor should be able to inspect it under confidentiality.

The third is an upstream and route schedule. HSB should state the number and capacity of Navkar circuits, handoff sites, physical carriers, street-route separation and power independence. Any second carrier should be visible in a tested failover or supported by a contract and route configuration. Two cables in one duct should be described as common-risk, not diverse.

The fourth is a power schedule. For every active node, HSB should identify normal supply, battery capacity, measured runtime at current load, generator availability where applicable and the last full discharge or transfer test. Customer equipment should be outside the provider guarantee unless HSB supplies backup there.

The fifth is field-repair evidence. HSB and each cable-operator partner should maintain an escalation list, technician coverage, building-access contacts, splice and device spares, and fault records showing acknowledgement, arrival and restoration times. Median performance alone is not enough; the longest outages reveal whether staffing survives difficult conditions.

The sixth is capacity evidence. Thirty days of busy-hour measurements, customer-serving-node utilisation, packet loss, latency and jitter would show whether the network meets the service sold. A controlled upstream failure should demonstrate that backup capacity, if any, carries expected demand. HSB should also state its public-address and IPv6 policy.

The seventh is basic customer-channel repair. The main domain should contain current plans, legal identity, service area, support contacts, complaint escalation and a status page. The payment portal needs a valid certificate and clear operator identity. These do not make fibre more diverse, but they reduce avoidable friction and provide a way to communicate during faults.

None of these requests is exotic for a connectivity supplier. They translate vague resilience into inspectable facts. HSB already has some foundations: a current licence, a current route, its own ASN, its own address block and valid route-origin security. The unanswered questions sit below and beyond that edge.

HSB is live at the internet edge and opaque underneath it

The original hypothesis was a regional ISP whose bill depends on access plant, upstream routes and field repair. The evidence supports only the second half without qualification. HSB's internet edge is live. Its two /24s are visible, correctly originated and protected by valid route-origin authorisations. The licensed company is current in the Department of Telecommunications list, and its principal, address, phone and brand align with the older number-resource holder and customer app.

The regional scale does not survive. The company markets one city, not a broad region. The latest named regulator return is 39 broadband subscribers. The claim of thousands remains unreconciled. One network, Navkar Supertech, is the only observed BGP neighbour. The access medium, physical route, circuit count, partner ownership, point of presence, power protection, spare stock and restoration performance are all undisclosed. Customer-facing web maintenance is visibly weak.

This does not make HSB fictional or necessarily unreliable. It makes it small, bounded and difficult to evaluate. A local ISP can create real value by knowing buildings, responding quickly and reaching customers that larger providers overlook. Its resilience is then carried as much by accurate cable knowledge, a nearby technician and a spare optical device as by an autonomous-system number.

The network evidence is best graded Medium for current operation and Weak for physical resilience. HSB has crossed the threshold from a name to a routed and licensed service. It has not crossed the threshold from reachability to demonstrated redundancy. Until it does, customers should read the monthly bill as payment for a live Ulhasnagar path whose visible upstream is Navkar and whose local repair chain remains to be proved.