asn.dev

Observed topology

AS200185 XANDMAIL-ASN Aruba S.p.A.

Hosting APNIC Content

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

Transit

Upstream networks

All 22

Networks observed carrying traffic for AS200185: 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
AS3356Level 3 Parent, LLCTransitIPv4 IPv6240
AS1299Arelion Sweden ABTransitIPv4 IPv6138
AS6939Hurricane Electric LLCTransitIPv4 IPv670
AS174Cogent Communications, LLCTransitIPv4 IPv667
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv629
AS1836green.ch AGResidentialIPv4 IPv610
AS12859BIT BVHostingIPv4 IPv610
AS24482SG.GSHostingIPv4 IPv610
AS34019Hivane AssociationUnclassifiedIPv4 IPv610
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv610

All 22 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS31034Aruba S.p.A.HostingIPv4596

Adjacency

Adjacent networks

All 23

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

ASNetworkTypeFamiliesPaths seen
AS31034Aruba S.p.A.HostingIPv4736
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv6380
AS3356Level 3 Parent, LLCTransitIPv4 IPv6240
AS1299Arelion Sweden ABTransitIPv4 IPv6138
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv6127
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv6114
AS8551Bezeq International Ltd.UnclassifiedIPv4113
AS6939Hurricane Electric LLCTransitIPv4 IPv670
AS33891Core-Backbone GmbHHostingIPv469
AS174Cogent Communications, LLCTransitIPv4 IPv667

All 23 adjacent →

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.