Server Move Completed

[Titan]

Troubles connecting as previously reported. Both Mac and XP.

Could get the header but the galaxy was slow.

The stripped version of cp was much faster but still slower than I would expect.

How to purge cache or whatever was recommended?

Thanks.

[Titan]

Also, on Shaw in McKenzie Towne. Other sites seem fine.

[Titan]

iPhone seems ok. Not great.

[onetwo_threefour]

None of the suggestions here have fixed the problem for me. The only things I haven't done are to wipe and reinstall IE8 or Vista.
I did get the forum main page to load in IE8 after about a 1 minute delay maybe half an hour ago, but couldn't link to this thread. Even on a fresh install of firefox and chrome, it still doesn't work properly. I truly think it's a Vista issue, although that makes very little sense.

Since I'm not at work today I'm paying from my phone, which seems as fast as usual.

[GoFlambe]

Not a Vista issue. I use XP and Gentoo Linux and I get the same behaviour no matter what operating system or browser.

If everyone experiencing the issue is using Shaw (and in the Calgary area?), then it could be a routing issue on the ISP end. I tried running a traceroute to forum.calgarypuck.com and on my machine, it looks like it goes to the US via cogentco and then up to rackster.com.

Just curious, but is CP hosted in Kelowna now?

Edit: Duh. Rackster.com uses Cogent. Hmm, I wonder what's causing these issues?

[GoFlambe]

OK, kind of experiencing slowness now so I did an mtr to forum.calgarypuck.com. This is what I'm currently getting:

Host Loss% Snt Last Avg Best Wrst StDev
1. 192.168.2.38 0.0% 21 0.6 0.7 0.6 0.8 0.0
2. ???
3. rd1no-ge5-0-0-1.cg.shawcable.net 0.0% 21 17.3 12.7 7.9 29.2 5.5
4. rc1no-pos10-0.cg.shawcable.net 0.0% 21 11.2 39.1 8.2 199.3 61.1
5. rc1so-pos15-0.cg.shawcable.net 0.0% 21 10.0 12.2 8.7 34.1 5.7
6. rc2wh-pos0-8-2-0.vc.shawcable.net 0.0% 21 24.6 25.7 22.5 37.3 3.3
7. rc2sj-pos6-0-0.cl.shawcable.net 0.0% 21 55.7 48.8 44.5 85.0 9.1
8. gi1-19.mpd01.sjc03.atlas.cogentco.com 0.0% 21 46.6 57.0 44.5 237.0 41.4
9. te8-2.mpd01.sjc01.atlas.cogentco.com 0.0% 21 48.3 47.7 45.2 59.2 3.5
10. te2-4.mpd01.sfo01.atlas.cogentco.com 0.0% 21 57.2 63.3 55.6 117.6 16.8
11. te4-1.mpd01.mci01.atlas.cogentco.com 0.0% 21 70.5 72.0 68.9 81.2 3.3
12. te2-1.mpd01.ord01.atlas.cogentco.com 0.0% 21 69.4 71.0 68.4 85.1 3.6
13. te3-7.mpd01.ymq02.atlas.cogentco.com 0.0% 21 86.3 88.8 86.2 96.9 2.5
14. te4-3.ccr01.ymq01.atlas.cogentco.com 0.0% 21 87.5 89.6 86.2 102.5 5.1
15. vl3502.na01.b019086-1.ymq01.atlas.cogentco.com 0.0% 21 87.8 89.9 86.3 125.7 8.3
16. 38.104.152.78 52.4% 21 176.5 178.3 175.0 187.6 4.0
17. incore01.rackster.com 0.0% 21 177.6 180.8 174.0 204.0 7.2
18. infw01.rackster.com 0.0% 21 181.3 180.9 175.7 193.7 4.5
19. indist01.rackster.com 0.0% 21 185.3 182.1 174.8 197.2 6.9
20. ???

Upwards of 50% packet loss at 38.104.152.78. That could explain some of the slowness. For anyone who has a consistently working connection (and has the ability), what does the mtr output look like?

