Connection problems?


#1

Is anybody experiencing connection problems lately? I can’t seem to upload any files via Fetch or any other FTP client. I can download no problem but it’s impossible to upload. It looks like the file is being uploaded but it just sits until it times out. Also, when using a content manager, Expression Engine, it takes forever to update a template or to do anything.
Just wondering if it’s just me or anybody else having the same problems. any suggestions? I have already emailed support but I’m still waiting. thanks!


#2

I thought maybe I was just going insane. You’re not alone. I’ve been having trouble trying to upload using a number of different FTP programs (WS_FTP, CuteFTP, Transmit, Windows FTP) on a couple of computers over the last several days and it either times out at 100% or it looks like it uploads but only uploads a fraction of the file or it gives 450 or 554 errors – it’s driving me batty because I’m ending up with chopped up, incomplete files on the site.

I’ve emailed them as well – have you heard anything back from them yet?


#3

I am having exactly the same problem! Typically the file upload will get up to around 32 k and then the connection will time out; downloads are fine. I have tried FileZilla, WS FTP and, today, FTP Voyager. None work, and changing settings (PASV, compression, etc.) makes no difference.

For the last 24 hours I have been pulling my hair out screwing around with MTU settings and so on, and nothing is working.

I am not having this problem from my office PC, just the one at home, and I am wondering (maybe) if it has something to do with the most recent XP security patch from Microsoft interacting (perhaps) with Dreamhost’s firewall. Other hosts (WELL.com and 1and1) work fine.

John


tranquileye.com
I recommend Dreamhost.


#4

Hrm - all 3 of you are apparently subscribers of rogers.com. I’ve gotten one complaint this week about weird network issues (slowness and apparent packet loss) to them… thus far, it seems as if the problem is within their network (or else with an intermediary network). Traffic to and from rogers is taking an asymetric path; as far as I can tell, the problem seems to be on the inbound path, over which we have much less influence. I can try messing with some stuff over here, but you may want to try and contact their support team.

Are you guys seeing any packet loss or latency in general, or does the problem only seem to happen with FTP? If you have access to an alternate connection, do you still see the problem from there?

If you want to ping your domain and let it run for a few hundred pings at least, and then send me the statistics section at the end (via support), along with a traceroute, that might be helpful.


#5

Thanks for your speedy help with this.

Ping stats:

Ping statistics for 66.33.209.189:
Packets: Sent = 689, Received = 652, Lost = 37 (5% loss),
Approximate round trip times in milli-seconds:
Minimum = 98ms, Maximum = 218ms, Average = 110ms

Traceroute:

Tracing route to tranquileye.com [66.33.209.189]
over a maximum of 30 hops:

1 25 ms 29 ms 29 ms tlgw27.slnt.phub.net.cable.rogers.com [24.157.72 .1]
2 26 ms 29 ms 29 ms 10.1.65.1
3 27 ms 29 ms 29 ms gw01-vlan966.slnt.phub.net.cable.rogers.com [66. 185.93.213]
4 28 ms 29 ms 29 ms gw01.rchrd.phub.net.cable.rogers.com [66.185.82. 133]
5 29 ms 29 ms 29 ms gw01.flfrd.phub.net.cable.rogers.com [66.185.82. 129]
6 43 ms 29 ms 29 ms gw02.mtnk.phub.net.cable.rogers.com [66.185.82.1 25]
7 35 ms 36 ms 35 ms gw02.wlfdle.phub.net.cable.rogers.com [66.185.80 .145]
8 34 ms 35 ms 35 ms gw04.ym.phub.net.cable.rogers.com [66.185.83.130 ]
9 48 ms 47 ms 47 ms p13-0.core02.ord01.atlas.cogentco.com [66.28.4.2 13]
10 46 ms 47 ms * p15-0.core01.ord03.atlas.cogentco.com [154.54.2. 242]
11 37 ms 41 ms 39 ms gblx.ord03.atlas.cogentco.com [154.54.11.102]
12 93 ms 95 ms 92 ms so1-0-0-622M.ar1.LAX3.gblx.net [67.17.73.42]
13 119 ms 120 ms 119 ms GE1-GX.dreamhost.com [67.17.162.162]
14 * * 119 ms basic-pat.balrog.dreamhost.com [66.33.209.189]

Trace complete.

John


tranquileye.com
I recommend Dreamhost.


#6

Here are my ping stats:

