Skip to main content

AS152045

IDNIC-PNT-AS-ID

PT Petabyte Network Indonesia

Registry

Authoritative registration data

AS number
152045
Name
IDNIC-PNT-AS-ID
Organisation
PT Petabyte Network Indonesia
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 AS152045
210.79.146.0/24 IPv4 /24 not checked
210.79.147.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 AS152045
Address families
CDIX 10,000 Mbps IPv4
DE-CIX ASEAN 10,000 Mbps IPv4
DE-CIX Jakarta 10,000 Mbps IPv4
IIX-Jakarta 10,000 Mbps IPv4 · IPv6
JKT-IX: Main 10,000 Mbps IPv4
ODIX Omadata 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 AS152045 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

2 networks seen before AS152045 in AS paths

Observed upstreams
Families
AS147094 567 763
v4
AS154146 3 3
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS152045 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 1
v4
AS35280 F5 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.