asn.dev

Observed topology

AS6723 UA-XAIM

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS6723: 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
AS6663Euroweb Romania S.R.L.UnclassifiedIPv4 IPv6219
AS28917Fiord Networks, UABUnclassifiedIPv465
AS3255LLC EKSINTECHUnclassifiedIPv4 IPv648
AS6939Hurricane Electric LLCTransitIPv436
AS9002RETN LimitedUnclassifiedIPv4 IPv626
AS3303Swisscom (Schweiz) AGResidentialIPv410
AS24482SG.GSHostingIPv4 IPv67

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS43967TEREMKY LAN ISP LLCUnclassifiedIPv42,802
AS13307"AS6723" LIMITED LIABILITY COMPANYUnclassifiedIPv4 IPv6632
AS15683"AS6723" LIMITED LIABILITY COMPANYUnclassifiedIPv4 IPv6555
AS59636TOV TELEODINResidentialIPv48

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS43967TEREMKY LAN ISP LLCUnclassifiedIPv42,802
AS6663Euroweb Romania S.R.L.UnclassifiedIPv4 IPv62,377
AS3255LLC EKSINTECHUnclassifiedIPv4 IPv61,603
AS13307"AS6723" LIMITED LIABILITY COMPANYUnclassifiedIPv4 IPv6904
AS15683"AS6723" LIMITED LIABILITY COMPANYUnclassifiedIPv4 IPv6555
AS9002RETN LimitedUnclassifiedIPv4 IPv6231
AS28917Fiord Networks, UABUnclassifiedIPv4205
AS3303Swisscom (Schweiz) AGResidentialIPv4121
AS6939Hurricane Electric LLCTransitIPv478
AS24482SG.GSHostingIPv4 IPv665

All 11 adjacent →

Provenance

Where this comes from

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