asn.dev

Observed topology

AS206766 PROXYWING Travchis LLC

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS206766: 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
AS8849Melbikomas UABHostingIPv41,245
AS204490Kontel LLCUnclassifiedIPv4260
AS58325Hydra Communications LtdHostingIPv4236
AS48716PS Internet Company LLPUnclassifiedIPv4186
AS56630Melbikomas UABHostingIPv4181
AS140443PT Herza Digital IndonesiaHostingIPv4118
AS398465Rackdog, LLCResidentialIPv4117
AS263812SONDATECH S.A.S.UnclassifiedIPv459

Transit

Downstream networks

inferred

Networks for which AS206766 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

observed

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

ASNetworkTypeFamiliesPaths seen
AS8849Melbikomas UABHostingIPv41,245
AS204490Kontel LLCUnclassifiedIPv4260
AS58325Hydra Communications LtdHostingIPv4236
AS48716PS Internet Company LLPUnclassifiedIPv4186
AS56630Melbikomas UABHostingIPv4181
AS140443PT Herza Digital IndonesiaHostingIPv4118
AS398465Rackdog, LLCResidentialIPv4117
AS263812SONDATECH S.A.S.UnclassifiedIPv459

Provenance

Where this comes from

Derived from routing tables collected at 2026-11-08 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.