IBSS Nepal and the Economics of Visible Yet Dependent Internet Infrastructure

IBSS Nepal and the Economics of Visible Yet Dependent Internet Infrastructure

Research Thesis

IBSS Nepal is a small but analytically useful case study, because it distinguishes three elements often conflated in public debate about internet companies: the ownership of visible Internet number resources, the control of physical connectivity, and the commercial promise of managed services for businesses. Public records show an enterprise-focused Kathmandu-based Internet service provider (ISP), a network service provider, with visible Autonomous System records in APNIC, portable IPv6 resources, RPKI-validated emitted prefixes, NPIX peering, and an active website selling enterprise fiber, public IP addresses, managed services, enterprise Wi-Fi, campus networks, hotel networks, web/cloud services, and network consulting. It does not show, with the same clarity, a large national access network, independently controlled international capacity, a fully documented ownership chain, or a clear and unambiguous relationship between the brand, the legal entity, the registry holder, and the successor network identity. This gap is the central economic fact. IBSS Nepal's value is not so much that of a mass broadband brand, but rather that of a semi-visible infrastructure intermediary: a company capable of pooling scarce public IP address space, local peering, last-mile execution, support workforce, and vendor integration into professional-grade connectivity in a market where upstream bandwidth, regulatory approvals, foreign exchange clearances, tax disputes, and vendor concentration can dominate unit economics. APNIC records associate AS18395 and AS23672 with "I.B.SYS. Solution Nepal Pvt. Ltd." and ORG-IN13-AP / "IBSS Nepal", while the active website presents IBSS Nepal Pvt. Ltd. as an enterprise broadband and network solutions provider.

The evidence supports a two-part thesis. First, IBSS Nepal appears to position itself economically as a niche enterprise access and managed network services provider rather than a mass-market ISP. Its own materials emphasize enterprise-grade SLAs, dedicated public IP addresses for SMEs and business plans, professional fiber, point-to-point leased line vocabulary, managed monitoring, hotel Wi-Fi, campus connectivity, corporate networks, cybersecurity, and data center support services. Its FAQ states that service is 'only in Kathmandu', while the homepage mentions coverage inside the Kathmandu valley and expansion across the country, a common ambiguity for operators whose commercial reach exceeds their physically held access footprint.

Second, network records show that visible Internet number resources confer credibility but not full autonomy. AS23672 is currently the most important active entity: BGP.tools records it as active, emitting several IPv4 prefixes and an IPv6 allocation, with valid RPKI for listed routes, and with a visible upstream/peer dependency on AS151396 Sajilo Net. NPIX lists IBSS Nepal Pvt. Ltd. as a full member on AS23672 with a 10 Gbps connection to NPIX DataHub, an open peering policy, and no route server client status. However, historical and adjacent records introduce ambiguity: AS18395 remains in IBSS's APNIC registry context, but Hurricane Electric indicates it has not been visible in the global routing table since January 2024; PeeringDB still keeps AS56196 as "IBSS Nepal Internet" at the NPIX DataHub exchange point; and the old IBSSNET-NP role/abuse records are mixed with Airwave contact information.

Identity: a brand, a registry entity, and a set of names

The canonical operational target is best described as IBSS Nepal, operating publicly under the name IBSS Nepal Pvt. Ltd. and appearing in APNIC registry documents under ORG-IN13-AP / "IBSS Nepal" and in aut-num descriptions as "I.B.SYS. Solution Nepal Pvt. Ltd.". The current APNIC WHOIS record for AS18395 states as-name: IBSYS-AS-AP, description "I.B.SYS. Solution Nepal Pvt. Ltd.", country Nepal, organization ORG-IN13-AP, abuse contactabuse@ibssnepal.com.np, and an address in Kathmandu, Ram Mandir Marg, Battisputali. The APNIC organization entity identifies "IBSS Nepal" as a local Internet registry, with emailinfo@ibssnepal.com.npand the same phone and address pattern. AS23672 carries the same APNIC identity.

The namespace is not clean. The 2013 NPIX announcement welcomed "IBSS Nepal Pvt. Ltd." and described "Integrated Business System Solution Nepal Pvt. Ltd." as a Kathmandu ISP providing Internet via wireless and fiber. JobsNepal describes IBSS Nepal Pvt. Ltd. as established in 2007 and part of a "syndicate of independent business groups", with ambitions in networking, wireless Internet services, telecom solutions, and IP telephony. LinkedIn presents "IBSS Nepal Pvt. Ltd." as an ISP and managed network service provider for the enterprise sector, founded in 2007, headquartered in Kathmandu, with 11-50 employees, but also lists the company type as "Partnership". These are not fatal contradictions, but they matter economically because registry control, operational control, and shareholder control can diverge in small ISP markets.

The strongest operational identity is therefore: IBSS Nepal is an enterprise ISP and network services operator based in Kathmandu, active under the IBSS Nepal Pvt. Ltd. brand, using visible APNIC resources linked to I.B.SYS. Solution Nepal Pvt. Ltd. and ORG-IN13-AP. The unresolved question is whether "IBSS Nepal", "IBSS Nepal Pvt. Ltd.", "I.B.SYS. Solution Nepal Pvt. Ltd.", and the old records "IBSSNET-NP / IBSS Nepal Internet" refer to a single continuous business owner, a brand evolution, a registry cleanup, or a relationship with another operator such as Airwave. This distinction would change the economics: a continuous owner has resource continuity and accumulated customer capital; a successor brand may have inherited useful number resources without full customer continuity; a reseller or affiliated brand may rely more heavily on upstream and parent infrastructure than its public website implies.

