asn.dev

Observed topology

AS59278 VNTNET-AS-ID PT Jaringan VNT Indonesia

Residential ARIN Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS59278: 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
AS4787PT Cyberindo AditamaResidentialIPv4448
AS4800PT Aplikanusa LintasartaHostingIPv465
AS24482SG.GSHostingIPv48
AS7717OpenIXP ASNUnclassifiedIPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS150211PT Jaringan VNTNET IndonesiaUnclassifiedIPv4197
AS149682PT Aplikasi Platform NomadenUnclassifiedIPv4132
AS149929PT Aplikasi Platform GigaUnclassifiedIPv4132
AS153143PT Melodiva Music GatewayUnclassifiedIPv4132

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS4787PT Cyberindo AditamaResidentialIPv4955
AS150211PT Jaringan VNTNET IndonesiaUnclassifiedIPv4197
AS149682PT Aplikasi Platform NomadenUnclassifiedIPv4132
AS149929PT Aplikasi Platform GigaUnclassifiedIPv4132
AS153143PT Melodiva Music GatewayUnclassifiedIPv4132
AS4800PT Aplikanusa LintasartaHostingIPv4130
AS24482SG.GSHostingIPv416
AS7713PT Telekomunikasi IndonesiaResidentialIPv46
AS7717OpenIXP ASNUnclassifiedIPv62

Provenance

Where this comes from

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