asn.dev

Observed topology

AS20640 TITAN-NETWORKS Titan Networks Internet & Telecommunications Service Providing GmbH

Unclassified RIPE

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

Transit

Upstream networks

All 17

Networks observed carrying traffic for AS20640: 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 LLCTransitIPv4 IPv678
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv64
AS24482SG.GSHostingIPv4 IPv62
AS212024Marc SchmittUnclassifiedIPv4 IPv62
AS213241TECHIT.BE SRLResidentialIPv4 IPv62
AS6461Zayo BandwidthTransitIPv41
AS8551Bezeq International Ltd.UnclassifiedIPv41
AS12859BIT BVHostingIPv41
AS17639Converge ICT Solutions Inc.UnclassifiedIPv61
AS20485Joint Stock Company TransTeleComUnclassifiedIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS216106JustFiberNet GmbHUnclassifiedIPv465
AS44227Stefan WildUnclassifiedIPv4 IPv618

Adjacency

Adjacent networks

All 19

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6130
AS216106JustFiberNet GmbHUnclassifiedIPv465
AS44227Stefan WildUnclassifiedIPv4 IPv618
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv611
AS24482SG.GSHostingIPv4 IPv65
AS212024Marc SchmittUnclassifiedIPv4 IPv65
AS213241TECHIT.BE SRLResidentialIPv4 IPv65
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv64
AS8551Bezeq International Ltd.UnclassifiedIPv43
AS20485Joint Stock Company TransTeleComUnclassifiedIPv43

Provenance

Where this comes from

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