MTR Test from Israel
2 nodes in Netanja, Petach Tikwa · IIX Tel Aviv
Israel — 2 Nodes
MTR Traceroute from Israel
MTR from our Israeli nodes runs continuous per-hop latency and loss measurements from AS206446 toward your target. Traffic from CLOUD LEASE in Petah Tikva or Netanya exits through Israeli upstream transit providers before reaching IIX or an international gateway. The international path from Israel to Europe runs over undersea cable — FLAG or SEA-ME-WE — typically via a landing station in Tel Aviv or Haifa before onward transit through Mediterranean PoPs.
A typical MTR from Israel to a Frankfurt target shows: 1–2 hops inside AS206446 adding 1–3 ms, then a hop to the Israeli international gateway around 5–8 ms, then a cable segment through Cyprus or Egypt adding 20–30 ms, then Central European transit arriving at Frankfurt around 55–62 ms total. A large latency jump at the cable segment hop is expected given the geographic distance — this is not congestion but physical propagation delay over several thousand kilometers of undersea cable.
MTR from both Israeli nodes to the same target is useful for path comparison. Both nodes are in the same metro and AS, so diverging MTR paths between them would indicate that AS206446 is load-balancing over multiple upstream transit providers. If one node shows a significantly faster path, it suggests one transit choice is better-peered with the target — information useful for selecting which node to use as a primary reference for Israeli reachability testing.
Israel Network Infrastructure
Israel's internet infrastructure is concentrated in the Tel Aviv metropolitan area, where the country's main IX facilities, data centers, and carrier hotels are located. IIX (Israel Internet Exchange) operates the primary peering fabric, used by domestic ISPs, content providers, and CDN PoPs. ISUOG serves as a secondary IX. Both are located within the Tel Aviv metro corridor, where the bulk of Israeli carrier and hosting infrastructure is physically housed. Petah Tikva and Netanya — the two cities hosting our probe nodes — are approximately 15 km apart and both fall within this metro concentration.
International connectivity from Israel exits almost entirely via undersea cables. The FLAG and SEA-ME-WE cable systems land at Haifa and Tel Aviv, providing primary capacity toward Europe through the Mediterranean. A secondary path runs overland via Egypt through the Sinai. The Tel Aviv-to-Frankfurt path runs approximately 50–60 ms on well-routed cable capacity. Tel Aviv to London sits around 60–68 ms. Tel Aviv to New York is approximately 125–135 ms over trans-Atlantic cable. These RTTs are competitive with Southern European locations, placing Israel within useful range of European CDN infrastructure.
Major Israeli carriers include Bezeq International (AS8551), which operates the main domestic fixed-line backbone, Partner Communications (AS12400), HOT Telecom (AS5486), and Cellcom. The commercial ISP and hosting market is served by additional providers including CLOUD LEASE (AS206446), which hosts both of our probe nodes. AS206446 is a cloud hosting and colocation provider with presence in Petah Tikva and Netanya, both served via Israeli domestic backbone with onward transit toward IIX and international gateways.
Israel has one of the highest average fixed-line broadband speeds in the region, driven by widespread fiber deployment and competitive ISP pricing. The Israeli market is unusually well-peered for its geographic location — proximity to Europe via undersea cable and active participation at IIX means many European CDN edges serve Israel with latency comparable to what Southern European users see. Akamai, Cloudflare, and AWS all maintain edge PoPs in the Tel Aviv region.
We operate two probe nodes in Israel — one in Petah Tikva and one in Netanya — both via CLOUD LEASE (AS206446). Having two nodes in the same AS and metro area means results are typically consistent, but running both simultaneously confirms that neither node has a local routing anomaly. For targets with Anycast or GeoDNS, both nodes should return identical or near-identical results given their geographic proximity and shared upstream.