asn.dev

Observed topology

AS50670 VTELJO VTEL HOLDINGS LIMITED/JORDAN CO.

Unclassified RIPE NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS50670: 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
AS12975Palestine Telecommunications Company (PALTEL)UnclassifiedIPv42,859
AS8697Jordan Telecommunications PSCUnclassifiedIPv4 IPv61,381
AS48832Jordanian mobile phone services LtdUnclassifiedIPv41,005
AS9038Al Bahrainia al Urdunia Liltaknia Wa Alitisalat Plc. CoMobileIPv427

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS206553Al-Hikma Pharmaceuticals LLCUnclassifiedIPv4180
AS28730Broadband Communications LPSUnclassifiedIPv4159
AS211826Stability for Integrated Server Hosting LtdUnclassifiedIPv4120
AS39918Azadea Group Holding SALUnclassifiedIPv48

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS12975Palestine Telecommunications Company (PALTEL)UnclassifiedIPv43,075
AS8697Jordan Telecommunications PSCUnclassifiedIPv4 IPv61,660
AS48832Jordanian mobile phone services LtdUnclassifiedIPv41,005
AS206553Al-Hikma Pharmaceuticals LLCUnclassifiedIPv4180
AS28730Broadband Communications LPSUnclassifiedIPv4159
AS211826Stability for Integrated Server Hosting LtdUnclassifiedIPv4120
AS9038Al Bahrainia al Urdunia Liltaknia Wa Alitisalat Plc. CoMobileIPv427
AS39918Azadea Group Holding SALUnclassifiedIPv48

Provenance

Where this comes from

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