Aayat Host: The Economics of a Hosting Name Attached to a Thin, Dormant ASN

Aayat Host: The Economics of a Hosting Name Attached to a Thin, Dormant ASN

The fork: access carrier, hosting operator, reseller, or resource identity?

Aayat Host presents a sharp business-model fork. One reading is that it is a local Bangladeshi access provider: an internet service provider selling broadband or IP connectivity to households, small businesses, or local enterprises. A second reading is that it is a hosting operator: a small web, VPS, colocation, or server-rental brand with its own address resources. A third reading is that it is a reseller or white-label operator: commercially active under the Aayat Host name, but dependent on another ISP, hosting platform, or upstream network for real delivery. The fourth reading is that it is primarily a thin ASN and resource identity: a registered APNIC entity with an autonomous system number and IP resources, but little visible evidence of an independently operating network or customer-facing hosting business.

The evidence favors the fourth reading, with a qualified version of the second and third close behind. Aayat Host is real at the internet-resource layer. AS148978 is registered under APNIC as AAYAT-AS-AP, described as Aayat Host, associated with Bangladesh, and tied to organisation handle ORG-AH10-AP; bgp.tools records the ASN as active and allocated under APNIC, with registration dated October 25, 2021. But the same routing view states that AS148978 is “not currently in the global routing table” and originates zero IPv4 and zero IPv6 prefixes. IPinfo likewise classifies AS148978 as inactive, with zero hosted domains, zero IPv4 addresses, zero IPv6 addresses, no peers, no upstreams, no downstreams, and no traceroute data. That combination is not what a visible access ISP looks like, and it is not what an at-scale hosting network usually looks like. It is the profile of a resource holder or an unannounced ASN, possibly with addresses routed through someone else.

The hosting interpretation still matters because several non-primary data sources attach Aayat Host and the domain aayathost.com to address space in the 103.175.56.0/23 range, and IP2Location classifies 103.175.57.0 as data-center, web-hosting, or transit usage under AS148978. IPGeolocation similarly labels 103.175.57.103 as company “Aayat Host,” type “HOSTING,” domain aayathost.com, while also showing AS0 and no route for that specific IP in its current lookup. These are not proof of retail hosting sales; IP-to-company and geolocation databases can lag reality, inherit registry labels, or reflect older routing. But they do explain why the brand should be treated first as a hosting/resource label, not as a conventional mass-market broadband ISP.

The access-provider interpretation is the weakest because the observable infrastructure does not show an eyeball network. A local ISP normally leaves traces: active originated prefixes, transit providers, exchange participation, router hostnames, residential IP reputation, BTRC licence visibility, customer complaints, package advertisements, field-installation language, or social pages selling monthly broadband plans. The public record reviewed here instead shows an APNIC organisation, an inactive ASN, address-resource certification, and one reachable Aayat-described /24 being originated by another Bangladeshi network, D-NET SERVICE, not by AS148978. BigDataCloud shows 103.175.56.0/24 as globally reachable and associated with Aayat Host, but its carrier path is AS135615 D-NET SERVICE via AS58717 Summit Communications. bgp.tools’ AS135615 page lists 103.175.56.0/24 with the prefix description “Aayat Host” under D-NET’s originated prefixes.

The most economically useful conclusion is therefore not simply “Aayat Host is a host” or “Aayat Host is an ISP.” It is this: Aayat Host is best read as a small Bangladesh-linked APNIC resource identity with hosting semantics and outsourced or delegated routing, whose commercial importance depends less on visible customer scale than on scarce IPv4 resources, possible reseller economics, and the option value of becoming a routable network later. That distinction changes the entire economic interpretation. A broadband ISP earns from dense last-mile relationships and field service. A hosting company earns from server utilization, IP reputation, uptime, support, and customer churn management. A reseller earns from arbitrage, trust, and low acquisition cost. A thin resource identity earns, or can later earn, from address scarcity, credibility, delegated routing, and optionality.

Identity: the network record is stronger than the operating brand

