Observed topology

AS214215 FARICE-RISP-AS

Unclassified RIPE

Upstreams 1 carry this network

Downstreams 6 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 0

Upstream graph Who carries AS214215, and who carries them, drawn as a map up to the transit-free core. 0 exchanges Where AS214215 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS214215: 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.

AS	Network	Type	Families	Paths seen
AS1299	Arelion Sweden AB	Transit	IPv4	59

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS12969	Ljosleidarinn ehf	Residential	IPv4	59
AS30818	Advania Island ehf	Hosting	IPv4	59
AS43892	Sensa ehf	Unclassified	IPv4	59
AS44735	Nova hf	Unclassified	IPv4	59
AS206010	Umbra Service Center Management	Unclassified	IPv4	59
AS216017	Opin Kerfi hf	Unclassified	IPv4	59

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS1299	Arelion Sweden AB	Transit	IPv4	413
AS12969	Ljosleidarinn ehf	Residential	IPv4	59
AS30818	Advania Island ehf	Hosting	IPv4	59
AS43892	Sensa ehf	Unclassified	IPv4	59
AS44735	Nova hf	Unclassified	IPv4	59
AS206010	Umbra Service Center Management	Unclassified	IPv4	59
AS216017	Opin Kerfi hf	Unclassified	IPv4	59

Provenance

Where this comes from

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