asn.dev

Observed topology

AS42611 ZZOOMM Full Fibre Limited

Residential RIPE

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

Transit

Upstream networks

All 20

Networks observed carrying traffic for AS42611: 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
AS6461Zayo BandwidthTransitIPv4 IPv684
AS174Cogent Communications, LLCTransitIPv4 IPv681
AS6939Hurricane Electric LLCTransitIPv4 IPv663
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv617
AS50304Blix Solutions ASUnclassifiedIPv410
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv66
AS24482SG.GSHostingIPv4 IPv66
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv66
AS48185team.blue NVUnclassifiedIPv4 IPv66
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv66

All 20 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS213094Full Fibre LimitedUnclassifiedIPv4 IPv6368

Adjacency

Adjacent networks

All 21

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

ASNetworkTypeFamiliesPaths seen
AS213094Full Fibre LimitedUnclassifiedIPv4 IPv6368
AS6461Zayo BandwidthTransitIPv4 IPv6228
AS174Cogent Communications, LLCTransitIPv4 IPv6191
AS6939Hurricane Electric LLCTransitIPv4 IPv675
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv637
AS50304Blix Solutions ASUnclassifiedIPv422
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv613
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv613
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv613
AS6797GlobalConnect ABUnclassifiedIPv411

All 21 adjacent →

Provenance

Where this comes from

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