Check-Host.cc

TCP 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

TCP Port Testing from Israel

TCP checks from our Petah Tikva and Netanya nodes (AS206446) attempt a SYN-ACK handshake to your host on the specified port and measure connection time. This verifies port-level reachability from Israeli carrier infrastructure — useful for confirming that application ports are open for Israeli users, and for diagnosing reports of connectivity problems from the region. TCP checks reflect actual firewall rules and routing behaviour, unlike ICMP-based ping.

Expected TCP handshake times from Israel: to Frankfurt-region targets ~52–60 ms, to Amsterdam ~58–66 ms, to London ~63–70 ms, to US East Coast ~128–138 ms. These reflect the underlying cable RTT with no queuing penalty. A TCP check that completes faster than these baselines suggests the target is Anycast-routed to a local or regional edge — for example, a Cloudflare-fronted service will complete the TCP handshake locally at a Tel Aviv PoP in under 5 ms.

A failed TCP check from Israel when the port is reachable from Europe is typically caused by: a firewall or security group blocking Middle Eastern or non-EU ASNs, geo-IP policy restricting Israeli IP space, or cloud provider regional restrictions. Comparing against our Turkish and UAE-region nodes helps determine whether the block is Israel-specific or applies to the broader Middle East IP range.

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.