271 packets transmitted, 220 packets received, 18% packet loss
round-trip min/avg/max = 92.084/99.48/229.172 ms

and traceroute results:

Tracing route to www.dreamhost.com [66.33.206.47] over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 10 ms 8 ms 22 ms 10.45.40.1
3 9 ms 28 ms 12 ms gw03- vlan201.wlfdle.phub.net.cable.rogers.com [6
6.185.90.161]
4 26 ms 9 ms 8 ms gw01-
vlan961.wlfdle.phub.net.cable.rogers.com [6
6.185.93.65]
5 48 ms 11 ms 8 ms gw02.wlfdle.phub.net.cable.rogers.com
[66.185.80
.130]
6 10 ms 9 ms * gw04.ym.phub.net.cable.rogers.com
[66.185.83.130 ]
7 23 ms 23 ms 66 ms p13-0.core02.ord01.atlas.cogentco.com
[66.28.4.2 13]
8 30 ms 21 ms 22 ms p15-0.core01.ord03.atlas.cogentco.com [154.54.2. 242]
9 32 ms 21 ms 25 ms gblx.ord03.atlas.cogentco.com
[154.54.11.102]
10 80 ms 80 ms 79 ms so1-0-0-622m.ar1.lax3.gblx.net
[67.17.73.42]
11 93 ms 93 ms 116 ms ge1-gx.dreamhost.com [67.17.162.162]
12 99 ms 93 ms 92 ms dreamhost.com [66.33.206.47]

Trace complete.

We still can’t FTP to any of our 4 websites. Downloading is still OK but not uploading. We have tried uploading the same files to other servers like Primus and IASL. no problems there. So, if it is a Rogers’ thing then shouldn’t we have the same problem FTP-ing to any server?

Also, we are experiencing problems with our email. We can send and receive email as long as there are no attachments. Once there is an attachment, it keeps trying to upload until it times out with an error:
“smtp server not responding. server unexpectedly terminated connection. protocol smtp port 25 secure (ssl) no. socket error 10053 error #0x800cc0f

We tried to send an email with an attachment using the dreamhost webmail, it returns an 'action cancelled" page.

We desperately need to get this problem resolved as soon as possible in order to meet our deadlines. Any suggestions will be greatly appreciated.

thanks for response.


#7

Here’s my traceroute (and I’m getting 14% packet loss and round trip times of 93-203 ms on a ping of 250 to the same site).

Tracing route to www.acountrypractice.com [66.33.209.82]

over a maximum of 30 hops:

1 <10 ms <10 ms <10 ms 192.168.0.1
2 <10 ms 15 ms 16 ms 10.44.104.1
3 47 ms 15 ms 16 ms gw03.slnt.phub.net.cable.rogers.com [66.185.90.145]
4 <10 ms 16 ms 31 ms gw01-vlan962.slnt.phub.net.cable.rogers.com [66.185.93.197]
5 <10 ms 16 ms <10 ms gw01.rchrd.phub.net.cable.rogers.com [66.185.82.133]
6 15 ms 16 ms * gw01.flfrd.phub.net.cable.rogers.com [66.185.82.129]
7 47 ms 16 ms 15 ms gw02.mtnk.phub.net.cable.rogers.com [66.185.82.125]
8 16 ms 16 ms 31 ms gw02.wlfdle.phub.net.cable.rogers.com [66.185.80.153]
9 * * * Request timed out.
10 * 31 ms 47 ms p13-0.core02.ord01.atlas.cogentco.com [66.28.4.213]
11 62 ms 63 ms 31 ms p15-0.core01.ord03.atlas.cogentco.com [154.54.2.242]
12 32 ms 31 ms 31 ms gblx.ord03.atlas.cogentco.com [154.54.11.102]
13 141 ms 78 ms 94 ms so1-0-0-622M.ar1.LAX3.gblx.net [67.17.73.42]
14 * 93 ms 125 ms GE1-GX.dreamhost.com [67.17.162.162]
15 156 ms * 93 ms basic-heavy.tank.dreamhost.com [66.33.209.82]

Trace complete.

Just wanted to point out that I’ve been having trouble doing anything of an interactive nature with dreamhost site pages for a few weeks – uploading files, posting messages, trying to access Webmail, doing anything in the web panel. Posting and doing anything in Webmail and the web panel take forever but I can eventually get through to what I’m trying to do (though frankly I had easier access with dialup even doing those and that’s kind of sad). I 've only been trying to FTP anything for the last couple of days and that’s when I really noticed problems. I don’t have a problem uploading anything to any other web site through Rogers and upload tests give great results.


