..And I'm typing this from Mazeda Internet. Had some issues with cabling but at the end of the day all is well. They have benefited from the recent Google peering contracts (or they may have gotten into it themselves). Qubee is so far behind.
Note: 22.214.171.124 was my first DNS resolution for the PQDN google.com, which isn't the case for consecutive pings (cache is bypassed).
~# traceroute -T 126.96.36.199
traceroute to 188.8.131.52 (184.108.40.206), 30 hops max, 60 byte packets
1 192.168.1.1 (192.168.1.1) 34.838 ms 34.968 ms 35.142 ms
2 10.108.36.1 (10.108.36.1) 42.250 ms 42.405 ms 42.709 ms
3 172.16.172.13 (172.16.172.13) 42.803 ms 43.052 ms 43.081 ms
4 220.127.116.11 (18.104.22.168) 43.238 ms 43.378 ms 43.710 ms
5 cache.google.com (22.214.171.124) 43.476 ms 43.905 ms 44.345 ms
And looks like gaming on SEA servers should be a smooth experience (which most of you on wired Internet already enjoy):
My remote work latency has also improved, though still not lag-free (most of it propagation delay due to geographical distance, nothing much to do about it). I may start using mosh  in place of ssh. Anyway, I will see how far Mazeda takes me. Again, I want to thank you guys for your genuine, quick and reasoned feedback. I don't know where else I would've taken my concerns!
~$ ping -c 5 singtel.com.sg
PING singtel.com.sg (126.96.36.199) 56(84) bytes of data.
64 bytes from 188.8.131.52: icmp_seq=1 ttl=242 time=93.1 ms
64 bytes from 184.108.40.206: icmp_seq=2 ttl=242 time=94.2 ms
64 bytes from 220.127.116.11: icmp_seq=3 ttl=242 time=90.7 ms
64 bytes from 18.104.22.168: icmp_seq=4 ttl=242 time=91.4 ms
64 bytes from 22.214.171.124: icmp_seq=5 ttl=242 time=94.7 ms