Spider Net and the microeconomics of the small ISP layer in Bangladesh: route visibility, customer trust, and viability against upstream dependency

Summary

• What it says: Spider Net is not a company that can be understood through a conventional corporate profile.
• Main topic: Network-resource evidence; Peering and transit; Registry governance
• Context: Telecommunications / Company research / Asia-Pacific

Spider Net and the microeconomics of the small ISP layer in Bangladesh: route visibility, customer trust, and viability against upstream dependency

Spider Net is not a company that can be understood through a conventional corporate profile. Its public website provides little information. Its brand footprint is modest. Its corporate control record is incomplete. Yet, its network traces are unusually instructive. Spider Net appears in APNIC registries as a local Bangladeshi internet operator associated with ORG-SN17-AP, AS138651, an address in Chattogram, a /22 IPv4 allocation, and a /32 IPv6 allocation. Its visible routing is smaller than its registered address inventory. Its evidence of control over the retail market is stronger in a customer app than in a marketing site.

Its evidence-led relationships points to the practical dependency chain of broadband in Bangladesh: local access license, APNIC resources, upstream transit, NTTN backbone, IIG connectivity, payment rails, field repair, and customer trust.

The central conclusion is that Spider Net economically resembles less an autonomous “telecommunications company” than a compact bundle of scarce local rights and operational relationships. This bundle includes a BTRC upazila/thana ISP identity in Chattogram Sadar, an APNIC-registered network identity, a small routed IPv4 perimeter, a dormant or underused IPv6 resource, a billing and support channel via a mobile app, and a local contact surface. This bundle can generate real cash flows even when the company has little public media presence.

It can also become fragile if any of the many non-retail dependencies fails: route sponsorship, IIG terms, leased transmission, license renewal, customer support quality, payment channel reliability, or field repair density.

Evidence is thin on formal ownership, audited financial statements, litigation, funding, and management. It is stronger on network registration, public BGP visibility, license geography, customer control tooling, and the dependency structure on wholesalers. This asymmetry is the key point. In the fragmented broadband market of Bangladesh, the economic substance of many small networks is not visible in press releases or investor documents.

It is visible in who originates their prefixes, which upstream providers see them, whether RPKI is valid, whether customers can pay via bKash and open support tickets, whether the operator is listed in the ISP association and BTRC registers, and whether the license category confines the operator to a small geographic area.

Identity: a small ISP from Chattogram, not a well-defined corporate group

The most defensible canonical identity is “Spider Net,” a Bangladeshi network operator and local ISP identity linked to Chattogram. The APNIC organization registration for ORG-SN17-AP lists the organization name as Spider Net, the country as Bangladesh, the address as “7 No. Nabab Sirajjuddoula Road, Kotowali,” the phone number as +8801837686343, and the contact email as[email protected]. The APNIC registration classifies the organization as a local internet registry, not as a corporate group with subsidiaries or a public company reporting perimeter.

The same identity appears in the BTRC upazila/thana ISP license list. The official BTRC PDF line names “Spider Net,” places it in Chattogram Sadar, gives the address as “7 No. Nabab Sirajdulla Road, Kotowali, Chattagram,” and lists license number 14.32.0000.702.47.043.22.376.

The line also shows license validity until July 31, 2023, and a subsequent renewal date of August 1, 2023, in a document titled upazila/thana license list “dated 18-12-2024.” This creates ambiguity about the renewal status rather than a clear conclusion of an active license: Spider Net is clearly within the universe of official licenses, but the examined public line does not, by itself, prove that the license was active after the stated validity date.

The ISP Association of Bangladesh member list also contains a “Spider Net” profile, member number B-074, with the BTRC license category “Upazila/Thana,” an address at Anderkilla/Chittagong, the email[email protected], and the same mobile number that appears in the APNIC registers. The same ISPAB page also lists distinct entities with confusingly similar names, including Spider Mesh in Bogura and Spider Networks in Kuakata/Patuakhali. This is important because the public market contains several “Spider” broadband labels in Bangladesh, and only the Chattogram/Kotowali/AS138651 evidence matches the target studied here.

None of the examined public sources establish that Spider Net is a subsidiary of Coronet Corporation Limited, Orange Communication, Orange Bangladesh, Exabyte, Plusnet, Windstream, or any other network operator. The relationship clues are clues of routing policy and network market, not evidence of corporate control. BGP.tools shows AS138651 in several AS-SET contexts, including Coronet, Orange, Windstream, Plusnet, iTel, Summit, and other Bangladeshi network sets.

Such AS-SET memberships can mean that an upstream provider or routing policy manager is willing to accept and propagate a customer's prefixes; they prove neither ownership nor merger.

This distinction is economically important. The operational control of a local ISP can be independent even when its routing policy is integrated into the AS-SETs of larger providers. Conversely, a small ISP can be commercially dependent on a larger IIG, aggregator, or neighboring ISP without any public merger-acquisition transaction. In the case of Spider Net, the public record proves a local network identity and suggests several wholesale routing relationships, but it does not prove the existence of a parent company.

What the registered network proves

Spider Net's APNIC address records show a significant but small resource base. The IPv4 allocation is 103.135.136.0–103.135.139.255, a /22 containing 1,024 IPv4 addresses, with the network name SPIDERNET-BD, the organization ORG-SN17-AP, the country Bangladesh, and the status “ALLOCATED PORTABLE.” The record points to MAINT-SPIDERNET-BD and the abuse contact IRT-SPIDERNET-BD.

The IPv6 allocation is 2404:7ec0::/32, also under SPIDERNET-BD and ORG-SN17-AP. The APNIC IPv6 record gives the same Chattogram/Kotowali address context and an abuse validation date of January 2026. The existence of a /32 IPv6 allocation shows that Spider Net has the registry capacity to operate IPv6 at scale, at least on paper. It does not prove active retail IPv6 service.

