Skip to main content

AS38763

CYBERBINTAN-AS-ID

PT. Cyber Bintan

Registry

Authoritative registration data

AS number
38763
Name
CYBERBINTAN-AS-ID
Organisation
PT. Cyber Bintan
Country
Flag of Indonesia ID Indonesia
RIR
APNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

7

IPv6 prefixes

0

Total announced

7

Announced prefixes

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

Prefixes announced by AS38763
122.129.200.0/24 IPv4 /24 not checked
122.129.201.0/24 IPv4 /24 not checked
122.129.202.0/24 IPv4 /24 not checked
122.129.203.0/24 IPv4 /24 not checked
122.129.204.0/24 IPv4 /24 not checked
122.129.205.0/24 IPv4 /24 not checked
122.129.206.0/24 IPv4 /24 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 AS38763
Address families
IIX-Jakarta 1,000 Mbps IPv4

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 AS38763 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

1 networks seen before AS38763 in AS paths

Observed upstreams
Families
AS4800 LINTASARTA-AS-AP 258 2,084
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS38763 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
AS24482 SGGS-AS-AP 1 1
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.