AP Jannat Mir Internet Service routes 512 IPv4 addresses, but its Ashulia access network remains a public-record blind spot

Summary

• The strongest evidence of current operation is AS140087. On 10 July 2026 it originated 103.148.82.0/24 and 103.148.83.0/24 through Summit Communications and Earth Telecommunication, with valid RPKI origin authorisations and full visibility among the IPv4 peers counted by RIPE RIS.
• The physical and legal picture is much weaker. The latest company-specific BTRC list found for this review records an Ashulia Upazila/Thana ISP licence with validity ending on 13 July 2024, while no later renewal document was located. That is an unresolved status question, not proof of cancellation.
• Two upstream autonomous systems reduce one form of dependence, but they do not demonstrate two separately powered points of presence, two street routes or automatic failover. No public network map, fibre-ring diagram, capacity statement, outage history, backup-power schedule or field-repair service level was found.
• The evidence therefore supports a small Ashulia access-network classification, but only at a cautious grade. Customers appear to buy a local connection whose quality depends on wholesale transport, a compact IPv4 edge and local repair labour that outsiders cannot yet audit.

The route exists; the operating picture is incomplete

There are two easy mistakes to make with a small Internet provider. The first is to dismiss it because its corporate footprint is slight. The second is to treat an autonomous system number as if it were a complete X-ray of the business. Jannat Mir Internet Service sits between those errors.

The routing evidence is unusually clear for a company with so little conventional disclosure. APNIC's registration for AS140087 identifies Jannat Mir Internet Service in Bangladesh, marks the number resource active and dates its registration to 7 February 2020. The associated 103.148.82.0 to 103.148.83.255 allocation is a portable /23, equal to 512 IPv4 addresses, registered to the same organisation. On the publication date, bgp.tools' live view of AS140087 showed that address space announced as two /24 routes, both RPKI-valid, with Summit Communications, AS58717, and Earth Telecommunication, AS58715, visible as upstreams.

RIPE NCC provides an independent view. Its routing-status record for AS140087 showed two IPv4 prefixes, 512 addresses and no IPv6 announcement. At the 08:00 UTC observation on 10 July, all 327 full-table IPv4 peers included in that result could see the resource. The same record says RIPE RIS first saw one of the network's routes on 12 February 2020. This is persuasive evidence that Jannat Mir controls a small but globally reachable Internet edge and that it was routing on the day of publication.

It is not a subscriber census. It does not say how many homes are connected, whether the access network is fibre all the way to the premises, how much bandwidth is purchased, whether either upstream is saturated at busy hours, or how many minutes a technician needs to reach a broken distribution box. A route can remain visible while a neighbourhood splitter is dark. A provider can also serve many users behind shared addressing, so 512 public IPv4 addresses cannot be converted into 512 connections. Conversely, unused addresses can be announced without carrying customer traffic.

Cloudflare Radar adds a useful but bounded signal. Its AS140087 overview classifies the network in Bangladesh and displays an APNIC-derived estimate of roughly 7,400 users. That should not be repeated as a company subscriber number. APNIC explains that its per-ISP population estimates are derived from sampled advertising measurements, national Internet-population estimates and assumptions about user distribution. APNIC estimates overall uncertainty of about 20 per cent and warns that smaller networks are less reliable. The number suggests human use at a scale consistent with a local access provider; it does not establish contracts, revenue, active lines or service geography.

The appropriate conclusion is therefore asymmetric. Jannat Mir's routed network is well supported. Its access operation is plausible and has several live-looking customer interfaces. Its physical resilience, present regulatory standing and commercial scale are not publicly demonstrated.

A licence tied the company to Ashulia, but the renewal is unresolved

The best geographic anchor comes from the regulator rather than the company's branding. In the Bangladesh Telecommunication Regulatory Commission's Upazila/Thana ISP licence list dated 18 December 2024, entry 748 names Jannat Mir Internet Service, assigns it to Ashulia and gives the address as Jamgora, Diakhali, Zirabo, Ashulia, Savar, Dhaka. It also gives licence number 14.32.0000.702.47.114.23.637. That entry is the strongest basis for calling the company a local or regional ISP rather than merely an address holder.