What the company sells: professional access plus managed ambiguity

IBSS Nepal's public offering is not a pure access product. The homepage markets "IBSS Internet Services" with enterprise-grade SLAs, multiple redundancies, backup plans, global terminations, domestic peering, international peering with a Tier 1 network, and support systems. It highlights 24-hour fiber optics, high-speed professional broadband, public IP addresses for SME and enterprise plans, fast installation, 24/7 support, engineering staff, and a wide range of products from broadband and intranet to web hosting, hardware, and network peripherals. This is a service bundle rather than a simple bandwidth proposition.

The dedicated broadband page pushes the same bundle upmarket. It addresses business customers, large corporations, and multinationals; uses leased line vocabulary; promises dedicated bandwidth, symmetric upload and download speeds, network redundancy, proactive monitoring, managed services, static IP, bundled voice lines, and Microsoft Office 365 tools. The economic meaning is that IBSS attempts to convert bandwidth from a commodity to a managed services contract. A typical residential ISP competes mainly on Mbps, price, bundled TV offers, and installation speed. An enterprise ISP can also charge for availability, static addressing, local loop resilience, firewall/routing design, monitoring, account management, and operational hassle reduction.

The enterprise solutions page expands the addressable market to hotels, colleges, higher education institutions, and corporate networks. It offers hotel Wi-Fi for star-rated hotels, Campus Connect for educational institutions, corporate network design using vendors such as Extreme Networks, Cisco, and Juniper, and cybersecurity services. The managed services page adds network monitoring, network-level support, service relationship management, project supervision, data center support, and network consulting. These pages do not prove that IBSS owns a large data center or a nationwide fiber backbone; they prove that IBSS sells itself as the party capable of assembling connectivity, equipment, support labor, and vendor products into an operational service.

The customer interface reinforces this economy. The "Getting Started" page states that the technical team installs an ONT at the customer's premises, the customer connects a router, and a portal/mobile app is used for bills, data consumption, plan upgrades, and support tickets. The FAQ specifies that IBSS offers high-speed Internet, dedicated business bandwidth, and custom network solutions; it currently provides services only in Kathmandu; technical issues are supposed to be resolved within two hours; installation takes one to two business days; routers are not included in the installation package; IBSS applies a fair use policy; and payments include online payments, bank transfers, eSewa, and Khalti. This is operationally important because it reveals a hybrid between enterprise service and mass ISP process: portal billing and fair use policy imply a standardized access economy, while dedicated bandwidth and SLA language imply premium service segmentation.

Geography and network layer

The public footprint is concentrated in Kathmandu. The website shows a coverage map of the Kathmandu Valley and states that IBSS has wide network coverage inside the Kathmandu Valley, while the FAQ specifies that service is currently only in Kathmandu. The current NPIX member listing places IBSS's exchange connection at NPIX DataHub in Kathmandu, and APNIC contact addresses place the organization in Battisputali, Kathmandu. Old NPIX documents from 2013 described IBSS as a Kathmandu ISP using wireless and fiber. Together, these sources indicate a metropolitan enterprise access operator, not a proven nationwide fixed-access platform.

The network layer footprint is more substantial than a mere web hosting shop, but smaller than Nepal's major mass-market ISPs. AS23672 is active and emits several IPv4 prefixes and a /32 IPv6 allocation. BGP.tools classifies it as an "Eyeball" network, ranks it within Nepal for traffic estimates, unique domains, emitted IPv4 space, and emitted IPv6 space, and shows current emission of five /24 IPv4 blocks plus a /32 IPv6 allocation. APNIC's IPv6 record shows 2402:3020::/32 as a portable IPv6 resource allocated to IBSYS-NP, associated with I.B.SYS. Solution Nepal Pvt. Ltd. This is real evidence of network infrastructure: it means IBSS is not simply a reseller without a routing identity.

Yet the layer evidence is uneven. AS18395, the ASN given in the user's starting evidence, remains in APNIC's public context under the same IBSS/I.B.SYS organization, but Hurricane Electric indicates that AS18395 has not been globally visible since January 4, 2024, and had only a single IPv4 prefix in the historical view. The economically relevant inference is not that AS18395 is worthless; it is that the live production network seems to have moved to AS23672 and possibly records tied to AS56196. In small ISP markets, inactive ASNs can still hold option value, documentary value, or legacy customer value, but live BGP visibility is what reveals actual traffic-carrying production.

AS56196 adds a second layer of ambiguity. PeeringDB lists "IBSS Nepal Internet" on AS56196, with public peering at NPIX DataHub and IPv4/IPv6 addresses, while the current NPIX member page lists IBSS Nepal Pvt. Ltd. as AS23672 at NPIX DataHub with the same exchange IPv4 address and indicates that IPv6 is not enabled and the route server client flag is "No". Hurricane Electric shows AS56196 as visible, with two emitted prefixes, valid RPKI status, and observed peers including Ncell and Sajilo Net. This could be an obsolete PeeringDB record, a migration from AS56196 to AS23672, dual AS operation, or a downstream/client routing relationship. The economic significance is clear even if the business fact is unresolved: external databases may overestimate or mislabel operational control, so counterparties must assess IBSS's network capacity using live BGP, NPIX, APNIC, and contractual evidence jointly, not a single database.

