Baipail Network And Internet Service makes a local connectivity bill depend on upstream routes and field repair

Summary

• Baipail Network And Internet Service is identifiable as an Ashulia ISP through a 2022 tariff approval, a BTRC upazila/thana licence-list entry, ISPAB membership, a live company website and an APNIC allocation. Those records support a real local-provider history, but they do not establish that its licence, published packages or retail operation are current in July 2026.
• APNIC allocated 103.181.162.0/23, or 512 IPv4 addresses, to the business in February 2022. Baipail's AS149514 originated both component /24 routes at first. The upper half has been originated by Virgo Communication Ltd's AS58945 since 2024; the lower half moved from AS149514 to Business Zone Limited's AS153038 on 18 June 2026. AS149514 now originates no visible prefix.
• The lower-half handoff was deliberate enough to be reflected in the APNIC address record, route object and RPKI authorisation. It may represent managed routing, wholesale integration, address use by another operator or a wider transition. It does not, by itself, prove a sale, a merger, the end of Baipail's retail service or the physical path used by an Ashulia customer.
• Baipail's website still shows the packages approved in 2022, from 5 Mbps for Tk500 to 20 Mbps for Tk1,200, with a maximum 1:8 contention ratio in the approval letter. Bangladesh introduced lower national price points later. The site does not publish a dated current tariff, subscriber count, aggregate upstream capacity, utilisation, access technology, coverage map or service-level results, so retail speed cannot be converted into installed or usable network capacity.
• The sound assessment is a downgrade from an independently visible regional ISP to a historically licensed local access business with uncertain current routed control. Evidence of two physically independent upstreams, diverse NTTN paths, backup power, stocked spares, crew response and current licensing would be needed before calling the service resilient.

On 18 June, the route stopped ending at Baipail

The clearest fact about Baipail Network And Internet Service is also the most inconvenient for a conventional company profile. Until 17 June 2026, route collectors saw 103.181.162.0/24 originated by Baipail's own autonomous system, AS149514. From 18 June, the same prefix appeared behind AS153038, the autonomous system registered to Business Zone Limited. RIPEstat's routing history shows the change without an overlapping period: Baipail's origin disappears, then Business Zone's begins.

This was not merely a transient path seen by one observer. RIPEstat's current routing status showed the Business Zone origin to every reporting IPv4 peer at the 10 July observation time. Hurricane Electric's prefix view likewise names AS153038 as the origin. The APNIC route object was changed to AS153038 on 18 June, and origin validation for that pairing was valid. An announcement from the old Baipail AS would instead have returned an invalid-ASN result under the current authorisation.

The prefix record carries two identities at once. Its network name and description now say Business Zone Limited, while its maintainer, incident contact and administrative role still point to Baipail. The covering 103.181.162.0/23 allocation remains registered by APNIC to Al Amin trading as Baipail Network And Internet Service. These are not clerical details that can be collapsed into a simple ownership claim. They show that address stewardship, routing origin, technical maintenance and retail service can sit at different boundaries.

There are several plausible explanations. Business Zone may originate the prefix as part of a managed upstream arrangement. Baipail may still operate access lines and customer support while another network supplies the routed core. The addresses may have been assigned for Business Zone's own use. The change may be one stage in a commercial transfer or technical migration. Public routing records cannot choose among those possibilities, and no public announcement located for this profile explains the change.

That uncertainty defines the resilience question. If Baipail still bills households or businesses in Ashulia, a working service could depend on Baipail's local access plant, an NTTN circuit, a handoff into Business Zone, Business Zone's border routers and international connectivity, plus power at every active point. If the retail business has changed hands or gone quiet, the website and historic approval may outlive the network they describe. Either way, the company name alone no longer marks the last globally visible routing decision.

A local ISP history is well supported

The operating history is more substantial than a stray company name. A Bangladesh Telecommunication Regulatory Commission licence list dated 18 December 2024 identifies Baipail Network and Internet Service as an upazila/thana ISP for Ashulia. It gives the address as Baipail Masjid, North Gazirchat, Ashulia, Savar, Dhaka, and lists licence number 14.32.0000.702.47.806.22.439.