But the dates matter. The same entry shows licence validity to 13 July 2024 and a next-renewal date of 14 July 2024. A later company-specific e-licence or renewed validity date was not found. The regulator's current License Issuance and Management System says that from 17 May 2025 it moved applications for issue, renewal and changes to electronic licences and instructed existing licensees to create accounts and update their records. That administrative transition makes absence from an older public PDF especially difficult to interpret. It could reflect a lapse, a pending or completed renewal that is not discoverable in the older list, or incomplete publication.

The legal rule is less ambiguous than the company outcome. BTRC's ISP licensing guideline says a licensee should apply 180 days before expiry and that a licence stands cancelled after its expiry if it is not renewed, with penalties if service continues without a valid licence. The record available here does not show whether Jannat Mir completed that step. It would be wrong to call the company currently licensed merely because it once appeared on the list; it would be equally wrong to call it cancelled without a cancellation notice or definitive current register.

The Internet Service Providers Association of Bangladesh offers a secondary clue and another warning about record quality. Its member page for Jannat Mir identifies an Upazila licence type, membership number C-340 and the same broad Jamgora/Ashulia location, but shows no point-of-presence list, no licence number and no establishment date. The page says both "Member Since" and "Valid Till" are 31 December 2025. That internally odd combination is not a substitute for a regulator's renewal record. It does, however, connect the association listing to the same local provider identity.

This unresolved status should change how customers, suppliers and counterparties assess the network. A buyer considering a business connection should request the current e-licence and approved tariff in addition to a service quotation. A wholesale carrier should know which legal entity signs the circuit agreement. A landlord or factory should establish who may install and maintain cable on the premises. These are ordinary diligence questions, not allegations of non-compliance.

Jamgora is not an abstract service area

The company's own contact page narrows the address from an upazila to a commercial street setting. The Jannat Mir contact page places the office at Jamgora Chowrasta, Bagbari Road, opposite Brookhill Market, Ashulia, and publishes three support numbers. Its about page says the service operates in Jamgora and claims optical-fibre Internet. Those statements align with the regulator's locality and with the APNIC address attached to the network registration.

Ashulia is a demanding place for a small access provider because residential and industrial uses sit close together. The Bangladesh Export Processing Zones Authority says Dhaka EPZ helped turn Savar-Ashulia into an industrial hub, with more than 90,000 jobs across garments, shoes, electronics and other manufacturing. That does not prove Jannat Mir serves the export-processing zone or any named factory. It does show why local connectivity can matter beyond evening video traffic.

Jamgora, Diakhali and Zirabo appear repeatedly in descriptions of Ashulia's factory belt. The Export Promotion Bureau, for example, lists YP Ashulia Ltd at Jamgora Bottola on Bagbari Road, while reporting on factory closures has identified Jamgora and Zirabo among the affected industrial locations. These references establish a mixed neighbourhood of households, shops, worker accommodation and industrial premises. They do not establish Jannat Mir's customer list.

That distinction is commercially important. A local provider might connect homes only, small offices and shops, or corporate sites as well. Jannat Mir's navigation offers both residential and corporate Internet pages, but the site gives no verifiable client names, installed-line totals or service boundary. The reasonable description is therefore an Ashulia access provider with potential exposure to both household and business demand, not an industrial-network specialist.

The question "who is affected when it fails?" has to be answered conditionally. If the footprint is concentrated around the published Jamgora office, a distribution failure could affect homes, local merchants, workers using digital payments and communications, and any small offices on the same branch. If corporate circuits are actually sold, the consequences could include production reporting, buyer communications, cloud applications, security monitoring and payroll access. No public evidence permits a count of those users or a claim that a particular factory depends on AS140087.

The retail connection crosses several ownership boundaries

