asn.dev

Observed topology

AS206907 UAGROUP UAGROUP LLC

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS206907: 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
AS57455Filanco Ukraine Ltd.UnclassifiedIPv496
AS41435UnderNet LLCUnclassifiedIPv424
AS50263A-Systems Sp. z o.o.UnclassifiedIPv44
AS1257Tele2 Sverige ABMobileIPv42
AS3303Swisscom (Schweiz) AGResidentialIPv42
AS24482SG.GSHostingIPv42

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS211195PE Domoslavskiy Sergiy VolodymyrovychUnclassifiedIPv449
AS39848CityLan LLCResidentialIPv41

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS57455Filanco Ukraine Ltd.UnclassifiedIPv4135
AS211195PE Domoslavskiy Sergiy VolodymyrovychUnclassifiedIPv449
AS41435UnderNet LLCUnclassifiedIPv430
AS50263A-Systems Sp. z o.o.UnclassifiedIPv47
AS3303Swisscom (Schweiz) AGResidentialIPv43
AS24482SG.GSHostingIPv43
AS1257Tele2 Sverige ABMobileIPv42
AS39848CityLan LLCResidentialIPv41

Provenance

Where this comes from

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