Observed topology
AS20647 IPB IPB Internet Provider in Berlin GmbH
Hosting RIPE NSP
Transit
Upstream networks
Networks observed carrying traffic for AS20647: 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 |
|---|---|---|---|---|
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 132 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 117 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 94 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 26 |
| AS3320 | Deutsche Telekom AG | Mobile | IPv4 | 24 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 11 |
| AS3333 | Reseaux IP Europeens Network Coordination Centre (RIPE NCC) | Unclassified | IPv4 IPv6 | 10 |
| AS48185 | team.blue NV | Unclassified | IPv4 IPv6 | 10 |
| AS48362 | Stadtwerke Feldkirch | Residential | IPv4 IPv6 | 10 |
| AS50300 | CustodianDC Limited | Unclassified | IPv4 IPv6 | 10 |
Transit
Downstream networks
Networks for which AS20647 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS200770 | REQUISIS GmbH | Unclassified | IPv4 IPv6 | 276 |
| AS34591 | havel:lab e.V. | Unclassified | IPv4 IPv6 | 269 |
| AS199789 | Route 128 GmbH | Unclassified | IPv4 IPv6 | 130 |
| AS212583 | FOCUSNET GMBH | Unclassified | IPv4 IPv6 | 121 |
| AS199118 | Heinlein Support GmbH | Hosting | IPv4 IPv6 | 103 |
| AS49130 | SysEleven GmbH | Unclassified | IPv4 IPv6 | 95 |
| AS33811 | Digitas GmbH | Hosting | IPv4 | 75 |
| AS208559 | IPB Internet Provider in Berlin GmbH | Unclassified | IPv4 | 58 |
| AS62317 | digmedia GmbH | Unclassified | IPv4 IPv6 | 54 |
| AS50030 | System & Project GmbH | Unclassified | IPv4 IPv6 | 24 |
Adjacency
Adjacent networks
Every AS seen directly next to AS20647 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 408 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 387 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 341 |
| AS200770 | REQUISIS GmbH | Unclassified | IPv4 IPv6 | 276 |
| AS34591 | havel:lab e.V. | Unclassified | IPv4 IPv6 | 269 |
| AS199789 | Route 128 GmbH | Unclassified | IPv4 IPv6 | 225 |
| AS212583 | FOCUSNET GMBH | Unclassified | IPv4 IPv6 | 121 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 119 |
| AS199118 | Heinlein Support GmbH | Hosting | IPv4 IPv6 | 103 |
| AS49130 | SysEleven GmbH | Unclassified | IPv4 IPv6 | 95 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-25 12:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.17M 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.