The canonical identity visible in primary network records is “Aayat Host.” The APNIC-derived record on IPSHU shows AS148978 with network name AAYAT-AS-AP, country Bangladesh, description Aayat Host, and source APNIC. The same record links the entity handle ORG-AH10-AP to Aayat Host as registrant, registered September 28, 2021, last changed September 5, 2023, with a Dhaka Banani address, phone number, and info@aayathost.com. It also shows administrative and technical contact handle AHA17-AP, “Aayat Host administrator,” with abuse@aayathost.com.

That is a meaningful identity floor. It shows that Aayat Host is not merely an SEO listing or a random geolocation label. It has an APNIC organisation object, an ASN, maintainer references, an abuse contact structure, and associated email domains. In internet-infrastructure intelligence, those are not cosmetic details. They are the primitives by which addresses, ASNs, abuse responsibilities, and route authority are assigned. A company can have no public marketing site and still be operationally meaningful if it controls number resources, maintains route objects, and appears in routing.

But the same identity record also introduces ambiguity. The abuse record exposed by APNIC-derived sources uses the group name IRT-AAYAT-BD, a Gmail abuse mailbox, and an address written as “2080 One White Oak Ln Building 2 APT 2208,” while the administrative contact points back to Banani, Dhaka. APNIC’s WHOIS output for the abuse role shows mamunict98@gmail.com as the abuse mailbox and indicates that the IRT email was validated on December 15, 2025. The coexistence of a domain-based contact, a Gmail abuse contact, and two address contexts is not fatal; small network operators often use personal or legacy email during early-stage registration. But it is a maturity signal. Larger ISPs and professional hosting companies tend to normalize contact addresses, publish NOC pages, operate ticketing systems, and maintain consistent corporate registries.

The domain aayathost.com is also present in the resource data. IPinfo lists aayathost.com as the ASN domain and links to host.io for that domain, while IP2Location and IPGeolocation use the same domain in IP-to-company or AS metadata. However, the public operating footprint is thin. The reviewed search record did not surface a rich company website, price sheet, WHMCS storefront, job advertisements, customer reviews, service-status page, social channel, or support documentation comparable to a mature retail hosting or broadband business. IPinfo’s AS148978 page reports zero hosted domains on the ASN, which matters because hosting businesses normally leave DNS and hosted-domain exhaust even when their corporate site is small.

The naming ambiguity is commercially important. “Aayat Host” is close to many unrelated uses of “Aayat” and “Ayat,” including non-infrastructure entities and media results. In a market such as Bangladesh, where many small ISPs, resellers, freelancers, and local IT shops use similar naming conventions, the exact spelling and domain matter. The target here is not “Ayat Network,” not a call-center business, not a media brand, and not a generic hosting keyword. The defensible target anchor is AS148978, ORG-AH10-AP, AAYAT-AS-AP, and aayathost.com.

The routing contradiction: certified resources, inactive ASN, delegated reachability

The core infrastructure fact is a contradiction only if one assumes that an ASN must carry its own traffic. Aayat Host has an ASN and address resources, but AS148978 is not presently visible as a route origin in the global table. bgp.tools says AS148978 is not currently in the global routing table and originates zero IPv4 and zero IPv6 prefixes. IPinfo independently shows the ASN as inactive with zero IPv4 and IPv6 addresses, no peers, no upstreams, and no downstreams. These sources are consistent: as an autonomous routing entity, Aayat Host is dormant.

At the same time, Aayat Host appears to have certified number-resource context. An RPKI certificate view for the relevant resource holder shows subordinate resources including AS148978, IPv4 prefix 103.175.56.0/23, and IPv6 prefix 2001:df7:ed80::/48, with the certificate valid from December 15, 2025, to January 31, 2027. This is stronger than a mere geolocation guess: it shows a resource-certification context connecting Aayat Host’s ASN to a /23 IPv4 block and a /48 IPv6 block. It does not, by itself, prove that Aayat Host is originating routes, that it has customers, or that any particular ROA authorizes a specific origin AS. It proves that the resource set exists in the RPKI certification chain.

