asn.dev

Observed topology

AS205847 BORDERLINK

Unclassified RIPE

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

Transit

Upstream networks

All 20

Networks observed carrying traffic for AS205847: 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 IPv6549
AS174Cogent Communications, LLCTransitIPv4 IPv690
AS6939Hurricane Electric LLCTransitIPv4 IPv638
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv614
AS50304Blix Solutions ASUnclassifiedIPv46
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv65
AS48185team.blue NVUnclassifiedIPv4 IPv65
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv65
AS24482SG.GSHostingIPv4 IPv64
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv64

All 20 upstreams →

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 20

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

ASNetworkTypeFamiliesPaths seen
AS6461Zayo BandwidthTransitIPv4 IPv6549
AS174Cogent Communications, LLCTransitIPv4 IPv690
AS6939Hurricane Electric LLCTransitIPv4 IPv638
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv614
AS50304Blix Solutions ASUnclassifiedIPv46
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv65
AS48185team.blue NVUnclassifiedIPv4 IPv65
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv65
AS24482SG.GSHostingIPv4 IPv64
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv64

All 20 adjacent →

Provenance

Where this comes from

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