QUOTE(jolmy @ Mar 11 2020, 10:13 PM)
Below my speedtest for 500Mbps just now:

[/URL]
I suspect this got to do with TIME's IPv4 Routing congestion. When browsing an IPv4-only website, I notice it slows down a lot today.
However, on IPv6 enabled sites such as Facebook & Lowyat.net, everything feels fast as usual.
Good to know I am not the only one with this issue currently.
Using IPV6 doens't seem to make any difference by comparing the latency of IPV6 vs IPV4 seems to indicate a congestion issue.
» Click to show Spoiler - click again to hide... «
ping6 ipv6.google.com
PING6(56=40+8+8 bytes) 2001:f40:904:dc10:9000:9566:2ec3:3dc6 --> 2404:6800:4001:80d::200e
16 bytes from 2404:6800:4001:80d::200e, icmp_seq=0 hlim=55 time=58.508 ms
16 bytes from 2404:6800:4001:80d::200e, icmp_seq=1 hlim=55 time=58.960 ms
16 bytes from 2404:6800:4001:80d::200e, icmp_seq=2 hlim=55 time=58.920 ms
16 bytes from 2404:6800:4001:80d::200e, icmp_seq=3 hlim=55 time=58.564 ms
16 bytes from 2404:6800:4001:80d::200e, icmp_seq=4 hlim=55 time=62.039 ms
--- ipv6.l.google.com ping6 statistics ---
5 packets transmitted, 5 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 58.508/59.398/62.039/1.333 ms
ping google.com
PING google.com (216.58.221.206): 56 data bytes
64 bytes from 216.58.221.206: icmp_seq=0 ttl=56 time=61.413 ms
64 bytes from 216.58.221.206: icmp_seq=1 ttl=56 time=65.542 ms
64 bytes from 216.58.221.206: icmp_seq=2 ttl=56 time=59.680 ms
64 bytes from 216.58.221.206: icmp_seq=3 ttl=56 time=59.954 ms
64 bytes from 216.58.221.206: icmp_seq=4 ttl=56 time=60.063 ms
--- google.com ping statistics ---
5 packets transmitted, 5 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 59.680/61.330/65.542/2.189 ms