That is why I am puzzled.
If we attribute the issue to high ping due to bad routing, then all of us should be affected. But apparently only some SingTel users are affected.
It could be because they might be so unfortunate to go through even worse routing (say through China Telecom) due to different IP address segment or different Taobao server locations.
Simple ping and traceroute may be able to check whether the hypothesis is correct.
Singtel are making 2 separate BGP announcements under 121.7.x, instead of announcing the whole range as a /16 they have split it into a pair of /17 announcements:
https://bgp.he.net/AS9506#_prefixes
Wether both of these prefixes are announced to their various peers equally, or accepted by those peers i couldn't say.
There could also be other problems, such as rogue announcements or localised misconfigurations. The ipv4 address space is small and very messy, it's not uncommon for companies to have used previously unallocated address space internally. For instance there's a lot of companies that use 1.1.1.x as the captive portal page on their wifi etc.
This only manifests itself when someone is actually allocated the address space and tries to communicate with you, for instance someone using a wifi setup like this would be unable to access the cloudflare dns service now using the 1.1.1.1 address.