asn.dev

Observed topology

AS31396 JULE Juliane Holzt

Unclassified RIPE Non-Profit

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

Transit

Upstream networks

All 11

Networks observed carrying traffic for AS31396: 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
AS34872Sarah Rossius trading as Servperso SystemsHostingIPv4 IPv652
AS48646SDRmedia Verwaltungs GmbHUnclassifiedIPv625
AS6939Hurricane Electric LLCTransitIPv48
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv63
AS24482SG.GSHostingIPv4 IPv62
AS401753BIXCE IncUnclassifiedIPv4 IPv62
AS56662Marcin GondekUnclassifiedIPv61
AS57821Nonattached Network e.V.UnclassifiedIPv41
AS199854Jens ThiesUnclassifiedIPv61
AS202365Omer GOLGELIUnclassifiedIPv41

All 11 upstreams →

Transit

Downstream networks

inferred

Networks for which AS31396 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 11

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

ASNetworkTypeFamiliesPaths seen
AS34872Sarah Rossius trading as Servperso SystemsHostingIPv4 IPv652
AS48646SDRmedia Verwaltungs GmbHUnclassifiedIPv625
AS6939Hurricane Electric LLCTransitIPv48
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv63
AS24482SG.GSHostingIPv4 IPv62
AS401753BIXCE IncUnclassifiedIPv4 IPv62
AS56662Marcin GondekUnclassifiedIPv61
AS57821Nonattached Network e.V.UnclassifiedIPv41
AS199854Jens ThiesUnclassifiedIPv61
AS202365Omer GOLGELIUnclassifiedIPv41

All 11 adjacent →

Provenance

Where this comes from

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