#8

It’s not as cut and dried as “I don’t have problems connecting to anywhere else, so the problem is on your side” (and from our point of view, we don’t hear of anyone else having these problems…). Could one of you folks maybe try posting traceroutes and ping tests (the same ones) to a site that you’re not seeing these problems with?

Also, could you do extended ping tests to the following:
ge1-gx.dreamhost.com
fe1-mz.dreamhost.com
ge1-l3.dreamhost.com

I can try shifting traffic so that the outbound route is symetrical to the inbound route, but I don’t think that will fix the problem. I went ahead and did that, so let me know if this somehow clears up the problem (or makes it worse). My guess is that maybe there’s some sort of problem with the inbound route (which is also passing through Cogent on its way to us).

The difficult thing here is going to be getting through to anyone at Rogers who can actually figure out what’s going on here - I imagine their first tier support won’t be much help. However, if you send them the traceroutes and ping statistics showing how much packet loss you’re seeing to our network, they may be able to do something to clean that up a little.


#9

Just thought I’d let you know that I tried it all again and I was able to upload a couple of files without it doing any retries. And I’m only getting a fairly minimal 3% packet loss to the site right now.


#10

Here are the results for the tests you have requested. I hope you can figure this out.
We were able to upload files that are up to 20K without it timing out but we still can’t send any emails with attachments. And it is still painfully SLOW!!!

ge1-gx.dreamhost.com
152 packets transmitted, 145 packets received, 4% packet loss
round-trip min/avg/max = 79.515/93.197/285.795 ms

fe1-mz.dreamhost.com
202 packets transmitted, 201 packets received, 0% packet loss
round-trip min/avg/max = 93.796/109.039/325.906 ms

ge1-l3.dreamhost.com
211 packets transmitted, 211 packets received, 0% packet loss
round-trip min/avg/max = 87.322/102.862/326.709 ms

Traceroute & ping results:

Tracing route to www.iasl.com http://www.iasl.com [216.8.142.114]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 12 ms 10 ms 9 ms 10.45.40.1
3 8 ms 10 ms 33 ms gw03-vlan201.wlfdle.phub.net.cable.rogers.com [6
6.185.90.161]
4 8 ms 11 ms 30 ms gw0


#11

Having problems even posting on this board.

here are the results again.

ge1-gx.dreamhost.com
152 packets transmitted, 145 packets received, 4% packet loss
round-trip min/avg/max = 79.515/93.197/285.795 ms

fe1-mz.dreamhost.com
202 packets transmitted, 201 packets received, 0% packet loss
round-trip min/avg/max = 93.796/109.039/325.906 ms

ge1-l3.dreamhost.com
211 packets transmitted, 211 packets received, 0% packet loss
round-trip min/avg/max = 87.322/102.862/326.709 ms

Traceroute & ping results:

Tracing route to www.iasl.com http://www.iasl.com [216.8.142.114]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 12 ms 10 ms 9 ms 10.45.40.1
3 8 ms 10 ms 33 ms gw03-vlan201.wlfdle.phub.net.cable.rogers.com [6
6.185.90.161]
4 8 ms 11 ms 30 ms gw01-vlan961.wlfdle.phub.net.cable.rogers.com [6
6.185.93.65]
5 27 ms 12 ms 26 ms gw02.wlfdle.phub.net.cable.rogers.com [66.185.80
.130]
6 26 ms 24 ms 24 ms dcr1-so-3-1-0.newyork.savvis.net [206.24.207.85]

7 53 ms 53 ms 43 ms agr3-so-0-0-0.newyork.savvis.net [206.24.207.58]

8 26 ms 26 ms 26 ms acr1-loopback.newyork.savvis.net [206.24.194.61]

9 41 ms 33 ms 24 ms cable-and-wireless-peering.newyork.savvis.net [2
06.24.195.150]
10 26 ms 46 ms 69 ms ewr-core-02.inet.qwest.net [205.171.17.129]
11 40 ms 34 ms 33 ms chi-core-01.inet.qwest.net [205.171.8.229]
12 34 ms 38 ms 43 ms chi-edge-09.inet.qwest.net [205.171.20.126]
13 37 ms 40 ms 42 ms 65.113.255.210
14 53 ms 53 ms 40 ms uaca6.win.mnsi.net [216.8.137.200]
15 49 ms 82 ms 51 ms vlan36.caterpillar.iasl.com [216.8.136.10]
16 49 ms 51 ms 52 ms lan1.toron01svr.iasl.com [216.8.142.114]

