DNS Test from Israel
2 nodes in Netanja, Petach Tikwa · IIX Tel Aviv
Israel — 2 Nodes
DNS Testing from Israel
A DNS check from our Israeli nodes queries your domain's authoritative nameservers directly from AS206446 IP space and records the response. This confirms that your authoritative DNS is resolving correctly from the Israeli network environment. It is particularly relevant if you use GeoDNS to return different records for Middle Eastern or Israeli users — for example, pointing them to a regional CDN edge or an origin server in Europe rather than the US.
Our DNS check bypasses recursive resolver caches entirely and queries the authoritative tier directly. This shows what your nameservers are currently returning, not what a cached resolver may still be serving. For recent DNS changes — such as a TTL-expired record update or a new subdomain — this is the correct method to verify that the change is live at the authoritative level from an Israeli network vantage point.
AS206446 (CLOUD LEASE) is RIPE-registered Israeli address space and should be correctly classified as IL / Middle East by all major GeoDNS providers. If a DNS check from our Israeli nodes returns an unexpected IP — for example, a US-region record instead of an EU or Middle East record — your GeoDNS policy is either not covering AS206446 correctly or is applying a broader classification than expected. Cross-referencing against our Turkish and German nodes helps narrow down whether the misclassification is Israel-specific or affects the broader RIPE region.
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.