asn.dev

Observed topology

AS206626 PSD Group

Unclassified RIPE NSP

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

Transit

Upstream networks

All 14

Networks observed carrying traffic for AS206626: 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
AS6939Hurricane Electric LLCTransitIPv4327
AS2914NTT America, Inc.TransitIPv488
AS34549meerfarbig GmbH & Co. KGHostingIPv424
AS3741Dimension DataUnclassifiedIPv48
AS17639Converge ICT Solutions Inc.UnclassifiedIPv48
AS24482SG.GSHostingIPv48
AS33891Core-Backbone GmbHHostingIPv48
AS37100SEACOM LimitedUnclassifiedIPv48
AS37721Virtual Technologies & SolutionsResidentialIPv48
AS48185team.blue NVUnclassifiedIPv48

All 14 upstreams →

Transit

Downstream networks

inferred

Networks for which AS206626 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 14

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4327
AS2914NTT America, Inc.TransitIPv488
AS34549meerfarbig GmbH & Co. KGHostingIPv424
AS3741Dimension DataUnclassifiedIPv48
AS17639Converge ICT Solutions Inc.UnclassifiedIPv48
AS24482SG.GSHostingIPv48
AS33891Core-Backbone GmbHHostingIPv48
AS37100SEACOM LimitedUnclassifiedIPv48
AS37721Virtual Technologies & SolutionsResidentialIPv48
AS48185team.blue NVUnclassifiedIPv48

All 14 adjacent →

Provenance

Where this comes from

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