Servers bouncing up and down

[BradSTL]

Can we get some word about the fact that the servers keep kicking everybody out roughly every 3 to 5 minutes tonight?

[imper1um]

Same. wtf is going on?

[-FN-]

It has nothing to do with the servers ironically. Level3 is having either severe hardware issues or DOS attacks. Their Chicago, Dallas, and Denver nodes are all suffering 50-60% packet loss. Do a Trace Route to the Game Server's IP (tracert 62.140.29.52) and see what you get...

[imper1um]

They have a node in Orlando too, looks like. It heads off to New York before it hits London then Hamburg. Timed out slightly between New York and London, but that's a big hop.

[System]

is like the whole game down now?

[whifix]

I'm tempted to use a pay for access remote proxy or vpn service like FindNot (http://www.findnot.com/index.html) to route around level 3.

[Mr Friendly]

ah good, its not just me =p :lol:

[Dr Strange]

*cries*

must resist....

(do you know how hard it is to not be able to reply to something, cause everything you say can be considered as trolling)

[MeWhiteWolf]

http://www.whitewolf.com.au/wtfnc.JPG
now i've seen it all

[Dr Strange]

Tracing route to 62.140.29.52 over a maximum of 30 hops

1 6 ms 5 ms 5 ms 10.64.128.1
2 6 ms 6 ms 5 ms gig2-1.chrlncalb-rtr1.carolina.rr.com
3 7 ms 7 ms 7 ms srp12-0.chrlncsa-rtr3.carolina.rr.com
4 6 ms 8 ms 24 ms srp2-0.chrlncsa-rtr2.carolina.rr.com
5 6 ms 19 ms 7 ms son0-0-3.chrlncsa-rtr6.carolina.rr.com
6 16 ms 8 ms 7 ms 66.185.138.69
7 7 ms 7 ms 7 ms bb2-cha-P0-2.atdn.net
8 12 ms 11 ms 12 ms bb2-atm-P6-0.atdn.net
9 12 ms 11 ms 11 ms pop2-atm-P1-0.atdn.net
10 24 ms 21 ms 21 ms so-1-3-0.gar2.Atlanta1.Level3.net
11 21 ms 21 ms 21 ms so-3-3-0.bbr1.Atlanta1.Level3.net
12 27 ms 38 ms 27 ms ae-0-0.bbr1.NewYork1.Level3.net
13 * 97 ms 91 ms as-0-0.bbr2.London1.Level3.net
14 121 ms 108 ms 112 ms so-1-0-0.mp2.Hamburg1.Level3.net
15 109 ms 108 ms 107 ms ge-5-2.hsa2.Hamburg1.Level3.net
16 110 ms 111 ms 107 ms ge-2-0.edge1.ham1.de.inetbone.net

17 107 ms 109 ms 109 ms 212.162.3.84
18 107 ms 107 ms 116 ms 62.140.29.52


god i hate these overseas pingtimes, ingame im aways pinging 130-165. 100ish I can live with but a 170 ping is a bit high for a 5mb downstream cable line

[imper1um]

It seems that the New York node has blown up. Washington node has been turned online to fix the problem.

[El Jimben]

That sounds bad Strange considering I ping 60-80 on DSL o_O Though I live in U.K. so I guess being closer to Germany has something to do with it (?)

[Dr Strange]

That sounds bad Strange considering I ping 60-80 on DSL o_O Though I live in U.K. so I guess being closer to Germany has something to do with it (?)

Well I'm American. East coast thank god, if I was on the West coast I'd just be unable to play (add another 100ms to the ping time and you'll have a West coast cable/dsl speed to the NC server)

It's stable and everything, fine for playing. Just the ping will spike occasionally and player interpolation gets kinda funky (go to El Farid with 8 people, sooner or later someones gonna be floating in the ceiling)

[CMaster]

That sounds bad Strange considering I ping 60-80 on DSL o_O Though I live in U.K. so I guess being closer to Germany has something to do with it (?)
"Ping" is a response time, not a measue of bandwidth. To get a ping time, you com[puter sends "ping" across the network. The server upon recieveing this sends "pong" back. The ping value are given is the time for this to take place in milliseconds. HEnce the distance is a major issue. ((I'm not sure I got the exact mechanics right there, but the concept is right)

[Dr Strange]

"Ping" is a response time, not a measue of bandwidth. To get a ping time, you com[puter sends "ping" across the network. The server upon recieveing this sends "pong" back. The ping value are given is the time for this to take place in milliseconds. HEnce the distance is a major issue. ((I'm not sure I got the exact mechanics right there, but the concept is right)

That's right.

[RDevz]

"Ping" is a response time, not a measue of bandwidth. To get a ping time, you com[puter sends "ping" across the network. The server upon recieveing this sends "pong" back. The ping value are given is the time for this to take place in milliseconds. HEnce the distance is a major issue. ((I'm not sure I got the exact mechanics right there, but the concept is right)

Also, remember that signals take time to travel. It takes light 42ms to travel 8000 miles in vacuo, and light travels significantly slower in glass fiberoptic cables than it does in a vacuum. If you're on the west coast of the US, it's going to be physically impossible to get a ping under 60ms.