Observed topology
AS21473 PFALZKOM Pfalzkom GmbH
Unclassified APNIC
Transit
Upstream networks
Networks observed carrying traffic for AS21473: 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 |
|---|---|---|---|---|
| AS5405 | Inter.link GmbH | Unclassified | IPv4 IPv6 | 422 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 361 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 325 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 275 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 93 |
| AS3320 | Deutsche Telekom AG | Mobile | IPv4 IPv6 | 81 |
| AS2914 | NTT America, Inc. | Transit | IPv4 | 55 |
| AS34309 | Link11 GmbH | Unclassified | IPv4 | 49 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 IPv6 | 46 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 IPv6 | 40 |
Transit
Downstream networks
Networks for which AS21473 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS214319 | blackpoint GmbH | Unclassified | IPv4 IPv6 | 314 |
| AS61310 | prego services GmbH | Unclassified | IPv4 IPv6 | 166 |
| AS203604 | Soluvia IT-Services GmbH | Unclassified | IPv4 | 160 |
| AS35501 | Deere & Company Corp | Unclassified | IPv4 IPv6 | 143 |
| AS209400 | KurpfalzTEL GmbH | Unclassified | IPv4 IPv6 | 135 |
| AS43911 | Tom Merlin Eichhorn | Unclassified | IPv4 IPv6 | 96 |
| AS212226 | Jana Steuber | Unclassified | IPv4 IPv6 | 95 |
| AS56368 | Nicola von Thadden | Unclassified | IPv4 IPv6 | 82 |
| AS59675 | mywire Datentechnik GmbH | Unclassified | IPv4 IPv6 | 79 |
| AS209781 | BASF Digital Solutions GmbH | Unclassified | IPv4 | 74 |
Adjacency
Adjacent networks
Every AS seen directly next to AS21473 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS5405 | Inter.link GmbH | Unclassified | IPv4 IPv6 | 870 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 753 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 733 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 503 |
| AS214319 | blackpoint GmbH | Unclassified | IPv4 IPv6 | 314 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 190 |
| AS3320 | Deutsche Telekom AG | Mobile | IPv4 IPv6 | 187 |
| AS2914 | NTT America, Inc. | Transit | IPv4 | 181 |
| AS12857 | Manage Now GmbH | Unclassified | IPv4 IPv6 | 175 |
| AS61310 | prego services GmbH | Unclassified | IPv4 IPv6 | 166 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-16 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.23M 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.