asn.dev

Observed topology

AS4622 ID-NIC Indonesia Network Information Center

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS4622: 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
AS55685PT Jala Lintas MediaUnclassifiedIPv4 IPv6408
AS24213PT. Arsen Kusuma IndonesiaUnclassifiedIPv4 IPv673
AS133095PT Pusat Fiber IndonesiaUnclassifiedIPv461
AS24482SG.GSHostingIPv4 IPv612
AS139955PT DATA PRIMA SOLUSINDOResidentialIPv44
AS150506PT Pusat Fiber IndonesiaUnclassifiedIPv43

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS55685PT Jala Lintas MediaUnclassifiedIPv4 IPv6408
AS24213PT. Arsen Kusuma IndonesiaUnclassifiedIPv4 IPv673
AS133095PT Pusat Fiber IndonesiaUnclassifiedIPv461
AS24482SG.GSHostingIPv4 IPv612
AS139955PT DATA PRIMA SOLUSINDOResidentialIPv44
AS150506PT Pusat Fiber IndonesiaUnclassifiedIPv43

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-17 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.18M 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.