help server is super laggy 150

[greens]

up in smoke usually ping under 20 holdin 150 what up


C:\>tr 67.168.82.40

NFO win32 trace tool v1.01, copyright (c)2004 Nuclearfallout Enterprises, Inc.

Tracing route to c-67-168-82-40.client.comcast.net [67.168.82.40]
with up to 30 hops:

1 1.0 ms 0.4 ms 0.4 ms border5.fe6-29.nuclearfallout-4.sef.pnap.net [66.150.165.187]
2 0.3 ms 0.3 ms 0.3 ms core3.ge2-0-bbnet1.sef.pnap.net [63.251.160.3]
3 2.1 ms 0.5 ms 0.5 ms POS1-3.GW8.SEA1.ALTER.NET [157.130.191.29]
4 1.2 ms 0.7 ms 0.6 ms 109.ATM2-0.XR2.SEA1.ALTER.NET [152.63.105.222]
5 0.9 ms 2.0 ms 1.0 ms 0.so-0-0-0.XL2.SEA1.ALTER.NET [152.63.106.233]
6 0.9 ms 0.7 ms 1.6 ms POS7-0.BR1.SEA1.ALTER.NET [152.63.105.21]
7 147.7 ms 152.6 ms 156.4 ms 204.255.174.170 [204.255.174.170]
8 155.1 ms 152.5 ms 149.0 ms 12.123.44.178 [12.123.44.178]
9 151.0 ms 153.4 ms 151.7 ms gar3-p360.st6wa.ip.att.net [12.123.44.145]
10 153.1 ms 152.1 ms 153.6 ms 12.119.199.22 [12.119.199.22]
11 155.9 ms 155.7 ms 155.7 ms 12.244.64.101 [12.244.64.101]
12 * * * Request timed out.
13 167.1 ms 159.4 ms 162.7 ms c-67-168-82-40.client.comcast.net [67.168.82.40]

Trace complete.

[bOoya]

looks to me like either alter or at&t are having a router problem, shouldnt worry about it too much, its likely that they are working on it as we speak.

[Edge100x]

Definitely you should email us problems like this, that's the fastest way for us to take care of them. We will forward them onto InterNAP, which can reconfigure the routing.

[MP5]

I have been having same problem at weed|reefer dome. did ip trace with McAfee and got same as trace above (obviously ping slightly different). I even traced http://www.nucleafallout.net and had same result, it hangs at a server right before the one i want and looses my packets. Ingame i have no packet loss (net_graph 3) but constant 100 choke.

please help edge!!

couldnt find e-mail for yall so here is my ip: 24.21.166.190 (comcast so it may change)

and tracert

Tracing route to 66.150.165.168 over a maximum of 30 hops

1 15 ms 51 ms 7 ms 10.142.192.1
2 9 ms 7 ms 10 ms 12.244.84.65
3 8 ms 10 ms 10 ms 12.244.64.129
4 9 ms 11 ms 12 ms 12.244.64.150
5 14 ms 15 ms 13 ms 12.118.177.45
6 12 ms 14 ms 13 ms gbr1-p80.st6wa.ip.att.net [12.123.203.182]
7 14 ms 13 ms 15 ms gar2-p360.st6wa.ip.att.net [12.123.44.113]
8 * * * Request timed out.
9 133 ms 139 ms 134 ms border5.ge2-1-bbnet2.sef.pnap.net [63.251.160.74
]
10 132 ms 132 ms 134 ms 66.150.165.168

Trace complete.

Done a trace like 10 times now have some saved from McAfee also. Same outcome tho.

[Edge100x]

Our email is rentals@nuclearfallout.net.

[MP5]

tried to connect to weed.nuclearfallout.net all day thursday the 28th and all i got was a "reliable channel overflow" message from cs.

any help?

Also, according to McAfee, almost all of the servers that are in my ip trace are in the same building. It gives GPS location as: 47.61 N, 122.333 W. & of the 11 nodes in the hop are at this location.
I hope im not being naive beliving these corodinates.

[Edge100x]

Better to email us about server-specific problems.

It makes sense that most of the routers would be in the same building, yes.

[MP5]

Today is the first day, no choke no lag, more fun.
Crossing my fingers it isn't a fluke.

NFo Rocks!

[aBstracT]

Hehe

[Edge100x]

The UUnet peering issues in Seattle are very easy to route around.