Summary

The registration layer of the internet records intentions; the routing layer records behaviour. For most large networks the two agree closely enough that nobody asks. For AS17494 — the autonomous system whose APNIC whois description line reads 'Telecom Operator & Internet Service Provider as well' — the two layers tell different stories about identity, scale and maintenance discipline, and the gap between them is a useful case study in what public network-resource evidence can and cannot prove.

Start with what is not in dispute. AS17494 was allocated by APNIC on 7 December 2000, status Allocated, allocated country Bangladesh, and the allocation is reflected consistently by IPinfo and BGPView. https://ipinfo.io/AS17494 https://bgpview.io/asn/17494 The authoritative whois objects, inspected in this run through third-party mirrors of the APNIC record, describe the aut-num as BTTB-AS-AP, carry the two description lines already quoted, sit under organisation ORG-BTTB1-AP — registered as 'Bangladesh Telegraph & Telephone Board', org-type LIR, addressed at Telejogajog Bhaban, 37/E, Eskaton Garden, Dhaka — and were last modified on 18 January 2021 (the organisation object on 5 September 2023). The maintainer chain runs through APNIC-HM and MAINT-BD-BTTB, with an IRT object addressed to 'Data and Internet Service, Bangladesh Telecommunications Company Ltd, Moghbazar Telephone Bhaban, Dhaka'. https://records.ping.pe/whois/AS17494

Then look at behaviour. At a recent snapshot bgp.he.net observed AS17494 originating 49 prefixes — 36 IPv4 and 13 IPv6 — covering 75,520 IPv4 addresses, with 729 prefixes announced once more-specific advertisements are included, 4,680 IPv4 and 1,619 IPv6 AS paths observed, and 388 observed BGP peers. The same page flags diagnostic conditions: 'AS17494 announces bogons', and of the originated prefixes 37 were RPKI-valid and 12 RPKI-invalid at that snapshot. https://bgp.he.net/AS17494 A per-prefix mirror lists 38 announced prefixes from the ASN, including the aggregates 114.130.128.0/18, 123.49.0.0/18, 180.211.128.0/17, 203.112.192.0/19 and — notably for an APNIC network — 209.58.24.0/24, an ARIN-range block, plus many more-specific /24s; most prefixes there are RPKI-valid, with 103.110.215.0/24 and 2407:5000:b::/48 flagged invalid. https://records.ping.pe/AS17494 Qrator's Radar monitoring, over the window 18 June to 18 September 2026, shows roughly 35 active prefixes with propagation to 521–580 observers — about 100% global visibility — and RPKI and route-object validity on the active rows. That is three months of continuous, globally propagated origination: the strongest single demonstration in this record that the ASN is operated, not merely held. https://radar.qrator.net/as/17494

The interconnection mechanism that makes those routes reachable is visible from both ends. PeeringDB network record 13897, whose organization field reads 'Bangladesh Telecommunications Company Limited(BTCL)', documents interfaces at four exchange points with the same interface addresses that bgp.he.net and WorldIP independently show: 80.249.211.151 and 2001:7f8:1::a501:7494:1 at AMS-IX Amsterdam; 103.27.171.154 and 2401:7500:fff6::267 at DE-CIX Mumbai; 27.111.228.145 and 2001:de8:4::1:7494:1 at Equinix Singapore; and 195.66.226.78 (with 2001:7f8:4::4456:1 in the IPv6 view) at LINX LON1. https://www.peeringdb.com/asn/17494 https://bgp.he.net/AS17494 https://worldip.io/asn/17494 Upstream transit is observed from Bharti Airtel (AS9498), Tata Communications America (AS6453), NTT (AS2914), Telecom Italia Sparkle (AS6762) and Hurricane Electric (AS6939) on the ping.pe peers page, which reports 68 upstreams, 116 peers and 63 downstreams for the ASN; the IPv4 adjacency report at bgp.potaroo.net shows a tighter view of 62 adjacencies — six upstream (adding Zayo AS6461 and PCCW AS3491) and 56 downstream — with downstream networks that include GrameenPhone, Robi/Axiata, BdREN, the Bangladesh Computer Council, BTCL-ISP (AS45588), the University of Dhaka, AmberIT, Radiant, DESCO, the Special Security Force and, across protocol families, Cloudflare (AS14789). https://records.ping.pe/peers/AS17494 https://bgp.potaroo.net/cgi-bin/as-report?as=AS17494&v=4&view=2.0 https://www.cidr-report.org/cgi-bin/as-report?as=AS17494&v=6&view=2.0

