asn.dev

Observed topology

AS213586 SM-Consulting-Services SM Consulting Services, MB

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS213586: 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
AS8772Netassist International EOODUnclassifiedIPv6397
AS29632Netassist International EOODUnclassifiedIPv6196
AS6939Hurricane Electric LLCTransitIPv654
AS41051Openfactory GmbHUnclassifiedIPv637
AS212895Johannes ErnstUnclassifiedIPv623
AS28917Fiord Networks, UABUnclassifiedIPv610
AS198651HOSTLINE, UABUnclassifiedIPv66
AS24482SG.GSHostingIPv62
AS401753BIXCE IncUnclassifiedIPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS205676DCE Solutions UABUnclassifiedIPv633

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS8772Netassist International EOODUnclassifiedIPv6397
AS29632Netassist International EOODUnclassifiedIPv6196
AS6939Hurricane Electric LLCTransitIPv654
AS41051Openfactory GmbHUnclassifiedIPv637
AS205676DCE Solutions UABUnclassifiedIPv633
AS198651HOSTLINE, UABUnclassifiedIPv625
AS212895Johannes ErnstUnclassifiedIPv623
AS28917Fiord Networks, UABUnclassifiedIPv622
AS24482SG.GSHostingIPv63
AS401753BIXCE IncUnclassifiedIPv63

Provenance

Where this comes from

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