Trace complete.

ping results for iasl.com:

203 packets transmitted, 203 packets received, 0% packet loss
round-trip min/avg/max = 47.16/55.435/107.887 ms

Tracing route to www.primus.ca http://www.primus.ca [216.254.141.10]
over a maximum of 30 hops:

1 <1 ms <1 ms 1 ms 192.168.0.1
2 9 ms 13 ms 10 ms 10.45.40.1
3 51 ms 10 ms 9 ms gw03-vlan201.wlfdle.phub.net.cable.rogers.com [6
6.185.90.161]
4 13 ms 11 ms 39 ms gw01-vlan961.wlfdle.phub.net.cable.rogers.com [6
6.185.93.65]
5 41 ms 8 ms 34 ms gw02.wlfdle.phub.net.cable.rogers.com [66.185.80
.130]
6 8 ms 29 ms 11 ms gw01.front.phub.net.cable.rogers.com [66.185.81.
18]
7 32 ms 23 ms 9 ms gw-primuscanada.torontointernetxchange.net [198.
32.245.22]
8 8 ms 32 ms 9 ms 216.254.129.3 [216.254.129.3]
9 14 ms 47 ms 38 ms web.tor.primus.ca [216.254.141.10]

Ping test for www.primus.ca
208 packets transmitted, 207 packets received, 0% packet loss
round-trip min/avg/max = 8.368/15.84/58.796 ms


#12

First, the sites that I’m having no problem with:

well.com
Packets: Sent = 311, Received = 310, Lost = 1 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 99ms, Maximum = 347ms, Average = 118ms

Tracing route to well.com [206.14.209.5]
over a maximum of 30 hops:

1 28 ms 29 ms 29 ms tlgw27.slnt.phub.net.cable.rogers.com [24.157.72 .1]
2 27 ms 29 ms 29 ms 10.1.65.1
3 28 ms 30 ms 29 ms gw01-vlan967.slnt.phub.net.cable.rogers.com [66. 185.93.217]
4 30 ms 29 ms 29 ms gw01.rchrd.phub.net.cable.rogers.com [66.185.82. 133]
5 28 ms 29 ms 29 ms gw01.flfrd.phub.net.cable.rogers.com [66.185.82. 129]
6 33 ms 29 ms 30 ms gw02.mtnk.phub.net.cable.rogers.com [66.185.82.1 25]
7 35 ms 35 ms 35 ms gw02.wlfdle.phub.net.cable.rogers.com [66.185.80 .153]
8 49 ms 53 ms 54 ms dcr1-so-4-2-0.NewYork.savvis.net [206.24.207.97]
9 52 ms 51 ms 47 ms agr4-so-0-0-0.NewYork.savvis.net [206.24.207.62]
10 202 ms 47 ms 48 ms acr1-loopback.NewYork.savvis.net [206.24.194.61]
11 54 ms 50 ms 54 ms p4-2-1-0.r04.nycmny01.us.bb.verio.net [129.250.9 .77]
12 57 ms 53 ms 53 ms p16-1-1-0.r20.nycmny01.us.bb.verio.net [129.250. 2.36]
13 116 ms 119 ms 120 ms p16-0-1-1.r20.mlpsca01.us.bb.verio.net [129.250. 5.112]
14 120 ms 119 ms 119 ms p64-0-0-0.r21.snjsca04.us.bb.verio.net [129.250. 5.3]
15 116 ms 119 ms 119 ms p16-7-0-0.r00.snjsca04.us.bb.verio.net [129.250. 5.136]
16 116 ms 119 ms 119 ms p4-2-0-0.a01.snfcca02.us.ra.verio.net [129.250.1 6.18]
17 120 ms 120 ms 119 ms ge-1-2.a02.snfcca02.us.da.verio.net [129.250.122 .252]
18 117 ms 120 ms 119 ms fa-3-21.a02.snfcca02.us.ce.verio.net [206.14.211 .66]
19 116 ms 119 ms 119 ms well.com [206.14.209.5]