The visible routed piece is more revealing. BigDataCloud shows 103.175.56.0/24 as Aayat Host and globally reachable, but carried by AS135615 D-NET SERVICE, with AS58717 Summit Communications in the carrier path. bgp.tools for AS135615 lists 103.175.56.0/24 with description “Aayat Host” among D-NET’s originated prefixes. BGP.he also lists 103.175.56.0/24 under AS135615’s originated prefixes, with D-NET peers/upstreams including Summit Communications, Rego Communications, and EXABYTE. The address label points to Aayat Host, but the route origin points to D-NET.

That pattern has several possible explanations. Aayat Host may have delegated part of its address block to D-NET for transit or customer reachability. D-NET may be providing upstream, colocation, or operational BGP service on behalf of Aayat. Aayat may have acquired or requested resources but never completed independent multihoming. Or the public databases may be reflecting stale registry descriptions while D-NET is the actual access/hosting operator using the space. The point is not to choose a single private arrangement without evidence. The point is to recognize that the commercial center of gravity is not AS148978 as a live independent network. It is the relationship among Aayat’s resource record, D-NET’s route origination, and the Bangladesh wholesale connectivity stack.

This matters because routing independence is a form of bargaining power. A hosting or ISP operator that originates its own prefixes from its own ASN, maintains multiple upstreams, signs correct RPKI route-origin authorizations, and participates in exchanges has more ability to switch suppliers, manage outages, shape routes, and sell “network” credibility. An operator whose address space is carried by another local ISP has lower capital requirements but weaker control. It may buy simplicity at the price of dependence. For a small hosting brand, that trade can be rational: let a more established ISP handle BGP and upstreams while the brand focuses on customers, billing, and support. For an access ISP, the same dependence can be a constraint on margins and service quality.

The unannounced IPv6 resource is another maturity signal. The RPKI certificate view includes 2001:df7:ed80::/48, yet the major ASN views show AS148978 originating zero IPv6 prefixes. In a mature hosting network, IPv6 announcement is not mandatory, but its absence reduces the evidence of production-grade network operation. In Bangladesh’s local retail market, IPv4 demand and NAT realities may still dominate customer economics, so lack of visible IPv6 is not disqualifying. But for a hosting company seeking technical differentiation, IPv6 deployment is a low-cost credibility marker. Here it is absent from the visible AS148978 routing layer.

Why “Host” is not enough: four economic readings

1. The access-provider reading

If Aayat Host were an access provider, its economics would be those of a local ISP: recurring monthly access revenue, installation fees, router and drop-cable costs, field technicians, neighborhood density, local word-of-mouth, and churn management. The main assets would be customer relationships, last-mile reach, wholesale bandwidth contracts, and operating licences. Switching costs would be meaningful for residential and SME customers because changing broadband providers requires installation, downtime, router reconfiguration, and local support coordination. The gross-margin challenge would come from upstream bandwidth, NTTN lease costs, last-mile maintenance, power backup, technician utilization, and price competition.

Bangladesh regulation makes that model visible when it is real. BTRC’s ISP regulatory framework divides ISP licences into Nationwide, Divisional, District, and Upazila/Thana categories. The guideline text and screenshot record also state that no person or business entity may build, maintain, or operate ISP systems or services without a licence, and that ISPs provide internet/data and IP services to end users. The guideline further shows structural dependence on licensed transmission infrastructure: an ISP is to lease or sub-lease transmission capacity from NTTN operators, with last-mile length rules and specific conditions for wireless links.

Against that regulatory backdrop, Aayat Host’s public access-provider evidence is weak. No visible AS148978 routes, no AS148978 upstreams, no AS148978 downstreams, no customer-facing broadband plans, and no clear BTRC licence trace in the reviewed evidence are all negative indicators. Searches within BTRC’s 2024 Divisional ISP licence-list PDF did not find “Aayat,” “Aayat Host,” or “Ayat.” That is not conclusive because it is one list, one category family, and names can differ across legal entity, trading name, and licence class. But it is still negative evidence for the hypothesis that Aayat Host is a visible divisional ISP under that exact name.

