asn.dev

Observed topology

AS45725 KINGS-AS-ID - Kings Network Indonesia, PT

Residential RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS45725: 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
AS133840PT Jala Lintas MediaUnclassifiedIPv41,258
AS38158PT. Cyberindo AditamaUnclassifiedIPv4 IPv61,026
AS55685PT Jala Lintas MediaUnclassifiedIPv4335
AS147094PT. MITRA VISIONER PRATAMAUnclassifiedIPv4 IPv6181
AS59282PT Giga Patra MultimediaResidentialIPv462
AS24482SG.GSHostingIPv4 IPv610
AS35280F5 Networks SARLHostingIPv43

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS207571Windhu PrasetiaUnclassifiedIPv4 IPv6104

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS133840PT Jala Lintas MediaUnclassifiedIPv41,258
AS38158PT. Cyberindo AditamaUnclassifiedIPv4 IPv61,071
AS55685PT Jala Lintas MediaUnclassifiedIPv4 IPv6382
AS147094PT. MITRA VISIONER PRATAMAUnclassifiedIPv4 IPv6189
AS207571Windhu PrasetiaUnclassifiedIPv4 IPv6104
AS59282PT Giga Patra MultimediaResidentialIPv462
AS24482SG.GSHostingIPv4 IPv612
AS35280F5 Networks SARLHostingIPv43

Provenance

Where this comes from

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