The Internet Service Providers Association of Bangladesh entry repeats the company name, Ashulia address, website and phone number. It names Al-Amin as owner and gives membership number C-385. APNIC's covering allocation uses the legal style "Al Amin t/a Baipail Network And Internet Service," connecting the individual, trading name and network resources without requiring a guess from a similar brand.

The company's website is also live. It calls the business an ISP in Baipail, advertises broadband and Wi-Fi, provides phone numbers, and places the office on Baipail Masjid Road near Ashulia thana. Its contact number overlaps with the ISPAB and APNIC records. A linked BTRC tariff approval, dated 10 March 2022, is addressed specifically to Baipail Network and Internet Service.

Together these records establish more than a dormant resource entry. They show a business that obtained local regulatory permission, received a company-specific tariff decision, joined its trade association, presented retail packages, and acquired internet number resources. AS149514 and the covering IPv4 allocation were registered in February 2022, close to the tariff approval. The lower /24 first became globally visible from Baipail's AS in March 2022. The documentary and routing chronology fits the launch or formalisation of a small local provider.

The geography is equally specific. Ashulia is not a claim of nationwide reach. The licensing guideline in force when Baipail was approved defined an upazila/thana licence as authority to serve the administrative area named in that licence. The BTRC ISP guideline distinguished nationwide, divisional, district and upazila/thana providers, and limited the last category to its particular local area.

That is why "regional ISP" is a useful analytical category here, but only at the small end of the range. The public facts support a Baipail and Ashulia access business. They do not support a Dhaka-wide network, a nationwide backbone or service throughout Bangladesh. Nor do they identify every neighbourhood reached inside Ashulia. The office address is not a coverage map.

Current status is weaker than the history

The same sources that establish Baipail also expose a time gap. The BTRC list is a snapshot from December 2024. In Baipail's row, the fields headed licence validity and next renewal date contain 29 May and 30 May 2024. Because both dates had already passed when the list was issued, the row proves that the regulator carried the licensee in that compilation; it does not prove a renewal through July 2026. A BTRC licensee-list landing page confirms the regulator maintains category lists, but the publicly accessible material found here did not provide a newer company-specific validity date.

ISPAB's detailed entry has a similar limitation. It records membership "since" and "valid till" as 31 December 2024. Membership expiration is not the same as business closure, and a stale association page is not a regulatory finding. It simply means that the association listing cannot certify current standing.

The website is live but appears old. Its public page metadata dates the home page to January 2022, and the visible packages correspond to the March 2022 tariff letter. Bangladesh later changed national broadband price points. A BTRC tariff notice published in February 2026 superseded the old price floor, and contemporary reporting described a 5 Mbps maximum price of Tk400 from July 2025. A page that still begins at 5 Mbps for Tk500 is therefore a poor guide to what a customer can order now.

There is one encouraging current signal. APNIC's incident-contact record says Baipail's two network email addresses were validated in March 2026, and the entity was updated in May. That indicates someone still controlled or responded through those contacts shortly before the route transition. It does not show how many subscribers were online, whether invoices were being issued, or whether Baipail rather than another operator was handling service calls.

The responsible conclusion is neither "defunct" nor "fully operational." Baipail has a well-supported operating history and recently maintained resource contacts. Its own autonomous system, however, has no current route, its two component address blocks are now originated by other networks, its public tariff is stale, and no current licence certificate or retail status notice was located. Current independent operation remains unverified.

The /23 tells a longer transition story

APNIC allocated 103.181.162.0/23 to Baipail on 14 February 2022. A /23 contains 512 IPv4 addresses and can be announced as one route or divided into two /24s of 256 addresses each. Baipail used the latter arrangement. RIPEstat history for 103.181.163.0/24 shows AS149514 originating the upper half from 2022 into early 2024.

That upper half then moved first. APNIC's current record describes 103.181.163.0/24 as Virgo Communication Ltd space and its route object authorises AS58945. RIPEstat showed AS58945 as the current origin on 10 July 2026. The sub-allocation record was last changed in June 2024. Virgo is publicly identifiable as an international internet gateway operator; its own records use the Virgo IIG name, and Bangladesh Submarine Cable accounts have listed Virgo Communication Ltd-IIG as a customer.

