agreed, I did mant tracerts that day. I should have posted an appropriate one

The problem went away all by itself. and now it has resurfaced.
Since the problem is often associated with degraded conventional internet traffic I'm inclined to look outside my LAN for the source, Hellstra has recently upgraded the area to Level2 and everything has been UTS ever since
So withiut any further ado, the output to my most oft frequented arena.
C:\Documents and Settings\AHII>tracert 206.16.60.39
Tracing route to 206.16.60.39 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.2.1
2 26 ms 27 ms 27 ms 122-148-0-246.core.dodo.com.au [122.148.0.246]
3 * 26 ms 27 ms dodosyd-core001-vlan101.core.dodo.com.au [122.14
8.0.1]
4 28 ms 30 ms 42 ms GigabitEthernet1-1.ken12.Sydney.telstra.net [165
.228.144.93]
5 43 ms 51 ms 99 ms 10GigabitEthernet0-1-0-2.ken-core4.Sydney.telstr
a.net [203.50.20.1]
6 * * 72 ms TenGigE0-1-0-2.chw-core2.Sydney.telstra.net [203
.50.19.129]
7 44 ms 48 ms 31 ms Port-Channel2.oxf-core1.Sydney.telstra.net [203.
50.6.2]
8 39 ms 70 ms 38 ms 10GigabitEthernet6-0.syd-core04.Sydney.reach.com
[203.50.13.34]
9 69 ms 38 ms 49 ms i-10-0.syd-core03.net.reach.com [202.84.221.85]
10 31 ms 59 ms 49 ms i-4-2.sydp-core01.net.reach.com [202.84.249.13]
11 185 ms 189 ms 200 ms i-14-0.wil-core03.net.reach.com [202.84.143.246]
12 222 ms 299 ms 192 ms i-1-2.wil04.net.reach.com [202.84.251.154]
13 405 ms 339 ms 397 ms las-bb1-link.telia.net [80.239.193.221]
14 232 ms 212 ms 219 ms las-bb1-link.telia.net [80.91.252.29]
15 287 ms 329 ms 240 ms gr1-a350s5.wswdc.ip.att.net [192.205.34.13]
16 242 ms 260 ms 231 ms tbr1.la2ca.ip.att.net [12.123.222.34]
17 282 ms 477 ms 319 ms tbr1.dlstx.ip.att.net [12.122.10.49]
18 228 ms 310 ms 238 ms br2.dlstx.ip.att.net [12.123.16.209]
19 276 ms 261 ms 287 ms mdf1-gsr12-1-pos-7-0.dal1.attens.net [12.122.255
.82]
20 245 ms 340 ms 269 ms mdf1-bi8k-1-eth-1-1.dal1.attens.net [63.241.192.
250]
21 311 ms 241 ms 308 ms 206.16.60.39
Trace complete.
C:\Documents and Settings\AHII>