asn.dev

Observed topology

AS41108 FIRSTROOT-AS

Hosting RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS41108: 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
AS30962comtrance service GmbHHostingIPv4 IPv6925

Transit

Downstream networks

All 19

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

ASNetworkTypeFamiliesPaths seen
AS209859Florian Martin EsserUnclassifiedIPv4 IPv6114
AS207378DIRK MUTTERLOSEUnclassifiedIPv459
AS209185Tim NiemeyerUnclassifiedIPv4 IPv650
AS199462NETISP LTDUnclassifiedIPv633
AS200201Tomasz KepczynskiUnclassifiedIPv633
AS207792Darius JockelUnclassifiedIPv633
AS208449Micky Del Favero trading as "BeeCloudy.net"UnclassifiedIPv633
AS210887Yannic SackUnclassifiedIPv633
AS212704Daniel GroeberUnclassifiedIPv633
AS215080Jana Amelie SteuernagelUnclassifiedIPv633

Adjacency

Adjacent networks

All 20

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

ASNetworkTypeFamiliesPaths seen
AS30962comtrance service GmbHHostingIPv4 IPv61,478
AS209859Florian Martin EsserUnclassifiedIPv4 IPv6114
AS207378DIRK MUTTERLOSEUnclassifiedIPv459
AS209185Tim NiemeyerUnclassifiedIPv4 IPv650
AS199462NETISP LTDUnclassifiedIPv633
AS200201Tomasz KepczynskiUnclassifiedIPv633
AS207792Darius JockelUnclassifiedIPv633
AS208449Micky Del Favero trading as "BeeCloudy.net"UnclassifiedIPv633
AS210887Yannic SackUnclassifiedIPv633
AS212704Daniel GroeberUnclassifiedIPv633

Provenance

Where this comes from

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