Observed topology
AS3292 TDC TDC AS
Residential RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS3292: 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.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 1,344 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 1,299 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 1,209 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 1,046 |
| AS3320 | Deutsche Telekom AG | Mobile | IPv4 IPv6 | 664 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 409 |
| AS577 | Bell Canada | Mobile | IPv4 IPv6 | 338 |
| AS6453 | TATA COMMUNICATIONS (AMERICA) INC | Transit | IPv4 IPv6 | 334 |
| AS6762 | TELECOM ITALIA SPARKLE S.p.A. | Transit | IPv4 IPv6 | 318 |
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 IPv6 | 202 |
Transit
Downstream networks
Networks for which AS3292 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS48854 | team.blue Denmark A/S | Hosting | IPv4 IPv6 | 1,625 |
| AS62319 | Itm8 A/S | Unclassified | IPv4 IPv6 | 1,473 |
| AS44398 | Itm8 A/S | Unclassified | IPv4 IPv6 | 902 |
| AS47527 | DLX A/S | Unclassified | IPv4 IPv6 | 823 |
| AS203953 | Hiper A/S | Unclassified | IPv4 IPv6 | 800 |
| AS49010 | Herning Kommune | Unclassified | IPv4 IPv6 | 689 |
| AS24800 | BornFiber Service Provider ApS | Unclassified | IPv4 IPv6 | 558 |
| AS29156 | DXC Technology Danmark A/S | Unclassified | IPv4 IPv6 | 505 |
| AS49974 | Bo data ApS | Unclassified | IPv4 IPv6 | 502 |
| AS201271 | Nordea Bank Abp | Unclassified | IPv4 IPv6 | 358 |
Adjacency
Adjacent networks
Every AS seen directly next to AS3292 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 4,396 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 3,739 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 2,446 |
| AS48854 | team.blue Denmark A/S | Hosting | IPv4 IPv6 | 2,297 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 1,887 |
| AS3320 | Deutsche Telekom AG | Mobile | IPv4 IPv6 | 1,690 |
| AS62319 | Itm8 A/S | Unclassified | IPv4 IPv6 | 1,473 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 1,454 |
| AS577 | Bell Canada | Mobile | IPv4 IPv6 | 1,452 |
| AS44398 | Itm8 A/S | Unclassified | IPv4 IPv6 | 966 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-15 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.09M 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.