The lower half remained the visible Baipail route for another two years. Older routing summaries accordingly described AS149514 as a small single-homed network with one upstream, Rego Communications Ltd's AS149994, and one /24. One AS149514 route summary captured that topology, while IPinfo's AS149514 page described 256 IPv4 addresses, no IPv6 and one upstream. Those pages are useful historic snapshots; after the June 2026 origin change, they must not be read as the current state.

The move of 103.181.162.0/24 to Business Zone completed the withdrawal of Baipail's own origin. RIPEstat's AS overview reported the AS unannounced on 10 July, and its announced-prefix response returned no prefix. Its neighbour response also returned no visible neighbour. The number remains registered to Baipail, but a registered ASN without an announcement is not a current traffic path.

This sequence matters more than the raw address count. Baipail once originated both halves of its allocation. One half has been routed by another operator since 2024; the remaining half changed origin in June 2026. That pattern supports a technical or commercial transition away from independent origin at AS149514. It does not reveal whether customer sessions moved with the routes, whether Baipail retained retail responsibility, whether the addresses serve Baipail customers, or whether the physical access network changed at all.

An IPv4 allocation is also not a capacity figure. Five hundred and twelve addresses do not equal 512 subscribers: addresses may be assigned to routers, infrastructure, servers or customers; customers may share addresses through carrier-grade NAT; some addresses may be reserved or unused; and the two /24s are now described under other networks. No subscriber estimate should be derived from the block.

Nor is the absence of a Baipail IPv6 announcement proof that customers lack IPv6. They could receive space originated by an upstream, or receive only IPv4. The public records simply do not show an IPv6 prefix originated by AS149514. For an operator whose own AS is now quiet, current customer addressing needs direct confirmation rather than inference from its 2022 resource allocation.

Route origin is control over an announcement, not a deed to fibre

BGP tells neighbouring networks which autonomous system is making a prefix reachable. It does not describe the fibre route from a home, the ownership of a pole, the location of an optical line terminal, the terms of a wholesale contract or the company that answers the support phone. The current AS153038 origin therefore proves that Business Zone is the globally visible origin of 103.181.162.0/24. It does not prove that Business Zone owns Baipail's drops, cabinets, switches or customers.

The inverse is equally important. APNIC's covering allocation to Baipail does not prove that Baipail currently controls the route at the border. Route collectors and the valid authorisation show that it does not originate the lower /24 today. Registry stewardship and live origin have separated.

The regulatory architecture makes such separation unsurprising. The 2018 BTRC ISP guideline required ISPs to connect to an International Internet Gateway for internet bandwidth, lease transmission from licensed Nationwide Telecommunication Transmission Network operators, and connect to a National Internet Exchange for domestic traffic. It allowed Wi-Fi for access with regulatory approval and referred to local last-mile connectivity. In other words, a small retail ISP was expected to assemble service from layers supplied by other licensed operators rather than own an international cable and national fibre backbone.

At the local edge, Baipail could own or operate customer drops and electronics while leasing transport. It could use fibre to homes, Ethernet in buildings, authorised Wi-Fi links or a mixture. The website says broadband and Wi-Fi, but it does not name GPON, EPON, fixed wireless, cable, radio bands, OLTs, ONUs, tower sites or pole routes. The featured services do not settle the access medium.

At the routed edge, another AS can announce Baipail-allocated space under an authorised arrangement. That may simplify upstream management or migration. It may also remove the visible proof that Baipail has an independently controlled external path. The resilience of such a service depends on the contracts, handoffs and failover configuration between the local operator and the originating network, none of which is public here.

This is why the June transition should not be sensationalised as a hijack. The route object, address description and RPKI authorisation were updated in alignment, and the prefix is globally visible as valid from AS153038. Those coordinated changes look authorised. They also do not justify declaring a merger or acquisition. The sound statement is narrower: the public routing boundary changed, and the commercial and physical boundary behind it is undisclosed.

Retail speed is not installed capacity

