Quote:
Originally Posted by photon
What ISP are all you guys that have problems on?
I'm using Shaw at the moment.
http://calgarypuck.dreamhosters.com/v374/header.png
That's the site we use to host all the small images for the site at the moment, try just that link and see if it pops up right away or if there's a long delay (Shift-F5 forces it to get the image). |
I tried this link, and the image is very quick to load.
Quote:
Originally Posted by photon
|
Extremely slow. I get around 2.5 kb/s.
This is with a Shaw connection with an ip of 174.0.232.x.
Here is the trace route:
Tracing route to forum.calgarypuck.com [66.209.190.109]
over a maximum of 30 hops:
1 * * * Request timed out.
2 8 ms 9 ms 7 ms rd1no-ge5-0-0-1.cg.shawcable.net [64.59.139.66]
3 12 ms 9 ms 9 ms rc1no-pos10-0.cg.shawcable.net [66.163.71.133]
4 9 ms 8 ms 10 ms rc2so-tge0-0-1-0.cg.shawcable.net [66.163.77.9]
5 24 ms 22 ms 23 ms rc2wh-tge0-2-1-0.vc.shawcable.net [66.163.77.226
]
6 46 ms 64 ms 75 ms rc4sj-pos0-0-1-0.cl.shawcable.net [66.163.77.234
]
7 56 ms 55 ms 75 ms gi1-19.mpd01.sjc03.atlas.cogentco.com [154.54.10
.57]
8 74 ms 56 ms 61 ms te2-2.mpd01.sjc01.atlas.cogentco.com [66.28.4.73
]
9 46 ms 46 ms 45 ms te2-4.mpd01.sfo01.atlas.cogentco.com [66.28.4.14
9]
10 67 ms 85 ms 68 ms te4-1.mpd01.mci01.atlas.cogentco.com [154.54.6.3
3]
11 70 ms 69 ms 70 ms te7-2.mpd01.ord01.atlas.cogentco.com [154.54.7.1
37]
12 89 ms 88 ms 88 ms te3-7.mpd01.ymq02.atlas.cogentco.com [38.20.46.1
0]
13 87 ms 90 ms 95 ms te4-3.ccr01.ymq01.atlas.cogentco.com [154.54.0.2
1]
14 87 ms 91 ms 90 ms vl3502.na01.b019086-1.ymq01.atlas.cogentco.com [
38.20.33.38]
15 180 ms 175 ms 175 ms 38.104.152.78
16 181 ms * 177 ms incore01.rackster.com [66.209.176.3]
17 175 ms 183 ms 182 ms infw01.rackster.com [66.209.176.9]
18 179 ms 180 ms 187 ms indist01.rackster.com [66.209.176.14]
19 * * * Request timed out.
Here is a ping to the server before rackster.com:
Pinging 38.104.152.78 with 32 bytes of data:
Reply from 38.104.152.78: bytes=32 time=193ms TTL=244
Reply from 38.104.152.78: bytes=32 time=175ms TTL=244
Reply from 38.104.152.78: bytes=32 time=183ms TTL=244
Reply from 38.104.152.78: bytes=32 time=175ms TTL=244
Reply from 38.104.152.78: bytes=32 time=184ms TTL=244
Reply from 38.104.152.78: bytes=32 time=175ms TTL=244
Reply from 38.104.152.78: bytes=32 time=176ms TTL=244
Reply from 38.104.152.78: bytes=32 time=181ms TTL=244
Reply from 38.104.152.78: bytes=32 time=174ms TTL=244
Reply from 38.104.152.78: bytes=32 time=173ms TTL=244
Reply from 38.104.152.78: bytes=32 time=178ms TTL=244
Reply from 38.104.152.78: bytes=32 time=214ms TTL=244
Reply from 38.104.152.78: bytes=32 time=274ms TTL=244
Reply from 38.104.152.78: bytes=32 time=199ms TTL=244
Reply from 38.104.152.78: bytes=32 time=179ms TTL=244
Reply from 38.104.152.78: bytes=32 time=179ms TTL=244
Reply from 38.104.152.78: bytes=32 time=200ms TTL=244
Reply from 38.104.152.78: bytes=32 time=182ms TTL=244
Reply from 38.104.152.78: bytes=32 time=179ms TTL=244
Reply from 38.104.152.78: bytes=32 time=184ms TTL=244
Reply from 38.104.152.78: bytes=32 time=178ms TTL=244
Reply from 38.104.152.78: bytes=32 time=178ms TTL=244
Reply from 38.104.152.78: bytes=32 time=178ms TTL=244
Reply from 38.104.152.78: bytes=32 time=174ms TTL=244
Reply from 38.104.152.78: bytes=32 time=182ms TTL=244
Reply from 38.104.152.78: bytes=32 time=176ms TTL=244
Reply from 38.104.152.78: bytes=32 time=182ms TTL=244
Reply from 38.104.152.78: bytes=32 time=175ms TTL=244
Reply from 38.104.152.78: bytes=32 time=184ms TTL=244
Reply from 38.104.152.78: bytes=32 time=194ms TTL=244
Reply from 38.104.152.78: bytes=32 time=175ms TTL=244
Reply from 38.104.152.78: bytes=32 time=181ms TTL=244
Reply from 38.104.152.78: bytes=32 time=175ms TTL=244
Reply from 38.104.152.78: bytes=32 time=179ms TTL=244
Reply from 38.104.152.78: bytes=32 time=179ms TTL=244
Ping statistics for 38.104.152.78:
Packets: Sent = 35, Received = 35, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 173ms, Maximum = 274ms, Average = 184ms
Here is a ping to incore01.rackster.com:
Pinging incore01.rackster.com [66.209.176.3] with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 66.209.176.3: bytes=32 time=199ms TTL=243
Reply from 66.209.176.3: bytes=32 time=197ms TTL=243
Request timed out.
Request timed out.
Reply from 66.209.176.3: bytes=32 time=187ms TTL=243
Reply from 66.209.176.3: bytes=32 time=190ms TTL=243
Request timed out.
Reply from 66.209.176.3: bytes=32 time=196ms TTL=243
Request timed out.
Reply from 66.209.176.3: bytes=32 time=201ms TTL=243
Request timed out.
Reply from 66.209.176.3: bytes=32 time=193ms TTL=243
Request timed out.
Reply from 66.209.176.3: bytes=32 time=186ms TTL=243
Reply from 66.209.176.3: bytes=32 time=188ms TTL=243
Request timed out.
Request timed out.
Reply from 66.209.176.3: bytes=32 time=191ms TTL=243
Request timed out.
Request timed out.
Request timed out.
Reply from 66.209.176.3: bytes=32 time=186ms TTL=243
Request timed out.
Reply from 66.209.176.3: bytes=32 time=186ms TTL=243
Request timed out.
Reply from 66.209.176.3: bytes=32 time=185ms TTL=243
Request timed out.
Ping statistics for 66.209.176.3:
Packets: Sent = 29, Received = 13, Lost = 16 (55% loss),
Approximate round trip times in milli-seconds:
Minimum = 185ms, Maximum = 201ms, Average = 191ms
Seems after 38.104.152.78 I seem to get packet loss.
Using a proxy connection based out of Chicago, this problem does not happen, only with my Shaw connection at home.
Also the stripped down version seems to work, but not as fast as I would expect it to.
Hope this helps.