asn.dev

Observed topology

AS206383 VOXLAN-AS VOXLAN LTD.

Unclassified RIPE Network Services

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

Transit

Upstream networks

All 19

Networks observed carrying traffic for AS206383: 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
AS1299Arelion Sweden ABTransitIPv4 IPv6154
AS6939Hurricane Electric LLCTransitIPv4 IPv669
AS203598SIMPLEX SOFTWARE & INTERNET SERVICES LTDUnclassifiedIPv461
AS3356Level 3 Parent, LLCTransitIPv436
AS9002RETN LimitedUnclassifiedIPv436
AS3257GTT Communications Inc.TransitIPv4 IPv620
AS5511Orange S.A.TransitIPv4 IPv616
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv4 IPv615
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv68
AS24482SG.GSHostingIPv4 IPv68

All 19 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS205874Zero Byte LtdUnclassifiedIPv416

Adjacency

Adjacent networks

All 20

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv6164
AS6939Hurricane Electric LLCTransitIPv4 IPv669
AS203598SIMPLEX SOFTWARE & INTERNET SERVICES LTDUnclassifiedIPv461
AS3356Level 3 Parent, LLCTransitIPv436
AS9002RETN LimitedUnclassifiedIPv436
AS3257GTT Communications Inc.TransitIPv4 IPv623
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv4 IPv618
AS5511Orange S.A.TransitIPv4 IPv616
AS205874Zero Byte LtdUnclassifiedIPv416
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv68

All 20 adjacent →

Provenance

Where this comes from

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