Edit: That was from my home Shaw connection. Work uses Telus, and while there's still some packet loss at that IP, it's nowhere near as bad. Here's the output from work:

Host Loss% Last Avg Best Wrst StDev
1. 199.126.15.132 0.0% 0.1 0.1 0.1 0.2 0.0
2. 10.138.64.1 0.0% 10.1 16.0 10.0 170.8 21.3
3. 154.11.214.1 0.0% 10.3 16.9 9.8 142.6 24.0
4. chcgildtgr00.bb.telus.com 0.0% 39.7 40.6 39.0 50.8 2.7
5. 154.11.2.50 0.0% 39.7 49.1 39.1 238.0 33.3
6. te3-1.ccr02.ord03.atlas.cogentco.com 0.0% 39.5 50.5 39.2 243.7 38.2
7. te1-1.mpd02.ord01.atlas.cogentco.com 0.0% 40.0 49.7 39.1 226.9 34.9
8. te4-7.mpd01.ymq02.atlas.cogentco.com 1.0% 61.3 71.2 60.2 248.1 33.7
9. te4-3.ccr01.ymq01.atlas.cogentco.com 0.0% 61.5 65.4 60.4 137.5 14.3
10. vl3502.na01.b019086-1.ymq01.atlas.cogentco.com 0.0% 61.8 62.3 60.7 128.1 7.0
11. 38.104.152.78 2.0% 156.4 155.8 148.3 342.9 24.9
12. incore01.rackster.com 0.0% 148.9 156.7 148.5 361.8 24.2
13. infw01.rackster.com 0.0% 155.3 153.2 148.6 186.9 4.6
14. indist01.rackster.com 0.0% 152.9 153.7 148.6 264.4 11.7
15. ???

Running both simultaneously and while my home Shaw connection has around 49% packet loss, the same connection over Telus has, well, 0% right now (it was fluctuating between 2-4% when I started editing this message).

So this is what I can't understand. While both connections use different routes, the last two hops before 38.104.152.78 are pretty much the same. So why is the Shaw connection experiencing 50% packet loss at that point and the Telus one is not? This confuses me. Is Shaw mangling packets? If so, perhaps there's QoS being implemented at that IP and is giving low priority to stuff coming in from Shaw? I'm shooting from the hip here now. If anyone has a better idea, please share.

[photon]

That's very very helpful Flambe.. this almost sounds like a problem we had a loooong time ago, where almost everyone was fine but a few people would get their IPs banned from the firewall and couldn't access the forum anymore. So maybe somehow a few people got their IPs put in a pool, or IPs are already in a pool where their connection to the server is throttled.

If anyone else has any mtr reports to submit that would be great. I'll contact the colo with this.

[photon]

http://winmtr.sourceforge.net/

For those on windows, not at home so can't try it on windows.

[FlamesKickAss]

i am in mckenzie towne, tried on google chrome and it gets in here after a lot of retries.

will try that other program but have no idea how to use it

edit: got the program working i think.... it just sits there. I tried to ping the ip above and all 4 packets failed

and every site ive gone to works fast. i tried the archive line photon posted and its slow for that too. roommate just tried iPhone on same wifi network and it worked fine

[photon]

For WinMTR you want to put in forum.calgarypuck.com as the destination.

I've sent an email to the hosting guys to see if they can see any packet loss on their end.

[ikaris]

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.

Originally Posted by photon

http://forum.calgarypuck.com/galaxy.jpg

Right click and save that image and see what kind of transfer speeds you get.

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.

[ikaris]

Seems I'm following the same route as GoFlambe. I wonder if he (and others) are on the same subnet as I am?

As well, out of curiousity, is it really cheaper to get hosting out of California versus something at 151 Front Street (Toronto)?

EDIT: My bad, I see you're using Rackster as mentioned by GoFlambe and they are out of Kelowna. Too bad they only seem to use Cogent (the absolute cheapest tier provider out there).

[GoFlambe]

Originally Posted by ikaris

