asn.dev

Observed topology

AS48646 STEFAN6 SDRmedia Verwaltungs GmbH

Unclassified RIPE NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS48646: 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
AS6939Hurricane Electric LLCTransitIPv633
AS24482SG.GSHostingIPv61
AS34549meerfarbig GmbH & Co. KGHostingIPv61
AS56662Marcin GondekUnclassifiedIPv61
AS401753BIXCE IncUnclassifiedIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS211972Marc Schulz-NarresUnclassifiedIPv640
AS203478Sarah MaedelUnclassifiedIPv626
AS31396Juliane HolztUnclassifiedIPv625
AS209859Florian Martin EsserUnclassifiedIPv44
AS209768white2net SrlResidentialIPv62
AS212120Tom HerbersUnclassifiedIPv62
AS210951Josef MieglUnclassifiedIPv61
AS211635Stefan NagelUnclassifiedIPv61

Adjacency

Adjacent networks

All 16

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv6116
AS211972Marc Schulz-NarresUnclassifiedIPv640
AS203478Sarah MaedelUnclassifiedIPv626
AS31396Juliane HolztUnclassifiedIPv625
AS29632Netassist International EOODUnclassifiedIPv67
AS34549meerfarbig GmbH & Co. KGHostingIPv65
AS209859Florian Martin EsserUnclassifiedIPv44
AS24482SG.GSHostingIPv62
AS56662Marcin GondekUnclassifiedIPv62
AS57821Nonattached Network e.V.UnclassifiedIPv42

All 16 adjacent →

Provenance

Where this comes from

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