Visible Internet number resources as economic assets

IBSS Nepal's visible number resources matter because they are scarce coordination assets. ASNs, route entities, RPKI-validated prefixes, and public IP assignments give a company a place in the global routing system. They also make the company legible for customers who need static IPs, VPNs, hosted services, whitelists, firewall rules, point-to-point connectivity, and remote monitoring. IBSS's website explicitly advertises dedicated public IP addresses for all SME and enterprise plans. This is not just a technical feature; it is a monetizable complement to enterprise connectivity, especially when IPv4 addresses are scarce and business customers need stable addressing for inbound services, VPN endpoints, CCTV/NVR access, payment systems, office servers, remote administration, or cloud access controls.

The IPv4 evidence suggests a modest but significant resource base. BGP.tools lists AS23672 as emitting five /24 IPv4 prefixes and a /32 IPv6 prefix, the listed routes carrying valid RPKI certification. IPinfo and DB-IP mirrors show AS23672 associated with approximately 1,280 to 2,048 IPv4 addresses depending on counting method and route visibility, while some historical or secondary records attach Airwave or other labels to certain ranges. The exact address count is less important than the economic structure: a few /24s are enough to sustain a profitable enterprise ISP or managed access niche, but not enough to make public IP assignment an unconstrained product. Public IPs can become a margin lever because the operator can ration them, bundle them with higher-tier plans, or reserve them for customers with higher willingness to pay.

RPKI validity is an underappreciated quality signal. It does not prove customer satisfaction, network diversity, or ownership clarity. It shows that the resource holder or its routing administrator has created a route origin authorization matching visible announcements. In a market where small networks often operate on legacy records, stale route entities, and third-party operational help, valid RPKI reduces one category of operational risk: accidental or malicious route origin conflicts. For enterprise buyers, the value is indirect. A valid RPKI posture will not make a weak last mile reliable, but it improves the credibility of the provider's routing hygiene and reduces the likelihood of traffic being rejected by networks enforcing route origin validation.

A local exchange point presence has a different economic role. NPIX states its purpose is to help ISPs keep local traffic local, and the current member page shows IBSS Nepal Pvt. Ltd. as a full member with a 10 Gbps connection to NPIX DataHub. Local peering can reduce upstream transit costs, lower latency to domestic services, improve resilience for national traffic, and make a small ISP more credible to business customers whose users consume local content, government services, payment gateways, domestic cloud, and other Nepal-hosted resources. But NPIX also lists IBSS as not a route server client. This may mean IBSS relies on bilateral sessions rather than the route server, or the public listing is incomplete; either way, an open peering policy does not automatically equal full domestic reach.

Supplier dependence: upstreams, facilities, equipment, and foreign exchange

IBSS Nepal's economics are heavily supplier-dependent. The live AS23672 record on BGP.tools shows AS151396 Sajilo Net as its visible upstream/peer for IPv4 and IPv6. Sajilo Net is itself a Nepali ISP whose BGP.tools profile shows it peering with several networks and using WorldLink International Transit Services as upstream; IPinfo similarly lists AS151396 peers including AS23672 and upstream AS45274 WorldLink International Transit Services. If this live route view reflects IBSS's current production dependency, then IBSS's wholesale bargaining position is not that of a large national operator buying diversified international transit directly at scale. It is closer to a downstream or lateral customer of another domestic ISP/network service provider, with exposure to that provider's transit quality, payment discipline, routing policy, and capacity planning.

The APNIC import/export policy is broader than the live BGP view. The APNIC WHOIS record for AS23672 lists imports from AS135327, AS4613, AS58504, and AS45845 and exports to these ASes. These names suggest historical or intended routing relationships with Asianet, Mercantile, TechMinds, and NIIG/other Nepali networks, but the current live BGP.tools view emphasizes Sajilo. This divergence is common: IRR and WHOIS policy entities can outlive changed business arrangements. Economically, stale policy data can create a false impression of transit diversity. For a buyer of IBSS services, the important question is not whether the old route policy entities name multiple networks; it is how many paying upstreams are active, provisioned with capacity, contractually committed, and independently routed today.

Facility dependence is also visible. NPIX lists IBSS's exchange connection at NPIX DataHub, and DataHub markets itself as a cloud hosting and data center service provider in Nepal, with colocation, backup, disaster recovery, DNS, firewall as a service, entity storage, private cloud, public cloud, and related services. A 10 Gbps NPIX port at DataHub is useful infrastructure, but it also means IBSS's peering economics depend on the exchange fabric, the facility, cross-connects, power, and physical access. If IBSS sells data center support or enterprise connectivity around this ecosystem, the company can capture service margin without owning the facility. This is not a weakness per se; it is a capital-light model. The risk is that the customer may perceive "data center solutions" as owned infrastructure when public evidence supports a support/integration role more strongly than facility ownership.

Equipment and vendor dependence is embedded in the service offering. IBSS names Extreme Networks for switching and Cisco and Juniper for routing and firewall in its enterprise network product. This can be valuable for quality perception, but it imports purchasing exposure: hardware costs in foreign currency, lead times, spare parts, support contracts, licenses, software subscriptions, and certification labor. For a small provider, gross margin on managed network can be attractive when equipment resale and support are bundled with monthly service, but purchasing leverage is limited. The provider must either pass equipment costs to customers, carry inventory, or standardize designs enough to avoid balance-sheet strain.