The AS number is AS138651, named SPIDERNET-AS-AP. BGP.tools reports that Spider Net operates in Bangladesh, originating two IPv4 prefixes and no IPv6 prefixes. The two visible originated prefixes are 103.135.136.0/24 and 103.135.137.0/24, each shown as RPKI-valid. The same page reports two observed upstream providers: AS137526 Plusnet Inc and AS139009 Windstream Communication Limited. Hurricane Electric's BGP Toolkit independently shows that AS138651 originates two IPv4 prefixes, no IPv6 prefixes, two observed BGP peers, 512 IPv4 addresses originated, and RPKI-valid IPv4 routes.

The gap between the APNIC /22 and the currently observed /24s originated by AS138651 is one of the most important economic facts in the file. Spider Net holds or is registered for 1,024 IPv4 addresses, but AS138651 visibly originates 512 IPv4 addresses via its own ASN. BGP.tools shows that 103.135.138.0/24 is originated by AS150774 EXABYTE LTD and described as Spider Net, while AS150178 EXABYTE LTD is shown originating 103.135.139.0/24, also described as Spider Net.

The route entity material derived from APNIC for 103.135.138.0/24 also shows route entities pointing to ASNs linked to Exabyte, including AS150178 and AS150774, with descriptions that include EXABYTE LTD and Md. Aziz Uddin at the same Kotowali address.

There are three economically plausible interpretations. First, Spider Net may directly operate the 136/24 and 137/24 blocks while allowing the other two /24s to be routed by, leased through, or technically managed by networks linked to Exabyte. Second, a larger upstream provider or aggregator may carry portions of Spider Net's address space for customer, NAT, backup, or transition purposes. Third, the allocation may reflect legacy registry ownership while the actual traffic-serving role of certain parts of the /22 has migrated to other ASNs. None of these interpretations can be proven by BGP alone.

But all point to the same economic structure: the addressing asset is separable from the retail brand, and routing control can migrate before legal or brand records do.

The absence of IPv6 announcements is also revealing. A /32 IPv6 allocation is a major technical asset for a small ISP. Yet, BGP.tools and Hurricane Electric show no IPv6 prefixes originated by AS138651. This suggests either limited IPv6 deployment, a lack of public visibility of IPv6 routes from AS138651, or IPv6 service delivered in another way not visible through the examined AS. Economically, the consequence is that Spider Net likely remains dependent on scarce IPv4 addresses and carrier-grade NAT for much of its retail service, unless IPv6 is deployed privately or via another operator.

For a small ISP, IPv6 is not just a matter of technical modernization. It affects customer support burden, gaming and telework complaints, static IP monetization, abuse attribution, and negotiation with upstream providers.

Route visibility as a form of market capital

For a small ISP, an ASN is partly a technical identifier and partly a market credential. AS138651 makes Spider Net visible to upstream providers, route collectors, abuse desks, and business customers. It also allows the operator to maintain portable address space, originate routes, and implement RPKI. This produces a modest but real form of bargaining capital. A reseller without its own ASN and portable space can be cut off, renumbered, or absorbed more easily. A small ISP with portable addresses and valid RPKI can change upstream providers or connect to multiple providers with less disruption, at least in theory.

Spider Net's current route visibility is narrow but not trivial. Two /24s are visible from AS138651, both RPKI-valid, and no downstream ASNs are reported by IPinfo. IPinfo classifies the ASN type as ISP, reports 512 IPv4 addresses and no IPv6 addresses under AS138651, shows no domains hosted on the ASN, and lists Plusnet and Windstream as peers/upstream providers. BGP.tools and Hurricane Electric converge on the same basic picture: a small Bangladeshi stub ISP with two IPv4 BGP neighbors, no visible IPv6 origination, and no public downstream cone.

This matters because route visibility disciplines the business model. Spider Net does not appear to be a wholesale transit provider. It does not use its ASN to build a large downstream cone. It does not visibly host websites at scale. IPinfo reports zero domains hosted on AS138651, and Host.io shows that spidernetctg.com itself resolves to a shared hosting environment of the Akamai Connected Cloud/Linode type rather than being hosted on Spider Net's own ASN. The economic center of the network is therefore probably not datacenter hosting, transit resale, or enterprise cloud connectivity.

It is more likely fixed access: residential broadband, small business internet, local packages, bill collection, and field service.

The RPKI-valid status of the originated prefixes is a positive technical signal. In a market of many small broadband labels, RPKI validity reduces the risk of route hijacking and indicates that Spider Net or its technical counterpart maintains the route origin authorization process. It is not a guarantee of service quality. It is a signal that the operator is not merely a neighborhood cable reseller without registry competence. This distinction affects upstream provider trust and customer trust differently. Upstream providers care that routes are valid and contacts are reachable.

Retail customers care that the line works during peak hours and that someone answers when the fiber is cut.

The customer control surface is stronger than the website

Spider Net's website is not a strong public channel. Host.io identifies spidernetctg.com as resolving to 172.234.24.211 under AS63949 Akamai Connected Cloud, with an OpenResty “Redirection…” title and no significant backlink footprint. A direct interpretation as a marketing site would give the impression that the company is inactive or underdeveloped. That would be misleading if taken in isolation.

The most informative evidence of the customer channel is the Android app “Spider Net,” developed by SoftifyBD. The Google Play listing describes a utility that allows customers to see downloaded and uploaded data usage since the last server connection, request package changes, test router connectivity, open support tickets, send messages to the technical team, pay monthly bills via bKash without extra charges, view payment history, receive notifications of outages/offers/news, and automatically reconnect after a disconnection for non-payment once payment is made. The listing shows an update date of December 29, 2025, and over 50 downloads.

The app's functions reveal the real operational problem of a local ISP. Spider Net's economics rely on reducing the cost of small transactions: bill reminders, payment reconciliation, disconnection and reconnection for non-payment, support ticket triage, package change management, and basic customer diagnostics. A mobile app does not prove scale, but it proves that the operator has invested in a retail control plane. The commercially most significant feature is not branding; it is the auto-reconnect mechanism after bKash payment. This feature compresses the cash conversion cycle. It reduces field visits for collections.

