QUOTE(bluemind @ Jun 16 2024, 03:50 AM)
Some user report that it is due to cable fault and repair in the other thread so it could be multiple causes. Anyway I checked digi seems slightly better though I don't use wifi so I can't check with the AWS server in the game itself. Now in am it seems there is new routing using kslrml02.my.bb.gin.ntt.net for instance, and ping is 200-300ms which is the best you can get. Nothing surprising or new in this scenario since it has been awhile with this issue, usually if you complain to AWS they will say it is your ISP has bad routing, and ISP will say is out of their control. In the end it is not an issue consumer can easily solve on their own besides changing ISP or using extra paid services to get better routing.
I am starting to doubt if TM misconfigured their BGP.
TM never advertise their prefix to TATA, IPv4 or IPv6.
TM only advertise their IPv6 prefix to NTT.
If you read the BGP output, all routes go to AS1299 first, including NTT (IPv4).
I didn't read the BGP output yesterday, just the Trace, hence I miss this!
That means anything that route to TATA is broken.
All IPv4 routing to NTT is also broken.
To reach AS1299 (Arelion aka Twelve99) both NTT and TATA has to egress at HK or JP. For traffic to US this is not really a problem because they will reach JP and HK before MY.
But if you go to AWS SG, it need to go to HK before coming back.
Even if you dump TATA's BGP output in ECBJ1 Cyberjaya or KT1 Kuala Lumpur, next hop is still AS1299.
NTT Looking Glass
https://www.gin.ntt.net/looking-glass-landing/This post has been edited by kwss: Jun 16 2024, 11:45 AM