Those downstream names are the economically meaningful part of the record. A national-tier transit operator's value is its customer base, and the adjacency lists suggest AS17494 carries routes for a substantial slice of Bangladeshi institutional and commercial connectivity — mobile operators, a national research network, government bodies, universities, and a long tail of local ISPs. The IPv4 report's origination arithmetic (~81,664 addresses originated, ~154,112 with transit, 35 current prefixes with 19 withdrawn inside its report window) is consistent with a network that both serves customers and advertises more-specific routes than its aggregates strictly require. https://bgp.potaroo.net/cgi-bin/as-report?as=AS17494&v=4&view=2.0

Now the discrepancies — because they are not noise, they are the story. Every tracker reports different relationship counts: bgp.he.net 388 observed peers; ping.pe 68/116/63; IPinfo 50 peers, 6 upstreams, 50 downstreams; BGPView 94 peers with 30 IPv4 prefixes, 74 peers and 7 upstreams in the IPv4 view and just 2 IPv6 prefixes visible, against 13 on bgp.he.net; WorldIP 40 prefixes covering only 31,744 addresses. https://bgp.he.net/AS17494 https://records.ping.pe/peers/AS17494 https://ipinfo.io/AS17494 https://bgpview.io/asn/17494 https://worldip.io/asn/17494 bgp.he.net's own IPv4 mirror showed different announcement totals (742 all / 729 v4) than the main page (729 / 716), pure crawl-to-crawl drift in rolling route-view data. https://bgp.he.net/AS17494 The adjacency reports themselves warn that upstream/downstream labels are strictly topological descriptions relative to the collection point, not provider/customer/peer business relationships. https://www.cidr-report.org/cgi-bin/as-report?as=AS17494&v=6&view=2.0 https://bgp.potaroo.net/cgi-bin/as-report?as=AS17494&v=4&view=2.0 The lesson is methodological: with public routing data, the honest unit of evidence is a named tracker's named snapshot, and any article that silently merges them manufactures precision that does not exist.

The identity collision is the deepest discrepancy, and it runs through every layer. The directory entry at btw.media names the operator with the description string — 'Telecom Operator & Internet Service Provider as well' — and reports Network identity AS17494, ASNs: 1, Related networks: 5,006, two services ('Managed network' and 'Internet service provider', each 'Not yet assessed · 1 record'), confidence-tiered relationship edges anchored on Cloudflare (upstream High confidence, 21 records; downstream High confidence, 20 records and Medium, 12 records, latest 2026-06) and a route-origin edge for 203.112.192.0/24 (Medium confidence, 448 records, latest 2026-08), with on-page markers 'Last updated: 2026-05-14' and 'Data as of 2026-07'. https://btw.media/en/directory/telecom-operator-internet-service-provider-as-well But the description string is exactly that: a free-text line in a whois object, not a legal name. The same objects' organisation field names BTTB; PeeringDB names BTCL; the customer as-set's description reads "BTCL's AS-SET for its Customers"; and website attributions across aggregators point to btcl.gov.bd, with PeeringDB listing the peering policy at btcl.com.bd. https://records.ping.pe/whois/AS17494 https://www.peeringdb.com/asn/17494 https://bgp.he.net/irr/as-set/AS17494:AS-CUSTOMERS https://ipinfo.io/AS17494 https://bgpview.io/asn/17494 No source in this package states or dates a formal succession between the Bangladesh Telegraph & Telephone Board and Bangladesh Telecommunications Company Limited; the naming split is an observed co-occurrence on the same ASN's records, and it should be presented as such rather than asserted as corporate history.

