Observed topology
AS35223 HOI-AS Hoi Internet AG
Residential RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS35223: 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 |
|---|---|---|---|---|
| AS59890 | Kabel-TV Lampert GmbH & Co KG | Residential | IPv4 IPv6 | 73 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 IPv6 | 44 |
| AS12387 | TON Total optical Networks AG | Unclassified | IPv4 IPv6 | 22 |
| AS4455 | IX Reach Ltd | Unclassified | IPv4 IPv6 | 21 |
| AS49432 | Dominic Schallert trading as schallert.com e.U. | Unclassified | IPv4 IPv6 | 3 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 2 |
| AS34019 | Hivane Association | Unclassified | IPv4 IPv6 | 2 |
| AS1836 | green.ch AG | Residential | IPv4 | 1 |
| AS34927 | iFog GmbH | Hosting | IPv6 | 1 |
Transit
Downstream networks
Networks for which AS35223 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS21113 | Hilti AG | Unclassified | IPv4 | 39 |
Adjacency
Adjacent networks
Every AS seen directly next to AS35223 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS59890 | Kabel-TV Lampert GmbH & Co KG | Residential | IPv4 IPv6 | 103 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 IPv6 | 44 |
| AS21113 | Hilti AG | Unclassified | IPv4 | 39 |
| AS4455 | IX Reach Ltd | Unclassified | IPv4 IPv6 | 29 |
| AS12387 | TON Total optical Networks AG | Unclassified | IPv4 IPv6 | 22 |
| AS49432 | Dominic Schallert trading as schallert.com e.U. | Unclassified | IPv4 IPv6 | 3 |
| AS1836 | green.ch AG | Residential | IPv4 | 2 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 2 |
| AS34019 | Hivane Association | Unclassified | IPv4 IPv6 | 2 |
| AS34927 | iFog GmbH | Hosting | IPv6 | 1 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-13 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.40M 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.