Ok color me surprised but aside from the odd rubber banding on GW2 using MWEB, looks like everything is mostly back to normal in terms of feel. I'll post the tracerts I did anyways just purely because I did them (got lazy on the MWEB side of things as I got sidetracked actually playing GW2). Testing was done during dynamic events in the Cursed Shore area where huge groups of people get together to AoE lots of stuff, resulting in a good testing environment for lag.
ADSL Link Downstream Upstream
Link Rate 2048 Kbps 512 Kbps
Line Attenuation 38.0 dB 23.5 dB
Noise Margin 19.4 dB 14.0 dB
Included just for relevance.
Openweb:
GW2 Tracert
Tracing route to 206-127-159-190.plaync.com [206.127.159.190]
over a maximum of 30 hops:
1 1 ms <1 ms 4 ms 192.168.0.1
2 11 ms 11 ms 10 ms 196-215-94-1.dynamic.isadsl.co.za [196.215.94.1]
3 13 ms 19 ms 14 ms 196.38.72.125
4 * 14 ms 11 ms 196.35.115.136
5 12 ms 19 ms 15 ms core2b-ctn-gi0-1.ip.isnet.net [168.209.2.3]
6 166 ms 168 ms 167 ms 168.209.246.66
7 163 ms 167 ms 164 ms 195.50.124.33
8 164 ms 167 ms 163 ms vl-3602-ve-226.csw2.London1.Level3.net [4.69.166.149]
9 163 ms 163 ms 165 ms ae-56-221.ebr2.London1.Level3.net [4.69.153.129]
10 178 ms 180 ms 173 ms ae-23-23.ebr2.Frankfurt1.Level3.net [4.69.148.194]
11 174 ms 180 ms 183 ms ae-92-92.csw4.Frankfurt1.Level3.net [4.69.140.30]
12 176 ms 189 ms 172 ms ae-4-90.edge6.Frankfurt1.Level3.net [4.69.154.202]
13 172 ms 203 ms 177 ms 195.16.161.58
14 175 ms 175 ms 174 ms 206-127-157-86.plaync.com [206.127.157.86]
15 173 ms 177 ms 173 ms 206-127-157-102.plaync.com [206.127.157.102]
<snip>
Tracing route to
www.openweb.co.za [41.72.150.7]
over a maximum of 30 hops:
1 1 ms 3 ms 4 ms 192.168.0.1
2 10 ms 12 ms 10 ms 196-215-94-1.dynamic.isadsl.co.za [196.215.94.1]
3 12 ms 12 ms 12 ms cdsl1-ctn-vl2173.ip.isnet.net [196.38.72.113]
4 12 ms 12 ms 17 ms 196.35.115.128
5 22 ms 16 ms 14 ms core1a-ctn-gi0-1.ip.isnet.net [168.209.2.5]
6 13 ms 18 ms 14 ms 168.209.6.130
7 14 ms 13 ms 19 ms 41-208-29-210.mtnns.net [41.208.29.210]
8 14 ms 15 ms 12 ms 196.44.0.75
9 38 ms 44 ms 34 ms rb-cr-1.za--ct-cr-1.za.mtnns.net [196.44.31.128]
10 37 ms 45 ms 40 ms jh-dca-2.za--jh-cr-1.za-a.mtnns.net [196.44.0.221]
11 36 ms 41 ms 40 ms ge11-0-0.gw2.jnb6.za.mtnbusiness.net [196.30.1.22]
12 36 ms 35 ms 35 ms vlan9.hr3.jnb6.za.mtnbusiness.net [196.30.156.136]
13 39 ms 40 ms 34 ms core-router1.jnb2.host-h.net [196.30.213.108]
14 39 ms 36 ms 35 ms firewall1.jnb1.host-h.net [196.31.215.69]
15 36 ms 43 ms 35 ms mail.openweb.co.za [41.72.150.7]
Tracing route to
www.bbc.net.uk [212.58.246.91]
over a maximum of 30 hops:
1 <1 ms 1 ms <1 ms 192.168.0.1
2 12 ms 11 ms 10 ms 196-215-94-1.dynamic.isadsl.co.za [196.215.94.1]
3 13 ms 13 ms 12 ms cdsl1-ctn-vl2173.ip.isnet.net [196.38.72.113]
4 13 ms 13 ms 12 ms 196.35.115.128
5 191 ms 249 ms 239 ms core1b-ctn-gi0-2.ip.isnet.net [168.209.6.4]
6 166 ms 163 ms 163 ms 168.209.201.6
7 163 ms 163 ms 162 ms bbc-linx.pr01.thdow.bbc.co.uk [195.66.224.103]
8 * * * Request timed out.
9 163 ms 163 ms 163 ms ae0.er01.cwwtf.bbc.co.uk [132.185.254.93]
10 163 ms 164 ms 166 ms 132.185.255.165
11 164 ms 164 ms 163 ms bbc-vip012.cwwtf.bbc.co.uk [212.58.246.91]
Trace complete.
MWEB
Tracing route to
www.bbc.net.uk [212.58.244.66]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.0.1
2 19 ms 24 ms 25 ms 41-135-70-1.dsl.mweb.co.za [41.135.70.1]
3 12 ms 21 ms * 197-84-8-58.cpt.mweb.co.za [197.84.8.58]
4 13 ms 13 ms 14 ms 197-84-3-2.cpt.mweb.co.za [197.84.3.2]
5 157 ms 159 ms 164 ms TenGigE0-7-0-3.12.cpt-p-1.mweb.co.za [196.28.178.113]
6 160 ms 159 ms 159 ms 197-84-4-193.cpt.mweb.co.za [197.84.4.193]
7 158 ms 159 ms 159 ms 176.67.177.131
8 159 ms 165 ms 164 ms xe-8-1-0.edge3.London1.Level3.net [195.50.124.133]
9 169 ms 174 ms 165 ms vl-3603-ve-227.csw2.London1.Level3.net [4.69.166.153]
10 * * * Request timed out.
11 163 ms 159 ms 158 ms BBC-TECHNOL.edge4.London1.Level3.net [212.113.14.222]
12 * * * Request timed out.
13 161 ms 157 ms 158 ms ae0.er01.telhc.bbc.co.uk [132.185.254.109]
14 166 ms 166 ms 159 ms 132.185.255.148
15 160 ms 158 ms 157 ms bbc-vip111.telhc.bbc.co.uk [212.58.244.66]
As you can see, tracert's look fine. I'll switch back and forth during the course of the month to compare the 2 services. Good to see some level of normality back with MWEB again.