The access-provider reading would become more plausible if a BTRC licence appeared under Aayat Host or a proprietor-linked legal name, if customer posts showed broadband installations, if Aayat began originating residential-looking address pools, or if it appeared at BDIX/ISPAB-NIX with customer traffic. None of that is in the public record reviewed here. Commercially, therefore, the access reading should be treated as a low-probability interpretation unless hidden under a different legal name.

2. The hosting-operator reading

The hosting reading is more plausible because of the name, domain, and IP classification. “Host” is not determinative, but Aayat Host’s domain appears in ASN metadata, and IP2Location labels 103.175.57.0 as data-center/web-hosting/transit usage with ASN AS148978 and domain aayathost.com. IPGeolocation’s company data for 103.175.57.103 says Aayat Host, type HOSTING, domain aayathost.com, while its network layer currently shows no route and AS0 for that IP. The combined signal is that Aayat Host has been treated by IP-intelligence vendors as a hosting/data-center identity, even if current routing is not cleanly visible under AS148978.

If Aayat is a hosting operator, it is probably not a large one. A visible hosting company normally produces many external traces: name servers, reverse DNS, shared-hosting domains, cPanel/WHM names, MX records, abuse tickets, uptime pages, reseller packages, SSL certificates, customer reviews, marketplace posts, Facebook ads, and price tables. IPinfo reports zero hosted domains on AS148978. That does not rule out hosting if Aayat’s addresses are routed through D-NET, if customers use Cloudflare, if the company resells third-party infrastructure, or if the address block is dormant. But it does rule out the simple claim that AS148978 is visibly hosting domains at scale.

The economics of a small Bangladeshi host are very different from those of a global cloud. Revenue would likely come from shared hosting, small VPS instances, reseller hosting, domain and SSL add-ons, business email, backup, and occasional managed services. Customer acquisition would depend on trust, price, local payment convenience, fast support in Bangla, and the ability to rescue small businesses from confusing global platforms. Customers would include freelancers, agencies, small retailers, educational projects, mosques, NGOs, and SMEs that need websites and email more than elastic compute. The support burden would be high relative to revenue because small hosting customers often need migration help, DNS fixes, WordPress repair, email deliverability support, and payment reminders.

The margin structure is unforgiving. Upstream bandwidth and rented servers may be priced in dollars or tied to hard-currency equipment cycles, while customers pay in taka and are price-sensitive. Hardware depreciation, power backup, cooling, security, and colocation costs can eat margin if the host owns servers. If the host resells another platform, gross margin improves operationally but shrinks commercially because the upstream supplier captures infrastructure economics. IP reputation is another constraint. A small host with a /24 can lose email deliverability or attract abuse risk quickly; one bad spam customer can damage the value of the address pool. The APNIC/RPKI record gives Aayat Host infrastructure credibility, but the lack of public hosted-domain scale suggests that credibility has not translated into a visible hosting estate.

3. The reseller or white-label reading

The reseller reading explains the record more elegantly. Aayat Host may be a commercial front end that depends on D-NET or another supplier for routing, server placement, or wholesale internet. In this model, Aayat does not need to operate a full network. It can sell hosting, IP services, or small business IT packages while outsourcing the heavy parts: upstream transit, colocation, BGP announcements, power, server inventory, and possibly even support tooling. The visible D-NET origination of 103.175.56.0/24 is consistent with that kind of arrangement.

This model lowers capital requirements but changes bargaining power. A reseller can start with little money, avoid licence complexity if it is not selling access directly, and focus on customer trust. It can survive with a thin public footprint if sales happen through personal networks, Facebook, local agencies, WhatsApp, or freelancer channels. But supplier bargaining becomes the central economic risk. If D-NET or another upstream controls routing, service restoration, packet loss, port capacity, or abuse handling, Aayat’s customer promise depends on someone else’s operational discipline. The reseller owns the angry customer but not necessarily the router.

