dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
17
share rss forum feed

Moostang

join:2009-03-24
Tyler, TX
reply to frivolous

Re: Routing Problems

If it's supposed to be under -20ms then i'm betting that the return path is coming back in somewhere other than California. On your game server that you run, run a trace-route back to your public IP and post it here (you can omit the last hop to keep your IP confidential). That should tell us where it comes back in at.


frivolous

join:2012-01-04
Arcata, CA

I will get one going the other way - in the mean time here is another one - worse than before

C:\Users\Mike>tracert 64.94.100.195

Tracing route to c-64-94-100-195.internap-la.nfoservers.com [64.94.100.195]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 7 ms 7 ms 7 ms 10.30.16.1
3 76 ms 83 ms 84 ms 173-219-251-220-link.sta.suddenlink.net [173.219
.251.220]
4 68 ms 64 ms 67 ms 173-219-251-154-link.sta.suddenlink.net [173.219
.251.154]
5 44 ms 45 ms 122 ms ae2-307.sjc12.ip4.tinet.net [216.221.157.165]
6 71 ms 29 ms 27 ms xe-3-3-0.lax20.ip4.tinet.net [89.149.184.149]
7 38 ms 39 ms 41 ms internap-gw.ip4.tinet.net [77.67.79.58]
8 37 ms 39 ms 39 ms border2.po2-20g-bbnet2.lax010.pnap.net [216.52.2
55.93]
9 114 ms 103 ms 101 ms nuclearfallout-53.border2.lax010.pnap.net [63.25
1.209.182]
10 118 ms 121 ms 119 ms c-64-94-100-195.internap-la.nfoservers.com [64.9
4.100.195]

Trace complete.


frivolous

join:2012-01-04
Arcata, CA
reply to Moostang

Looking forward to the fix tomorrow i nthe am, Moostang suggested running a trace route back to my ip - here it is

1 0.1 ms 0.1 ms 0.1 ms router.internap-la.nfoservers.com [64.94.101.254]
2 0.6 ms 0.3 ms 0.3 ms border2.te9-4.nuclearfallout-53.lax010.pnap.net [63.251.209.181]
3 0.5 ms 0.5 ms 0.4 ms core1.po2-20g-bbnet2.lax.pnap.net [216.52.255.65]
4 0.8 ms 0.8 ms 0.7 ms xe-0-3-0-1.r04.lsanca03.us.bb.gin.ntt.net [198.172.90.25]
5 0.5 ms 0.5 ms 0.5 ms xe-1.level3.lsanca03.us.bb.gin.ntt.net [129.250.9.202]
6 8.7 ms 12.9 ms 8.6 ms vlan80.csw3.LosAngeles1.Level3.net [4.69.144.190]
7 20.8 ms 9.0 ms 8.9 ms ae-83-83.ebr3.LosAngeles1.Level3.net [4.69.137.41]
8 8.9 ms 8.9 ms 8.9 ms ae-3-3.ebr1.SanJose1.Level3.net [4.69.132.9]
9 13.4 ms 8.8 ms 16.2 ms ae-71-71.csw2.SanJose1.Level3.net [4.69.153.6]
10 8.8 ms 8.9 ms 8.9 ms ae-2-70.edge2.SanJose1.Level3.net [4.69.152.79]
11 9.4 ms 9.4 ms 9.3 ms SUDDENLINK.edge2.SanJose1.Level3.net [4.79.238.38]
12 19.3 ms 19.4 ms 41.3 ms 173-219-251-155-link.sta.suddenlink.net [173.219.251.155]
13 17.8 ms 17.8 ms 17.8 ms 173-219-251-225-link.sta.suddenlink.net [173.219.251.225]
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.

**On a side note - A raise is in order for all the work you have done!



moldypickle

join:2009-01-04
Haughton, LA
kudos:2
Reviews:
·Suddenlink

But still, how is it you are able to fix probably 80% or better of the problems of this whole forum, yet we haven't had literally 1 person on here saying ANY previous attempt at contact w/ CS has worked.....

It's even more mind blowing when you inform us you're not even really in the CS chain,,,, but still fix the shit for us (or get it fixed).

Probably wouldn't be so bad if there were even 1 in 12 phone support people that had a clue wtf they were talking about :--
30/2 Suddenlink : Current
5/1 CMA : Old
15/2 TWC : Old