[JRV]

Avian, no offense intended, but the first 3 paragraphs of your message accomplish nothing except to make you sound defensive. The 4th paragraph does little to diminish that effect; actually, it underscores it. Not the first time I've noticed that on this board, either.

Specifically, you keep coming back to the irrelevance of the 56k listener count, but until this last message from you, I had no way to determine the 128k listener count. But I did guess that there is a typical ratio of 56k listeners to 128k listeners and that you might know what that is. Looks like roughly 10%. If so, my observations are relevant, if unavoidably imprecise.

Your last 4 paragraphs are constructive, and all I needed to hear. Here are the answers:

PING

Reply from xxx.xxx.xxx.xxx: bytes=32 time=92ms TTL=109
Reply from xxx.xxx.xxx.xxx: bytes=32 time=82ms TTL=109
Reply from xxx.xxx.xxx.xxx: bytes=32 time=70ms TTL=109
Reply from xxx.xxx.xxx.xxx: bytes=32 time=69ms TTL=109

Ping statistics for 64.202.98.44:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 69ms, Maximum = 92ms, Average = 78ms

================

TRACERT

1 43 ms 37 ms 24 ms adsl-xxx-xxx-xxx-xxx.dsl.hstntx.swbell.net [xxx.xxx.xxx.xxx]
2 19 ms 19 ms 19 ms dist1-vlan60.hstntx.swbell.net [151.164.11.190]
3 20 ms 18 ms 19 ms bb1-g8-0.hstntx.swbell.net [151.164.11.246]
4 20 ms 200 ms 24 ms core1-p6-1.crhstx.sbcglobal.net [151.164.188.5]
5 26 ms 41 ms 23 ms core3-p14-2.crdltx.sbcglobal.net [151.164.188.165]
6 38 ms 47 ms 47 ms core1-p2-0.crdltx.sbcglobal.net [151.164.242.106]
7 38 ms 48 ms 38 ms bb1-p14-2.rcsntx.sbcglobal.net [151.164.240.73]
8 23 ms 26 ms 25 ms bb1-p14-0.pxdltx.sbcglobal.net [151.164.242.142]
9 26 ms 24 ms 27 ms 198.32.114.12
10 63 ms 62 ms 61 ms ge1-2-605m2-chi-b1-00.bb.webusenet.net [64.154.59.177]
11 60 ms 61 ms 62 ms ge1-6.b2.chg.servercentral.net [64.154.39.6]
12 68 ms 95 ms 67 ms server.domain.tld [xxx.xxx.xxx.xxx]

Trace complete.

===================

At this writing, I've been streaming from RadioStorm.com at 128 for 90 minutes.

Flawless.

Not even any prebuffering that I've noticed. This is at 10:30 AM CT, a time at which I often encounter the problem with AM every 3 or 4 minutes. I will stay with RadioStorm this morning and see if I have any problems.