asn.dev

Observed topology

AS200023 QONNECTED-AS Qonnected B.V.

Residential RIPE

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

Transit

Upstream networks

All 27

Networks observed carrying traffic for AS200023: 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
AS174Cogent Communications, LLCTransitIPv4 IPv6471
AS8455atom86 BVHostingIPv4 IPv6412
AS6939Hurricane Electric LLCTransitIPv4 IPv6205
AS50304Blix Solutions ASUnclassifiedIPv4 IPv652
AS24482SG.GSHostingIPv4 IPv627
AS58057Securebit AGUnclassifiedIPv4 IPv627
AS4657StarHub LtdResidentialIPv425
AS34927iFog GmbHHostingIPv425
AS37100SEACOM LimitedUnclassifiedIPv425
AS37721Virtual Technologies & SolutionsResidentialIPv425

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS208715BroadbandNL B.V.UnclassifiedIPv4286
AS34766atom86 BVUnclassifiedIPv4134
AS211982Contict B.V.UnclassifiedIPv458
AS211713Connectium B.V.HostingIPv4 IPv630
AS208622Fiberlinq B.V.UnclassifiedIPv47

Adjacency

Adjacent networks

All 36

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

ASNetworkTypeFamiliesPaths seen
AS174Cogent Communications, LLCTransitIPv4 IPv6736
AS8455atom86 BVHostingIPv4 IPv6457
AS208715BroadbandNL B.V.UnclassifiedIPv4286
AS6939Hurricane Electric LLCTransitIPv4 IPv6285
AS34766atom86 BVUnclassifiedIPv4274
AS50304Blix Solutions ASUnclassifiedIPv4 IPv661
AS211982Contict B.V.UnclassifiedIPv458
AS24482SG.GSHostingIPv4 IPv650
AS6696VERIXI SAUnclassifiedIPv446
AS17639Converge ICT Solutions Inc.UnclassifiedIPv446

Provenance

Where this comes from

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