Baipail's 2022 approval is unusually useful because it puts numbers around the retail offer. It approved 5 Mbps for Tk500, 8 Mbps for Tk650, 10 Mbps for Tk800, 12 Mbps for Tk850, 15 Mbps for Tk1,000 and 20 Mbps for Tk1,200. It set a maximum shared contention ratio of 1:8. The company site displays all except the 12 Mbps tier and repeats "Unlimited BDIX Bandwidth" and 24/7 phone and online support for each visible package.

These figures describe products, not the network behind them. A 20 Mbps package states the nominal rate sold to one account under approved terms. It does not reveal how many such accounts share an aggregation port, the size of the IIG purchase, the NIX or cache capacity, the oversubscription at an OLT or switch, or the headroom during the evening peak. Even the 1:8 contention limit cannot be converted into an aggregate without the number and mix of subscribers and the points at which sharing occurs.

The distinction is especially important because the website separates "BDIX bandwidth" and an advertised FTP speed of up to 100 MB from the retail internet package. Domestic caches or exchange-reachable content can perform differently from international destinations. A speed test to a nearby server may show the local access and cache path, while a call to a foreign cloud service exercises international transit. Neither result alone measures every part of the service.

The claim of unlimited BDIX bandwidth is also not evidence of direct exchange membership. No Baipail record was found in PeeringDB, and the public routing view does not show AS149514 at an exchange in July 2026. The service could reach domestic content through an upstream or reseller. That is common and technically useful, but it means the exchange path may share the same wholesale handoff as other traffic. Direct port, route-server and physical-location evidence would be needed to describe Baipail as a peer in its own right.

National numbers cannot fill the company gap. BTRC reported 14.95 million ISP and PSTN subscriptions in April 2026, reflecting the importance of fixed access in Bangladesh. It did not publish a Baipail subscriber count in that table. Cloudflare has presented a small estimated user population for AS149514 in prior snapshots, but an estimate tied to an ASN loses meaning after the customer's prefix changes origin. It should not be treated as a billing total.

Installed capacity would require an inventory: upstream committed rates, NTTN circuit sizes, exchange or cache ports, router and switch throughput, OLT uplinks, optical split ratios, radio-sector capacity if any, and power limits at each active site. Usable capacity would then subtract protocol overhead, contention, congestion, failed components, maintenance reservations and failover headroom. None of those company-specific numbers is public.

The later national tariff change sharpens the economics. A lower regulated price can improve affordability, but it also increases the importance of density and cost control for a local operator. Revenue must cover upstream bandwidth, leased transmission, poles or ducts where applicable, active equipment, premises, electricity, batteries, customer devices, installation, billing, licence costs and support labour. Baipail's own current package mix and cost base are unknown, so profitability cannot be calculated. The visible 2022 price card is evidence of the old retail proposition, not of current margin.

The old single-upstream picture cannot be carried forward

Before the origin change, several independent routing summaries agreed on a simple logical topology: AS149514 originated one /24 and reached the wider internet through Rego Communications Ltd's AS149994. That was a meaningful warning about visible concentration. If the one observed adjacency disappeared and no hidden standby session existed, Baipail's route would disappear with it. It was not proof that only one physical cable entered Ashulia, because BGP does not expose every standby circuit or leased path, but it was the only active external relationship visible from the public table.

The current picture belongs to a different network. RIPEstat's AS153038 neighbour view reported five left-side neighbours for Business Zone on 10 July 2026, including AS149994 and AS58945. Its announced-prefix view showed 22 prefixes, including Baipail's former lower /24. At the AS level, Business Zone therefore presents more external reach than the old Baipail origin did.

It would be a mistake to award that entire diversity to Baipail. The neighbour set describes AS153038 across all prefixes and locations. One connection may serve a data centre, another a different city, and another a subset of routes under a commercial policy. A network can have five BGP neighbours while a particular customer handoff still enters one router over one NTTN path. It can also announce the same route to multiple providers that share a building, power feed or fibre corridor.

