asn.dev

Observed topology

AS395753 KKR - KKR

Unclassified ARIN

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

Transit

Upstream networks

All 13

Networks observed carrying traffic for AS395753: 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
AS702Verizon BusinessUnclassifiedIPv4389
AS703Verizon BusinessUnclassifiedIPv4342
AS174Cogent Communications, LLCTransitIPv4252
AS3356Level 3 Parent, LLCTransitIPv4188
AS7018AT&T Enterprises, LLCResidentialIPv4167
AS701Verizon BusinessResidentialIPv4155
AS3491PCCW Global (HK) Ltd.TransitIPv4128
AS3257GTT Communications Inc.TransitIPv459
AS4637Telstra GlobalUnclassifiedIPv438
AS25394MK Netzdienste Verwaltungs GmbH trading as MK Netzdienste GmbH & Co. KGResidentialIPv424

Transit

Downstream networks

inferred

Networks for which AS395753 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

All 13

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

ASNetworkTypeFamiliesPaths seen
AS702Verizon BusinessUnclassifiedIPv4389
AS703Verizon BusinessUnclassifiedIPv4342
AS174Cogent Communications, LLCTransitIPv4252
AS3356Level 3 Parent, LLCTransitIPv4188
AS7018AT&T Enterprises, LLCResidentialIPv4167
AS701Verizon BusinessResidentialIPv4155
AS3491PCCW Global (HK) Ltd.TransitIPv4128
AS3257GTT Communications Inc.TransitIPv459
AS4637Telstra GlobalUnclassifiedIPv438
AS25394MK Netzdienste Verwaltungs GmbH trading as MK Netzdienste GmbH & Co. KGResidentialIPv424

Provenance

Where this comes from

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