Observed topology
AS3209 VODANET Vodafone GmbH
Residential RIPE Cable/DSL/ISP
Transit
Upstream networks
Networks observed carrying traffic for AS3209: 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 |
|---|---|---|---|---|
| AS1273 | IDDQD-AS | Business | IPv4 IPv6 | 14,005 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 2,917 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 IPv6 | 604 |
| AS3320 | Deutsche Telekom AG | Mobile | IPv4 IPv6 | 517 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 38 |
| AS24961 | WIIT AG | Hosting | IPv6 | 1 |
| AS58057 | Securebit AG | Unclassified | IPv4 | 1 |
Transit
Downstream networks
Networks for which AS3209 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS15933 | ith Kommunikationstechnik GmbH | Unclassified | IPv4 | 1,081 |
| AS201299 | BWI GmbH | Unclassified | IPv4 IPv6 | 538 |
| AS21207 | E.ON Verwaltungs GmbH | Unclassified | IPv4 IPv6 | 512 |
| AS213251 | Marcel Andrew Zaiser trading as Metaliance ISP Systems e.k | Unclassified | IPv4 IPv6 | 411 |
| AS29239 | I-NetPartner GmbH Online Services | Unclassified | IPv4 IPv6 | 349 |
| AS15415 | Oberberg-Online Informationssysteme GmbH | Unclassified | IPv4 IPv6 | 318 |
| AS204028 | Dolphin IT-Systeme e.K. | Unclassified | IPv4 IPv6 | 264 |
| AS198311 | Flughafen Berlin Brandenburg GmbH | Unclassified | IPv4 IPv6 | 243 |
| AS201878 | Stadtwerke Muehlheim am Main GmbH | Unclassified | IPv4 IPv6 | 204 |
| AS12557 | SimpleThings GmbH | Unclassified | IPv4 IPv6 | 185 |
Adjacency
Adjacent networks
Every AS seen directly next to AS3209 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS1273 | IDDQD-AS | Business | IPv4 IPv6 | 20,847 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 3,949 |
| AS15933 | ith Kommunikationstechnik GmbH | Unclassified | IPv4 | 1,081 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 IPv6 | 1,014 |
| AS3320 | Deutsche Telekom AG | Mobile | IPv4 IPv6 | 661 |
| AS201299 | BWI GmbH | Unclassified | IPv4 IPv6 | 538 |
| AS21207 | E.ON Verwaltungs GmbH | Unclassified | IPv4 IPv6 | 512 |
| AS204028 | Dolphin IT-Systeme e.K. | Unclassified | IPv4 IPv6 | 495 |
| AS16024 | GELSEN-NET Kommunikationsgesellschaft mbH | Unclassified | IPv4 IPv6 | 448 |
| AS213251 | Marcel Andrew Zaiser trading as Metaliance ISP Systems e.k | Unclassified | IPv4 IPv6 | 411 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-07 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 72.97M 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.