It also turns prepaid or quasi-prepaid disconnection into a low-friction enforcement tool.

The app's data safety disclosure also indicates that data is not encrypted in transit and cannot be deleted, according to the Google Play listing. For a small ISP, this is not a trivial footnote. Customer self-service systems builds trust when they work, but they also broaden the operator's digital risk surface. Billing records, outage notices, router connectivity checks, and support tickets can become sources of privacy and reputation risk if poorly secured. Small networks often modernize billing before professionalizing security governance; the Spider Net app evidence should be read in that context.

The channel evidence suggests that Spider Net's customer relationships are local and operational rather than media-driven. Customers likely discover the operator through neighborhood availability, technician recommendation, building-level cabling, word of mouth, local Facebook or phone contacts, and the practical fact that the line can be installed quickly. The app then supports retention and collections. In such a market, a weak website is not fatal. It is a missed trust signal for business customers, but residential broadband in dense neighborhoods is often sold by field presence and price rather than search engine credibility.

Geographic footprint and operational layer

Spider Net's strongest geography is Chattogram. APNIC gives Kotowali/Chittagong. The BTRC upazila/thana list places the license holder in Chattogram Sadar. ISPAB gives an address at Anderkilla/Chittagong. IP geolocation providers also place Spider Net IP samples in Chittagong, although IP geolocation should not be treated as precise evidence of operational footprint. IPGeolocation.io places 103.135.137.104 in Chittagong and associates it with AS138651 and Spider Net.

AbuseIPDB's WHOIS/geolocation view for 103.135.138.197 labels the usage type as fixed ISP and associates the domain with spidernetctg.com, but it places the sample IP in Cox's Bazar/Chittagong; this should be treated as a third-party geolocation signal, not a confirmed service area map.

The BTRC license category is more economically important than the exact geolocation of individual IP addresses. Bangladesh's ISP guidelines define license categories including national, divisional, district, and upazila/thana. They also restrict last-mile deployment: a license holder can generally provide last-mile internet service within a radius of about three kilometers in metropolitan areas and six kilometers elsewhere, subject to local authority ordinances and BTRC instructions. This regulatory geography pushes small ISPs toward dense local access economics.

It is difficult for an upazila/thana operator to become a national brand without new licenses, acquisitions, or wholesale/partnership agreements. The relevant question is not “How many cities does Spider Net serve?” but “How many buildings, alleys, small businesses, and profitable household clusters can it serve within its authorized and physically accessible territory?”

The operational layer also appears to be retail access rather than wholesale transit. There is no evidence of downstream AS customers. There is no evidence of a public PeeringDB profile for AS138651 in the examined searches. IPinfo reports no domains hosted. The routing table shows a small access network with upstream dependency, not a regional backbone. The app shows billing and customer support, not wholesale provisioning. The ISPAB and BTRC categories show a local access license, not an IIG or NTTN license. Taken together, these facts place Spider Net in the last-mile and near-last-mile economics of Bangladesh broadband.

Bangladesh's regulatory stack turns every local ISP into a dependency manager

Bangladesh's broadband rules structurally separate local access from upstream layers. The 2020 ISP regulatory and licensing guidelines state that an ISP licensee may provide internet, data communication, and IP-based services, and may lease or sub-lease a transmission network from licensed NTTN operators. The guidelines also state that ISP licensees must connect to licensed international internet gateways for leased internet bandwidth and connect to national internet exchange facilities for domestic inter-operator traffic.

This framework makes upstream dependency a designed feature, not an accident. A local ISP such as Spider Net cannot simply become a vertically integrated operator of national fiber, international gateway, and retail access by preference. It buys or leases crucial inputs. It depends on IIGs for international bandwidth. It depends on NTTNs or equivalent transmission arrangements for fiber/backhaul. It depends on NIX arrangements for domestic traffic exchange. It depends on BTRC license rules and tariff guidelines. It depends on local authorities for physical access, roadworks, pole routes, and practical last-mile installation conditions.

This dependency stack creates margin compression. The retail price is visible and politically sensitive; wholesale bandwidth and transmission costs are less visible but determine gross margin. If retail customers expect “unlimited” service at a regulated or market-converged monthly price, peak-hour usage growth must be absorbed by buying more capacity, tolerating congestion, or tightening contention ratios. The cheapest way to survive is local density: many customers per route meter, low frequency of technician dispatches, high payment collection, and low churn.

NTTN pricing illustrates the cost mechanism. A 2021 Financial Express report on BTRC-approved NTTN tariffs indicated that up to 10 Mbps of regular capacity bandwidth would cost Tk 200 to 300 in metropolitan areas and Tk 400 to 500 outside metropolitan areas, with cheaper rates for higher bandwidth ranges. IIG pricing also affects small ISP margins.

A 2024 Business Standard report indicated that Bangladesh's internet gateways proposed reducing minimum selling prices for ISPs, including a proposed reduction from Tk 365 to Tk 215 per Mbps per month for ISPs buying up to 500 Mbps in Dhaka and from Tk 399 to Tk 265 outside Dhaka, with larger volume buyers benefiting from lower proposed rates. The pattern is economically clear: large buyers get better unit costs, while small networks must either aggregate demand through wholesalers or accept weaker procurement leverage.

The regulatory environment also signals consolidation pressure. The BTRC broadband connectivity report includes a policy suggestion to reduce the number of ISP licenses and combine or recycle more than 2,000 ISP licenses. The Daily Star reported in 2022 that 286 ISPs were to be disconnected and quoted the ISPAB president saying that over 40% of those 286 were not operating or operating on a very limited scale.

A 2024 Financial Express report indicated that BTRC issues ISP licenses in four categories and that license issuance had been suspended from March 1 of that year while new guidelines were being developed, with ISPAB citing oversaturation in specific areas as the reason for the earlier halt to new ISP licenses.

For Spider Net, this means viability is not just a question of whether customers like the service. It is also a question of whether the regulatory system continues to tolerate many small access license holders, whether renewal dossiers are clean, and whether the operator can maintain enough scale to justify its separate existence.

