Observed topology
AS205112 PHILUNET PHILUNET GmbH
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS205112: 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 | 438 |
| AS13030 | Init7 (Switzerland) Ltd. | Hosting | IPv4 | 143 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 130 |
| AS17639 | Converge ICT Solutions Inc. | Unclassified | IPv4 IPv6 | 20 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 20 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 IPv6 | 20 |
| AS42708 | Glesys Sweden AB | Unclassified | IPv4 IPv6 | 20 |
| AS48185 | team.blue NV | Unclassified | IPv4 IPv6 | 20 |
| AS204092 | Association GRIFON | Unclassified | IPv4 IPv6 | 20 |
| AS401753 | BIXCE Inc | Unclassified | IPv4 IPv6 | 20 |
Transit
Downstream networks
Networks for which AS205112 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS15987 | Portunity GmbH | Hosting | IPv4 IPv6 | 944 |
| AS57154 | Stadtwerke Konstanz GmbH | Residential | IPv4 IPv6 | 232 |
| AS60123 | Stadtverwaltung Remscheid | Unclassified | IPv4 | 120 |
| AS210780 | Stadt Wuppertal | Unclassified | IPv4 IPv6 | 94 |
| AS48821 | Mauve Mailorder Software Verwaltung GmbH | Hosting | IPv4 IPv6 | 92 |
| AS202739 | Daniel Czerwonk | Unclassified | IPv6 | 19 |
| AS206356 | Freifunk Essen e.V. | Unclassified | IPv4 IPv6 | 19 |
| AS207160 | Factory Campus Verwaltungs-GmbH | Unclassified | IPv4 IPv6 | 7 |
| AS212567 | Freie Netze Muenchen e.V. | Unclassified | IPv4 | 2 |
Adjacency
Adjacent networks
Every AS seen directly next to AS205112 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS50629 | LWLcom GmbH | Unclassified | IPv4 IPv6 | 1,193 |
| AS15987 | Portunity GmbH | Hosting | IPv4 IPv6 | 944 |
| AS13030 | Init7 (Switzerland) Ltd. | Hosting | IPv4 | 516 |
| AS57154 | Stadtwerke Konstanz GmbH | Residential | IPv4 IPv6 | 349 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 292 |
| AS60123 | Stadtverwaltung Remscheid | Unclassified | IPv4 | 120 |
| AS210780 | Stadt Wuppertal | Unclassified | IPv4 IPv6 | 94 |
| AS48821 | Mauve Mailorder Software Verwaltung GmbH | Hosting | IPv4 IPv6 | 92 |
| AS401753 | BIXCE Inc | Unclassified | IPv4 IPv6 | 63 |
| AS208972 | GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI | Unclassified | IPv4 IPv6 | 61 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-08 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.00M 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.