SDR Routing Inefficiency for IDC (Moldova/Transnistria)

Hello,
I am reporting a specific networking inefficiency within the Steam Datagram Relay (SDR) system affecting players in Tiraspol, Moldova / Transnistria using the IDC (Interdnestrcom) ISP.

The core of the issue is that in standard Apex Legends matches, my latency to Frankfurt servers is a stable 50ms. However, in Ranked matches, the SDR coordinator consistently forces a route through suboptimal relays, resulting in a persistent latency of 80-86ms.

My local infrastructure is fully optimized with a fiber-optic connection. Direct ICMP tests show a latency of only 4ms to 1.1.1.1 and approximately 10-12ms to the edge of my ISP's main backbone. This confirms that the connection from my home to the European internet exchange points is excellent and the bottleneck is not on my side or my ISP’s local network.

Despite this low base latency, Resource Monitor analysis reveals that in Ranked mode, the SDR system selects relay nodes that add a 30ms+ overhead. These detours through Valve nodes in the 155.133.x.x or 146.66.x.x ranges do not align with the most efficient physical path available from my region. Furthermore, I have observed that as the server load decreases during a match, the latency often drops back to 50ms, which suggests that the initial route assignment for my IP range is being handled inefficiently by the SDR coordinator.

I have already ensured that "Steam Networking" is set to "Always" and have eliminated all local hardware bottlenecks. Could you please review the SDR Routing Tables for the IDC (Moldova/Transnistria) network? It appears the coordinator is not correctly identifying the shortest path to Frankfurt for this specific network, leading to a degraded experience in competitive play.