The as-set is where the registration ledger most visibly outruns the operational one. AS17494:AS-CUSTOMERS, registered in APNIC, declares on the order of a thousand-plus member ASNs — including AS17494 itself, which is atypical — and contains duplicates, case-inconsistent entries ("as136004", "As133954", "As138497") and malformed identifiers ("AS1347121", "AS386001"). Against this, operational observation shows 56–63 downstream adjacencies. https://bgp.he.net/irr/as-set/AS17494:AS-CUSTOMERS https://records.ping.pe/peers/AS17494 https://bgp.potaroo.net/cgi-bin/as-report?as=AS17494&v=4&view=2.0 An IRR as-set documents declared intent and the reach of import/export policy; it is not a live-peer list, and this one is evidently not cleanly maintained. The aut-num's own import/export policy lines — announce and accept ANY to AS3491, AS7374, AS5400, AS702 and AS6762 — are likewise historical registration text, not proof of current transit contracts. https://records.ping.pe/whois/AS17494

The self-maintained PeeringDB layer adds its own caution. Its self-reported fields claim 500,000 IPv4 prefixes and 50,000 IPv6 prefixes, versus the roughly 30–49 prefixes actually originated in global routing — an error of four orders of magnitude that suggests placeholder data. Its traffic fields (500–1000 Gbps, heavy inbound, Asia Pacific scope, open peering policy, 'Never via route servers') are reproduced by WorldIP and BGPView but remain self-reported; the interconnection facilities it lists — Arelion St. Petersburg SAP/M1, Bharti Airtel Mumbai, TATA Communications Chennai and Mumbai — are declarations, not observations. The record also shows 'Never via route servers' coexisting with documented sessions at four route-server-based exchanges, which is a peering-preference statement, not an absence of IXP presence; its Route Server and Looking Glass URL fields appear without values; RIR status was last updated 2024-06-26 and the record itself on 2023-01-26 with peering info updated 2026-04-24. https://www.peeringdb.com/asn/17494 https://worldip.io/asn/17494 https://bgpview.io/asn/17494

Even the registry hygiene has visible defects. A whois-mirror validation remark, dated 2026-03-31, marks the IRT object's registered abuse mailbox — an address on a gov.bd domain — as invalid while validating a personal gmail.com address; a second mirror's snapshot from 2025-01-28 shows no such remark, so mirrors desynchronize. https://records.ping.pe/whois/AS17494 https://bgpview.io/asn/17494 The remark is itself unverified against whois.apnic.net, which this run did not query directly. bgp.he.net's 'announces bogons' flag coexists with mostly RPKI-valid origination; the two diagnostics measure different things, and neither should be read as a verdict. https://bgp.he.net/AS17494

What does the assembled record prove, and what does it not? It proves, with multi-source corroboration, that AS17494 is a continuously operated transit and ISP network with a Bangladeshi customer base, global transit relationships, presence at four major exchanges and near-universal propagation of its originated space. It does not prove who, in a corporate-law sense, operates it: the record offers BTTB as the registered organisation, BTCL as the operational-facing identity, and a description string as the name most aggregators and directories display.

It does not validate the self-reported scale figures, and it cannot reconcile relationship counts across methodologies. Those are the open conditions: a direct whois.apnic.net query to confirm the current objects and the abuse-contact validation state; a registry or corporate source that dates the BTTB–BTCL succession; and cross-checking the ARIN-range 209.58.24.0/24 origination against RPKI ROA ownership. Until then, the fair summary is the one the evidence supports: the network is real, and its public identity is still partly a description line.