Server connections

M

m0dicon

Registered User
Joined
Nov 16, 2008
Messages
35
Maybe it's just me, but I've been losing connection to your Suez server a lot lately and have a horrible ping of 180 to 200. Have waited a few days for it to drop back to usual 30-40ms, but it has not.

Weird thing is that the ping to the other server's addresses, All Titans for example, is ok.

Could the box need a reset or a tech request initiated on it?


results of pinging suez server:

Pinging 64.34.213.40 with 32 bytes of data:
Reply from 64.34.213.40: bytes=32 time=151ms TTL=115
Reply from 64.34.213.40: bytes=32 time=142ms TTL=115
Reply from 64.34.213.40: bytes=32 time=159ms TTL=115
Reply from 64.34.213.40: bytes=32 time=154ms TTL=115

Ping statistics for 64.34.213.40:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 142ms, Maximum = 159ms, Average = 151ms

results of pinging all titans server:

Pinging 64.34.213.41 with 32 bytes of data:
Reply from 64.34.213.41: bytes=32 time=40ms TTL=115
Reply from 64.34.213.41: bytes=32 time=44ms TTL=115
Reply from 64.34.213.41: bytes=32 time=38ms TTL=115
Reply from 64.34.213.41: bytes=32 time=43ms TTL=115

Ping statistics for 64.34.213.41:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 38ms, Maximum = 44ms, Average = 41ms
 
The server gets hit by DDOS attacks a fair amount. Its not likely just you, if you ping shoots through the roof, so does everyone elses.

And resetting the server continuously is time consuming.
 
Vengeance0058 said:
The server gets hit by DDOS attacks a fair amount. Its not likely just you, if you ping shoots through the roof, so does everyone elses.

And resetting the server continuously is time consuming.
Click to expand...

Like I said, this is not a one time or one day increase. I don't cry ping.
 
i'm not personally having any issues. I know for a while on the east coast there has been some routing issues. In any case i put in a ticket with the tracert and i'll see what they have to say.
 
Modicon I went through Hell with my ISP to get a router fixed in Cleveland. I was out for 5 - 6 weeks. It turned out to be the routers routing and not the actual router. Apparently my return traffic was going elsewhere. I highly recommend calling and getting the process started at your ISP.

Some of the standard tools you can use are pathping, ping, and tracert (on windows anyways). Also I did a little research and found some reverse trace route sites. Mainly Colleges and such. Google that and that will help pinpoint the problem area.

The thing that pissed me off about my problem was that I was the only one that called initially, so they (RR) pretty much ignored it until others chimed in. It is important to get a call in to them and hopefully a neighbor or someone else that is having issues. They probably will not see a 115ms pings being a problem at first. Initially when I sent them the tracert for the servers they tried to tell me it was not their issue at all, because it showed a Washington hop as the problem. So in order to prove what the problem was I had to do tests on their network only and then do a few reverses to determine what router was having a fit.

Personally I think someone hacked the router and was redirecting traffic to ??? for whatever reason.


EDIT: also look up a program called ping plotter. Its not free, but you can use it for thirty days free. Found it to be easy to use and handy for getting a data-graph for ping data.
 
Try a trace route to the server and find out if you're getting a bad hop somewhere.
 
OK ran a few tracerts. Looks like more than one problem here?


Tracing route to 64.34.213.40 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms xxxxxxxxxxxx
2 19 ms 29 ms 9 ms xxxxxxxxxx
3 9 ms 11 ms 8 ms te-8-4-ur01.xxxxxx.savannah.comcast.net [xxxxxxxxxx]
4 8 ms 21 ms 11 ms te-8-4-ar01.savannah.ga.savannah.comcast.net [68.86.250.17]
5 15 ms 30 ms 26 ms te-4-4-ar01.southside.fl.jacksvil.comcast.net [68.86.168.201]
6 28 ms 23 ms 21 ms te-0-2-0-4-cr01.miami.fl.ibone.comcast.net [68.86.93.157]
7 22 ms 23 ms 34 ms xe-10-1-0.edge2.Miami1.Level3.net [64.156.8.9]
8 43 ms 22 ms 31 ms ae-32-52.ebr2.Miami1.Level3.net [4.69.138.126]
9 171 ms 159 ms 182 ms ae-2-2.ebr2.Atlanta2.Level3.net [4.69.140.142]
10 160 ms 164 ms 168 ms ae-72-72.csw2.Atlanta2.Level3.net [4.69.148.250]
11 31 ms 31 ms 55 ms ae-71-71.ebr1.Atlanta2.Level3.net [4.69.148.245]
12 170 ms 177 ms 169 ms ae-6-6.ebr1.Washington12.Level3.net [4.69.148.106]
13 162 ms 163 ms 163 ms ae-8-8.ebr1.Washington1.Level3.net [4.69.143.217]
14 185 ms 179 ms 176 ms ae-91-91.csw4.Washington1.Level3.net [4.69.134.142]
15 184 ms 177 ms 176 ms 4.69.149.203
16 45 ms 42 ms 40 ms PEER-1-NETW.edge2.Washington3.Level3.net [4.71.234.6]
17 * * * Request timed out.
18 * * * Request timed out.
19 172 ms 192 ms 175 ms 64.34.213.40
 
