asn.dev

Observed topology

AS203714 LLCFLEX-AS

Unclassified RIPE

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

Transit

Upstream networks

All 15

Networks observed carrying traffic for AS203714: 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
AS199599Telecom-Birzha, LLCUnclassifiedIPv4188
AS43298Storm Networks LLCUnclassifiedIPv4118
AS49063Data Storage Center JSCUnclassifiedIPv482
AS31500Global Network Management IncUnclassifiedIPv478
AS48399Svyaz VSD LLCUnclassifiedIPv442
AS6939Hurricane Electric LLCTransitIPv410
AS8218Zayo Infrastructure France SAUnclassifiedIPv46
AS24482SG.GSHostingIPv46
AS37721Virtual Technologies & SolutionsResidentialIPv46
AS49673Truenetwork LLCUnclassifiedIPv46

All 15 upstreams →

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 15

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

ASNetworkTypeFamiliesPaths seen
AS199599Telecom-Birzha, LLCUnclassifiedIPv4188
AS43298Storm Networks LLCUnclassifiedIPv4118
AS49063Data Storage Center JSCUnclassifiedIPv482
AS31500Global Network Management IncUnclassifiedIPv478
AS48399Svyaz VSD LLCUnclassifiedIPv442
AS6939Hurricane Electric LLCTransitIPv410
AS8218Zayo Infrastructure France SAUnclassifiedIPv46
AS24482SG.GSHostingIPv46
AS37721Virtual Technologies & SolutionsResidentialIPv46
AS49673Truenetwork LLCUnclassifiedIPv46

All 15 adjacent →

Provenance

Where this comes from

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