Skip to main content

AS138734

BTELECOM-AS-IN

Bakliwal Telecom Services Pvt Ltd

Registry

Authoritative registration data

AS number
138734
Name
BTELECOM-AS-IN
Organisation
Bakliwal Telecom Services Pvt Ltd
Country
Flag of India IN India
RIR
APNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

6

IPv6 prefixes

1

Total announced

7

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS138734
103.137.84.0/23 IPv4 /23 not checked
103.166.12.0/23 IPv4 /23 not checked
103.137.84.0/24 IPv4 /24 not checked
103.137.85.0/24 IPv4 /24 not checked
103.166.12.0/24 IPv4 /24 not checked
103.166.13.0/24 IPv4 /24 not checked
2406:bec0::/32 IPv6 /32 not checked

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS138734
Address families
Extreme IX Delhi: Extreme IX LAN 10,000 Mbps IPv4 · IPv6
Extreme IX Mumbai: Extreme IX 10,000 Mbps IPv4 · IPv6
NIXI Delhi 10,000 Mbps IPv4 · IPv6

No rows match “”.

Showing – of

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS138734 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

3 networks seen before AS138734 in AS paths

Observed upstreams
Families
AS9498 BBIL-AP 627 1,666
v4 v6
AS4755 TATACOMM-AS 293 739
v4
AS9583 SIFY-AS-IN 1 2
v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS138734 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS35280 F5 2 5
v4 v6

No rows match “”.

Showing – of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.