asn.dev

Observed topology

AS49909 DIRECT-ONE-AS Direct One SA

Unclassified RIPE NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS49909: 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, LLCTransitIPv478
AS6939Hurricane Electric LLCTransitIPv4 IPv636
AS9009M247 Europe SRLHostingIPv4 IPv633
AS24482SG.GSHostingIPv4 IPv63
AS20764CJSC RASCOMUnclassifiedIPv42

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS59532COMETEINET TELECOM SRLUnclassifiedIPv4240
AS35261Core Telecom S.R.L.UnclassifiedIPv4180
AS56729AT NET SRLUnclassifiedIPv4180
AS57446Telemont Service S.R.L.UnclassifiedIPv428
AS52189OMEGA NET SRLUnclassifiedIPv411
AS50447ELECTROGRUP SAUnclassifiedIPv45

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS174Cogent Communications, LLCTransitIPv4476
AS59532COMETEINET TELECOM SRLUnclassifiedIPv4240
AS35261Core Telecom S.R.L.UnclassifiedIPv4180
AS56729AT NET SRLUnclassifiedIPv4180
AS6939Hurricane Electric LLCTransitIPv4 IPv6154
AS9009M247 Europe SRLHostingIPv4 IPv6139
AS57446Telemont Service S.R.L.UnclassifiedIPv428
AS5483Magyar Telekom Plc.MobileIPv412
AS52189OMEGA NET SRLUnclassifiedIPv411
AS24482SG.GSHostingIPv4 IPv68

All 12 adjacent →

Provenance

Where this comes from

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