Check-Host.cc

UDP Test from Israel

2 nodes in Netanja, Petach Tikwa · IIX Tel Aviv

Israel — 2 Nodes

Cities
Netanja, Petach Tikwa
ISPs / ASNs
CLOUD LEASE Ltd AS206446
Datacenters
CLOUD LEASE Ltd
Internet Exchanges
IIX Tel Aviv — Israel Internet Exchange, primary national peering point in Tel Aviv
ISUOG — Secondary Israeli IX, operates alongside IIX in the Tel Aviv metro

UDP Testing from Israel

UDP checks from our Israeli nodes send a packet to the specified port and wait for a response. This is relevant for testing DNS resolvers, WireGuard or OpenVPN endpoints, SIP infrastructure, and game servers that need to be reachable from Israeli users. Israeli ISP infrastructure does not block UDP outbound on commercial connections, so a no-response result from our nodes indicates the block is on the target side or in transit rather than inside Israel.

For VPN or tunneling services with Israeli users, a UDP check from AS206446 confirms whether the endpoint is reachable from one of Israel's main hosting ASNs. WireGuard endpoints will not reply to a UDP probe unless the peer is configured — a no-response result is normal for correctly deployed WireGuard. OpenVPN UDP and game server protocols that do send an unauthenticated reply to a probe will confirm reachability by returning any packet.

Running UDP checks from both Israeli nodes simultaneously is a quick consistency test. Since both nodes share the same upstream (AS206446) and international transit path, differing results between the two on the same target would indicate a per-node routing anomaly. Consistent no-response from both confirms the issue is not node-specific but is a general problem with the path from Israeli networks to the target.

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.