o-ox-ox1.org
Ping statistics for 217.160.226.88:
Packets: Sent = 244, Received = 243, Lost = 1 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 33ms, Maximum = 165ms, Average = 45ms

Tracing route to o-ox-ox1.org [217.160.226.88]
over a maximum of 30 hops:

1 28 ms 29 ms 29 ms tlgw27.slnt.phub.net.cable.rogers.com [24.157.72 .1]
2 29 ms 29 ms 29 ms 10.1.65.1
3 24 ms 29 ms 30 ms gw01-vlan966.slnt.phub.net.cable.rogers.com [66. 185.93.213]
4 28 ms 29 ms 29 ms gw01.rchrd.phub.net.cable.rogers.com [66.185.82. 133]
5 30 ms 29 ms 29 ms gw01.flfrd.phub.net.cable.rogers.com [66.185.82. 129]
6 34 ms 29 ms 30 ms gw02.mtnk.phub.net.cable.rogers.com [66.185.82.1 25]
7 31 ms 35 ms 35 ms gw02.wlfdle.phub.net.cable.rogers.com [66.185.80 .153]
8 52 ms 47 ms 47 ms dcr1-so-3-1-0.NewYork.savvis.net [206.24.207.85]
9 50 ms 47 ms 45 ms dcr2-loopback.NewYork.savvis.net [206.24.194.100 ]
10 46 ms 48 ms 47 ms 144.232.9.117
11 49 ms 251 ms 47 ms sl-gw30-nyc-0-0.sprintlink.net [144.232.13.20]
12 46 ms 48 ms 48 ms sl-schlu4-1-0.sprintlink.net [144.232.228.6]
13 47 ms 47 ms 47 ms a0nycc2.gw-core-a.nyc.schlund.net [217.160.229.1 04]
14 52 ms 45 ms 49 ms perfora.net [217.160.226.88]

Trace complete.

Dreamhost sites:

ge1-gx.dreamhost.com
Ping statistics for 67.17.162.162:
Packets: Sent = 199, Received = 194, Lost = 5 (2% loss),
Approximate round trip times in milli-seconds:
Minimum = 84ms, Maximum = 315ms, Average = 102ms

fe1-mz.dreamhost.com
Ping statistics for 216.193.192.50:
Packets: Sent = 272, Received = 272, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 101ms, Maximum = 377ms, Average = 120ms

ge1-l3.dreamhost.com
Ping statistics for 64.156.46.110:
Packets: Sent = 226, Received = 226, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 90ms, Maximum = 330ms, Average = 110ms

tranquileye.com
Ping statistics for 66.33.209.189:
Packets: Sent = 323, Received = 306, Lost = 17 (5% loss),
Approximate round trip times in milli-seconds:
Minimum = 87ms, Maximum = 305ms, Average = 99ms


tranquileye.com
I recommend Dreamhost.


#13

[quote]It’s not as cut and dried as “I don’t have problems connecting to anywhere else, so the problem is on your side”

[/quote]

I am more than willing to believe that Rogers is the problem.


tranquileye.com
I recommend Dreamhost.


#14

Hrm… well one person says it seems better; another says it hasn’t changed. It is possible that I’m missing something here, but all the tests I’ve done indicate that the packet loss seems to be within Rogers’s network. I gotta assume (since we’re not, as far as I know, seeing this problem to / from anywhere else) that the problem isn’t on our side. I’ve done pretty much everything I can do on my side to check up on this.

I tried contacting them, but they don’t have any publicly available NOC info (I actually spent a fair amount of time / effort looking for this)… AND, even their regular customer support number won’t accept calls from outside of Canada. So if someone can get me a working number to a network engineer over there, I’ll be happy to talk to them; otherwise, just keep bugging support until they get someone to look into it.


#15

My FTP tests are still failing :frowning:

I encourage anyone who is having this problem to contact Rogers and keep on them until it is fixed. This may well be my “last straw” experience with them.


tranquileye.com
I recommend Dreamhost.


#16

I should point out that when I said it worked last night, I only made a test with some small files and then went to bed. Today, after seeing the comments here, I tried with files of various sizes and see that files under about 12K upload slowly but without timing out. Anything larger gets restarted numerous times as it times out (e.g. a 15K file took 11 minutes to upload because it kept timing out and restarting; presumably if I left a 600K file sitting there for a few hours it might eventually load assuming enough restarts and/or increasing the timeout time).

