asn.dev

Observed topology

AS35223 HOI-AS

Residential RIPE

Upstreams 9 carry this network
Downstreams 2 this network carries
Adjacent (IPv4) 10
Adjacent (IPv6) 8
Upstream graph Who carries AS35223, and who carries them, drawn as a map up to the transit-free core. 2 exchanges Where AS35223 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

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.

ASNetworkTypeFamiliesPaths seen
AS59890Kabel-TV Lampert GmbH & Co KGResidentialIPv4 IPv667
AS33891Core-Backbone GmbHHostingIPv4 IPv644
AS12387TON Total optical Networks AGUnclassifiedIPv4 IPv628
AS4455IX Reach LtdUnclassifiedIPv4 IPv620
AS49432Dominic Schallert trading as schallert.com e.U.UnclassifiedIPv4 IPv63
AS24482SG.GSHostingIPv4 IPv62
AS34019Hivane AssociationUnclassifiedIPv4 IPv62
AS1836green.ch AGResidentialIPv41
AS34927iFog GmbHHostingIPv61

Transit

Downstream networks

inferred

Networks for which AS35223 was observed as the last hop before the origin, meaning it appears to provide them transit.

ASNetworkTypeFamiliesPaths seen
AS21113Hilti AGUnclassifiedIPv437
AS49652Domar Treuhand- und Verwaltungs-AnstaltUnclassifiedIPv425

Adjacency

Adjacent networks

All 11

Every AS seen directly next to AS35223 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS59890Kabel-TV Lampert GmbH & Co KGResidentialIPv4 IPv6121
AS33891Core-Backbone GmbHHostingIPv4 IPv644
AS21113Hilti AGUnclassifiedIPv437
AS4455IX Reach LtdUnclassifiedIPv4 IPv628
AS12387TON Total optical Networks AGUnclassifiedIPv4 IPv628
AS49652Domar Treuhand- und Verwaltungs-AnstaltUnclassifiedIPv425
AS49432Dominic Schallert trading as schallert.com e.U.UnclassifiedIPv4 IPv63
AS24482SG.GSHostingIPv4 IPv62
AS34019Hivane AssociationUnclassifiedIPv4 IPv62
AS1836green.ch AGResidentialIPv41

All 11 adjacent →

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-16 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.23M 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.