The reseller model also explains why Aayat could value an APNIC identity even with little visible traffic. Owning or being associated with an ASN and address space can raise credibility with technical customers, enable future migration, support dedicated-IP offerings, or provide insulation against being seen as just another shared-hosting affiliate. In a crowded market, “we have our own ASN/IP block” can be a trust signal even if day-to-day routing is delegated. That claim is economically useful because customers cannot easily verify the depth of the network; they see uptime, support speed, price, and whether email works.

The downside is that reseller businesses have weak pricing power. Customers can compare against global cloud providers, cheap Indian or Singaporean VPS sellers, domain registrars, local cPanel resellers, Facebook-based hosting shops, and even free website builders. Switching costs exist but are narrow. A small business that has email, DNS, website files, and domain registration bundled with one provider may hesitate to move. But a technically literate customer can migrate a WordPress site or VPS fairly quickly. Therefore, unless Aayat controls either a trusted local channel or a scarce technical asset such as clean IPv4 addresses, reseller margins remain fragile.

4. The thin ASN/resource-identity reading

The thin-resource-identity reading is the most strongly supported. It says Aayat Host’s visible significance lies in number-resource registration rather than in an observable operating business. AS148978 exists. Aayat Host exists as an APNIC organisation. A /23 IPv4 resource and a /48 IPv6 resource appear in the RPKI certificate view. But the ASN is inactive in global BGP, and the most visible Aayat-described /24 is originated by D-NET.

This does not mean “fake.” Thin resource identities can be perfectly legitimate. A company may acquire resources before launching. It may pause operations. It may use its addresses through an upstream’s ASN. It may maintain registry compliance while waiting for customer demand. It may have private customers that do not show up through hosted-domain databases. Or it may be a legal or administrative shell around resources that are operationally used elsewhere. The intelligence judgment should avoid legal overstatement and focus on economics: the asset is visible; the operating company is not.

IPv4 scarcity gives even a small /23 commercial meaning. A /23 contains 512 IPv4 addresses. In hosting, clean IPv4 addresses can be monetized through dedicated IP add-ons, VPS allocations, VPN or remote-access services, mail infrastructure, and B2B leasing or delegation. In access networks, a /23 can support only a modest number of customers without carrier-grade NAT, but it can still support public-IP upsells or business customers. In either case, the address resource is more economically concrete than the marketing footprint.

The option value is the key. Aayat Host can become more operationally significant if it begins originating AS148978, signs and maintains route-origin authorizations, adds upstreams, announces IPv6, creates a PeeringDB profile, joins local IX fabrics, or publishes hosting packages. Until then, its commercial weight is latent. It is a call option on network operation, not evidence of current scale.

Bangladesh’s local-market economics make thinness rational

Bangladesh’s internet market encourages both fragmentation and supplier dependence. BTRC and industry reporting show a large, regulated, crowded market in which many ISPs compete for local customers while relying on upstream infrastructure categories such as IIGs and NTTNs. BTRC’s framework requires ISP licensing and separates service categories; public reporting has described BTRC actions to disconnect or cancel non-compliant ISPs and to manage licence conversion under the 2020 guidelines.

The Financial Express reported that BTRC rejected 301 ISP applications to avoid overcrowding, with more than half from Dhaka, and quoted ISPAB saying around 2,700 ISPs were working in the country, with some local areas having more than ten ISPs where only two might suffice. The same report noted licence-renewal requirements and tariff-approval obligations. That environment matters for Aayat Host because it reduces the attractiveness of becoming yet another fully visible retail ISP without scale. The access market is crowded, regulated, operationally messy, and exposed to licence enforcement.

Demand is large, but not evenly available to small fixed operators. AMTOB’s BTRC-sourced May 2026 figures show 134.07 million internet subscribers in Bangladesh, of which 119.12 million were mobile internet and 14.95 million were ISP plus PSTN. Mobile therefore dominates total internet access, while fixed ISP connections are a smaller but still substantial market. This creates a difficult strategic landscape for small providers: mobile broadband constrains consumer pricing and acts as a substitute, while fixed broadband customers demand reliability, low latency, and local support.