Naw, its just the first hop in Atlanta that is screwing you over. Call your ISP and tell them you did a tracert and are having issues there. Most likely theyll say they cant do anything about it, but its worth a shot. Otherwise, its probably a problem that will fix itself in a week to a month

"1 <1 ms <1 ms <1 ms xxxxxxxxxxxx
2 19 ms 29 ms 9 ms xxxxxxxxxx
3 9 ms 11 ms 8 ms te-8-4-ur01.xxxxxx.savannah.comcast.net [xxxxxxxxxx]
4 8 ms 21 ms 11 ms te-8-4-ar01.savannah.ga.savannah.comcast.net [68.86.250.17]
5 15 ms 30 ms 26 ms te-4-4-ar01.southside.fl.jacksvil.comcast.net [68.86.168.201]
6 28 ms 23 ms 21 ms te-0-2-0-4-cr01.miami.fl.ibone.comcast.net [68.86.93.157]
7 22 ms 23 ms 34 ms xe-10-1-0.edge2.Miami1.Level3.net [64.156.8.9]
8 43 ms 22 ms 31 ms ae-32-52.ebr2.Miami1.Level3.net [4.69.138.126]
9 171 ms 159 ms 182 ms ae-2-2.ebr2.Atlanta2.Level3.net [4.69.140.142
10 160 ms 164 ms 168 ms ae-72-72.csw2.Atlanta2.Level3.net [4.69.148.250]
11 31 ms 31 ms 55 ms ae-71-71.ebr1.Atlanta2.Level3.net [4.69.148.245]
12 170 ms 177 ms 169 ms ae-6-6.ebr1.Washington12.Level3.net [4.69.148.106]
13 162 ms 163 ms 163 ms ae-8-8.ebr1.Washington1.Level3.net [4.69.143.217]
14 185 ms 179 ms 176 ms ae-91-91.csw4.Washington1.Level3.net [4.69.134.142]
15 184 ms 177 ms 176 ms 4.69.149.203
16 45 ms 42 ms 40 ms PEER-1-NETW.edge2.Washington3.Level3.net [4.71.234.6]
17 * * * Request timed out.
18 * * * Request timed out.
19 172 ms 192 ms 175 ms 64.34.213.40"
 
Not necessarily Bot. When I was having my issues it showed Washington Level 3 as the issue, and after talking to them on the phone and doing some tests they helped me narrow it down to RR's network.

Modicon do some tests entirely on Comcasts network to see if you have issues there. Try a tracert to a Comcast website first to see if all the hops are entirely on their network. If it is and you have issues then that will help narrow it down and they will now believe you have an issue they can do something about.

It could also be that hop in Atlanta that is having an issue, but I don't think so, because I have no issues with that router or server. Me not having issues pinging that hop does not mean much, since we get their by different routes. My bet is on a backbone router on Comcasts network that is redirecting your return traffic to La La land. If that device is not sending and receiving correctly then it will skew tracert readings and give false information.

Basically what I'm trying to say is that a tracert does not definitively prove that the hop your seeing as the issue is the actual issue. The real problem with it not being on their network (comcasts) they will say its not their problem. Do some tracert's that stay entirely on their network. Meaning all the hops will say something or other about comcast as you can see from your results above.

On a side note you do know Comcast and Level3 are in a little bit of a battle right now. I doubt very much that that is the issue, but be aware that they are in a heated debate over lots of money presently (Google netflix + level3).

Other things that Comcasts guilty of and could be related;
Throttling
Prime time restrictions (they control traffic according to peak times and data priority)
Bandwidth quotas. (if your over some pre-determined limit they limit you not necessarily with your knowledge)
 
You must log in or register to reply here.
Back
Top