asn.dev

Observed topology

AS43848 GAMSJAEGER Unterauerstrasse 7

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

All 19

Networks observed carrying traffic for AS43848: 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
AS28889LinzNet Internet Service Provider GmbHUnclassifiedIPv4650
AS6939Hurricane Electric LLCTransitIPv4175
AS34549meerfarbig GmbH & Co. KGHostingIPv457
AS204577LinzNet Internet Service Provider GmbHUnclassifiedIPv440
AS33891Core-Backbone GmbHHostingIPv438
AS1836green.ch AGResidentialIPv419
AS3303Swisscom (Schweiz) AGResidentialIPv419
AS6797GlobalConnect ABUnclassifiedIPv419
AS8551Bezeq International Ltd.UnclassifiedIPv419
AS12779IT.Gate S.p.A.UnclassifiedIPv419

All 19 upstreams →

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 19

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

ASNetworkTypeFamiliesPaths seen
AS28889LinzNet Internet Service Provider GmbHUnclassifiedIPv4650
AS6939Hurricane Electric LLCTransitIPv4175
AS34549meerfarbig GmbH & Co. KGHostingIPv457
AS204577LinzNet Internet Service Provider GmbHUnclassifiedIPv440
AS33891Core-Backbone GmbHHostingIPv438
AS1836green.ch AGResidentialIPv419
AS3303Swisscom (Schweiz) AGResidentialIPv419
AS6797GlobalConnect ABUnclassifiedIPv419
AS8551Bezeq International Ltd.UnclassifiedIPv419
AS12779IT.Gate S.p.A.UnclassifiedIPv419

All 19 adjacent →

Provenance

Where this comes from

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