For a small operator, hosting can be more attractive than access because it avoids last-mile installation and regulatory exposure. But hosting also faces globalized competition. A Bangladeshi customer can buy from local hosts, Indian hosts, Singapore VPS providers, global hyperscalers, domain registrars, and cheap shared-hosting platforms. The advantage of a local host is not raw infrastructure superiority; it is convenience, trust, local language support, payment channels, and help with migration. That is why a thin resource identity may be rational: acquiring an ASN and address space gives infrastructure credibility without committing immediately to the full fixed-cost base of an ISP or data center.

D-NET’s role also fits the market structure. D-NET SERVICE appears as an active Bangladesh network, registered in 2016, with upstreams including Summit Communications, Rego Communications, and EXABYTE, and with 103.175.56.0/24 described as Aayat Host among its originated prefixes. For Aayat, using such a network could be cheaper and simpler than building independent BGP operations, contracting multiple upstreams, and maintaining exchange ports. For D-NET, carrying another labelled prefix can monetize existing upstream relationships and routing capability.

This is not unusual in fragmented ISP markets. Smaller licence holders, local cable operators, hosting resellers, and address holders often rely on upstream networks for transit, NTTN access, or BGP origination. The economic logic is layered: the customer-facing brand owns trust and billing; the access or upstream network owns physical reach and routing; the number-resource holder owns registry identity; and the end user experiences one blended service. Aayat Host’s public evidence fits a layered model better than a vertically integrated one.

Supplier dependence and margin pressure

If Aayat Host is commercially active, its dependency surface is larger than its visible brand suggests. At the routing layer, the obvious dependency is D-NET for 103.175.56.0/24 reachability. D-NET in turn depends on upstreams including Summit Communications, Rego Communications, and EXABYTE, according to bgp.tools and BGP.he views. BigDataCloud’s path for 103.175.56.0/24 identifies D-NET and Summit in the carrier chain. That means Aayat’s reachable address economics, at least for that /24, are indirectly exposed to D-NET’s upstream economics and operational quality.

For a hosting reseller, that dependency affects gross margin in three ways. First, the supplier sets the wholesale bandwidth or server price. If upstream costs rise, the reseller either absorbs the hit or raises prices in a market where customers can comparison-shop. Second, the supplier determines service quality. Packet loss, route instability, congestion, or abuse blacklisting hits the customer-facing brand even when the reseller cannot directly fix the network. Third, the supplier controls operational tempo. A reseller’s support promise is only as fast as its escalation path.

For a direct host with its own servers, the dependency moves from pure wholesale bandwidth to colocation, power, hardware, and repair. Bangladesh’s power, cooling, and datacenter environment makes reliable hosting more capital-intensive than a domain-reseller storefront. A small host must either pay for credible facilities or accept higher outage risk. If it rents foreign VPS capacity, it gains reliability but loses local latency and differentiation. If it hosts locally through a partner, it gains local latency but inherits that partner’s operational constraints.

Payment friction also shapes margins. Local customers may prefer mobile financial services, bank transfer, cash-like settlement, or local invoicing, while many upstream costs, software licences, control panels, domains, SSL products, and cloud resources are dollar-linked. That currency mismatch hurts small hosts during exchange-rate pressure. It also increases administrative burden: chasing small monthly invoices can consume support time that would otherwise be used for technical operations.

Support burden is likely the largest hidden cost in any Aayat-like hosting model. Low-priced hosting attracts customers who need high-touch help: domain pointing, email setup, WordPress malware cleanup, PHP version changes, backups, SSL renewals, and content migration. Large hosts automate this through dashboards, documentation, and scale. Small hosts compete by being reachable on chat and phone. That can win customers, but it caps scalability because support labor grows with customer count and service complexity.

Customer acquisition and switching costs

Aayat Host’s apparent lack of broad public marketing changes how one should think about customer acquisition. A visible hosting company with search ads, social channels, and package pages competes in open acquisition markets. A thin operator may instead rely on personal networks, agency referrals, local IT contractors, or existing ISP relationships. That model can be profitable at small scale because acquisition costs are low and trust is pre-existing. It also makes public evidence sparse.