The biggest supplier-related risk in Nepal is not the vendor brand; it is international bandwidth and the state's role in foreign exchange clearance. In May 2024, AP reported broadband disruptions across much of Nepal after Indian vendors, from whom many private Nepali operators source bandwidth, cut service due to payment defaults. Private ISPs said they could not pay Indian bandwidth vendors because the government had not provided foreign exchange access while tax disputes remained unresolved; AP quoted Wlink saying its upstream vendor had disconnected internal links due to non-payment and inability to obtain government foreign exchange clearance. Kantipur reported before the disruption that ISPAN stated about 70% of Nepal's international bandwidth came from Airtel and that payments had been blocked for months amid disputes over maintenance fees and RTDF obligations.

For IBSS Nepal, no public source examined here proves a specific 2024 outage or non-payment event for the company. The sector-wide event nevertheless changes how its economics should be interpreted. A small ISP can present redundancy, peering, and support while being exposed to upstream payment chains and regulatory bottlenecks beyond its control. When the binding constraint is foreign exchange recommendation, tax interpretation, or a large upstream vendor's credit tolerance, the quality of the last-mile team matters less than the credit and regulatory situation of the upstream supply chain. This is the central lesson: in Nepal, outsourced connectivity is not a simple input; it is a political-financial dependency with outage characteristics.

Revenue logic and margin pressure

The likely revenue logic of IBSS Nepal is a three-part bundle. The first part is recurring Internet access: dedicated or semi-dedicated fiber broadband sold to SMEs, offices, corporations, colleges, and hotels. The second part is ancillary revenue: static/public IPs, voice lines, cloud or hosting, Microsoft tools, cybersecurity, managed Wi-Fi, hardware, firewall/routing, portal billing, monitoring, and support. The third part is project revenue: campus networks, hotel Wi-Fi design, enterprise LAN/WAN, data center support, and consulting. The website directly supports all three categories, although it does not disclose prices, customer numbers, revenue, or margins.

The margin profile is likely uneven. Basic bandwidth has the worst price dynamics because large Nepali ISPs can spread upstream capacity, advertising, billing systems, installation crews, and customer support over a much larger customer base. IBSS's best margin opportunities lie in higher-value-add enterprise support, managed Wi-Fi, static IP assignments, network monitoring, and customer-specific design. These services are less comparable on advertised Mbps. They also create relationship-based switching costs: a business that has firewall rules, public IP whitelists, VPN endpoints, on-site ONT placement, Wi-Fi controllers, switch configurations, VLANs, monitoring dashboards, and ticket history with a provider does not change as easily as a residential household picking a cheaper annual plan.

Pricing power thus comes less from monopolistic access than from operational embeddedness. IBSS can charge above basic access rates when the buyer values availability, fast local engineering response, static addressing, network design, and a single accountable point of contact. The two-hour support target in its FAQ and the one-to-two-business-day installation window are commercial signals: the company sells reduced downtime and coordination costs, not just raw bandwidth. But this pricing power has a ceiling. Enterprise buyers in Kathmandu can comparison-shop against larger ISPs and system integrators, and large customers may be able to multihome, negotiate direct service with larger operators, or demand SLAs with penalties.

Gross margin pressure comes from six sources. Upstream transit and domestic backhaul consume recurring costs. Field installation and repair consume labor and vehicles. ONTs, routers, switches, firewalls, fiber, cables, and spares introduce imported hardware exposure. Power, batteries, UPS systems, and facility/interconnection fees add fixed costs. Support and account management increase labor intensity, especially for business customers. Finally, regulatory fees, levies, RTDF obligations, tariff approvals, tax disputes, and foreign exchange clearances create working capital risk. Nepal's Telecommunications Act framework has been interpreted as requiring ISPs to pay a royalty and RTDF contribution, and Republica reported in 2025 that ISPs must pay 4% of revenue as royalty and 2% as RTDF, with litigation over whether maintenance fees are included.

The regulatory cost is not simply a percentage. It can become an input supply shock. New Business Age reported that the government suspended foreign exchange recommendations for international bandwidth payments while royalty and RTDF arrears remained unresolved, and Airtel cut services in May 2024 due to unpaid fees from Nepali ISPs. This mechanism turns a tax interpretation into a network quality event. For a provider like IBSS, whose public materials emphasize redundancy and support, the risk is that even good local operations can be compromised by sector-level upstream payment blockages.

Competition, substitutes, and buying power

The ISP market in Nepal is crowded. The 2025 industry update by SAMENA, citing Nepalitelecom, states that Nepal had 107 licensed ISPs, many operators have fewer than 20,000 customers, and the NTA was considering ISP mergers because the number of providers was becoming difficult to manage. The same source states that WorldLink leads with over 10 lakh customers, Nepal Telecom and DishHome have over 3 lakh customers, and other major operators average over 2 lakh customers. HimalPress, citing the NTA, reported that mobile broadband still accounts for over 89% of broadband subscriptions in Nepal, while fixed wired broadband is about 10.65%, with around 3.1 million fixed wired subscriptions and FTTH driven by ISPs.

