Lately I've noticed SI has slowed down significantly. I'm not sure if the problem is on my end or if its a problem on their end.
I would like people from time to time, maybe once a week or maybe even once a day (but no more than 3 times a day) to perform the following tests and then report them on this thread. And once you start posting, please keep posting so we can build a pile of evidence...
Hopefully this information can be used as evidence as how SI can solve the problem and make everyone's experience a little more grand.
If you have access to a DOS prompt while you are connected to the internet try the following commands:
ping -a -r 9 www.siliconinvestor.com > route80.txt
notepad route80.txt
----
You will see something like this (It shouldn't be identical unless you're using the same ISP/location, etc).
Pinging v10.go2net.com [206.253.217.10] with 32 bytes of data:
Reply from 206.253.217.10: bytes=32 time=220ms TTL=247
Route: washington.dc.southeast.us.psi.net [38.1.45.201] ->
rc11.se.us.psi.net [38.1.25.203] ->
se2.isc.us.psi.net [38.1.10.5] ->
204.6.118.189 ->
sl-bb3-rly-4-0-0.sprintlink.net [144.232.7.222] ->
144.232.15.114 ->
sl-bb13-pen-10-0.sprintlink.net [144.232.5.158] ->
sl-bb11-pen-7-1.sprintlink.net [144.232.9.142] ->
sl-bb10-sea-5-2.sprintlink.net [144.232.6.117]
Request timed out.
Reply from 206.253.217.10: bytes=32 time=501ms TTL=247
Route: washington.dc.southeast.us.psi.net [38.1.45.201] ->
rc11.se.us.psi.net [38.1.25.203] ->
se2.isc.us.psi.net [38.1.10.5] ->
204.6.118.189 ->
sl-bb3-rly-0-0-0.sprintlink.net [144.232.7.218] ->
sl-bb12-rly-9-0.sprintlink.net [144.232.7.214] ->
sl-bb11-rly-7-0.sprintlink.net [144.232.9.242] ->
sl-bb13-pen-10-0.sprintlink.net [144.232.5.158] ->
sl-bb11-pen-7-1.sprintlink.net [144.232.9.142]
Reply from 206.253.217.10: bytes=32 time=170ms TTL=247
Route: washington.dc.southeast.us.psi.net [38.1.45.201] ->
rc11.se.us.psi.net [38.1.25.203] ->
se2.isc.us.psi.net [38.1.10.5] ->
204.6.118.189 ->
sl-bb3-rly-4-0-0.sprintlink.net [144.232.7.222] ->
144.232.15.114 ->
sl-bb13-pen-10-0.sprintlink.net [144.232.5.158] ->
sl-bb11-pen-7-1.sprintlink.net [144.232.9.142] ->
sl-bb10-sea-5-2.sprintlink.net [144.232.6.117]
Just paste it into a post where the evidence can be examined at a later date.
------
For control purposes, add the following to a daily post
ping 127.0.0.1 > route127.txt
notepad route127.txt
-----
it will look something like this
--
Pinging localhost [127.0.0.1] with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<10ms TTL=128
Reply from 127.0.0.1: bytes=32 time<10ms TTL=128
Reply from 127.0.0.1: bytes=32 time<10ms TTL=128
Reply from 127.0.0.1: bytes=32 time<10ms TTL=128
-----
Once enough of us start posting this information SI should be able to glean what it needs to be able to fix this problem.
fwiw I'm using Windows NT... |