Business model: local density, not brand premium

Spider Net's likely revenue logic is standard for a small fixed broadband ISP: monthly retail subscriptions, installation fees, router or ONU/CPE economics, package upgrades, possible public/static IP fees, small business plans, and perhaps local dedicated or semi-dedicated lines. The app's functions confirm package change requests, monthly bill payment, support tickets, payment history, data usage visibility, and reconnection after non-payment. Public evidence does not establish exact pricing plans, subscriber counts, ARPU, or churn rate.

The cost structure is more deducible. A small ISP must pay for upstream internet capacity, domestic transmission/backhaul, last-mile materials, building access, technician labor, splicing and repair, routers or ONUs, local collection, power backup, billing software, license fees, registry maintenance, and support. It must also bear the risk of customer equipment damage, unpaid bills, cable cuts, power instability, neighborhood conflicts, and peak-hour congestion.

In this model, the listed subscription price is less important than the ratio between average monthly revenue and four operational variables: peak bandwidth consumed per active subscriber, field support cost per subscriber, churn and bad debt, and route/building density.

The profit engine of small ISPs can be expressed simply. A dense alley or apartment cluster becomes attractive when a single fiber route, a single splitter/OLT path, and a single technician visit can serve many paying customers. A dispersed customer base is less attractive because each installation and outage consumes labor and materials. A price-sensitive customer base is viable only if the service is standardized, collections are automated, and support is locally fast. The bKash payment and auto-reconnect features of the app directly address the collection piece of this problem.

The visible IP address inventory also shapes the revenue model. If AS138651 visibly originates only 512 IPv4 addresses while APNIC Labs' customer population estimates for SPIDERNET-AS-AP show an estimated user population between ten thousand and a few tens of thousands in 2025-2026, the network almost certainly does not assign unique public IPv4 addresses to all end users.

APNIC Labs' Bangladesh AS population pages show estimates for SPIDERNET-AS-AP such as 11,533 users on August 7, 2025, 14,881 users on January 12, 2026, 18,468 users on May 3, 2026, and 17,387 users around late June 2026; these are measurement estimates, not contractual subscriber counts.

These estimates must be used with caution. APNIC Labs estimates user populations from measurement systems and does not publish Spider Net's counts. Nonetheless, the order of magnitude is commercially useful. It implies a retail network much larger than its number of public IPv4 addresses, which is consistent with carrier-grade NAT and public address sharing. For small ISPs, CGNAT is economically rational because IPv4 addresses are scarce, but it creates quality-of-service friction. Customers who need gaming, video surveillance, remote access, VPN stability, or inbound connections may require static IPv4 addresses or port forwarding solutions.

Static public IP addresses then become a monetizable scarce product. Abuse management also becomes more difficult because many customers may share a public IP address at different times.

Pricing power is low. Retail broadband pricing in Bangladesh has been subject to “One country, one rate” tariff interventions since 2021, when BTRC set maximum broadband prices such as Tk 500 for 5 Mbps, Tk 700-800 for 10 Mbps, and Tk 1,100-1,200 for 20 Mbps or more, according to local press coverage of the policy launch. Subsequent local reports in 2026 described revised caps such as Tk 500 for 30 Mbps, Tk 1,000 for 100 Mbps, and Tk 3,000 for 250 Mbps, although the sources examined for this update are press reports rather than a tariff PDF directly retrieved from BTRC.

The broader point is stable: retail broadband is politically regulated and intensely competitive. A small ISP cannot rely on premium pricing unless serving a constrained building, a business niche, or an exceptionally service-sensitive clientele.

Supplier power and routing dependency

Spider Net's observed upstream providers are Plusnet Inc and Windstream Communication Limited. These providers are not just names in a table. They represent the buyer-supplier relationship that determines availability, latency, congestion, and cost. A dual-upstream setup is better than a single provider, but it is not deep resilience. If one provider raises prices, suffers a route leak, experiences congestion, or changes its commercial terms, Spider Net has limited visible alternatives unless it has dormant or off-table agreements via other IIGs or aggregators.

The AS-SET relationship clues broaden the dependency map. BGP.tools shows AS138651 listed in AS-SETs associated with Coronet IIG, Orange, Windstream, Plusnet, Summit, iTel, and other Bangladeshi providers. Coronet's own public website presents it as an IIG and IP transit company in Bangladesh offering dedicated internet access, IP transit, MPLS, IPLC, and related services. BGP.tools shows Coronet Corporation Limited, AS149765, with upstream providers including Bharti Airtel, Reliance Jio, Hurricane Electric, BSCCL, and Fiber@Home Global, and with a broader downstream/peering footprint than Spider Net.

Orange appears as another relevant network market clue. BGP.tools identifies AS137453 Orange Bangladesh and AS135341 Orange Communication as Bangladeshi retail networks with larger IPv4/IPv6 prefix sets and upstream relationships that include Exabyte, Windstream, Summit, Level3/CenturyLink, Earth Telecom, and each other. Exabyte is more directly involved in Spider Net's address space pattern because BGP.tools shows Exabyte ASNs originating 103.135.138.0/24 and 103.135.139.0/24 with Spider Net descriptions. PeeringDB lists Exabyte AS150774 as “Exabyte IIG,” network type NSP, with IPv4 and IPv6 support in its public profile.

The economic interpretation is not that Spider Net is owned by these entities. The interpretation is that Spider Net sits inside a local wholesale network. In Bangladesh, small ISP procurement leverage is often indirect. It may buy from one upstream provider today, have route entities maintained by another, appear in multiple providers' AS-SETs, and migrate parts of the address space between ASNs as commercial conditions change. This routing policy flexibility can improve viability, but it also reveals dependency.

The customer may see only “Spider Net.” The packet path may involve a larger IIG, a national fiber provider, a route sponsor, and an international transit chain before reaching the global internet.

Buyer power, churn, and the trust problem

