asn.dev

Observed topology

AS204598 AS-VILLAGENETWORKS Village Networks Ltd.

Unclassified RIPE Cable/DSL/ISP

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

Transit

Upstream networks

All 19

Networks observed carrying traffic for AS204598: 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
AS174Cogent Communications, LLCTransitIPv4 IPv675
AS6939Hurricane Electric LLCTransitIPv4 IPv639
AS12703Pulsant (Scotland) LtdHostingIPv4 IPv630
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv611
AS50304Blix Solutions ASUnclassifiedIPv46
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv64
AS24482SG.GSHostingIPv4 IPv64
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv64
AS48185team.blue NVUnclassifiedIPv4 IPv64
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv64

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS203460Village Networks Ltd.UnclassifiedIPv4 IPv688

Adjacency

Adjacent networks

All 23

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

ASNetworkTypeFamiliesPaths seen
AS174Cogent Communications, LLCTransitIPv4 IPv6112
AS203460Village Networks Ltd.UnclassifiedIPv4 IPv688
AS6939Hurricane Electric LLCTransitIPv4 IPv659
AS12703Pulsant (Scotland) LtdHostingIPv4 IPv633
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv616
AS50304Blix Solutions ASUnclassifiedIPv48
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv66
AS24482SG.GSHostingIPv4 IPv66
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv66
AS48185team.blue NVUnclassifiedIPv4 IPv66

Provenance

Where this comes from

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