Skip to main content

AS23756

PADINET-AS-ID

PADINET - Padi Internet

Registry

Authoritative registration data

AS number
23756
Name
PADINET-AS-ID
Organisation
PADINET - Padi Internet
Country
Flag of Indonesia ID Indonesia
RIR
APNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

41

IPv6 prefixes

9

Total announced

50

Announced prefixes

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

Prefixes announced by AS23756
117.102.224.0/19 IPv4 /19 not checked
202.6.224.0/20 IPv4 /20 RPKI valid
103.242.204.0/22 IPv4 /22 RPKI valid
150.107.132.0/22 IPv4 /22 not checked
103.242.204.0/24 IPv4 /24 not checked
103.242.205.0/24 IPv4 /24 RPKI valid
103.242.206.0/24 IPv4 /24 RPKI valid
117.102.224.0/24 IPv4 /24 not checked
117.102.225.0/24 IPv4 /24 not checked
117.102.226.0/24 IPv4 /24 RPKI valid
117.102.227.0/24 IPv4 /24 not checked
117.102.228.0/24 IPv4 /24 not checked
117.102.229.0/24 IPv4 /24 not checked
117.102.230.0/24 IPv4 /24 RPKI valid
117.102.231.0/24 IPv4 /24 not checked
117.102.232.0/24 IPv4 /24 RPKI valid
117.102.239.0/24 IPv4 /24 RPKI valid
117.102.243.0/24 IPv4 /24 RPKI valid
117.102.244.0/24 IPv4 /24 not checked
117.102.245.0/24 IPv4 /24 RPKI valid
117.102.252.0/24 IPv4 /24 not checked
117.102.253.0/24 IPv4 /24 not checked
117.102.254.0/24 IPv4 /24 not checked
150.107.132.0/24 IPv4 /24 RPKI valid
150.107.133.0/24 IPv4 /24 not checked
202.6.224.0/24 IPv4 /24 RPKI valid
202.6.225.0/24 IPv4 /24 not checked
202.6.226.0/24 IPv4 /24 not checked
202.6.227.0/24 IPv4 /24 not checked
202.6.228.0/24 IPv4 /24 RPKI valid
202.6.229.0/24 IPv4 /24 RPKI valid
202.6.230.0/24 IPv4 /24 not checked
202.6.231.0/24 IPv4 /24 not checked
202.6.232.0/24 IPv4 /24 not checked
202.6.233.0/24 IPv4 /24 not checked
202.6.234.0/24 IPv4 /24 RPKI valid
202.6.235.0/24 IPv4 /24 not checked
202.6.236.0/24 IPv4 /24 not checked
202.6.237.0/24 IPv4 /24 RPKI valid
202.6.238.0/24 IPv4 /24 RPKI valid
202.6.239.0/24 IPv4 /24 RPKI valid
2406:6200::/32 IPv6 /32 RPKI valid
2406:6200:100::/40 IPv6 /40 not checked
2406:6200:2000::/40 IPv6 /40 RPKI valid
2406:6200:200::/40 IPv6 /40 RPKI valid
2406:6200:2100::/40 IPv6 /40 RPKI valid
2406:6200:300::/40 IPv6 /40 not checked
2406:6200:400::/40 IPv6 /40 RPKI valid
2406:6200:500::/40 IPv6 /40 not checked
2406:6200::/40 IPv6 /40 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 AS23756
Address families
AIX 1,000 Mbps IPv4 · IPv6
EdgeNXT 10,000 Mbps IPv4 · IPv6
IIX-Jakarta 10,000 Mbps IPv4 · IPv6
IIX-JawaTimur 1,000 Mbps IPv4 · IPv6
JKT-IX: Main 1,000 Mbps IPv4
NCIX - neuCentrIX 2,000 Mbps IPv4
ODIX Omadata 2,000 Mbps IPv4 · IPv6
OpenIXP / NiCE 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 AS23756 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS23756 in AS paths

Observed upstreams
Families
AS38158 CBN-AS-ID 318 3,723
v4 v6
AS45147 NAPINFO-TRANSIT-AS-AP 175 3,018
v4 v6
AS55818 MCIX-AS-AP 131 2,702
v4 v6
AS7713 telkomnet-as-ap 67 710
v4

No rows match “”.

Showing – of

Observed downstreams

2 networks seen after AS23756 in AS paths

Observed downstreams
Families
AS58497 INTEGRA-AS-ID 160 390
v4
AS153962 APNIC ASN block 17 20
v4

No rows match “”.

Showing – of

Uncertain adjacencies

3 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 2 50
v4 v6
AS35280 F5 1 39
v4
AS58497 INTEGRA-AS-ID 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.