Use this forum if you have a relatively general question or comment about a game, Ventrilo, TeamSpeak, or Murmur/Mumble server with us. If you have a server-specific question that might not help out the community, please directly contact us through your control panel instead.
Ok here is the problem:
I log on one evening and my ping is great 45-85 right but I got off and went to get on an hour later and my ping was 245+ and no matter what I tried my ping would not go down I tried for 5 hours to get it to go down I checked my comp over so many times thinking maybe something was screwy. So I gave up and went to bed got up in the am and got on to test and what you know my ping was like 30-65 I don't get it. I thought it might just be alot of people online right well why was it low an hour earlier and then all screwey later
My guess is a router or server possibly went bad along your route to the server, but then fixed by morning. The next time you have this happen to you, please go to dos command prompt, and type tracert (your server IP without port here)
then copy and paste into this topic and we can help you out.
Ok now my server is timming out and my ping was go for like 2 sec and then bamm it was not and kick me off saying conection timmed out. I ran the Trace Route here is the results.
C:\>tracert shaggy.nuclearfallout.net
Tracing route to shaggy.nuclearfallout.net [209.189.55.250]
over a maximum of 30 hops:
1 10 ms 10 ms 20 ms ip68-110-12-1.tc.ph.cox.net [68.110.12.1]
2 10 ms 10 ms 10 ms ip68-0-128-145.tc.ph.cox.net [68.0.128.145]
3 10 ms 10 ms 10 ms ip68-0-128-137.tc.ph.cox.net [68.0.128.137]
4 20 ms 30 ms 20 ms chnddsrc02-pos0701.rd.ph.cox.net [68.2.15.253]
5 40 ms 20 ms 40 ms chndbbrc02-pos0101.rd.ph.cox.net [68.1.0.168]
6 141 ms 120 ms * chndbbrc01-pos0100.rd.ph.cox.net [68.1.0.162]
7 40 ms 31 ms 40 ms fed1bbrc02-pos0102.rd.sd.cox.net [68.1.0.167]
8 40 ms 30 ms 30 ms fed1bbrc01-pos0100.rd.sd.cox.net [68.1.0.202]
9 40 ms 60 ms 60 ms fed1bbrc01-pos0200.rd.sd.cox.net [68.1.0.193]
10 60 ms 80 ms 50 ms paix-0.plalca01.us.bb.verio.net [198.32.175.14]
11 51 ms 40 ms 50 ms p16-0-1-0.r20.plalca01.us.bb.verio.net [129.250.
3.78]
12 50 ms 60 ms 110 ms p64-0-0-0.r20.snjsca04.us.bb.verio.net [129.250.
2.71]
13 180 ms * 90 ms xe-0-2-0.r21.snjsca04.us.bb.verio.net [129.250.2
.73]
14 121 ms 90 ms 110 ms p16-1-1-1.r21.lsanca01.us.bb.verio.net [129.250.
2.186]
15 140 ms 121 ms 70 ms ge-1-2-0.a06.lsanca01.us.ra.verio.net [129.250.2
9.133]
16 50 ms 60 ms 60 ms p4-0-3-0.a00.irvnca18.us.ra.verio.net [129.250.4
6.96]
17 50 ms 60 ms 80 ms ge-1-1.a01.lsanca18.us.ra.verio.net [129.250.46.
126]
18 60 ms 70 ms 60 ms ge-1-1.a00.lsanca16.us.ra.verio.net [129.250.46.
106]
19 50 ms 50 ms 50 ms ge-3-3.a00.lsanca16.us.ce.verio.net [198.173.172
.158]
20 70 ms 70 ms 70 ms 209.189.55.250
Trace complete.
I also tried reconecting and it just timed out and did not connect any help would greatly be appriciated.
Ok, we discussed this in email already, but unfortunately the reverse trace shows that the problem may exist within the Cox network.
[root@irc root]# traceroute 68.110.13.53
traceroute to 68.110.13.53 (68.110.13.53), 30 hops max, 38 byte packets
1 ge-3-3-0.a02.lsanca02.us.ce.verio.net (209.189.55.225) 0.441 ms 0.260 ms 0.215 ms
2 ge-3-3.a00.lsanca16.us.ra.verio.net (198.173.172.157) 0.282 ms 0.347 ms 0.282 ms
3 ge-4-1.a01.lsanca18.us.ra.verio.net (129.250.46.105) 0.657 ms 0.361 ms 0.331 ms
4 ge-0-2-0.a00.lsanca18.us.ra.verio.net (129.250.46.125) 0.445 ms 0.433 ms 0.398 ms
5 p4-6-0-0.a06.lsanca01.us.ra.verio.net (129.250.46.97) 0.602 ms p4-2-0-0.a05.lsanca01.us.ra.verio.net (129.250.46.113) 0.600 ms 0.571 ms
6 xe-1-0-0-4.r21.lsanca01.us.bb.verio.net (129.250.29.136) 0.552 ms 0.555 ms 0.497 ms
7 p16-1-1-0.r21.snjsca04.us.bb.verio.net (129.250.2.187) 8.681 ms 8.546 ms 8.495 ms
8 xe-0-2-0.r20.snjsca04.us.bb.verio.net (129.250.2.72) 8.607 ms 8.606 ms 8.836 ms
9 p64-0-0-0.r20.plalca01.us.bb.verio.net (129.250.2.70) 9.131 ms 9.144 ms 9.192 ms
10 p16-0-0-0.r00.plalca01.us.bb.verio.net (129.250.3.79) 9.043 ms 9.114 ms 9.033 ms
11 PALTBBRJ01GEX0201A001.R2.PT.COX.net (198.32.176.144) 9.565 ms 9.281 ms 10.351 ms
12 paltbbrj01-pos000000.r2.pt.cox.net (68.1.0.192) 21.012 ms 21.034 ms 21.143 ms
13 fed1bbrc02-pos0100.rd.sd.cox.net (68.1.0.203) 21.052 ms 21.239 ms 21.073 ms
14 chndbbrc01-pos0102.rd.ph.cox.net (68.1.0.166) 29.262 ms 29.284 ms 29.270 ms
15 chnddsrc01-pos0901.rd.ph.cox.net (68.1.0.165) 29.332 ms 29.263 ms 29.292 ms
16 68.2.15.250 (68.2.15.250) 33.218 ms 33.155 ms 32.896 ms
17 ip68-0-128-142.tc.ph.cox.net (68.0.128.142) 195.202 ms 185.232 ms 202.378 ms
18 ip68-0-128-146.tc.ph.cox.net (68.0.128.146) 240.958 ms 275.838 ms 268.866 ms
19 ip68-110-13-53.tc.ph.cox.net (68.110.13.53) 277.590 ms 312.495 ms 263.655 ms
The best thing to do would be to contact your ISP.