This structure is important for IBSS. If the company had tried to compete as a mass-market consumer ISP, it would face the scale advantages of large players in marketing, international bandwidth purchasing, device procurement, TV/content bundles, call centers, and geographic density. Its public posture instead resembles a niche strategy: enterprise broadband, SME plans, colleges, hotels, and managed networks. This strategy is rational in a crowded market because the operator can trade scale for service intensity. A small ISP can survive if it has relationships in a dense commercial geography, responds faster than larger competitors, and bundles integration work that major ISPs consider outside their core product.

Buying power differs by segment. Small offices and SMEs have moderate buying power because they can compare fixed broadband plans and may not need deep customization. Large enterprises, hotels, and campuses have greater price negotiation power but also higher switching costs once the provider controls LAN design, Wi-Fi deployment, public IP assignment, and monitoring. Colleges and hotels are attractive because guest/user density creates high bandwidth demand and support sensitivity, but these customers may also demand SLAs, redundancy, and on-site response. IBSS's public promise to contact enterprise prospects within 24 hours and provide tailored solutions indicates a consultation-based sales model rather than self-service plan selection.

Substitutes include direct service from large ISPs, Nepal Telecom enterprise products, mobile broadband for backup or small offices, fixed wireless, other managed service providers, system integrators, and, in some cases, cloud-hosted applications that reduce the need for on-site static IP infrastructure. However, these substitutes are imperfect. Mobile broadband can serve as backup for an office but cannot fully replace symmetric professional fiber for many businesses. A system integrator can design the LAN/Wi-Fi but may not control public IPs, routing, or last-mile support. A large ISP may offer better upstream diversity but weaker personalized service for a small or medium business. IBSS's economic niche lies in the gaps between these substitutes.

Ownership, financing, management, and control context

Public evidence of ownership is thin. The active website gives contact details and product pages, but no shareholder register, audited financials, board of directors, capital history, or M&A transactions. LinkedIn indicates the company was founded in 2007, has 11-50 employees, and is a "Partnership" type, while JobsNepal describes a 2007 founding and a "syndicate of independent business groups". Tracxn describes IBSS Nepal as an unfunded Kathmandu-based company founded in 2007 providing wireless/fiber Internet, but this is a secondary aggregator, not a legal filing. No public filing examined here proves external equity funding, debt financing, acquisition, sale, or a named controlling shareholder.

The control question is complicated by legacy records linked to Airwave. An APNIC abuse role for IBSSNET-NP shows "IBSS Nepal Pvt. Ltd - network administrator" but listsabuse@airwave.com.npandkniroula@airwave.com.npin the abuse/validation context. A separate document for AS23866 shows IBSSNET-NP / "IBSS Nepal Internet" as inactive in some mirrors, while another nearby APNIC record associates AS23866 with Airwave Pvt. Ltd. These facts do not prove that Airwave owns IBSS Nepal, that IBSS owns Airwave resources, or that there was an M&A event. They prove that old registry documents and abuse contacts interleave IBSSNET-NP and Airwave in a way that should be resolved before attributing control value to legacy ASNs or IPv4 blocks.

Economically, each interpretation leads to a different model. If IBSS is independent and simply has stale records linked to Airwave, the issue is record hygiene and reputational due diligence. If IBSS operates as a brand or affiliate within a broader Airwave/Sajilo/partner network chain, then its cost base and resilience depend heavily on the upstream infrastructure and contracts of related parties. If IBSS provides routing, addressing, or managed services for downstream networks whose records retain old descriptors, then the company may have a wholesale or network management business not fully visible on its public website. If resources were transferred or re-documented toward 2025, as the recent APNIC organization updates suggest, then the most important question is whether customer contracts, IP rights, and routing control were transferred together.

APNIC records have been recently changed: AS18395 and AS23672 show a last modification in March 2026, and ORG-IN13-AP shows recent organizational changes in 2025. This could mean ordinary registry maintenance, resource cleanup, abuse contact validation, control migration, or preparation for operational changes. Without legal filings, the safest conclusion is not that IBSS changed ownership, but that its public registry layer is actively maintained. In a small ISP, active registry maintenance is itself significant because it implies someone has operational access to APNIC entities, maintainer credentials, abuse contacts, and route authentication processes.

Regulatory and quality-of-service risks

IBSS operates in a regulated telecommunications environment. The NTA license fee page states Internet service license fees including messaging of NR 300,000 and renewal fees of NR 270,000. An NTA MIS report from Ashoj 2076 shows "I.B.Sys.Solution Nepal Pvt. Ltd., Sinamangal, Kathmandu" renewing an Internet service license with messaging, and the same MIS annex lists IBSS Nepal Pvt. Ltd. with 350 wireless subscribers, 759 fiber, and 1,109 total Internet subscribers in that 2019 reporting period. This older subscriber count should not be taken as current, but it is useful as a scale anchor: IBSS was publicly recorded as a small operator compared to WorldLink, Subisu, Vianet, and Classic Tech at that time.

IBSS appeared in at least one public complaint about regulatory payments. The Himalayan Times reported in 2018 that the NTA warned eight ISPs, including "IBSS Nepal of Old Baneshwor", to settle outstanding fees or face legal action. This is dated and does not prove current delinquency. It shows that IBSS has been subject to the same fee compliance regime that later became a sector-wide dispute over maintenance fees, RTDF, and foreign exchange recommendations.

