asn.dev

Observed topology

AS8365 MANDA

Education RIPE

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

Transit

Upstream networks

All 33

Networks observed carrying traffic for AS8365: 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
AS1299Arelion Sweden ABTransitIPv4 IPv695
AS2914NTT America, Inc.TransitIPv4 IPv669
AS6939Hurricane Electric LLCTransitIPv4 IPv669
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv623
AS1836green.ch AGResidentialIPv4 IPv69
AS3320Deutsche Telekom AGMobileIPv4 IPv69
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv69
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv69
AS24482SG.GSHostingIPv4 IPv69
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv69

All 33 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS212795Fraunhofer-Gesellschaft zur Foerderung der angewandten Forschung e.V.UnclassifiedIPv4 IPv6678
AS12643Fraunhofer-Gesellschaft zur Foerderung der angewandten Forschung e.V.UnclassifiedIPv4 IPv6316
AS35548smartTERRA GmbHHostingIPv4 IPv6231
AS28714Fraunhofer-Gesellschaft zur Foerderung der angewandten Forschung e.V.UnclassifiedIPv4 IPv6151
AS50595Hochschule RheinMainUnclassifiedIPv4118
AS209499GSI Helmholtzzentrum fur Schwerionenforschung GmbHUnclassifiedIPv443
AS2857Johannes Gutenberg-Universitaet MainzEducationIPv4 IPv642
AS6766Chaos Computer Club Darmstadt e.V.UnclassifiedIPv633
AS201339Wissenschaftsstadt DarmstadtUnclassifiedIPv426

Adjacency

Adjacent networks

All 46

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

ASNetworkTypeFamiliesPaths seen
AS212795Fraunhofer-Gesellschaft zur Foerderung der angewandten Forschung e.V.UnclassifiedIPv4 IPv6678
AS1299Arelion Sweden ABTransitIPv4 IPv6401
AS35548smartTERRA GmbHHostingIPv4 IPv6368
AS12643Fraunhofer-Gesellschaft zur Foerderung der angewandten Forschung e.V.UnclassifiedIPv4 IPv6316
AS2914NTT America, Inc.TransitIPv4 IPv6215
AS6939Hurricane Electric LLCTransitIPv4 IPv6182
AS28714Fraunhofer-Gesellschaft zur Foerderung der angewandten Forschung e.V.UnclassifiedIPv4 IPv6151
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv6121
AS50595Hochschule RheinMainUnclassifiedIPv4118
AS48185team.blue NVUnclassifiedIPv4 IPv678

All 46 adjacent →

Provenance

Where this comes from

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