Skip to main content

AS139431

IJASA-AS-ID

PT. Integrasi Jasa Nusantara

Registry

Authoritative registration data

AS number
139431
Name
IJASA-AS-ID
Organisation
PT. Integrasi Jasa Nusantara
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 AS139431
103.143.22.0/24 IPv4 /24 not checked
103.143.23.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 AS139431
Address families
IIX-Jakarta 10,000 Mbps IPv4 · IPv6
JKT-IX: Main 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 AS139431 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

2 networks seen before AS139431 in AS paths

Observed upstreams
Families
AS137366 IFORTE-NAP-AS-ID 936 1,507
v4
AS23947 MORATELINDONAP-AS-ID 229 366
v4

No rows match “”.

Showing – of

Observed downstreams

2 networks seen after AS139431 in AS paths

Observed downstreams
Families
AS58375 UNUD-AS-ID 592 763
v4
AS137374 IDNIC-PROVBALI-AS-ID 286 361
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 4 5
v4
AS35280 F5 4 5
v4
AS131111 CEPATNET-AS-ID 3 3
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.