Retail customers have high buyer power when multiple local ISPs can serve the same building or alley and mobile data is an adequate fallback. They have lower buyer power when the building has only one practical cable route, an operator has already wired the premises, or the user relies on a known local technician. In the dense urban broadband markets of Bangladesh, both conditions can coexist. A customer may have many advertised options but only one or two reliable installers at the exact address.

For Spider Net, trust is produced operationally. The app enables support tickets and outage notices. The ISPAB and APNIC registers provide phone and email contacts. BGP records show the network is real and visible. But the weak website, limited public reviews, low app download count, and ambiguous license renewal line all limit externally visible trust. A customer choosing between a national ISP and Spider Net would not find the same public assurance signals.

This creates a local trust equilibrium. A small ISP can survive without national brand credibility if field response is superior. A fast repair after a fiber cut can matter more than a polished website. A technician who lives near the service area can be more valuable than a call center. A bKash reconnection after payment can reduce customer frustration more than a corporate portal. But this equilibrium is fragile.

If service quality degrades over two billing cycles, if evening speed collapses, or if support tickets go unanswered, churn can be rapid because the customer's switching cost is often just a new installation fee and a phone call to a competitor.

The app download count (50+) should not be interpreted as the subscriber count. Many customers may not install the app, pay through other channels, or share accounts across households. But the low public download count remains a signal: Spider Net's digital self-service channel is not operating at the visible scale of a mass national ISP. This is consistent with a local access network whose moat is geography and technician relationships, not consumer brand recognition.

Competition and substitutes

Spider Net competes with four classes of alternatives. The first consists of nearby local ISPs with similar BTRC categories and similar cost structures. ISPAB member pages around Chattogram show many upazila/thana broadband providers and small operators with local addresses, emails, and phone numbers. These operators compete on installation speed, monthly price, peak-hour quality, payment convenience, and technician responsiveness.

The second class is larger regional or national ISPs. Large networks can procure upstream capacity more cheaply, invest in better NOC functions, advertise more professionally, and sometimes offer bundled services. They can nevertheless be weaker at hyperlocal repair if their field force is overstretched or a particular neighborhood has access constraints. The competitive struggle is therefore not simply large versus small. It is procurement scale versus local density.

The third class is mobile broadband. Mobile operators are not always substitutes for fixed residential broadband because unlimited home use, gaming, streaming, and telework favor fixed connections. But mobile data is a powerful churn threat during outages. If a household can survive on mobile data for a week, it can tolerate a poor fixed ISP with less patience. If mobile plans become cheaper or 5G fixed wireless access strengthens, small fixed ISPs lose some of their captive demand.

The fourth class is informal or semi-formal resale. In fragmented markets, a customer may buy internet from a local cable operator, a building reseller, or a neighboring network that relies on an upstream ISP. Regulatory enforcement and license cleanup affect this layer. If BTRC strengthens enforcement, license-holding entities like Spider Net may benefit from reduced informal competition. If enforcement is uneven, informal resellers can compete with licensed ISPs by avoiding compliance costs.

The supplier side is also competitive but concentrated by function. Upstream IIGs and larger NSPs compete for ISP bandwidth, but small buyer leverage is limited by volume. NTTN/backhaul options may be limited by geography, last-mile civil constraints, and practical route availability. Payment rails like bKash reduce collection friction but create dependency on a third-party payment ecosystem. App vendors like SoftifyBD reduce software development cost but create supplier dependency for billing and support flows.

Ownership, funding, and control ambiguity

The public file does not identify Spider Net's beneficial owner, capitalization, bank debt, ownership structure, or management team. It reveals recurring contact clues. APNIC's organization and IRT registers show Spider Net contacts and the phone number +8801837686343. ISPAB lists the Spider Net email as[email protected]and the same mobile number. The APNIC-derived route entity material for 103.135.138.0/24 includes a route entity described with “Md. Aziz Uddin” and the same Kotowali address. These clues suggest an individual administrative or ownership control point, but they do not prove legal ownership.

This ambiguity is normal for small ISP intelligence. The economic assets of a local broadband operator are often not held in a tidy corporate shell. They may include a BTRC license, local right-of-way relationships, customer lists, unpaid receivables, installed fiber, OLTs and routers, IP resources, technician relationships, and upstream contracts. Funding may come from retained earnings, supplier credit, informal capital, customer installation fees, or local partners. None of this is visible in APNIC or BGP registries.

Bangladesh's ISP guidelines restrict license transfer and assignment without prior approval, which limits the simple sale or pledging of the license as if it were ordinary stock. In practice, consolidation can occur through customer migration, operational support, route sponsorship, address space routing changes, or brand continuity under a larger network, rather than through a clean public acquisition. This is why Spider Net's split routing via Exabyte-linked ASNs is more than a technical curiosity.

It is a possible early sign of operational dependency, shared route management, or partial migration of network assets, even if it is not proof of a merger-acquisition.

The unresolved control question changes the valuation. If Spider Net is an independent local ISP with active paying customers, its value lies in the customer portfolio, local access infrastructure, license, IP resources, and field team. If it is partially operationally absorbed by a larger provider, its stand-alone margin may be lower, but its customer relationships can still have acquisition value. If it is primarily an address/resource holder with a reduced retail base, the IPv4 and ASN assets dominate the economic story.

The updated app and APNIC Labs traffic estimates argue against pure dormancy, but they do not settle the ownership question.

Abuse, reputation, and security signals

No examined source establishes a major outage, litigation, supply conflict, license cancellation, or named cybersecurity incident concerning Spider Net. The public footprint does show weak abuse and reputation signals at the IP level. CleanTalk's page for 103.135.136.99 identifies the network as 103.135.136.0/24, AS138651, organization Spider Net, website spidernetctg.com, and lists a network spam rate of 8% while showing an AS spam rate of 0%.

IPGeolocation.io's page for 103.135.137.104 associates the IP with Spider Net and AS138651, assigns it a threat score of 75, and labels the IP as proxy, residential proxy, VPN, anonymous, and known attacker, while not classifying it as spam or bot.

