Summary

  • AS17494 is an active, sizeable network — approximately 500–1000 Gbps of self-declared traffic, 34–49 originated prefixes depending on the tracker, and public peering at AMS-IX, DE-CIX Mumbai, Equinix Singapore and LINX LON1 — yet no single public record names its operator consistently.
  • The APNIC registry object describes the operator with the free-text line "Telecom Operator & Internet Service Provider as well" and the organizational object ORG-BTTB1-AP carries the legacy name Bangladesh Telegraph & Telephone Board, while PeeringDB names Bangladesh Telecommunications Company Limited (BTCL).
  • The registry's listed abuse contact is flagged invalid by an APNIC remark, meaning the accountability channel of last resort is formally broken in the public record.
  • Monitoring counts diverge by wide margins across trackers — originated prefixes between 34 and 49, observed peers between 66 and 388 — so counterparty due diligence cannot lean on any single vantage point.

The identity problem starts in the registry itself. The APNIC aut-num object for AS17494 carries as-name BTTB-AS-AP and two description lines: "Telecom Operator & Internet Service Provider as well" and "Bangladesh Telegraph & Telephone Board(BTTB)". The organizational object ORG-BTTB1-AP is named Bangladesh Telegraph & Telephone Board. The object was last modified on 2021-01-18, and its notify addresses span two administrative domains, bttb.net.bd and btcl.net.bd — fossil evidence of the 2010-era corporate transition from the state telephone board to its successor company, Bangladesh Telecommunications Company Ltd. The related IRT object IRT-BTTB-BD lists a postal address of "Bangladesh Telecommunications Company Ltd, Moghbazar Telephone Bhaban, Dhaka", confirming the successor occupies the registry role. But the as-name and description were never updated to say so; instead, the description line asserts a role rather than naming a legal entity [https://wq.apnic.net/apnic-bin/whois.pl?object_type=aut-num&searchtext=AS17494].

That un-updated description line is not a cosmetic detail. Third-party aggregators index it, and readers who look up AS17494 on [https://ipinfo.io/AS17494] see the network named "Telecom Operator & Internet Service Provider as well" — a description, not a company. Meanwhile, PeeringDB, which operators rely on for peering policy and contact points, attributes the same AS to "Bangladesh Telecommunications Company Limited(BTCL)" with a website override to btcl.gov.bd, an IRR as-set of AS17494:AS-CUSTOMERS marked Verified, and RIR status ok; its public peering information was updated on 2026-04-24 [https://www.peeringdb.com/asn/17494]. A counterparty vetting a new session therefore sees two different organizations for the same number resource, depending on which database it queries first.

The operational footprint is real and large, whichever name applies. bgp.tools classifies the network as an "Eyeball" type operator, originating 34 IPv4 and 3 IPv6 prefixes, with 354 observed peers, 7 upstreams, 58 downstreams and a customer cone of 278 networks [https://bgp.tools/as/17494]. The upstream list reads like a who's-who of global transit: Bharti Airtel (AS9498), TATA Communications (AS6453), Cogent (AS174), Telecom Italia Sparkle (AS6762), NTT (AS2914), PCCW Global (AS3491) and Arelion (AS1299). Hurricane Electric's toolkit reports even higher counts — 49 originated prefixes, 729 announced, 388 observed BGP peers, and 75,520 originated IPv4 addresses — plus RPKI validation status of 37 valid and 12 invalid originated entries [https://bgp.he.net/AS17494]. A third-party tool, [https://bgp.gibir.net.tr/as/17494], shows yet another picture: 66 peers and 23 networks, with BTCL (AS45588), BdREN (AS63961) and Mango Teleservices (AS17806) among the listed peers.

The divergence itself is the finding. Originated-prefix counts range from 34 to 49 across trackers, and peer counts from 66 to 388 — a spread too wide to attribute to measurement noise alone, since each tracker reports from a different vantage point, at a different time, with different filtering. IPv4 address counts also disagree: 75,264 per IPinfo versus 75,520 per Hurricane Electric. None of these numbers is wrong in a strict sense; each is a snapshot from a specific vantage. But a due-diligence workflow that pulls a single tracker's figure will bake a temporary, vantage-dependent number into a permanent assessment.

The most consequential defect sits in the accountability channel. APNIC's whois lists an abuse contact for AS17494 — and simultaneously carries a remark that this address is invalid [https://wq.apnic.net/apnic-bin/whois.pl?object_type=aut-num&searchtext=AS17494]. For a network that carries eyeball traffic and customers, an invalid registered abuse contact means that network operators, hosting providers and security teams who need to report abuse have no working registry-designated channel. The fallback is PeeringDB, whose organization points to btcl.gov.bd — but PeeringDB is self-registered data, and its contact fields have been flagged as potentially stale in the same snapshot that verified its as-set.

What would resolve the identity split? Three observable conditions. First, an update of the aut-num description and as-name to name the operating legal entity, replacing the description line that currently does duty as a name. Second, a correction or validation of the registered abuse contact so that the APNIC remark disappears. Third, convergence of tracker counts as routing-state changes settle — or, more meaningfully, a published organizational statement tying the AS to a specific legal entity and support channel.

Until then, the prudent reading is: treat the APNIC organizational object and PeeringDB's BTCL attribution as the two best-supported identity claims, treat the description-line name as an artifact, and verify abuse handling through an out-of-band test rather than the registry field.

The economics follow the identity. A state-telecom successor of this scale buys transit from seven global carriers simultaneously — a redundancy premium that reflects both national-importance traffic and the difficulty of being the incumbent in a market where international capacity is the binding constraint. That purchasing power exists whether the operator is called BTTB, BTCL or "Telecom Operator & Internet Service Provider as well".

What the naming confusion does affect is counterparty cost: peering managers spend time resolving identity before signing; abuse reporters waste effort on a dead mailbox; and compliance teams flag the ASN as higher-risk simply because the paperwork does not match the network.