No public evidence examined here shows a major IBSS-specific outage, cyber incident, court judgment, license cancellation, customer class action, supply dispute, or major abuse event. This absence should be interpreted with caution. Small ISPs often leave few searchable public traces unless the regulator names them, customers post complaints, or routing/security events are externally indexed. The absence of public incidents is not evidence of high service quality; it is only the absence of visible negative signals in the sources examined.

License fragility is a sector risk. Republica reported in 2024 that the NTA revoked the licenses of C Data Communication and Life Net, one for not operating according to conditions and the other for not initiating renewal. Another report described the NTA revoking licenses of United Telecom, Max Net Solution, and Chitwan Network for renewal failures. These were not IBSS cases, but they illustrate the regulator's ability to remove inactive or non-compliant operators. In a market with many small ISPs, license renewal and fee compliance are not administrative afterthoughts; they are part of the business model.

Infrastructure service ambiguity as a business model

The most interesting feature of IBSS Nepal is not that it is obscure. It is that its obscurity is economically functional. The company's public website allows it to look like an enterprise ISP, a managed services provider, an enterprise Wi-Fi integrator, a web/cloud services provider, and a data center support company. Its registry layer allows it to look like a real network operator, with ASNs, IP resources, RPKI-validated routes, and exchange presence. Its dependency layer suggests it may rely heavily on domestic upstream providers, facility vendors, and supplier ecosystems. These three surfaces are not contradictory. They constitute the normal production function of a small infrastructure services company.

This ambiguity creates commercial flexibility. IBSS can sell to a hotel as a Wi-Fi and bandwidth solution, to a college as campus connectivity, to an SME as static IP fiber, and to a corporation as network support. It can use public IP resources and BGP visibility as trust signals while outsourcing parts of international capacity and facility infrastructure. It can compete with large ISPs by offering more personalized support and against system integrators by bundling actual connectivity. In other words, the company monetizes coordination costs. Its product is not just Internet access; it is reducing the customer's need to coordinate among ISP, router vendor, firewall vendor, Wi-Fi installer, data center provider, and help desk.

The same ambiguity creates due diligence risk. A customer or investor must ask which parts of the service are owned, leased, resold, integrated, or simply arranged. "Domestic peering" is supported by NPIX evidence; "international peering with a Tier 1 network" is less directly proved by live BGP for AS23672, which visibly depends on Sajilo Net. "Data center solutions" are presented as support services rather than owned data center facilities. "Wide network coverage" inside the Kathmandu Valley is plausible, but the FAQ's "only in Kathmandu" limits national interpretation. "Dedicated public IP addresses" are supported by the company's public claim and visible number resources, but exact IP assignment policy and usage are unknown.

Alternative hypotheses and what each would change

The baseline hypothesis is that IBSS Nepal is an independent Kathmandu-based enterprise ISP and managed network provider with live routing on AS23672, local peering at NPIX DataHub, modest IP resources, and upstream dependence on Sajilo Net or related domestic providers. Under this model, the company's economics are viable if it maintains dense enterprise accounts, converts public IPs and support into premium pricing, and avoids a commodity price war with large FTTH providers. The main constraints are purchasing leverage, upstream concentration, regulatory fees, and working capital exposure.

A second hypothesis is that IBSS is a successor or cleaned-up continuation of the old IBSSNET-NP / IBSS Nepal Internet resources, with AS18395 and AS56196 representing legacy or transitional routing identities. This would explain why AS18395 remains in APNIC records but is not active, why PeeringDB still shows AS56196 at NPIX, and why NPIX currently lists AS23672. Under this model, the economic asset is continuity: the company may have accumulated customer relationships, regulatory approvals, and address resources across multiple network identities. The risk is documentary friction: outdated databases can confuse customers, peers, abuse reporters, and regulators.

A third hypothesis is that IBSS's registry resources or operating rights are nested with Airwave or another partner. The Airwave-linked abuse contacts in old IBSSNET-NP documents and secondary IP range labels make this plausible but unproven. If true, the company's economics would depend on related-party arrangements: who owns the IPv4 space? Who controls the route entities and RPKI? Who pays APNIC fees? Who signs upstream transit contracts? Who bears outage penalties? Related-party infrastructure can be efficient if it reduces costs, but risky if customers do not know where responsibility lies.

A fourth hypothesis is that IBSS has only a small owned access footprint and relies heavily on upstream/backhaul/facility partners while selling a high-value-add managed services wrapper. This is common and commercially rational. It would mean the company's durable advantage is not hardware infrastructure scale but customer proximity, engineering responsiveness, static IP capability, and local business relationships. Under this model, gross margin is protected by services rather than bandwidth, and the main threat is large ISPs moving downmarket into managed enterprise support.

A fifth hypothesis is that the public footprint underestimates IBSS's activity because many enterprise service contracts, campus networks, or managed Wi-Fi deployments are not publicly named. The website's offerings for hotels, colleges, enterprises, and campuses could represent real deployments that do not appear in press releases. If true, the public BGP scale would underestimate the economic scale because managed LAN/Wi-Fi and support revenue can be significant without large emitted address space. The monitoring point would be hires, partner certifications, project references, and named customer case studies rather than just BGP prefixes.

What the evidence proves, suggests, and leaves open