A monthly broadband bill can look local even when most of the path is not owned by the company collecting it. Bangladesh's licensing structure makes that boundary explicit. BTRC's ISP guideline says an ISP should lease transmission from a licensed Nationwide Telecommunication Transmission Network operator, connect to a licensed International Internet Gateway for Internet bandwidth and connect to a National Internet Exchange for domestic inter-operator traffic. It also limits ordinary last-mile lengths to about three kilometres in metropolitan areas and six kilometres elsewhere, subject to local-authority instructions.

For Jannat Mir, the visible Internet path names two external networks. Summit Communications presents itself as a nationwide transmission and international-connectivity provider, with an extensive fibre footprint and services for ISPs. Earth Telecommunication presents AS58715 as an international gateway and IP-transit operation selling connectivity to Internet service providers. Their appearance immediately before AS140087 in public BGP paths is consistent with wholesale upstream service.

That does not disclose the contract. Public routing cannot show whether Jannat Mir buys directly from both companies, reaches one through a reseller, uses one as primary and one as standby, or changes policy by time and destination. It cannot show committed information rates, burst terms, ports, prices, payment status or repair obligations. Nor can it show whether the Summit and Earth handoffs enter the premises on distinct cables.

The ownership boundary can be divided into at least five layers.

First is the customer premises: router, optical network unit or other terminal, local power supply and the drop cable. These may be supplied by the ISP, owned by the subscriber or split between them.

Second is the access plant: distribution fibre or Ethernet, splitters, switches, cabinets and attachment points across the neighbourhood. Jannat Mir's site claims optical fibre but does not publish enough information to establish whether the full footprint is fibre-to-the-home, a mixed fibre-and-copper network, or fibre to local switches with shorter non-fibre drops.

Third is aggregation: the path from local branches to the routing edge. No public point-of-presence list or ring map was found. The ISPAB record explicitly returns no POP entries. It is therefore unknown whether all access branches converge on one room near Jamgora, on several powered sites, or on a carrier facility elsewhere.

Fourth is wholesale national and international transport. The two observed carriers matter here, along with any NTTN and exchange connections that are not visible in the public path.

Fifth is the wider Internet, including submarine and terrestrial international systems, content networks and destination services. A local ISP can engineer the first four layers well and still suffer when a distant cable or national instruction removes capacity. During the April 2024 SEA-ME-WE 5 outage, the Internet Society observed higher latency from Bangladesh to services normally reached through Singapore, while terrestrial routes and local caches reduced the damage. That episode illustrates why a customer's experience cannot be inferred from the condition of the drop cable alone.

The operator boundary is thus not a weakness by itself. Leasing long-haul infrastructure is how the regulated market is designed. The risk comes from an inability to tell where diversity ends. If two commercial upstreams share the same access duct, building entrance, aggregation switch, power feed or upstream border route, they can fail together even though the routing table displays two names.

What two upstreams do and do not buy

AS140087's two upstreams are the most concrete resilience feature in the public record. They are better than a single observed transit relationship because they create the possibility of surviving one carrier's routing or service failure. The routes are also protected at the origin: APNIC explains that RPKI Route Origin Authorisations let the address holder specify which autonomous system may originate a prefix. Both Jannat Mir /24s were marked valid, meaning the observed origin matched the signed authorisation.

These are meaningful positives. A valid origin reduces exposure to certain accidental or malicious route-origin errors. Two upstream paths give the operator policy choices and may support failover. The network also originates the two /24s separately, which can allow different routing treatment.

But none of those facts guarantees continuity. RPKI validates the authorised origin, not the physical health of the route, the legitimacy of every path segment, available capacity or last-mile power. Two BGP adjacencies do not prove two fibres. They do not show that backup routes are tested. They do not show whether both sessions terminate on one router or whether the router has redundant power.

RIPE NCC is explicit about the limits of observation. Its routing-status documentation says results reflect routes seen by RIS collectors and warns that an autonomous system may have neighbours not observed by those collectors. An older RIPE analysis of routing-data limitations notes that backup links may remain invisible until activated. Jannat Mir may therefore have more resilience than the two visible paths, or less physical independence than the two names imply.

