Observed topology
AS29670 IN-BERLIN-AS Individual Network Berlin e.V.
Unclassified RIPE Non-Profit
Transit
Upstream networks
Networks observed carrying traffic for AS29670: 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 |
|---|---|---|---|---|
| AS50629 | LWLcom GmbH | Unclassified | IPv4 IPv6 | 136 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 IPv6 | 115 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 103 |
| AS13030 | Init7 (Switzerland) Ltd. | Hosting | IPv4 IPv6 | 55 |
| AS3320 | Deutsche Telekom AG | Mobile | IPv4 IPv6 | 54 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 54 |
| AS5405 | Inter.link GmbH | Unclassified | IPv4 IPv6 | 27 |
| AS3333 | Reseaux IP Europeens Network Coordination Centre (RIPE NCC) | Unclassified | IPv4 IPv6 | 14 |
| AS17639 | Converge ICT Solutions Inc. | Unclassified | IPv4 IPv6 | 14 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 14 |
Transit
Downstream networks
Networks for which AS29670 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS208135 | Carl Fabian Luepke | Unclassified | IPv4 IPv6 | 382 |
| AS48387 | Christian Seitz | Unclassified | IPv4 IPv6 | 253 |
| AS60729 | Stiftung Erneuerbare Freiheit | VPN | IPv4 IPv6 | 192 |
| AS60802 | Kevin Buehl | Unclassified | IPv4 IPv6 | 175 |
| AS214033 | NOAH FINLEY WOLF | Hosting | IPv4 IPv6 | 131 |
| AS57024 | L33 NETWORKS SARL | Unclassified | IPv4 IPv6 | 130 |
| AS47496 | Yuqi Feng | Unclassified | IPv4 IPv6 | 94 |
| AS200490 | Felix Annen | Unclassified | IPv4 IPv6 | 78 |
| AS207510 | Luca Strick | Unclassified | IPv6 | 78 |
| AS59645 | Tobias Fiebig | Unclassified | IPv4 IPv6 | 73 |
Adjacency
Adjacent networks
Every AS seen directly next to AS29670 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 IPv6 | 702 |
| AS50629 | LWLcom GmbH | Unclassified | IPv4 IPv6 | 540 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 441 |
| AS208135 | Carl Fabian Luepke | Unclassified | IPv4 IPv6 | 382 |
| AS48387 | Christian Seitz | Unclassified | IPv4 IPv6 | 253 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 222 |
| AS60729 | Stiftung Erneuerbare Freiheit | VPN | IPv4 IPv6 | 192 |
| AS3320 | Deutsche Telekom AG | Mobile | IPv4 IPv6 | 182 |
| AS60802 | Kevin Buehl | Unclassified | IPv4 IPv6 | 175 |
| AS5405 | Inter.link GmbH | Unclassified | IPv4 IPv6 | 166 |
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.