The evidence proves that IBSS Nepal is an active public-facing enterprise broadband and network services brand in Kathmandu; that APNIC associates AS18395 and AS23672 with I.B.SYS. Solution Nepal Pvt. Ltd. and ORG-IN13-AP / IBSS Nepal; that AS23672 is active and emits RPKI-valid prefixes; that IBSS Nepal Pvt. Ltd. is listed as a full NPIX member with a 10 Gbps DataHub connection; that the company markets public IPs, professional fiber Internet, enterprise Wi-Fi, campus networks, cybersecurity, managed services, and data center support; and that old public regulatory documents recorded IBSS as a small ISP and renewing a license in Nepal.

The evidence suggests, but does not prove, that IBSS's current production network is centered on AS23672 rather than the starting AS18395; that it has passed through or alongside AS56196/IBSS Nepal Internet records; that it has significant dependence on domestic upstream providers; that its public IP pool is commercially valuable but limited; that its address and registry history may involve stale Airwave-linked records or a legacy relationship; and that its market strategy is niche enterprise service rather than mass national broadband.

The evidence leaves open the legal shareholder identity, audited financial position, exact customer count today, current license status beyond public lead indicators, exact upstream contracts, whether all announced resources are owned or managed on behalf of others, whether the Airwave-linked records reflect stale data or economic control, whether the company owns substantial fiber infrastructure outside the Kathmandu Valley, and whether its claimed redundancy includes independently contracted international transit or only upstream-provided redundancy. These unresolved facts are not peripheral. They determine whether IBSS should be assessed as a small asset-owning ISP, a managed services wrapper on partner networks, a successor to old number resources, or a hybrid of all three.

Evidence register

1. APNIC WHOIS for AS18395. Primary registry evidence linking the starting ASN to IBSYS-AS-AP, "I.B.SYS. Solution Nepal Pvt. Ltd.", country Nepal, ORG-IN13-AP / IBSS Nepal, Kathmandu address, and IBSS abuse contacts.
2. APNIC WHOIS for AS23672. Primary registry evidence showing the same IBSS/I.B.SYS organization, imports/exports, abuse contact, and recent modification date for the currently most visible ASN.
3. APNIC WHOIS IPv6 for 2402:3020::/32. Primary resource evidence showing an allocated portable IPv6 block, netname IBSYS-NP, and ORG-IN13-AP association.
4. APNIC/RDAP mirror for AS23672. Secondary but detailed RDAP evidence listing ORG-IN13-AP, contact data, abuse validation, and IP ranges associated with AS23672.
5. BGP.tools AS23672. Live routing evidence showing active status, emitted IPv4 and IPv6 prefixes, valid RPKI, "Eyeball" classification, rankings, and visible upstream/peer relationship with Sajilo Net.
6. Current NPIX member page for IBSS Nepal Pvt. Ltd. Primary exchange evidence showing AS23672 as a full member, open peering policy, join date, 10 Gbps DataHub connection, IPv4 exchange address, no route server client status, and IPv6 not enabled in this listing.
7. Hurricane Electric BGP Toolkit for AS18395. Live/historical BGP evidence indicating that AS18395 has not been globally visible since January 2024 and previously showed a single IPv4 prefix.
8. Hurricane Electric BGP Toolkit for AS56196. Routing evidence for the adjacent ASN IBSS Nepal Internet, including emitted prefixes, valid RPKI status, and observed peers.
9. PeeringDB AS56196 / IBSS Nepal Internet. User-maintained interconnection database evidence showing older or parallel IBSS Nepal Internet peering records at NPIX DataHub, useful mainly for identifying ambiguity and possible obsolescence.
10. APNIC role entity for IBSSNET-NP. Adjacent primary registry evidence showing older IBSS Nepal administrator language with Airwave abuse contact fields, central to the control ambiguity question.
11. APNIC/WHOIS mirror for AS23866 / Airwave. Secondary registry evidence indicating that old IBSSNET-NP / IBSS Nepal Internet records are interleaved with Airwave Pvt. Ltd. in public databases.
12. IBSS Nepal homepage. Primary operational evidence for enterprise broadband positioning, SLAs, redundancy claims, Kathmandu Valley coverage, dedicated public IPs, 24/7 support, web hosting, intranet, hardware, and network services.
13. IBSS Dedicated Broadband page. Primary product evidence for enterprise fiber, leased line vocabulary, dedicated bandwidth, symmetric speeds, redundancy, monitoring, managed services, static IPs, and bundled tools.
14. IBSS Enterprise Solutions page. Primary product evidence for hotel Wi-Fi, Campus Connect, academic institutions, corporate networks, references to Cisco/Juniper/Extreme vendors, and cybersecurity.
15. IBSS Managed Services page. Primary product evidence for monitoring, network-level support, service relationship management, project supervision, data center support, and network consulting.
16. IBSS Getting Started page. Primary operational evidence for ONT installation, customer router connection, portal billing, data consumption, plan upgrades, support tickets, mobile app, and support channels.
17. IBSS FAQ. Primary evidence for the service-only-in-Kathmandu statement, service categories, two-hour support target, installation window, router policy, fair use policy, payment methods, and refund policy.
18. IBSS LinkedIn profile. Semi-public company-channel evidence for founding year, headcount range, headquarters, specialties, enterprise ISP positioning, and recent B2B marketing hires.
19. IBSS JobsNepal profile. Semi-public channel evidence for "syndicate of independent business groups" language, 2007 founding, and product ambitions in networking, wireless Internet, telecom solutions, and IP telephony.
20. 2013 NPIX announcement. Historical exchange evidence that IBSS Nepal joined NPIX and was described as a Kathmandu ISP providing wireless and fiber Internet.
21. NTA MIS Ashoj 2076 PDF screenshots. Regulatory/statistical evidence that I.B.Sys.Solution Nepal renewed an Internet service license with messaging in 2019 and that IBSS Nepal was listed with 1,109 total subscribers in that period.
22. NTA license fee page. Regulatory evidence for Internet service license fees including messaging and renewal fees in Nepal.
23. Himalayan Times 2018 NTA warning. Public regulatory risk evidence that the NTA warned IBSS Nepal and other ISPs to settle outstanding fees.
24. Kantipur April 2024, report on ISPAN/bandwidth dispute. Local press evidence for Airtel concentration, blocked foreign exchange recommendations, maintenance fee/RTDF dispute, and potential Internet disruption.
25. Associated Press May 2024, Nepal broadband disruption. International press evidence that Indian vendors stopped bandwidth service to private Nepali operators due to payment defaults and foreign exchange constraints.
26. New Business Age November 2024, report on fee dispute. Local business press evidence for Supreme Court-linked royalty/RTDF dispute, installment requests, suspension of foreign exchange recommendations, and impact on Airtel service.
27. Republica February 2025, report on Vianet fees. Local press evidence that ISPs are subject to 4% royalty and 2% RTDF obligations and that the applicability of maintenance fees was contested.
28. SAMENA/Nepalitelecom 2025 report on ISP mergers. Market structure evidence for 107 licensed ISPs, many small operators below 20,000 customers, scale tier of major players, and NTA interest in mergers.
29. HimalPress/NTA report on broadband subscribers. Market evidence for mobile broadband dominance in Nepal, fixed wired share, number of FTTH connections, and ISP role in fixed broadband.
30. Republica and other license revocation reports. Sector risk evidence that the NTA can revoke ISP licenses for non-operation or renewal failure, relevant for small-operator regulatory risk even if not IBSS-specific.
31. Sajilo Net BGP/IPinfo records. Provider context evidence for network role, peers, upstream relationship with WorldLink International Transit Services from AS151396, and relationship with AS23672.
32. DataHub public site and NPIX facility record. Facility-context evidence that IBSS's NPIX connection is at DataHub and that DataHub markets cloud hosting, colocation, DNS, backup, and other data-center services.