In hosting, switching costs are asymmetric. For a simple static website, switching providers is easy. For a small business with domain registration, DNS, email, website files, database, backups, and payment integration all handled by one local provider, switching is emotionally and operationally harder. The provider may not have formal lock-in, but it controls knowledge. Customers do not know which registrar holds the domain, where nameservers point, who has cPanel access, whether email is backed up, or how to migrate safely. Small hosts therefore gain “soft switching costs” through service bundling and customer dependence.

In access provision, switching costs are more physical. A household or SME may need a new cable drop, new ONU/router, installation visit, and downtime. That creates more durable customer relationships if service quality is acceptable. But Aayat lacks the public access-provider signals that would make this model likely. Without evidence of last-mile network, the more plausible switching-cost mechanism is managed-service dependence rather than physical access lock-in.

If Aayat is mainly a resource holder, the “customer” may not be a retail user at all. It could be another network, reseller, or operational partner that needs addresses or registry association. In that case, switching costs are technical and administrative: renumbering servers, changing route objects, updating DNS, preserving IP reputation, and reconfiguring firewalls. Those switching costs can be meaningful even when the end-user brand is invisible.

Competition and substitutes

The competitive set depends on which reading is correct. As an access ISP, Aayat would face mobile broadband, national fixed operators, licensed local ISPs, neighborhood cable operators, and informal reseller networks. Mobile is the largest substitute by subscriber count in Bangladesh, with BTRC-sourced AMTOB data showing mobile internet far larger than ISP plus PSTN subscribers as of May 2026. That does not eliminate fixed broadband demand, but it caps pricing power for consumer access and raises expectations for always-available connectivity.

As a hosting company, the substitutes are broader and more global. A small Bangladeshi business can use a local cPanel host, a registrar bundle, a freelancer’s reseller account, Google Workspace plus a website builder, Cloudflare in front of a cheap origin, a VPS in Singapore or India, or hyperscale cloud. Local hosts win when customers want human support, Bangla communication, local payment, and someone to blame. They lose when customers demand enterprise uptime, compliance certifications, elastic infrastructure, or global brand assurance.

As a reseller, Aayat competes on trust and convenience rather than infrastructure. The brand must persuade customers that it will answer calls, keep services renewed, and solve problems. The APNIC identity helps only for technically aware customers. For most SME customers, the differentiators are price, responsiveness, and relationship.

As a resource identity, Aayat competes in a different market: scarcity and credibility. IPv4 address resources, especially clean ones with low abuse history, have economic value independent of retail customers. They can support hosting, VPN, enterprise NAT pools, dedicated IPs, or future ISP growth. The threat is not customer churn but registry compliance, abuse reputation, route misconfiguration, hijack risk, and supplier conflict.

Ownership, management, and trust signals

The public record confirms a registered network identity but does not provide a robust ownership narrative. The APNIC-derived organisation object names Aayat Host and gives a Dhaka Banani address, phone, and domain email. Administrative and technical roles are generic: “Aayat Host administrator.” The abuse contact includes a Gmail address and an IRT validation date in December 2025. These are operational contacts, not proof of beneficial ownership, financing, management team, or legal incorporation.

That ambiguity matters commercially. In infrastructure markets, trust depends on knowing who can be held accountable. Customers ask: who owns the servers, who controls the domain, who answers abuse complaints, who pays upstream bills, who renews licences, and who has authority to change routes? A thin public profile raises counterparty risk for larger customers. An SME may accept a phone number and a local relationship; an enterprise buyer will want legal documents, tax registration, SLA terms, and escalation contacts.

The contact pattern suggests a small or lightly institutionalized operation. A mature network operator normally has role-based emails such as noc@, abuse@, billing@, and support@ on its own domain, a published NOC page, consistent registry addresses, route-policy records, and visible customer communications. Aayat has some of those ingredients, particularly domain-based abuse/admin contacts, but not the surrounding institutional evidence. This does not mean the operator is unreliable. It means the public evidence is insufficient to assign enterprise-grade operating confidence.

