Observed topology

AS12486 TELEYEMEN Sanaa

Unclassified RIPE

Upstreams 5 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 5

Adjacent (IPv6) 2

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS12486: 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
AS35280	F5 Networks SARL	Hosting	IPv4	1,276
AS58453	China Mobile International Limited	Unclassified	IPv4	381
AS197206	BusinessCom CZ spol. s r.o.	Unclassified	IPv4	177
AS6774	Belgacom International Carrier Services SA	Unclassified	IPv4 IPv6	97
AS15412	Flag Telecom UK Limited	Unclassified	IPv4	45

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS25152	Reseaux IP Europeens Network Coordination Centre (RIPE NCC)	Unclassified	IPv6	1

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS35280	F5 Networks SARL	Hosting	IPv4	1,276
AS58453	China Mobile International Limited	Unclassified	IPv4	381
AS197206	BusinessCom CZ spol. s r.o.	Unclassified	IPv4	177
AS6774	Belgacom International Carrier Services SA	Unclassified	IPv4 IPv6	98
AS15412	Flag Telecom UK Limited	Unclassified	IPv4	45
AS25152	Reseaux IP Europeens Network Coordination Centre (RIPE NCC)	Unclassified	IPv6	1

Provenance

Where this comes from

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