asn.dev

Observed topology

AS42615 igloo22225 June Slater

Unclassified RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS42615: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv6309
AS13335Cloudflare, Inc.HostingIPv4 IPv6137
AS1299Arelion Sweden ABTransitIPv4 IPv668
AS58057Securebit AGUnclassifiedIPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS204318Benjamin Cartwright-CoxUnclassifiedIPv61,279
AS400564Weston Reed, Sole ProprietorshipUnclassifiedIPv4 IPv6169
AS398338Dollar Discount Hosting LLCHostingIPv6104
AS39335June SlaterUnclassifiedIPv4 IPv6102
AS401297June SlaterUnclassifiedIPv4 IPv673

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv61,948
AS204318Benjamin Cartwright-CoxUnclassifiedIPv61,279
AS400564Weston Reed, Sole ProprietorshipUnclassifiedIPv4 IPv6169
AS1299Arelion Sweden ABTransitIPv4 IPv6153
AS13335Cloudflare, Inc.HostingIPv4 IPv6137
AS398338Dollar Discount Hosting LLCHostingIPv6104
AS39335June SlaterUnclassifiedIPv4 IPv6102
AS401297June SlaterUnclassifiedIPv4 IPv673
AS58057Securebit AGUnclassifiedIPv65

Provenance

Where this comes from

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