Financing evidence is absent. There are no discovered press releases, funding announcements, M&A records, major procurement notices, or datacenter buildout claims tied to Aayat Host. That absence reinforces the micro-operator or resource-identity interpretation. If a company with a dormant ASN were preparing a material network rollout, one would expect supplier announcements, hiring, licence records, customer marketing, or route activation. The record is instead quiet.

What the evidence proves, suggests, and cannot resolve

The evidence proves that Aayat Host exists as an APNIC-linked network-resource identity. It proves that AS148978 is associated with Bangladesh, AAYAT-AS-AP, and organisation ORG-AH10-AP. It proves that the ASN is currently inactive in the major routing views reviewed here and originates no IPv4 or IPv6 prefixes. It proves that resource-certification data exists for AS148978, 103.175.56.0/23, and 2001:df7:ed80::/48. It proves that at least one Aayat-described prefix, 103.175.56.0/24, is visible through D-NET SERVICE rather than through AS148978.

The evidence suggests that Aayat Host is more hosting/resource-oriented than access-oriented. The name, domain, IP2Location usage classification, and IPGeolocation company classification all point toward hosting or data-center semantics. The absence of access-provider traces, the inactive ASN, and the Bangladesh licensing context make a standalone access ISP reading less likely.

The evidence also suggests supplier dependence. D-NET’s origination of 103.175.56.0/24, combined with D-NET’s upstream relationships, makes D-NET a key observed counterparty. Aayat may control or be associated with the address resource, but D-NET appears to provide the visible global route for at least one /24. Commercially, that makes D-NET’s routing quality, upstream contracts, and abuse handling central to any Aayat service using that range.

The evidence cannot resolve whether Aayat Host has paying customers. It cannot resolve whether Aayat owns servers, rents servers, resells hosting, leases addresses, or is dormant. It cannot resolve beneficial ownership or legal incorporation beyond the network contacts. It cannot resolve whether the 103.175.57.0/24 half of the /23 is unused, privately used, stale in geolocation databases, or routed in a way not captured by the reviewed public sources. It cannot resolve whether Aayat has a BTRC licence under another legal name. These unknowns are not minor; each changes the valuation of the business.

If Aayat has paying hosting customers, the business has recurring revenue and support obligations. If it merely holds resources, the asset is mostly option value and IPv4 scarcity. If it resells through D-NET, gross margin and service quality are supplier-constrained. If it is a hidden access provider under another licence name, the customer base and licence status would be the central diligence issues. The public record is not rich enough to choose among those private states with high confidence, but it is strong enough to reject the idea of Aayat Host as a visibly independent, scaled network.

Commercial judgment

Aayat Host should be treated as a small, infrastructure-adjacent Bangladeshi hosting/resource identity, not as a demonstrated scaled ISP. The strongest assets are registry legitimacy, an APNIC ASN, certified IPv4 and IPv6 resource context, and a domain-linked identity. The weakest assets are operating visibility, independent route origination, public customer evidence, brand presence, and institutional trust signals.

The company’s plausible revenue logic, if active, is narrow recurring service revenue from hosting, managed web services, address-enabled services, or reseller connectivity. Its pricing power is probably low unless it serves relationship-based local customers or controls clean IP addresses with specific utility. Its gross margin is likely supplier-shaped: D-NET or another upstream captures network economics; datacenter or server suppliers capture infrastructure economics; software vendors and registrars capture platform economics. Aayat’s margin, if any, comes from bundling, support, local trust, and customer inertia.

The most important economic fact is that Aayat’s visible network independence is weaker than its resource identity. A resource holder can become more powerful by activating its own ASN, adding upstreams, and making its routing portable. Until that happens, the business is exposed to the operator that actually carries traffic. That is why the hosting-versus-access question should be reframed. Aayat Host is not best understood as choosing between hosting and access at current scale. It is best understood as sitting between resource ownership and outsourced operation. The upside is optionality; the downside is opacity.

Evidence ledger