BTW I don’t know if it’s the changes you made yesterday or not, though, but ever since I’ve now been having trouble accessing Webmail – I keep getting:

ERROR
Error connecting to IMAP server: mail.motsa.com.
111 : Connection refused

Go to the login page

If I fight with it, I might get access to some of the folders but it takes a lot of retrying (and so far today I haven’t been able to access the Inbox at all).


Anyway, most of the other places I’ve been trying to (and been able to) upload to without trouble are message boards (e.g. at Yahoo) that I moderate so I did a traceroute and ping to their servers for you:

tracert health.groups.yahoo.com

Tracing route to groups1.vip.scd.yahoo.com [66.218.66.240]
over a maximum of 30 hops:

1 <10 ms <10 ms <10 ms 192.168.0.1
2 <10 ms 16 ms 31 ms 10.44.104.1
3 <10 ms 16 ms <10 ms gw03.slnt.phub.net.cable.rogers.com [66.185.90.145]
4 <10 ms 16 ms 15 ms gw01-vlan962.slnt.phub.net.cable.rogers.com [66.185.93.197]
5 <10 ms 31 ms 47 ms gw01.rchrd.phub.net.cable.rogers.com [66.185.82.133]
6 15 ms 32 ms 31 ms gw01.flfrd.phub.net.cable.rogers.com [66.185.82.129]
7 47 ms * 16 ms gw02.mtnk.phub.net.cable.rogers.com [66.185.82.125]
8 47 ms 31 ms 16 ms gw02.wlfdle.phub.net.cable.rogers.com [66.185.80.157]
9 31 ms 32 ms 47 ms igw01.ny8th.phub.net.cable.rogers.com [66.185.81.13]
10 * * * Request timed out.
11 125 ms 141 ms 125 ms vl144.pat1.pao.yahoo.com [216.115.96.50]
12 109 ms 141 ms 93 ms vl34.bas1-m.scd.yahoo.com [66.218.82.193]
13 110 ms 109 ms 110 ms UNKNOWN-66-218-82-238.yahoo.com [66.218.82.238]
14 109 ms 125 ms 141 ms groups1.vip.scd.yahoo.com [66.218.66.240]

Trace complete.

Ping statistics for 66.218.66.240:
Packets: Sent = 441, Received = 440, Lost = 1 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 93ms, Maximum = 172ms, Average = 106ms


Ping statistics for 67.17.162.162 (ge1-gx.dreamhost.com):
Packets: Sent = 250, Received = 222, Lost = 28 (11% loss),
Approximate round trip times in milli-seconds:
Minimum = 78ms, Maximum = 281ms, Average = 90ms

Ping statistics for 216.193.192.50 (fe1-mz.dreamhost.com):
Packets: Sent = 250, Received = 250, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 93ms, Maximum = 344ms, Average = 119ms

Ping statistics for 64.156.46.110 (ge1-l3.dreamhost.com):
Packets: Sent = 250, Received = 250, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 93ms, Maximum = 360ms, Average = 115ms

Like the others, I’ll try contacting Rogers (though I work for a US cable internet provider and, seeing how similar issues are dealt with there, I don’t hold out much hope that Rogers’ll actually do anything). Thanks for your help so far with this, Will.


#17

[I had a heck of a time posting to this thread – kept timing out trying to upload a new post; in the end, it was easier to edit a timed-out partial post than try to upload a new complete one]


#18

You could probably use a proxy to post on the forums. Although make sure to logout and all if you use one because you wouldn’t want anyone using your account.

willscorner.net


#19

Things are better today for my hosted domain…

Pinging tranquileye.com [66.33.209.189] with 32 bytes of data:
Ping statistics for 66.33.209.189:
Packets: Sent = 284, Received = 282, Lost = 2 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 89ms, Maximum = 429ms, Average = 111ms

…but worse for other Dreamhost servers:

Pinging ge1-gx.dreamhost.com [67.17.162.162] with 32 bytes of data:
Ping statistics for 67.17.162.162:
Packets: Sent = 246, Received = 219, Lost = 27 (10% loss),
Approximate round trip times in milli-seconds:
Minimum = 88ms, Maximum = 285ms, Average = 104ms


tranquileye.com
I recommend Dreamhost.


#20

Actually, in the time between the two ping tests, the connection degraded again :frowning:

Anyone had any luck with Rogers?


tranquileye.com
I recommend Dreamhost.