asn.dev

Observed topology

AS211506 SLAVCOM

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS211506: 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
AS12389PJSC RostelecomResidentialIPv433
AS12714PJSC MegaFonUnclassifiedIPv415
AS6939Hurricane Electric LLCTransitIPv48
AS8447A1 Telekom Austria AGResidentialIPv41
AS24482SG.GSHostingIPv41
AS37721Virtual Technologies & SolutionsResidentialIPv41
AS49673Truenetwork LLCUnclassifiedIPv41
AS50673Serverius Holding B.V.UnclassifiedIPv41
AS56655Gigahost ASUnclassifiedIPv41
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS211883LLC TRILANUnclassifiedIPv463

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS211883LLC TRILANUnclassifiedIPv463
AS12714PJSC MegaFonUnclassifiedIPv462
AS12389PJSC RostelecomResidentialIPv433
AS6939Hurricane Electric LLCTransitIPv417
AS8447A1 Telekom Austria AGResidentialIPv42
AS24482SG.GSHostingIPv42
AS37721Virtual Technologies & SolutionsResidentialIPv42
AS49673Truenetwork LLCUnclassifiedIPv42
AS50673Serverius Holding B.V.UnclassifiedIPv42
AS56655Gigahost ASUnclassifiedIPv42

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.