asn.dev

Observed topology

AS208016 TINC-AS

Unclassified RIPE

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

Transit

Upstream networks

All 17

Networks observed carrying traffic for AS208016: 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
AS8220COLT Technology Services Group LimitedHostingIPv4 IPv634
AS88811&1 Versatel GmbHResidentialIPv4 IPv619
AS6939Hurricane Electric LLCTransitIPv4 IPv614
AS3320Deutsche Telekom AGMobileIPv4 IPv67
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv63
AS24482SG.GSHostingIPv4 IPv62
AS29632Netassist International EOODUnclassifiedIPv62
AS34019Hivane AssociationUnclassifiedIPv4 IPv62
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv62
AS401753BIXCE IncUnclassifiedIPv4 IPv62

All 17 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS208015DIE Immobiliengesellschaft mbHUnclassifiedIPv4 IPv615

Adjacency

Adjacent networks

All 18

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

ASNetworkTypeFamiliesPaths seen
AS8220COLT Technology Services Group LimitedHostingIPv4 IPv634
AS88811&1 Versatel GmbHResidentialIPv4 IPv619
AS208015DIE Immobiliengesellschaft mbHUnclassifiedIPv4 IPv615
AS6939Hurricane Electric LLCTransitIPv4 IPv614
AS3320Deutsche Telekom AGMobileIPv4 IPv67
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv66
AS24482SG.GSHostingIPv4 IPv64
AS29632Netassist International EOODUnclassifiedIPv64
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv64
AS401753BIXCE IncUnclassifiedIPv4 IPv64

All 18 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.