The prefix-level view is narrower. RIPEstat's looking-glass response for 103.181.162.0/24 returned many global paths in which Virgo Communication's AS58945 sat immediately before AS153038. Other collectors and policies can expose different paths, and an AS path cannot locate a cable. The repeated adjacency nevertheless suggests that Virgo was an important propagation path for this prefix at the observation time. It does not establish that the lower /24 had access to every Business Zone neighbour or that a separate path could carry full load after a Virgo failure.

There is an additional reason to resist easy arithmetic. Virgo already originates the upper half of Baipail's covering allocation, 103.181.163.0/24. When the lower half is originated by Business Zone and often seen immediately behind Virgo, the two routes have different origin ASes but can still converge on the same wider supplier. Two origins are not necessarily two failure domains. The useful resilience question is whether their end-to-end physical and operational chains are independent, not whether two different numbers appear at the right edge of a route path.

Likewise, the continued appearance of Rego among Business Zone's neighbours does not mean Baipail retained its old Rego service. The relationship now belongs to AS153038's public topology. It may carry the Baipail prefix, provide standby, or serve unrelated Business Zone traffic. A current path sample, routing policy from the operators or a controlled failover result would be needed to assign a role.

This distinction has practical consequences during an incident. If the Ashulia access plant and NTTN circuit are healthy but Business Zone withdraws the prefix, customers using addresses in the lower /24 can lose global reach even though local optical light remains good. If Business Zone keeps announcing but its path to the Baipail handoff fails, the route may remain visible while customer packets cannot reach the local edge. If Virgo is a common upstream for both halves, a Virgo fault may affect addresses under two different origins. BGP visibility can show some of these states but not diagnose the street-level break by itself.

The transition may ultimately improve service. A larger origin network can offer more upstreams, more experienced routing staff, better filters and more spare capacity than a very small standalone AS. It may also centralise a failure or escalation path that was once local. Without a statement of the protected service, diverse transport, capacity after failover and responsibility for repair, neither benefit nor risk should be assumed. The routing evidence supports a change in operating architecture; it does not yet support a resilience grade.

The tariff letter describes a resilience standard, not performance

The 2022 approval did more than set prices. It attached Grade of Service conditions. Grade A contemplated multiple upstream redundancy, a point of presence with multiple underground NTTN paths, and continuous network-operations and care service. Grades B and C still referred to upstream and NTTN path resilience, with progressively lower uptime and longer restoration allowances. For an upazila ISP, the table set maximum restoration targets of four, five or six hours depending on grade, excluding delays dependent on IIG or NTTN providers.

Those conditions are valuable because they identify the exact dependencies a regulator expected operators to manage: upstreams, leased transmission, a local point of presence, care coverage and restoration. They are not a measurement of Baipail. The letter does not state which grade the company consistently achieved, publish audit results, or prove that two NTTN paths entered different ducts and buildings.

The approval also required complaint resolution, retention of complaint records and bill reductions after long continuous outages. Customers were to pay half the monthly bill after five continuous days without service, a quarter after ten days, and nothing for that month after fifteen. That is a consumer remedy for severe failure. It does not make a five-day outage acceptable, and it does not show how quickly Baipail historically repaired faults.

Marketing "24/7 support" is similarly bounded. A phone can be answered at any hour without a splicing crew, replacement optic, vehicle or safe site access being available at that hour. Conversely, a small local operator may restore a neighbourhood fault quickly because the technician and customer are close. Public evidence supplies no ticket statistics, staffing roster, mean time to repair, spare inventory or after-hours escalation path for Baipail.

The economic value of local support lies in reducing the time between detection and useful intervention. A remote upstream can see a BGP session fail; it cannot reconnect a severed drop in North Gazirchat. A local technician can inspect optical power and replace an ONU; that technician cannot repair an NTTN backbone or change an upstream route without escalation. Resilience depends on both layers working and on each party knowing where its responsibility begins.

Six failures can produce the same customer complaint

For a subscriber, most faults collapse into one sentence: the internet is down. For the operator, the location of the fault determines cost, repair authority and recovery time.

Customer power or equipment failure. A router, ONU, power adapter or internal cable can fail while the provider network remains healthy. If the customer's premises loses electricity, service ends unless both the network terminal and router have backup power. Baipail publishes no customer-device policy, replacement terms or battery option. The website's generic equipment-return link does not establish what device is supplied.

