Skip to main content

AS46026

BBT-AS-ID

BATAM BINTAN TELEKOMUNIKASI, PT

Registry

Authoritative registration data

AS number
46026
Name
BBT-AS-ID
Organisation
BATAM BINTAN TELEKOMUNIKASI, PT
Country
Flag of Indonesia ID Indonesia
RIR
APNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

14

IPv6 prefixes

0

Total announced

14

Announced prefixes

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

Prefixes announced by AS46026
175.111.112.0/21 IPv4 /21 not checked
103.135.72.0/22 IPv4 /22 not checked
103.135.72.0/24 IPv4 /24 not checked
103.135.73.0/24 IPv4 /24 not checked
103.135.74.0/24 IPv4 /24 not checked
103.135.75.0/24 IPv4 /24 not checked
175.111.112.0/24 IPv4 /24 not checked
175.111.113.0/24 IPv4 /24 not checked
175.111.114.0/24 IPv4 /24 not checked
175.111.115.0/24 IPv4 /24 not checked
175.111.116.0/24 IPv4 /24 not checked
175.111.117.0/24 IPv4 /24 not checked
175.111.118.0/24 IPv4 /24 not checked
175.111.119.0/24 IPv4 /24 not checked

No rows match “”.

Showing of

Source:ripestat:announced-prefixes observed

Observed adjacencies

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

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS46026 in AS paths

Observed upstreams
Families
AS136106 374 3,250
v4
AS138128 292 1,061
v4
AS4800 307 609
v4
AS138840 242 401
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS46026 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

2 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 1 5
v4
AS35280 1 2
v4

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.