Observed topology

AS212250 HORIZON-SCOPE Horizon Scope Mobile Telecom WLL

Unclassified RIPE Network Services

Upstreams 2 carry this network

Downstreams 2 this network carries

Adjacent (IPv4) 26

Adjacent (IPv6) 4

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS212250: 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
AS6939	Hurricane Electric LLC	Transit	IPv6	35
AS3356	Level 3 Parent, LLC	Transit	IPv6	33

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS205906	Informatics and Telecommunications Public Company (ITPC)	Unclassified	IPv4	116
AS203217	Horizon Scope Mobile Telecom WLL	Unclassified	IPv4	52

Adjacency

Adjacent networks

All 26

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

AS	Network	Type	Families	Paths seen
AS208293	AlSalam State Company	Unclassified	IPv4 IPv6	13,977
AS3356	Level 3 Parent, LLC	Transit	IPv4 IPv6	4,739
AS174	Cogent Communications, LLC	Transit	IPv4 IPv6	3,756
AS57344	Telehouse AD	Residential	IPv4	3,519
AS6762	TELECOM ITALIA SPARKLE S.p.A.	Transit	IPv4	1,801
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	873
AS211181	Civilisation Information Technology, communication and internet services Co., LTD	Unclassified	IPv4	784
AS205906	Informatics and Telecommunications Public Company (ITPC)	Unclassified	IPv4	116
AS203217	Horizon Scope Mobile Telecom WLL	Unclassified	IPv4	52
AS35280	F5 Networks SARL	Hosting	IPv4	25

All 26 adjacent →

Provenance

Where this comes from

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