The absent PeeringDB entry is another boundary. A query of the PeeringDB network interface for AS140087 returned no network record on the publication date. That means there is no operator-maintained public declaration there of exchange presence, facilities, traffic level, peering policy or network operations contact. It does not prove that Jannat Mir lacks domestic peering or NIX connectivity. PeeringDB participation is voluntary, and Bangladesh's licensing rules separately require NIX connection. It does mean outsiders cannot use that common operator database to verify where the network interconnects.

A serious resilience claim would need a route-and-facility schedule rather than a list of ASNs. It would identify each handoff building, carrier, circuit identifier, capacity, physical entrance and upstream border device; state whether the paths share ducts or poles; list the power autonomy at each site; and record the most recent failover test. Without those details, "dual upstream" should be read as logical diversity at the public edge, not proven end-to-end diversity.

Installed capacity is not visible in the address count

Small access networks are often described by the numbers that happen to be public: address space, advertised speed, estimated users or route count. None is installed capacity.

AS140087 has two /24 announcements. That says the network can originate 512 IPv4 addresses. It says nothing about whether the upstream handoffs are 1 Gbps, 10 Gbps or another size; whether both are simultaneously usable; how much capacity is committed; or how much remains free during the evening peak. The lack of a visible IPv6 prefix is evidence that AS140087 is not publicly originating IPv6, but it does not reveal the private addressing or translation design inside the access network.

The company website is particularly unsafe as a capacity source. Its home and package pages mix Bangla navigation and genuine-looking local support details with dollar-denominated offers, claims of 1 Gbps service, invented entertainment brands, zeroed counters, generic staff names and Latin placeholder text. The package page cannot support a claim about current speed, price, contention ratio or product availability. The contact page is more useful because its location and support numbers align with independent records, but even its claim of round-the-clock support is not backed by ticket statistics or service reports.

Bangladesh's tariff regime adds another reason to separate an advertised number from a delivered experience. BTRC's One Country, One Rate description established nationally framed shared-broadband prices and service expectations, and the underlying tariff order refers to grades of service and penalties. A new BTRC tariff notice was published in February 2026, but no current Jannat Mir approval was located. Consequently, no package price in the unfinished company site should be treated as current.

Usable capacity is the minimum capacity left after all bottlenecks and failure conditions are considered. A 10 Gbps port feeding an oversubscribed aggregation switch may deliver less than a smaller well-managed circuit. A second 10 Gbps port that shares a single fibre approach may add busy-hour headroom but no protection against a cable cut. A battery-rated cabinet may have little autonomy if batteries are old, hot or not charged. A large stock of customer devices may still be useless if the correct optical module or splice enclosure is missing.

For this company, installed and usable capacity remain undisclosed. The only defensible quantitative statements are the routed address count, the number of visible prefixes and upstreams, and the absence of an observed IPv6 origin.

Failure path one: the last mile is a repair business

For a customer, the most immediate failure is often not BGP. It is a severed drop, a damaged distribution fibre, a failed switch, a disturbed connector or a powerless customer device. The company controls some of these points and merely responds to others.

Jannat Mir's own pages make field labour part of the proposition. The site provides several phone numbers, a complaint form and a bill reminder that tells customers to contact support if service fails. Its about page has an unfinished counter for line workers rather than a real staffing number. The public face therefore acknowledges support as a local function but does not reveal the crew size, shift coverage, transport, skill mix or spare inventory needed to perform it.

That missing detail matters in an overhead-cable environment. Reporting from Dhaka has documented municipal removal of hanging Internet and television cables, with providers demanding a permanent solution for last-mile cable. A USAID assessment of Bangladesh's digital ecosystem identified damaged towers and cut fibre as physical-security challenges and reported substantial monthly cable-cut losses cited by an ISP. These are sector-wide observations, not evidence of a Jannat Mir incident. They show why route length, attachment rights and repair access belong in any assessment of a local network.

A single access cut can have different blast radii. A cut customer drop affects one premises. A cut feeder before a splitter or access switch can remove a street or building. A cut aggregation fibre can isolate several branches while AS140087 remains globally visible through equipment at the core. From outside, all three may look like a complaint that "the Internet is down," but the repair resources are different.