This should be treated as vendor-specific signals, not established facts. Residential broadband IP addresses often appear in proxy, scraping, credential stuffing, malware, or spam datasets because infected customers, resold access, or third-party proxy SDKs use end-user connections. A single IP label does not prove company complicity. But abuse reputation is economically relevant. If Spider Net's public IP addresses are used by residential proxy networks or compromised devices, upstream providers may receive complaints, customers may experience CAPTCHA friction, and the ISP may incur support costs.

CGNAT can amplify the problem by making abuse attribution more difficult.

The app's data safety declaration that data is not encrypted in transit is another risk signal, although it is self-reported via Google Play and may not describe all backend paths. If accurate, it would be a governance issue for customer privacy and account security. Small ISPs often adopt billing platforms to reduce labor costs before having formal privacy engineering, incident response, or vendor risk management. The next step in small ISP professionalism is not just more bandwidth; it is better identity, billing, and abuse control.

Alternative hypotheses and what each changes economically

The first hypothesis is that Spider Net is an active, independent local ISP in Chattogram. This is supported by the APNIC registration, BTRC/ISPAB identity, visible AS138651 routes, RPKI-valid prefixes, the client app updated in late 2025, and APNIC Labs population estimates. Under this hypothesis, the economics is simple: Spider Net derives revenue from retail access and survives by maintaining high local density, low wholesale input costs, automated payment collection, and responsive support. The main risks are regulatory renewal, upstream costs, churn, and field failures.

The second hypothesis is that Spider Net remains a retail brand or address holder while parts of its network functions are performed by larger operators. This is supported by the two /24s described as Spider Net originated by Exabyte ASNs, route entity material referencing Exabyte-linked origins, and AS-SET membership in larger provider sets. Under this hypothesis, Spider Net's stand-alone gross margin may be lower because more economic elements are captured by upstream or operational partners. But viability may improve if the larger partner provides route stability, procurement leverage, or technical support.

The third hypothesis is that Spider Net's license or retail operation is partially lapsed, while the network resources and some customer base persist through succession or partnership arrangements. The BTRC license list line showing a 2023 validity date in a 2024 list raises this question, although it does not prove expiration or closure. Under this hypothesis, the core value shifts from active retail cash flows to migration rights, customer relationships, route entities, IP resources, and whatever remains usable of the local infrastructure.

The updated app and APNIC Labs estimates make a full dormancy interpretation less likely, but the public file cannot rule out a partial operational transition.

The fourth hypothesis is that Spider Net is a resilient small local operator whose public website is simply unimportant. This is common in local access markets. The weak footprint of spidernetctg.com on Host.io would then say little about customer economics, while the app, phone contact, neighborhood presence, and visible routes carry more weight. Under this hypothesis, analysts should not over-penalize weak web marketing. The relevant indicators are route continuity, app activity, support responsiveness, payment behavior, and upstream provider changes.

The unresolved facts are commercially significant. A current BTRC renewal certificate would reduce regulatory risk. A customer count would determine whether APNIC Labs estimates overstate or understate the paying base. A wholesale invoice or upstream contract would reveal procurement leverage. A management confirmation would distinguish owner-controlled operation from partner-supported migration. A current routing policy from Exabyte, Coronet, Orange, Plusnet, or Windstream would clarify whether the routing clues are historical, active, or merely permissive.

Viability over the next 12 to 36 months

Spider Net can survive if it remains useful at the neighborhood level. The small ISP model is not obsolete in Bangladesh because local access is operationally granular. Large networks still need building entry, local repair, customer education, and collection. A small ISP with a dense service area, known technicians, automated payments, and acceptable upstream quality can defend a customer base even against larger brands. Spider Net has enough public evidence to be treated as a real network identity rather than a directory artifact.

But viability is conditional. The first condition is regulatory clarity. The ambiguity of the BTRC license list is not fatal, but it is significant. A local ISP with uncertain renewal status is vulnerable to regulatory enforcement, consolidation, and erosion of customer trust. The draft FTSP framework published by BTRC in 2025 proposed a technology-neutral fixed telecommunications service provider regime with national and district FTSP categories, a 10-year license term, and stated objectives including fair competition, SME participation, affordability, and quality.

If this framework or a similar successor consolidates licenses, Spider Net's value will depend on its ability to convert, partner, or be absorbed on favorable terms.

The second condition is upstream bargaining. Spider Net's visible AS has only two observed upstream providers. If wholesale bandwidth prices fall, small ISPs can benefit, but only if competition does not fully pass through the savings to customers. If wholesale terms tighten, small networks feel the pressure first. The presence of Spider Net prefixes originated by Exabyte and routing policy links with larger providers can be interpreted as a hedge: Spider Net may have more practical routing options than the two direct BGP peers suggest.

It can also be interpreted as dependency: parts of the network may already require larger operators to remain visible.

The third condition is peak-hour quality. IPinfo's network activity view characterizes AS138651 as a consumer ISP with evening and late-evening usage patterns. This is consistent with residential broadband economics. Evening peaks force the operator to choose between buying more capacity, accepting congestion, or managing customer expectations. In a low-price market, the difference between survival and churn is often the ability to maintain tolerable video, gaming, and telework between 8 p.m. and midnight.

The fourth condition is field operations. The app can reduce billing and support friction, but it cannot splice fiber, replace damaged ONUs, negotiate building access, or prevent local cable cuts. Small ISPs win when the local technician arrives quickly. They lose when every outage becomes a multi-day dispute. Field operations also determine capital efficiency: the same OLT, route, and technician can serve a profitable cluster or an unprofitable scatter of customers depending on local density.

The fifth condition is abuse and reputation management. Residential proxy and spam signals at the IP level do not prove wrongdoing, but they create costs. Upstream provider complaints, CAPTCHA issues for customers, and shared IP blacklisting can harm perceived quality. Better subscriber attribution, CGNAT logging, malware notification workflows, and abuse desk responsiveness are not luxuries for a small ISP; they protect upstream access and customer trust.

