asn.dev

Observed topology

AS208753 6NETWORK

Unclassified RIPE Educational/Research

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

Transit

Upstream networks

All 14

Networks observed carrying traffic for AS208753: 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
AS11967Hop179 OUUnclassifiedIPv4 IPv6154
AS34927iFog GmbHHostingIPv6114
AS53667FranTech SolutionsHostingIPv674
AS200950Calibour LimitedUnclassifiedIPv674
AS6517LAKENETWORKSHostingIPv666
AS44324MoeDove LLCResidentialIPv663
AS20473The Constant Company, LLCHostingIPv653
AS41720REVOLUTION PROVIDER SRLResidentialIPv639
AS139317Ningbo Dahuamao Information Technology Co LtdEducationIPv639
AS393577Tritan DevelopmentUnclassifiedIPv637

All 14 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS213573Bryan PediniUnclassifiedIPv632

Adjacency

Adjacent networks

All 15

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

ASNetworkTypeFamiliesPaths seen
AS11967Hop179 OUUnclassifiedIPv4 IPv6154
AS34927iFog GmbHHostingIPv6114
AS53667FranTech SolutionsHostingIPv674
AS200950Calibour LimitedUnclassifiedIPv674
AS6517LAKENETWORKSHostingIPv666
AS44324MoeDove LLCResidentialIPv663
AS20473The Constant Company, LLCHostingIPv653
AS47152Francesco Ascione trading as FIBERSIXResidentialIPv4 IPv644
AS41720REVOLUTION PROVIDER SRLResidentialIPv639
AS139317Ningbo Dahuamao Information Technology Co LtdEducationIPv639

All 15 adjacent →

Provenance

Where this comes from

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