The right operating questions are physical. Are feeder routes recorded accurately? Are fibres labelled at both ends? Are spare cores available? Are vulnerable road crossings protected? Does the operator have permission to work on each pole, building and market frontage? Are splicers and optical test equipment available at night? Are compatible optical network units, power adapters, small-form-factor pluggable modules and switches stocked locally? What is the mean time to locate a fault, not merely the mean time to close a ticket?

No public answer was found for Jannat Mir. The local address and multiple support numbers suggest proximity, which can shorten dispatch. They do not prove response performance. A small provider's advantage is often that a caller reaches someone who knows the street. Its disadvantage can be that the same few people sell connections, collect bills, configure routers and repair every cut. Until crew and incident data are available, local support labour should be treated as essential but unquantified capacity.

Failure path two: power can defeat an intact fibre

Optical fibre does not require power along every metre, but the devices at both ends do. A customer router and optical terminal need electricity. So do aggregation switches, optical line terminals, border routers, monitoring systems and cooling. The wholesale handoff depends on powered carrier equipment too.

The Jannat Mir site does not publish backup-power information. There is no battery runtime, generator arrangement, fuel reserve, dual-feed design or maintenance record for the Jamgora office or any remote cabinet. The public routing data cannot fill that gap. An ASN can continue to announce from a carrier facility while an access switch in Ashulia is dark, or disappear entirely if the routing equipment and handoffs share the same unprotected site.

Bangladesh's wider telecom sector illustrates the cost. A May 2026 analysis in The Daily Star on uninterrupted power for telecom networks described the much higher cost of diesel generation compared with grid electricity and the operational burden of sustaining connectivity through extended outages. That article concerns mobile infrastructure, not Jannat Mir's fixed network, but the engineering principle is shared: batteries convert a short interruption into continuity only until their stored energy is exhausted.

Power resilience has to be measured per layer. A subscriber may run a router from a small backup supply, yet still lose service because the building switch has none. The local switch may have a battery, yet lose the upstream because the next aggregation point is dark. A well-powered core may still be inaccessible if both wholesale carriers enter through an unpowered intermediate location. Stating that "the fibre works during load shedding" without identifying these active points is not a resilience claim.

For customers deciding whether to rely on this network, the practical test is an outage matrix. The operator should say which access technologies remain live during a grid cut, for how long, and under what load. It should distinguish the office, each remote cabinet and each carrier handoff. Business users should test their own router and terminal backup as well. Nothing in the available record shows that this work has or has not been done.

Failure path three: two carriers can still share one fate

The Summit and Earth paths lower the risk of a purely carrier-specific routing failure. They do not eliminate upstream loss.

One shared-fate possibility is the local approach. Both logical services could be delivered over one NTTN fibre or one building entry. Another is power: two handoffs can terminate in the same rack. A third is equipment: both BGP sessions can live on one border router. A fourth is policy: a configuration error can withdraw both /24s from both carriers at once. A fifth is national concentration beyond the immediate upstreams, where international routes converge on common terrestrial or submarine systems.

The 2024 national blackout shows the difference between engineering diversity and administrative reach. The Daily Star reported that international terrestrial and submarine bandwidth was withdrawn during the July shutdown. That event was not an accident and says nothing specific about Jannat Mir's conduct. It demonstrates that two commercial upstream names cannot protect a local access provider against every national-layer interruption.

Ordinary upstream incidents are less dramatic but more frequent: a port failure, maintenance error, fibre cut, route leak or payment dispute. The operator needs both technical failover and enough surviving capacity. If a primary 10 Gbps service fails onto a 1 Gbps backup, routes may remain up while applications become unusable. If inbound and outbound policy are not tested, some destinations may blackhole or return asymmetrically. Public BGP views do not disclose these conditions.

The evidence needed to upgrade the resilience assessment is straightforward: two physically diverse carrier letters or circuit diagrams; photos or facility records showing separate entries; router and power topology; failover test logs; and traffic graphs showing that either remaining circuit can carry an agreed critical load. The public record offers none of these, so the two-upstream result is a positive signal with a strict ceiling.