Local access cut. A fibre drop, distribution cable, Ethernet segment or wireless link can be damaged between the premises and the local aggregation point. The affected group depends on where the cut occurs: one home at a drop, a building at a distribution point, or a neighbourhood at a feeder. Restoration requires a technician who can locate the fault, obtain access, splice or replace the line, and verify light levels or link quality. No Baipail route map or access-medium inventory is public, so the blast radius cannot be estimated.

Point-of-presence power or electronics failure. An OLT, switch, edge router or media converter requires power and often cooling. Batteries cover only their rated load and duration; a generator adds fuel, maintenance and starting risk. The company publishes no point-of-presence count, battery runtime, generator arrangement or dual-feed claim. Bangladesh has seen cable damage and power loss combine in real outages: a 2024 BTRC statement reported by BSS described fibre cuts, tower outages and ISP restoration using generators in the Chittagong Hill Tracts. That example proves the failure combination is real in the country, not that Baipail suffered it.

Leased transmission failure. The BTRC architecture places NTTN transport between a local ISP and wider network services. Two commercial circuits are not physically diverse if they share the same pole, duct, bridge crossing, handhole, building entrance or powered aggregation site. The 2022 letter's reference to multiple underground NTTN paths for its highest grade recognises this problem. Baipail names no NTTN provider and publishes no route-diversity evidence.

Origin or upstream failure. Before June 2026, the lower /24 was visible behind AS149514 and older observers saw Rego Communications as the sole immediate upstream. It is now originated by AS153038. Business Zone has multiple visible neighbours across its entire network, but that does not prove that the Baipail prefix, or any Ashulia handoff, can use all of them during a failure. A second upstream at the origin network is useful only if route policy, transport, power and capacity permit the affected traffic to fail over.

Congestion without a hard outage. All links may remain up while evening demand exceeds a shared access, NTTN, cache or international path. Domestic services can appear fast while foreign applications degrade, or one neighbourhood can slow while the backbone is healthy. Routing visibility cannot measure Baipail's busy-hour utilisation, and the retail rates do not reveal it. Recovery may require capacity purchase or re-engineering rather than a field repair.

A seventh possibility now sits between the layers: transition error. When a prefix changes origin, route objects, authorisations, filters, reverse DNS, customer assignments and monitoring expectations must align. In Baipail's case, the visible route and RPKI state are aligned with AS153038, which reduces one class of failure. The split identity in the address record still leaves operational questions that only the parties can answer.

Ashulia makes a small network economically consequential

The likely service area is not an abstract rural dot. Baipail and Ashulia sit in a dense industrial and residential belt around Savar. The Bangladesh Export Processing Zones Authority describes Dhaka EPZ as a major Savar-Ashulia industrial hub with more than 90,000 workers. Public customs records also place factories on West Baipail Masjid Road and elsewhere in Ashulia.

This context raises the potential cost of a local outage, but it must be used carefully. No public customer list ties Dhaka EPZ, a named factory, a school, a clinic or a government office to Baipail Network And Internet Service. The company's site does mention dedicated links, but it gives no enterprise references or service commitments. It would be wrong to turn geographic proximity into a customer claim.

The defensible affected group is conditional. If Baipail continues to serve local households, those customers depend on connectivity for communications, education, entertainment, remote work and digital payments. If it serves nearby small businesses, an outage can interrupt cloud applications, orders, messaging and point-of-sale functions. If it sells dedicated links, those customers may have higher operational expectations. The number of affected connections and their economic weight remain unknown.

Local density can improve ISP economics because one feeder, cabinet or technician route can serve many premises. It can also concentrate risk: one cut near a busy road or one failed aggregation point can affect many customers at once. Industrial traffic and road works can complicate access to a fault. A small operator's advantage is familiarity with the area; its disadvantage may be limited spare stock and staff depth. Baipail publishes no evidence to quantify either side.

The June route transition adds another concentration question. A retail brand can remain local while more of its control plane and upstream operation is consolidated into a larger network. That may improve capacity, routing expertise and upstream choice. It may also make local service dependent on a remote change queue. The outcome depends on the contract and operating practice, not on whether the customer bill still carries the familiar name.