The sixth condition is IPv6. Spider Net has a /32 IPv6 allocation but no visible IPv6 origination from AS138651. Deploying IPv6 would not immediately remove the need for IPv4, but it would reduce future pressure on CGNAT, improve some application paths, and signal technical maturity. Not deploying IPv6 keeps the operator dependent on scarce IPv4 addresses and makes the demand for static public IPs harder to satisfy.

The most likely economic trajectory is not spectacular growth into a national ISP. It is either disciplined local survival, an operational partnership, or absorption into the access and routing ecosystem of a larger provider. Spider Net's value lies in its local anchoring and technical registration. Its vulnerability is that every layer above and below the retail customer is controlled by someone else.

Evidence register

1. APNIC WHOIS, organization ORG-SN17-AP, “Spider Net.” URL:https://wq.apnic.net/apnic-bin/whois.pl?searchtext=ORG-SN17-AP. This is the primary registry evidence for the Spider Net organization name, Bangladesh country code, Kotowali/Chittagong address, phone, email, admin contact, and APNIC organization identifier.
2. APNIC WHOIS, IPv6 allocation 2404:7ec0::/32, SPIDERNET-BD. URL:https://wq.apnic.net/apnic-bin/whois.pl?searchtext=2404:7ec0::/32. This proves a portable IPv6 allocation for Spider Net and provides abuse/IRT contact context.
3. AbuseIPDB WHOIS mirror for 103.135.138.197 / APNIC IPv4 registration and route entities. URL:https://www.abuseipdb.com/whois/103.135.138.197. This provides the 103.135.136.0–103.135.139.255 allocation, vendor usage type/geolocation context, and route entity evidence for Exabyte-linked origins on 103.135.138.0/24.
4. BGP.tools AS138651. URL:https://bgp.tools/as/138651. This is the primary public BGP source for AS138651's originated prefixes, RPKI status, observed upstream providers, APNIC aut-num fields, and AS-SET memberships.
5. Hurricane Electric BGP Toolkit, AS138651. URL:https://bgp.he.net/AS138651. This corroborates AS138651's two IPv4 prefixes, zero IPv6 prefixes, two BGP peers, and RPKI-valid originated routes.
6. IPinfo, AS138651. URL:https://ipinfo.io/AS138651. This corroborates the ASN name, ISP type, 512 IPv4 addresses, zero hosted domains, zero downstream, Plusnet/Windstream upstream context, pingable IPs, and consumer ISP activity pattern.
7. Host.io, spidernetctg.com. URL:https://host.io/spidernetctg.com. This shows the domain's hosted IP/ASN context, “Redirection…” page title, shared hosting environment, and absence of backlink/redirect footprint.
8. Google Play, “Spider Net” app by SoftifyBD. URL:https://play.google.com/store/apps/details?id=bd.com.softifybd.spider_net. This is the primary evidence of retail operations: usage viewing, package change, router test, ticketing, bKash payment, payment history, outage/offer/news notifications, auto-reconnect, update date, downloads, and data safety disclosure.
9. ISP Association of Bangladesh members page, Spider Net and similarly named entities. URL:https://ispab.org/members/S?page=5. This gives the Spider Net member number B-074, upazila/thana category, Anderkilla/Chittagong address, email, phone, and the distinction from Spider Mesh and Spider Networks.
10. BTRC Upazila/Thana ISP License List dated 18-12-2024. URL:https://objectstorage.ap-dcc-gazipur-1.oraclecloud15.com/n/axvjbnqprylg/b/V2Ministry/o/office-btrc/2024/12/29e9f4bf494145f5bfee76bd1a384ddc.pdf. This official list places Spider Net in Chattogram Sadar with license number 14.32.0000.702.47.043.22.376 and Kotowali address; it also creates renewal date ambiguity.
11. BTRC ISP Regulatory and Licensing Guidelines 2020. URL:https://btrc.gov.bd/sites/default/files/files/btrc.portal.gov.bd/notices/c71cc8a5_2753_4bf8_a72b_8b120dc21077/ISP%20Guideline%202020%20.pdf. This is the primary regulatory source for ISP service scope, license categories, last-mile distance limits, IIG/NIX interconnection obligations, and transfer restrictions.
12. Draft Regulatory and Licensing Guidelines for Fixed Telecommunications Service Providers, 2025. URL:https://btrc.gov.bd/sites/default/files/files/btrc.portal.gov.bd/notices/9478d892_7127_4686_8098_a3e4fe6d1ae5/Draft%20Regulatory%20and%20Licensing%20Guidelines%20for%20Fixed%20Telecom%20Service%20Provider.pdf. This is the primary regulatory monitoring source for a possible FTSP framework and license category restructuring.
13. BTRC Bangladesh Broadband Connectivity Report. URL:https://objectstorage.ap-dcc-gazipur-1.oraclecloud15.com/n/axvjbnqprylg/b/V2Ministry/o/office-btrc/2024/12/2553c9a48743467faaa8b420c2e6ecb5.pdf. This source is used for consolidation policy signals, including the suggestion to reduce, combine, or recycle more than 2,000 ISP licenses.
14. The Daily Star, “286 ISPs to be disconnected.” URL:https://www.thedailystar.net/business/economy/news/286-isps-be-disconnected-3065936. This local press source provides context on IIG function, license categories, and limited-operation ISPs.
15. The Financial Express, “BTRC restarts accepting ISP licence applications.” URL:https://today.thefinancialexpress.com.bd/trade-market/btrc-restarts-accepting-isp-licence-applications-1713376640. This source provides context on license categories, the suspension of new licenses, and oversaturation concerns.
16. The Financial Express, “BTRC okays tariffs for NTTN services.” URL:https://today.thefinancialexpress.com.bd/last-page/btrc-okays-tariffs-for-nttn-services-1628707314. This source is used for the NTTN cost structure and the volume-sensitive nature of transmission pricing.
17. The Business Standard, “Internet gateways propose 40% tariff cut.” URL:https://www.tbsnews.net/bangladesh/internet-gateways-propose-40-tariff-cut-how-it-may-benefit-broadband-users-986811. This source provides context on IIG wholesale pricing and scale effects in bandwidth purchasing.
18. The Daily Star, “One country, one rate: internet flat rate across the country soon.” URL:https://www.thedailystar.net/toggle/news/one-country-one-rate-internet-flat-rate-across-the-country-soon-2105929. This source documents the 2021 retail broadband tariff framework and regulated retail price context.
19. The Business Standard, “Broadband internet: rural users still pay higher, get lesser speed.” URL:https://www.tbsnews.net/bangladesh/telecom/broadband-internet-rural-users-still-pay-higher-get-lesser-speed-277135. This corroborates the 2021 “One country, one rate” price ranges and rural/urban pricing concerns.
20. NewsBangladesh, “New internet pricing enables broadband access.” URL:https://www.newsbangladesh.com/english/information-technology/news/125398. This is a press source for reported 2026 broadband price caps; it should be treated as secondary pending direct BTRC notice verification.
21. Views Bangladesh, “BTRC sets new internet prices.” URL:https://viewsbangladesh.com/btrc-sets-new-internet-prices/. This is another press source for reported 2026 broadband price caps and contention ratio discussion; it is used as secondary market context.
22. Coronet Corporation Ltd. website. URL:https://coronet.com.bd/. This source identifies Coronet as an IIG/IP transit company in Bangladesh and describes its DIA, IP transit, MPLS, IPLC, and related services.
23. BGP.tools AS149765, Coronet Corporation Limited. URL:https://bgp.tools/as/149765. This source provides Coronet's upstream providers, prefixes, and broader downstream/peering scale relative to Spider Net.
24. BGP.tools AS137453, Orange Bangladesh. URL:https://bgp.tools/as/137453. This source is used for Orange Bangladesh's network size, upstream providers, and relevance as a routing policy relationship clue.
25. BGP.tools AS135341, Orange Communication. URL:https://bgp.tools/as/135341. This source is used for Orange Communication's network size and upstream/downstream context.
26. BGP.tools AS150774, EXABYTE LTD. URL:https://bgp.tools/as/150774. This source shows 103.135.138.0/24, described as Spider Net, originated by Exabyte AS150774.
27. BGP.tools AS150178, EXABYTE LTD. URL:https://bgp.tools/as/150178. This source shows 103.135.139.0/24, described as Spider Net, originated by Exabyte AS150178.
28. PeeringDB, Exabyte AS150774. URL:https://www.peeringdb.com/net/33169. This source identifies Exabyte AS150774 as Exabyte IIG / Exabyte Limited and provides public peering profile context.
29. CleanTalk, spam report 103.135.136.99. URL:https://cleantalk.org/blacklists/103.135.136.99. This is a weak but relevant IP reputation signal for a Spider Net /24.
30. IPGeolocation.io, 103.135.137.104. URL:https://ipgeolocation.io/browse/ip/103.135.137.104. This is a third-party geolocation and security labeling source associating an IP sample with AS138651 and Spider Net; it is not treated as determinative.
31. APNIC Labs, Estimated customer populations by network for Bangladesh. URL:https://stats.labs.apnic.net/cgi-bin/aspop?c=BD. This is used with caution for estimated user population signals for SPIDERNET-AS-AP, not for subscriber counts.
32. APNIC RDAP information page. URL:https://www.apnic.net/about-apnic/whois_search/about/rdap/. This explains RDAP as an alternative to WHOIS and confirms APNIC support for RDAP/autnum queries, relevant to initial evidence.