Seems I'm following the same route as GoFlambe. I wonder if he (and others) are on the same subnet as I am?

My IP is currently on the 174.0.247.0/22 subnet. While this is a relatively new IP for me, I've had this one for a few months now.

If I can be of any more assistance, let me know. I needs me my CP, darnit!

[FlamesKickAss]

Okay so I tried a traceroute from my router last night and it pretty much froze on the 15th ip.

My ip is the 174.0.?.? (? because I am not at home). works just fine at work though. dont know who we use. I remember seeing it somewhere but dont know where.

[ikaris]

Maybe we're identifying a pattern? Shaw users that have IPs that start with a 174?

[GoFlambe]

Originally Posted by ikaris

Maybe we're identifying a pattern? Shaw users that have IPs that start with a 174?

Too early to tell. Too small of a sample size. Would love to hear from Shaw users in the Calgary area that actually work properly and see what their IPs are and what a traceroute and an mtr run looks like for them.

[GoFlambe]

Double post. Thought it hung again so hit the Submit button again.

[photon]

They've opened a ticket with their network provider, that IP where you saw the loss is before their network. So we'll see what they say.

[onetwo_threefour]

I had already emailed boardadmin with my home IP address which was 174.0.*.* when I first brought up this problem.


I am currently posting from a work computer, with Shaw as our provider and have a 174.0.*.* address on this computer but am loading no problem and was on the weekend as well while still having problems from my home PC.

According to whatismyip.com My Wii had the same IP as my home PC but didn't reallly have problems with loading CP, albeit on a different browser. (Opera) There's been a couple of occasions where there has been a bit of a slowdown on the Wii loading CP, but we're talking a couple of seconds, whereas on my PC it would never load at all.

Although I'm not having problems with this computer, here is the tracert from the comupter I am on

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
H:\>tracert forum.calgarypuck.com
Tracing route to forum.calgarypuck.com [66.209.190.109]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 18 ms 14 ms 7 ms rd1so-ge11-0-0-1.cg.shawcable.net [64.59.139.34]
4 14 ms 11 ms 9 ms rc2so-tge0-0-2-0.cg.shawcable.net [66.163.71.77]
5 22 ms 21 ms 23 ms rc2wh-tge0-9-2-0.vc.shawcable.net [66.163.77.162]
6 66 ms 44 ms 44 ms rc4sj-pos0-0-1-0.cl.shawcable.net [66.163.77.234]
7 263 ms 81 ms 269 ms gi1-28.mpd01.sjc03.atlas.cogentco.com [154.54.9.49]
8 56 ms 46 ms 45 ms te8-2.mpd01.sjc01.atlas.cogentco.com [154.54.6.237]
9 56 ms 57 ms 56 ms te2-4.mpd01.sfo01.atlas.cogentco.com [66.28.4.149]
10 101 ms 69 ms 80 ms te4-1.mpd01.mci01.atlas.cogentco.com [154.54.6.33]
11 67 ms 67 ms 67 ms te2-1.mpd01.ord01.atlas.cogentco.com [154.54.2.234]
12 89 ms 95 ms 85 ms te3-7.mpd01.ymq02.atlas.cogentco.com [38.20.46.10]
13 85 ms 85 ms 85 ms te4-3.ccr01.ymq01.atlas.cogentco.com [154.54.0.21]
14 87 ms 86 ms 87 ms vl3502.na01.b019086-1.ymq01.atlas.cogentco.com [38.20.33.38]
15 185 ms * * 38.104.152.78
16 189 ms 188 ms 187 ms incore01.rackster.com [66.209.176.3]
17 184 ms 185 ms 182 ms infw01.rackster.com [66.209.176.9]
18 181 ms * * indist01.rackster.com [66.209.176.14]
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
H:\>

[Titan]

Your IP Address Is: 174.0.191.x
This is my IP.
I am still having the same terrible load times. Mac osx, xp and iphone all are slow but all access the same router.

Just checked from my iPhone with wifi off and cp works fine.

Any suggestions?