Web Hosting Talk : Web Hosting Main Forums : Dedicated Server : Fastservers.net

[rickyram56]

I bought a server from fastservers.net and I'm very happy. Just recenly I did a speed test and I noticed it was real crappy. I contacted them and they said they'll investiage the problem and they haven't fixed it yet.

Does anyone else have this problem with fastservers.net? (well its slowservers.net now )

[Joshua]

Could you PM me a speed test file?

[Samuel]

There could be a number of issues as to why you're seeing crappy speeds.

Post a trace route.

[rickyram56]

The download is real crap but the upload is alright but not as fast as it was...

Tracing route to server.ramgobin.net [147.202.33.218]
over a maximum of 30 hops:

1 7 ms 12 ms 6 ms 10.54.152.1
2 7 ms 7 ms 7 ms 66.185.90.209
3 7 ms 9 ms 6 ms gw01.hnsn.phub.net.cable.rogers.com [66.185.80.2
1]
4 5 ms 8 ms 6 ms gw01.mtpk.phub.net.cable.rogers.com [66.185.81.2
13]
5 24 ms 27 ms 27 ms dcr1-so-4-2-0.NewYork.savvis.net [206.24.207.97]

6 34 ms * 40 ms dcr2-loopback.Chicago.savvis.net [208.172.2.100]

7 61 ms 32 ms 33 ms bpr1-so-0-0-0.ChicagoEquinix.savvis.net [208.175
.10.238]
8 33 ms 33 ms 33 ms 208.174.226.98
9 36 ms 32 ms 32 ms border3.ge3-0-bbnet2.chg.pnap.net [64.94.32.71]

10 47 ms 43 ms 47 ms teamtech-1.border3.chg.pnap.net [64.94.34.146]
11 45 ms 45 ms 44 ms team-cf-l3-sw1.teamnet.net [192.104.109.50]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
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.

[Samuel]

Looks like that server is in Cedar Falls, the firewall is stopping pings =) Nothing wrong with that trace.

[Arsalan]

From this trace it seems that there are connectivity issues between the following nodes on savvis.net;

5 24 ms 27 ms 27 ms dcr1-so-4-2-0.NewYork.savvis.net [206.24.207.97]

6 34 ms * 40 ms dcr2-loopback.Chicago.savvis.net [208.172.2.100]

7 61 ms 32 ms 33 ms bpr1-so-0-0-0.ChicagoEquinix.savvis.net [208.175
.10.238]

Is this a new issue? or is it an ongoing issue?

Also, apparently this is one of their new servers which should be on a better netwok (internap?) ?

[rickyram56]

This is a new issue...

This was a speed test taken when the speeds where good...

2004-07-27 16:29:17 EST: 10891 / 7207
Your download speed : 11153400 bps, or 10891 kbps.
A 1361.4 KB/sec transfer rate.
Your upload speed : 7380073 bps, or 7207 kbps.

[isildur]

Hey everybody-

It would be better if we kept isolated issues handled on our online support desk, instead of in this public forum as at times it can stir up a plethora of unnecessary bad blood. I'll be the first to go public with a major anomaly on any of the FastServers network segments.... but this particular instance is quite unique and needs to be handled behind-the-scenes.

I realize feedback from the community is always helpful, but in this case the return route to your outside cable IP reveals a major problem inside of Rogers.com -->
(included below)

We'll be getting in touch about this via our support desk shortly.

Thanks for your patience! Hopefully we can get in touch with the required individuals, wherever they're hiding, to get this sorted out at the ISP in question.



............................
traceroute 66.185.90.209
traceroute to 66.185.90.209 (66.185.90.209), 30 hops max, 38 byte packets
1 147.202.32.1 (147.202.32.1) 1.513 ms 0.937 ms 0.882 ms
2 team-cf-core.teamnet.net (192.104.109.55) 0.658 ms 0.599 ms 0.588 ms
3 border3.p4-1.teamtech-1.chg.pnap.net (64.94.34.145) 11.484 ms 11.918 ms 11.485 ms
4 core3.ge3-0-bbnet2.chg.pnap.net (64.94.32.67) 11.655 ms 11.698 ms 11.825 ms
5 208.174.226.97 (208.174.226.97) 11.796 ms 11.683 ms 11.646 ms
6 dcr2-so-4-3-0.Chicago.savvis.net (208.175.10.237) 11.874 ms bpr2-ae0.ChicagoEquinix.savvis.net (208.174.226.86) 11.763 ms 11.835 ms
7 dcr1-loopback.Chicago.savvis.net (208.172.2.99) 12.179 ms dcr1-so-4-0-0.Chicago.savvis.net (208.175.10.97) 12.184 ms dcr1-loopback.Chicago.savvis.net (208.172.2.99) 12.067 ms
8 telus-rogers.Chicago.savvis.net (208.175.10.110) 22.897 ms telus-rogers.Chicago.savvis.net (208.175.10.86) 23.442 ms telus-rogers.Chicago.savvis.net (208.175.10.110) 22.785 ms
9 gw02.wlfdle.phub.net.cable.rogers.com (66.185.80.2) 37.857 ms 35.955 ms 38.089 ms
10 gw01.basp.phub.net.cable.rogers.com (66.185.81.214) 36.883 ms 35.807 ms 36.377 ms
11 * * *
12 gw03.hnsn.phub.net.cable.rogers.com (66.185.80.18) 36.199 ms * *
................................

[Arsalan]

.. and there you go, an official responce in about 60 min... thats fast support

[rickyram56]

FastServers is fixing the problem