asn.dev

Observed topology

AS3213 BOGONS-ASN

Residential RIPE

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

Transit

Upstream networks

All 22

Networks observed carrying traffic for AS3213: 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 IPv6244
AS2914NTT America, Inc.TransitIPv4 IPv6190
AS6939Hurricane Electric LLCTransitIPv4 IPv6129
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv642
AS50304Blix Solutions ASUnclassifiedIPv426
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv615
AS24482SG.GSHostingIPv4 IPv615
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv615
AS48185team.blue NVUnclassifiedIPv4 IPv615
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv615

All 22 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS59817Oxletech LimitedUnclassifiedIPv4 IPv6195
AS8330LONAP LtdUnclassifiedIPv42

Adjacency

Adjacent networks

All 24

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

ASNetworkTypeFamiliesPaths seen
AS174Cogent Communications, LLCTransitIPv4 IPv6306
AS2914NTT America, Inc.TransitIPv4 IPv6243
AS59817Oxletech LimitedUnclassifiedIPv4 IPv6236
AS6939Hurricane Electric LLCTransitIPv4 IPv6171
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv658
AS50304Blix Solutions ASUnclassifiedIPv431
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv622
AS24482SG.GSHostingIPv4 IPv622
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv622
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv620

All 24 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.