Failure path four: congestion can hide behind a healthy route

Congestion is the failure that leaves every indicator deceptively green. The prefix is visible, the optical light is on, the customer is authenticated and packets move, but demand exceeds a bottleneck. Video buffers, calls break up and cloud sessions stall.

For a compact provider in a mixed residential and industrial area, demand may be uneven. Household use can peak in the evening. Business traffic can rise during working hours. Local caches or exchange routes can make domestic content fast while international applications remain constrained. The public address allocation cannot distinguish any of this.

The company publishes no traffic graphs, utilisation thresholds, contention policy, international-versus-domestic speed definition or latency objectives. Its unfinished package page should not be used to infer any. Cloudflare's AS page shows traffic observations and an estimated user population, but external application traffic is not a substitute for interface counters or contracted capacity.

Economically, this is where the monthly bill becomes a series of allocations. Part pays for upstream Internet capacity. Part pays for leased transport. Part covers address, routing, switching and access equipment. Part covers attachments, premises, power and backup. Part pays staff who answer phones, collect bills, provision customers and splice cables. Part funds replacements and growth. A low retail price can be sustainable if density is high, wholesale costs are favourable and operations are disciplined. It can also encourage high contention or defer maintenance. No company accounts are available to decide which description fits Jannat Mir.

Bangladesh had 14.62 million ISP and PSTN Internet subscribers in November 2025, according to BTRC's national subscriber series. That scale indicates a large fixed-access market, but it does not allocate any subscribers to Jannat Mir. The same market includes licensed nationwide providers, local licence holders and, according to recent reporting, many unlicensed resellers. A small operator therefore competes not only on advertised speed but on street availability, installation time, local content, trust and repair response.

The only credible way to evaluate congestion would be to inspect time-series utilisation on each access uplink and carrier handoff, alongside packet loss and latency to domestic and international destinations. The useful figure is not a port's nameplate rate but peak sustained load under normal and failover conditions. Until those measurements are disclosed, capacity remains unknown.

The bill and complaint pages are operational signals, not audited scale

Jannat Mir's most revealing public page is not its glossy home page. It is the payment-reminder subdomain, which tells a customer that service has been automatically disconnected for non-payment, gives a monthly deadline, names mobile-payment and cash options, repeats the Jamgora location and directs faults to support. The page is simple, but it describes the mundane loop that keeps a local ISP alive: provision, authenticate, bill, collect, suspend, restore and repair.

That is stronger evidence of an access business than the stock photographs and implausible dollar packages elsewhere on the site. It suggests that Jannat Mir has at least configured a customer-facing suspension and collection process. It cannot show how many customers have encountered it, whether the system is current, whether payment reconciliation is automated, or whether the process meets present consumer-protection and financial requirements.

The same caution applies to complaints. A complaint form and several telephone numbers indicate channels. They do not show whether calls are answered, tickets are timestamped, faults are classified, credits are issued or repeat incidents are analysed. "24/7 support" is a marketing statement until response and restoration performance can be examined.

For a small network, billing and field repair are coupled. Cash collected this month funds wholesale invoices, wages, fuel, spares and expansion. Slow collection can threaten a carrier payment; aggressive suspension can lose customers; weak fault handling can turn a technical incident into churn. The public site makes this coupling unusually visible but provides no financial statements or service metrics.

The commercial due-diligence request should therefore be modest and specific: current licence, approved tariff, anonymised active-line count, monthly churn, ageing of receivables, wholesale capacity and cost bands, capital-spares policy, ticket volumes, median first response, median restoration and the share of faults attributable to customer premises, access plant, power and upstreams. These figures would reveal far more than another claim of "high speed."

What can be said about current operating status

Three independent classes of evidence point towards an operating network on 10 July 2026.

The first is live routing. Two IPv4 /24s were originated by AS140087, visible across RIPE RIS and accepted through two upstreams. The routes were RPKI-valid.

The second is identity consistency. APNIC, BTRC, ISPAB and the company pages all connect Jannat Mir Internet Service to Bangladesh and, more specifically, Jamgora/Ashulia. Contact details also overlap across several records.

