asn.dev

Observed topology

AS215596 KISSGROUP

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS215596: 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
AS62000SERVERD SASHostingIPv4 IPv6336
AS6939Hurricane Electric LLCTransitIPv4 IPv694
AS1299Arelion Sweden ABTransitIPv4 IPv687
AS174Cogent Communications, LLCTransitIPv4 IPv647
AS24482SG.GSHostingIPv4 IPv610
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv610
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv610
AS204092Association GRIFONUnclassifiedIPv4 IPv610
AS6696VERIXI SAUnclassifiedIPv49

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS214708Cloud Telecom SASResidentialIPv4225
AS35426NXT Initiative SASHostingIPv4 IPv658
AS210339APEXI SASUnclassifiedIPv4 IPv638

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS62000SERVERD SASHostingIPv4 IPv6560
AS214708Cloud Telecom SASResidentialIPv4225
AS6939Hurricane Electric LLCTransitIPv4 IPv6123
AS1299Arelion Sweden ABTransitIPv4 IPv6117
AS174Cogent Communications, LLCTransitIPv4 IPv658
AS35426NXT Initiative SASHostingIPv4 IPv658
AS210339APEXI SASUnclassifiedIPv4 IPv638
AS204092Association GRIFONUnclassifiedIPv4 IPv617
AS24482SG.GSHostingIPv4 IPv615
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv615

All 12 adjacent →

Provenance

Where this comes from

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