What would demonstrate real redundancy

The first missing document is current regulatory standing. A licence certificate or current BTRC entry showing the authorised service area and validity period would settle whether the 2024 date gap is administrative history or a material change. A current tariff approval would show which packages and consumer protections apply after the national price revisions.

The second is a plain description of the operating boundary. Does Baipail still sell and support the retail connection? Which organisation operates the local aggregation equipment? Why are 103.181.162.0/24 and 103.181.163.0/24 described under Business Zone and Virgo? Is AS149514 retained for future use, or has external routing permanently moved? Answers need not expose sensitive configurations; they need only identify responsibility.

Physical redundancy requires route-level evidence. Two NTTN services should enter through separate paths, avoid the same pole or duct where practical, terminate on independent equipment and have enough capacity to carry the protected load. A statement that there are two providers is limited public evidence if both lease the same underlying strand or converge on one powered site. Periodic failover records are stronger than a diagram because they show that routing and capacity work when one path is removed.

Power resilience needs a load and duration, not the word "backup." The relevant facts are which OLTs, switches, routers and cooling systems are protected; battery age and tested runtime; generator availability; fuel autonomy; and who responds when a unit fails to start. Customer equipment is a separate boundary. A powered point of presence does not keep an unpowered home router online.

Field recovery can be demonstrated through staffing coverage, escalation contacts, typical acknowledgement time, repair-time distribution, major-incident logs and spare stock. Fibre closures, splitters, drop cable, SFPs, ONUs, power supplies and configured replacement routers matter only if they are compatible and reachable. A small local team does not need a vast warehouse, but it does need enough depth that illness, traffic, simultaneous cuts or unsafe conditions do not stop every repair.

Capacity evidence should separate domestic and international traffic, normal and peak utilisation, and installed and protected throughput. Subscriber package totals can exceed upstream capacity under contention, but the busy-hour experience should remain within the approved service standard. A useful disclosure would show peak utilisation on each critical link, the load after one path fails, and the threshold for augmentation without publishing customer-identifying data.

Finally, route safety should cover both current halves of the /23. The current origins are valid under RPKI, which is positive. Operators should also maintain accurate route objects, prefix filters, maximum-prefix limits, contact records and rollback procedures. Because the covering allocation remains Baipail's while other ASes originate both /24s, clear authorisation and incident responsibility are particularly important.

The bill may still be local, but the proof of resilience is elsewhere

Baipail Network And Internet Service is not an invented label looking for a network. Its Ashulia licence history, ISPAB entry, tariff decision, website, ASN and APNIC allocation all fit a genuine local ISP established in 2022. For several years, AS149514 visibly originated at least part of its address space. That deserves more weight than an unverified social-media page or a generic business listing.

The current evidence nevertheless forces a downgrade. The public tariff is from an older national price regime. The licence and association dates do not demonstrate standing in 2026. No access map, medium, point-of-presence inventory, subscriber count, upstream purchase, NTTN route, utilisation series, power design, crew capacity or recovery result is published. Most decisively, AS149514 no longer originates either half of the allocation made to Baipail.

The routing changes are authorised and orderly enough to rule out casual assumptions of a fault or hijack. They show a structural handoff, not its commercial meaning. Business Zone now originates the lower /24; Virgo originates the upper /24; Baipail remains the holder of the covering allocation and the incident contact on the lower half. That combination is compatible with a continuing retail business whose core is operated elsewhere, but it is also compatible with other arrangements.

For customers, the practical issue is not whose ASN appears at the end of a route. It is who owns the promise when the connection fails. Can the local team repair the drop? Can the NTTN path be bypassed? Can the current origin network reroute traffic? Does backup power last through the outage? Is there enough spare capacity after failover? Can one organisation see the whole incident and coordinate the others?

Until those answers are public, Baipail should be understood as a historically licensed Ashulia access provider with a live brand and recently maintained resource contacts, but without current proof of an independently routed or physically resilient network. The local bill may still fund a valuable service. The evidence does not yet show how much of that service remains under Baipail's direct control, or how quickly the chain would recover when its weakest link breaks.