asn.dev

Observed topology

AS8820 TAL-DE Tal.de GmbH

Hosting RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS8820: 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 IPv61,008
AS3356Level 3 Parent, LLCTransitIPv4 IPv6629
AS5405Inter.link GmbHUnclassifiedIPv4 IPv6303
AS3320Deutsche Telekom AGMobileIPv4 IPv6256
AS3223Voxility LLPHostingIPv4221
AS6939Hurricane Electric LLCTransitIPv4 IPv646
AS24482SG.GSHostingIPv4 IPv617
AS41692OpenCarrier eGUnclassifiedIPv614

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS15987Portunity GmbHHostingIPv4 IPv6495
AS60123Stadtverwaltung RemscheidUnclassifiedIPv459
AS60128ICIG Business Services GmbHUnclassifiedIPv425
AS43910Intra2net AGUnclassifiedIPv48

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS174Cogent Communications, LLCTransitIPv4 IPv61,162
AS3356Level 3 Parent, LLCTransitIPv4 IPv6836
AS15987Portunity GmbHHostingIPv4 IPv6495
AS5405Inter.link GmbHUnclassifiedIPv4 IPv6372
AS3320Deutsche Telekom AGMobileIPv4 IPv6309
AS3223Voxility LLPHostingIPv4279
AS6939Hurricane Electric LLCTransitIPv4 IPv670
AS60123Stadtverwaltung RemscheidUnclassifiedIPv459
AS41692OpenCarrier eGUnclassifiedIPv630
AS60128ICIG Business Services GmbHUnclassifiedIPv425

Provenance

Where this comes from

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