Skip to main content

AS151505

IDNIC-INNET-AS-ID

PT Iktiar Doa Tawakal

Registry

Authoritative registration data

AS number
151505
Name
IDNIC-INNET-AS-ID
Organisation
PT Iktiar Doa Tawakal
Country
Flag of Indonesia ID Indonesia
RIR
APNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

0

Total announced

2

Announced prefixes

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

Prefixes announced by AS151505
103.222.255.0/24 IPv4 /24 not checked
161.248.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 AS151505
Address families
IIX-Jakarta 10,000 Mbps IPv4
JKT-IX: Main 10,000 Mbps IPv4
OpenIXP / NiCE 10,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 AS151505 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS151505 in AS paths

Observed upstreams
Families
AS147094 MVNET-AS-ID 428 591
v4
AS23947 MORATELINDONAP-AS-ID 98 123
v4
AS141642 IDNIC-RINGNET-AS-ID 18 44
v4
AS4787 ASN-CBN 1 1
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS151505 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 SGGS-AS-AP 1 2
v4
AS35280 F5 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.