On 5/21/24 21:55, Dovid Bender wrote:
Could it be related to the fiber cut in the red sea?
Asia-Pac <=> North America is typically faster via the Pacific, not the Indian Ocean. The Red Sea cuts would impact Asia-Pac <=> Europe traffic. SMW-5 had an outage on the 19th of April around the Straits of Malacca between Malaysia and Indonesia. The suspected cause is a shunt fault. A shunt fault occurs when the cable insulation is damaged and exposes the electrical wire in the cable, causing a short. This shifts the virtual ground of the electrical circuit toward the shunt fault location. In many cases, the PFE (Power Feeding Equipment) farthest from the shunt is able to re-balance and pump enough power down the cable from the CLS to maintain the required voltage. However, in some cases - such as the one with this particular SMW-5 fault - the short can become significant enough that there is a total loss of current to drive the segment, leading to an outage. At this time, repairs are delayed until around end of May. But given the location of the fault, I don't see how it would impact traffic toward North America from Singapore. Impact seems to mainly be between Bangladesh <=> Singapore. This is Telstra: 1 * * i-92.sgcn-core01.telstraglobal.net (202.84.219.174) 8 msec 2 i-93.istt04.telstraglobal.net (202.84.224.190) 4 msec i-92.sgcn-core01.telstraglobal.net (202.84.219.174) [MPLS: Label 24210 Exp 0] 2 msec 2 msec 3 ae10.cr4-sin1.ip4.gtt.net (67.199.139.109) 22 msec i-91.istt04.telstraglobal.net (202.84.224.197) 3 msec ae10.cr4-sin1.ip4.gtt.net (67.199.139.109) 3 msec 4 ae16.cr0-mtl1.ip4.gtt.net (89.149.186.134) 239 msec ae10.cr4-sin1.ip4.gtt.net (67.199.139.109) 4 msec ae16.cr0-mtl1.ip4.gtt.net (89.149.186.134) 241 msec 5 ae16.cr0-mtl1.ip4.gtt.net (89.149.186.134) 241 msec ip4.gtt.net (72.29.198.6) 325 msec ae16.cr0-mtl1.ip4.gtt.net (89.149.186.134) 240 msec 6 10ge.mtl-bvh-xe3-1.peer1.net (216.187.113.107) 316 msec ip4.gtt.net (72.29.198.6) 330 msec 312 msec 7 managed5.top-consulting.net (69.90.179.5) 329 msec This is Arelion: Tracing the route to 69.90.179.5 1 sjo-b23-link.ip.twelve99.net (62.115.141.126) 183 msec sng-b4-link.ip.twelve99.net (62.115.137.243) 1 msec 10 msec 2 sjo-b23-link.ip.twelve99.net (62.115.136.166) 164 msec 164 msec 163 msec 3 nyk-bb1-link.ip.twelve99.net (62.115.137.168) 250 msec * motl-b2-link.ip.twelve99.net (62.115.137.143) 256 msec 4 motl-b1-link.ip.twelve99.net (62.115.126.220) 244 msec 245 msec 242 msec 5 aptummanaged-ic-367443.ip.twelve99-cust.net (62.115.174.15) 257 msec 256 msec 263 msec 6 10ge.mtl-bvh-xe3-1.peer1.net (216.187.113.107) 274 msec 268 msec 264 msec 7 managed5.top-consulting.net (69.90.179.5) 258 msec 259 msec 261 msec This is GTT: traceroute to 69.90.179.5 (69.90.179.5), 12 hops max, 52 byte packets 1 ae4.lr4-sin1.ip4.gtt.net (89.149.131.98) 1.015 ms 4.696 ms 0.741 ms MPLS Label=185733 CoS=0 TTL=1 S=1 2 et-0-0-4.lr3-lax2.ip4.gtt.net (89.149.131.233) 162.343 ms 163.306 ms 210.101 ms MPLS Label=983708 CoS=0 TTL=1 S=1 3 ae0.lr4-lax2.ip4.gtt.net (89.149.184.30) 161.869 ms 163.878 ms 163.078 ms MPLS Label=417505 CoS=0 TTL=1 S=1 4 ae14.lr7-chi1.ip4.gtt.net (89.149.143.161) 217.467 ms 202.565 ms 203.520 ms MPLS Label=188676 CoS=0 TTL=1 S=1 5 ae18.lr5-chi1.ip4.gtt.net (89.149.136.81) 206.519 ms 202.270 ms 203.047 ms MPLS Label=913278 CoS=0 TTL=1 S=1 6 ae19.lr6-chi1.ip4.gtt.net (89.149.141.194) 202.559 ms 202.853 ms 202.225 ms MPLS Label=422136 CoS=0 TTL=1 S=1 7 ae7.lr3-tor1.ip4.gtt.net (89.149.143.242) 212.461 ms 212.858 ms 230.237 ms MPLS Label=692593 CoS=0 TTL=1 S=1 8 ae6.cr9-mtl1.ip4.gtt.net (89.149.187.242) 221.465 ms 230.552 ms 218.920 ms MPLS Label=284571 CoS=0 TTL=1 S=1 9 ae16.cr0-mtl1.ip4.gtt.net (89.149.186.134) 217.961 ms 219.497 ms 219.392 ms 10 ip4.gtt.net (72.29.198.6) 217.164 ms 218.776 ms 217.011 ms 11 10ge.mtl-bvh-xe3-1.peer1.net (216.187.113.107) 220.991 ms 218.415 ms 220.009 ms 12 managed5.top-consulting.net (69.90.179.5) 217.273 ms 217.417 ms 217.079 ms Looks like Telstra are handing off to GTT. The latency increase at hop 6 suggests asymmetric routing. Arelion and GTT are within your 250ms spec, although it looks like GTT has more efficient U.S. routing to get to MTL. I'm not aware of any major subsea cut in Asia-Pac bar the SMW-5 one, so my guess is Linode and Digital Ocean might need to look into their routing with their upstreams out of Singapore. Mark.