Watchpoints

The first watchpoint is the BTRC license status. A current renewal record, a conversion into a district/FTSP framework, or removal from future official lists would significantly change the risk profile. The 2024 upazila/thana list confirms the identity and license number but shows a 2023 validity date, so the next public license record is a high-value trigger.

The second watchpoint is route origination. If AS138651 starts originating 103.135.138.0/24 and 103.135.139.0/24 again, the stand-alone network interpretation strengthens. If more Spider Net address space moves to Exabyte, Orange, Coronet, or another AS, the operational partner or absorption hypothesis strengthens. If the two current /24s from AS138651 disappear, the value of the independent Spider Net network would drop sharply.

The third watchpoint is upstream provider change. A shift from Plusnet/Windstream to Coronet, Exabyte, Orange, Summit, iTel, or another IIG/NSP would reveal new bargaining terms. A third direct upstream provider would improve resilience. A single upstream provider would increase outage and price risk.

The fourth watchpoint is RPKI validity. Spider Net's visible originated routes are RPKI-valid. Any invalid or not-found status would increase technical governance risk, especially if the address space continues to be divided among multiple ASNs.

The fifth watchpoint is IPv6 activation. A public announcement of 2404:7ec0::/32, or customer evidence of IPv6 service, would reduce long-term pressure on IPv4/CGNAT and signal higher technical maturity. The continued absence of IPv6 keeps the operator dependent on scarce IPv4 addresses and static IP monetization.

The sixth watchpoint is app activity. Continued updates on Google Play, more downloads, better data safety posture, and stable bKash payment features would support an active retail service interpretation. Outdated app updates or failing payment/reconnect functions would be a leading indicator on customer control operations.

The seventh watchpoint is abuse reputation. More residential proxy, spam, or “known attacker” signals on Spider Net IPs would increase the risk of upstream complaints and customer friction. Improvement would indicate better subscriber attribution, malware response, and improved CGNAT governance.

The eighth watchpoint concerns wholesale tariff changes. Further reductions in IIG or NTTN input prices would help small ISPs only if competition does not force full pass-through to retail customers. Wholesale increases or stricter contention rules would weigh on Spider Net's gross margin.

The ninth watchpoint is regulatory consolidation. Any implementation of the FTSP framework, license recycling, revenue-share change, or reduction in the number of small ISP licenses would change the option value of Spider Net's local license and customer portfolio.

The tenth watchpoint is local field evidence. New customer complaints, Facebook posts, technician hires, office changes, neighborhood expansion claims, or outage notices would be more valuable than generic website updates. For Spider Net, the economic truth will likely appear first in field operations, not in corporate announcements.