Why Internet Traffic from Israel to South Africa Detours via London
At first glance, data transmission between Jerusalem, Israel, and Amanzimtoti, South Africa, might seem straightforward and efficient: the straight-line distance between these points is 6,899 km, which suggests a minimum signal round-trip time (RTT) of 69 milliseconds, assuming the speed of light in optical fiber. However, GeoCables measurements reveal that the traffic route deviates significantly from the optimal path, reaching 243 ms RTT, nearly four times the physical limit. Instead of taking a direct route, packets are first sent through London, United Kingdom, before heading south to Durban, South Africa, adding 3,557 km to the straight-line distance.
Why does the route go through London?
The key network providers involved in the routing, AS1680 (Cellcom Fixed Line Communication L.P) in Israel and AS37468 (Angola Cables), play a significant role in this unusual path. Cellcom, as a local operator in Israel, forwards data to the nearest exchange points, but the lack of direct interconnections with South African operators forces traffic to seek transit routes through major international hubs. London, being one of the largest traffic exchange points in Europe, offers convenient peering opportunities for the Angola Cables network, which then delivers the data to South Africa. This is a typical example of transit economics: networks choose routes not based on geographic logic but on the availability and cost of inter-network connections.
Practical implications for users
243 ms RTT is a significant delay that can noticeably affect user experience. For instance, in video calls, such a delay results in noticeable pauses and reduced communication quality. In online gaming, where quick response times are crucial, delays above 100 ms are already considered critical, and 243 ms makes gameplay virtually impossible. For traders working with stock exchanges or other time-sensitive services, such delays can mean missed opportunities. Cloud services, such as document editing or application usage, also suffer: response times increase significantly, reducing productivity.
Infrastructure context: why does regional traffic "go astray"?
At first glance, Israel and South Africa could exchange traffic via submarine cables in the Red Sea and Indian Ocean. However, the reality is more complex. The lack of direct interconnections between operators in these regions forces data to take detours. London serves as a "crossroads" of the global internet thanks to its advanced infrastructure and numerous peering agreements. Cable systems such as WACS (West Africa Cable System) and SAT3/WASC, which connect South Africa to international hubs, also play a role in route selection, but their configuration does not provide a direct connection to Israel.
Real-world events near the route
GeoCables monitoring recorded several natural events that could have impacted internet infrastructure in the region. For example, on April 22, 2026, Turkey experienced a green-level flood threat approximately 477 km from the route. In June, floods were also reported in the Netherlands (June 30, 356 km from the route) and Belgium (June 23, 367 km from the route). However, GeoCables data analysis shows that the detour is solely due to routing decisions, not these events. Nevertheless, they highlight the complexity and vulnerability of global infrastructure, especially in regions with high natural disaster risks.
Conclusion
This example clearly demonstrates how transit economics and inter-network agreements shape internet routes, often far from the optimal geographic path. GeoCables continues to analyze such routes, helping operators and users understand why their data may travel halfway around the world, even when the physical proximity of points seems obvious. In an era of increasing demands for internet speed and stability, understanding these processes is becoming critically important for improving the global network.