The third is customer-facing infrastructure. The company domain exposes local-language residential and corporate navigation, support channels, a complaint page and a bill-suspension page. Although much of the site is unfinished, these elements are tailored to a local access operation.

Against that evidence are serious gaps. The latest located licence date had already passed. The ISPAB membership page does not demonstrate present validity. The website contains extensive placeholder material and cannot support package or capacity claims. No current network map, POP list, NIX record, PeeringDB declaration, named customer, tariff approval, financial statement, outage notice, traffic report, power design or crew metric was found.

The resulting operating-status judgement is "active routed network; access operation likely; current authorisation and resilience unverified." That is a downgrade from a fully evidenced regional infrastructure operator, but not a downgrade to a mere historical name. The distinction matters. A route observed today is more probative than a stale marketing page, while a route alone is much less probative than a current licence and physical asset schedule.

What would change the grade

The next increment of confidence does not require a grand disclosure. A small set of ordinary documents would resolve most of the uncertainty.

First, a current BTRC e-licence or regulator entry would settle the renewal question. It should match the operating name, licence number, category and Ashulia scope.

Second, an access map should mark the service boundary, aggregation sites and major feeder routes without exposing customer addresses. It should distinguish owned access plant from leased NTTN transport and state whether fibre is aerial, underground or carried through third-party premises.

Third, the company should identify the two upstream handoff locations and whether they are physically and electrically independent. A topology need not publish sensitive router addresses to show separate buildings, ducts, devices and power systems.

Fourth, capacity evidence should state carrier port rates, committed bandwidth, normal peak utilisation and single-upstream failover capacity. A month of graphs would distinguish nameplate capacity from usable headroom.

Fifth, the power schedule should list backup type and tested runtime for the core, handoffs and access cabinets. Customer-premises limitations should be explained separately.

Sixth, field operations should be made measurable: number of trained technicians per shift, service radius, stock of critical spares, fault-location capability, escalation path and restoration performance by incident class. These figures would test the proposition that proximity in Jamgora translates into resilience.

Finally, the provider should publish a concise incident history and maintenance channel. Silence is not evidence of perfect uptime. A credible outage notice that states scope, start time, cause, workaround and restoration can be a stronger trust signal than an unsupported availability percentage.

Until such evidence appears, customers should evaluate Jannat Mir at the service address rather than assume that Internet-edge diversity reaches the wall socket. Test latency and loss at busy hours. Ask what survives a power cut. Confirm how a corporate circuit is separated from residential contention. Request the current licence and tariff. For critical premises, combine connectivity with an independently routed backup and test the failover.

A small edge with a large local burden

AS140087 is small in address space but not necessarily small in consequence. Its two prefixes can carry the daily communications of thousands of people, according to an uncertain external estimate. Its likely service area sits inside a dense industrial and residential belt. A failure there may be invisible to national statistics while being immediate for a street, market, apartment building or workplace.

The available evidence also shows why the economics of a local ISP cannot be reduced to buying bandwidth and reselling it. Jannat Mir's customer pays one local bill, but the service crosses customer equipment, access fibre, attachment points, powered aggregation, leased transmission, exchange connectivity, two observed upstream carriers and international systems. Every layer has a different owner and repair clock. The local provider remains the party the customer calls even when the fault belongs elsewhere.

Two upstreams and valid route origins are worthwhile foundations. They demonstrate routing competence at the visible edge. They do not answer the questions that decide recovery: whether there is a second physical route, whether either circuit has spare capacity, whether the core and cabinets have power, whether a replacement module is on the shelf, and whether a technician can reach a cut fibre in the rain.

That is the evidence boundary around AP Jannat Mir Internet Service. The network should be recognised as a currently visible, locally anchored routing operation. It should not yet be presented as a proven resilient regional infrastructure platform. The next proof belongs on the ground in Ashulia: a current licence, a mapped access plant, separate handoffs, tested backup power, measured capacity and repair records that connect the public route to the customer's actual line.