asn.dev

Observed topology

AS149365 IDNIC-JAVAKREASINDO-AS-ID - PT Java Kreasindo Bersama

Hosting ARIN

Upstreams 4 carry this network
Downstreams 2 this network carries
Adjacent (IPv4) 7
Adjacent (IPv6) 0
Upstream graph Who carries AS149365, and who carries them, drawn as a map up to the transit-free core. 4 exchanges Where AS149365 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS149365: the AS immediately before it in a routing path. Ranked by how many paths showed the relationship, which reflects how widely it is used, not how much traffic crosses it.

ASNetworkTypeFamiliesPaths seen
AS138886PT Data Buana NusantaraResidentialIPv4122
AS58495PT Parsaoran Global DatatransUnclassifiedIPv44
AS138840PT. PARSAORAN GLOBAL DATATRANS - NAPUnclassifiedIPv44
AS24482SG.GSHostingIPv42

Transit

Downstream networks

inferred

Networks for which AS149365 was observed as the last hop before the origin, meaning it appears to provide them transit.

ASNetworkTypeFamiliesPaths seen
AS150558PT Wayabung Global NetworkUnclassifiedIPv42
AS154652PT Rambo Network Telekomunikasi IndonesiaUnclassifiedIPv41

Adjacency

Adjacent networks

observed

Every AS seen directly next to AS149365 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS138886PT Data Buana NusantaraResidentialIPv4122
AS58495PT Parsaoran Global DatatransUnclassifiedIPv44
AS138840PT. PARSAORAN GLOBAL DATATRANS - NAPUnclassifiedIPv44
AS141642PT Ring Media NusantaraResidentialIPv43
AS24482SG.GSHostingIPv42
AS150558PT Wayabung Global NetworkUnclassifiedIPv42
AS154652PT Rambo Network Telekomunikasi IndonesiaUnclassifiedIPv41

Provenance

Where this comes from

Derived from routing tables collected at 2026-11-02 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.44M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.

Inferred from path position, not from any declaration by either party. A network appearing here is carrying these routes; whether that is a paid transit arrangement, a backup, or something else is not something routing data can tell you. Adjacency is not the same as peering. Being next to each other in a path covers paid transit, settlement-free peering and customer connections alike, and routing data cannot distinguish them. Treat this as "these networks exchange routes", nothing more specific.

Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.