asn.dev

Observed topology

AS49584 DATAXION EasyTeam SAS

Unclassified RIPE NSP

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

Transit

Upstream networks

All 11

Networks observed carrying traffic for AS49584: 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 IPv6233
AS8220COLT Technology Services Group LimitedHostingIPv4 IPv6200
AS6939Hurricane Electric LLCTransitIPv4 IPv6182
AS24482SG.GSHostingIPv4 IPv613
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv613
AS6696VERIXI SAUnclassifiedIPv49
AS12779IT.Gate S.p.A.UnclassifiedIPv49
AS20766Association "Gitoyen"UnclassifiedIPv49
AS34927iFog GmbHHostingIPv49
AS37721Virtual Technologies & SolutionsResidentialIPv49

All 11 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS200741EasyTeam SASUnclassifiedIPv4180
AS209567Wshop SASUUnclassifiedIPv4120

Adjacency

Adjacent networks

All 13

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

ASNetworkTypeFamiliesPaths seen
AS6461Zayo BandwidthTransitIPv4 IPv6355
AS8220COLT Technology Services Group LimitedHostingIPv4 IPv6303
AS6939Hurricane Electric LLCTransitIPv4 IPv6222
AS200741EasyTeam SASUnclassifiedIPv4180
AS209567Wshop SASUUnclassifiedIPv4120
AS24482SG.GSHostingIPv4 IPv618
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv618
AS6696VERIXI SAUnclassifiedIPv414
AS12779IT.Gate S.p.A.UnclassifiedIPv414
AS20766Association "Gitoyen"UnclassifiedIPv414

All 13 adjacent →

Provenance

Where this comes from

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