asn.dev

Observed topology

AS61124 MARSTONS

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

All 22

Networks observed carrying traffic for AS61124: 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
AS3356Level 3 Parent, LLCTransitIPv4 IPv655
AS1299Arelion Sweden ABTransitIPv448
AS6939Hurricane Electric LLCTransitIPv4 IPv644
AS174Cogent Communications, LLCTransitIPv4 IPv634
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv614
AS50304Blix Solutions ASUnclassifiedIPv48
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv65
AS24482SG.GSHostingIPv4 IPv65
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv65
AS48185team.blue NVUnclassifiedIPv4 IPv65

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS206347Wessex Internet LimitedResidentialIPv4148
AS42217The Goodwood Estate Company LimitedUnclassifiedIPv4113

Adjacency

Adjacent networks

All 24

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4216
AS206347Wessex Internet LimitedResidentialIPv4161
AS42217The Goodwood Estate Company LimitedUnclassifiedIPv4113
AS3356Level 3 Parent, LLCTransitIPv4 IPv679
AS174Cogent Communications, LLCTransitIPv4 IPv664
AS6939Hurricane Electric LLCTransitIPv4 IPv660
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv620
AS50304Blix Solutions ASUnclassifiedIPv412
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv67
AS24482SG.GSHostingIPv4 IPv67

Provenance

Where this comes from

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