asn.dev

Observed topology

AS39878 RAUTER-AS Peter Rauter GmbH

Residential RIPE

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

Transit

Upstream networks

All 20

Networks observed carrying traffic for AS39878: 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
AS33891Core-Backbone GmbHHostingIPv4 IPv6165
AS1299Arelion Sweden ABTransitIPv4 IPv6103
AS6939Hurricane Electric LLCTransitIPv449
AS3257GTT Communications Inc.TransitIPv435
AS34549meerfarbig GmbH & Co. KGHostingIPv421
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv68
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv68
AS6797GlobalConnect ABUnclassifiedIPv47
AS8551Bezeq International Ltd.UnclassifiedIPv47
AS12779IT.Gate S.p.A.UnclassifiedIPv47

All 20 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS50920Kabel Braunau GmbHUnclassifiedIPv4 IPv6565

Adjacency

Adjacent networks

All 21

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

ASNetworkTypeFamiliesPaths seen
AS50920Kabel Braunau GmbHUnclassifiedIPv4 IPv6565
AS33891Core-Backbone GmbHHostingIPv4 IPv6385
AS1299Arelion Sweden ABTransitIPv4 IPv6206
AS6939Hurricane Electric LLCTransitIPv4115
AS3257GTT Communications Inc.TransitIPv479
AS34549meerfarbig GmbH & Co. KGHostingIPv454
AS6797GlobalConnect ABUnclassifiedIPv418
AS8551Bezeq International Ltd.UnclassifiedIPv418
AS12779IT.Gate S.p.A.UnclassifiedIPv418
AS20485Joint Stock Company TransTeleComUnclassifiedIPv418

All 21 adjacent →

Provenance

Where this comes from

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