Observed topology
AS12306 PLUSLINE Plus.line AG
Hosting RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS12306: 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 |
|---|---|---|---|---|
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 IPv6 | 475 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 168 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 124 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 117 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 68 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 52 |
| AS3320 | Deutsche Telekom AG | Mobile | IPv4 IPv6 | 46 |
| AS213241 | TECHIT.BE SRL | Residential | IPv4 IPv6 | 27 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 23 |
| AS34019 | Hivane Association | Unclassified | IPv4 IPv6 | 23 |
Transit
Downstream networks
Networks for which AS12306 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS29515 | Hessische Zentrale fuer Datenverarbeitung | Unclassified | IPv4 IPv6 | 438 |
| AS12291 | DHL AG | Unclassified | IPv4 | 300 |
| AS57358 | IMT-Systems GmbH | Unclassified | IPv4 IPv6 | 219 |
| AS62434 | DFS Deutsche Flugsicherung GmbH | Unclassified | IPv4 IPv6 | 210 |
| AS47487 | Transgourmet Deutschland GmbH & Co. OHG | Unclassified | IPv4 IPv6 | 189 |
| AS209943 | InSyst GmbH | Unclassified | IPv4 IPv6 | 155 |
| AS16188 | punkt.de GmbH | Unclassified | IPv4 IPv6 | 153 |
| AS16205 | DSI GmbH Daten Service Informationssysteme | Unclassified | IPv4 | 130 |
| AS44152 | adesso as a service GmbH | Unclassified | IPv4 | 117 |
| AS204723 | HaCon Ingenieurgesellschaft mbH | Unclassified | IPv4 IPv6 | 93 |
Adjacency
Adjacent networks
Every AS seen directly next to AS12306 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 IPv6 | 1,368 |
| AS29515 | Hessische Zentrale fuer Datenverarbeitung | Unclassified | IPv4 IPv6 | 438 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 394 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 368 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 312 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 303 |
| AS12291 | DHL AG | Unclassified | IPv4 | 300 |
| AS57358 | IMT-Systems GmbH | Unclassified | IPv4 IPv6 | 219 |
| AS62434 | DFS Deutsche Flugsicherung GmbH | Unclassified | IPv4 IPv6 | 210 |
| AS47487 | Transgourmet Deutschland GmbH & Co. OHG | Unclassified | IPv4 IPv6 | 189 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-11 10:00 UTC by route-views2,rrc00, as seen from 74 BGP vantage points across 73.24M 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.