Monitoring points

1. AS23672 upstream diversity. A shift from visible single dependence on Sajilo Net to several independently active upstreams would improve resilience and bargaining power; increased concentration would increase outage and price risk.
2. AS18395 reactivation or removal. If AS18395 becomes visible again, it could indicate dual-homing, customer migration, or resource reuse. If it is formally withdrawn or transferred, it would clarify whether the starting ASN is legacy rather than operational infrastructure.
3. AS56196 / PeeringDB cleanup. Alignment between PeeringDB, NPIX, APNIC, and live BGP would reduce identity ambiguity. Persistent inconsistency would remain a diligence discount for counterparties.
4. Airwave-linked registry resolution. Any formal evidence that the Airwave records are obsolete, affiliated, transferred, or customer-related would materially change the analysis of legacy resource control and abuse liability.
5. RPKI and prefix-origin changes. New valid ROAs, additional emitted prefixes, or withdrawals would show whether IBSS is expanding, consolidating, or reconfiguring its number resource base.
6. NPIX route server client status and IPv6 enablement. Becoming a route server client or enabling IPv6 at the exchange would improve local reach and technical maturity; continued non-use may indicate limited peering automation.
7. Named enterprise references. Public case studies for hotels, colleges, banks, campuses, or larger SMEs would confirm the company monetizes managed enterprise service rather than merely promoting it.
8. Regulatory fees and license status. Any NTA notice, renewal failure, royalty/RTDF dispute, or tariff approval issue would affect service continuity and working capital more than ordinary commercial competition.
9. Foreign exchange and upstream payment policy in Nepal. Sector-level changes in foreign exchange recommendation, bandwidth payment clearance, or maintenance fee taxation will directly affect operators like IBSS even without specific IBSS fault.
10. Consolidation pressure. If NTA-backed ISP mergers accelerate, IBSS could become an acquisition target, a forced consolidator, or a niche survivor depending on customer quality and resource control.
11. Public IP monetization. A tightening of IPv4 availability or a shift in customer demand for static IPs would increase the value of IBSS's address inventory; widespread CGNAT acceptance or enterprise IPv6-only adoption would reduce that premium.
12. Evidence of owned fiber expansion outside Kathmandu. A verified fiber footprint beyond the Kathmandu Valley would shift the company from a metropolitan niche operator to a broader access network story.
13. Data center ownership versus integration clarity. Evidence that IBSS owns facility infrastructure would increase asset intensity and potential control; evidence that it only integrates third-party facilities would maintain the capital-light but vendor-dependent model.
14. Enterprise push by large players. If WorldLink, Vianet, Subisu, Nepal Telecom, DishHome, or other large ISPs aggressively bundle managed Wi-Fi, static IPs, security, and campus support, IBSS's service margin niche would face direct scale competition.
15. Customer-visible outage history. A pattern of public complaints or availability failures would weaken the SLA premium; a clean, verifiable service history would strengthen the case for a profitable enterprise niche.