asn.dev

Observed topology

AS8241 RELLINE-AS

Unclassified RIPE NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS8241: 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
AS35598INETCOM CARRIER LLCUnclassifiedIPv484
AS57174Nets and Services JCSUnclassifiedIPv444
AS20764CJSC RASCOMUnclassifiedIPv428
AS62255BiMajLink d.o.o.UnclassifiedIPv422
AS1299Arelion Sweden ABTransitIPv49
AS49673Truenetwork LLCUnclassifiedIPv43
AS9049JSC "ER-Telecom Holding"UnclassifiedIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS209759Moy Telecom LLCUnclassifiedIPv4515
AS202599United Telecommunications Corporation LTDUnclassifiedIPv4100
AS39156First Telecom LtdUnclassifiedIPv46
AS44595AO Publishing House Seven DaysUnclassifiedIPv44

Adjacency

Adjacent networks

All 15

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

ASNetworkTypeFamiliesPaths seen
AS209759Moy Telecom LLCUnclassifiedIPv4576
AS20764CJSC RASCOMUnclassifiedIPv4397
AS35598INETCOM CARRIER LLCUnclassifiedIPv4175
AS1299Arelion Sweden ABTransitIPv4152
AS202599United Telecommunications Corporation LTDUnclassifiedIPv4100
AS62255BiMajLink d.o.o.UnclassifiedIPv491
AS39156First Telecom LtdUnclassifiedIPv456
AS57174Nets and Services JCSUnclassifiedIPv448
AS25478iHome LLCUnclassifiedIPv440
AS49673Truenetwork LLCUnclassifiedIPv417

All 15 adjacent →

Provenance

Where this comes from

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