Observed topology

AS41714 SpotNet_Ltd SPOT-NET LTD

Unclassified RIPE Cable/DSL/ISP

Upstreams 7 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 8

Adjacent (IPv6) 1

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS41714: 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
AS1680	Cellcom Fixed Line Communication L.P	Mobile	IPv4	684
AS8551	Bezeq International Ltd.	Unclassified	IPv4	652
AS208905	Exelera Telecom Ltd	Unclassified	IPv4	578
AS12400	Partner Communications Ltd.	Unclassified	IPv4 IPv6	431
AS12849	Hot-Net internet services Ltd.	Residential	IPv4	129
AS5486	Partner Communications Ltd.	Unclassified	IPv4	80
AS5585	Israel Internet Association	Unclassified	IPv4	3

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS51651	Nefesh B'Nefesh Aliyah (R.A.)	Unclassified	IPv4	62

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS8551	Bezeq International Ltd.	Unclassified	IPv4	712
AS1680	Cellcom Fixed Line Communication L.P	Mobile	IPv4	686
AS208905	Exelera Telecom Ltd	Unclassified	IPv4	578
AS12400	Partner Communications Ltd.	Unclassified	IPv4 IPv6	431
AS12849	Hot-Net internet services Ltd.	Residential	IPv4	129
AS5486	Partner Communications Ltd.	Unclassified	IPv4	80
AS51651	Nefesh B'Nefesh Aliyah (R.A.)	Unclassified	IPv4	62
AS5585	Israel Internet Association	Unclassified	IPv4	3

Provenance

Where this comes from

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