Someone can't read a traceroute!

Hops 7 and 8 seem to always be around 6-8ms, the NINTH hop is your problem.

Look at hop 8 vs 9. First result is 8ms then 28ms, second is 7ms then 33ms, third is 6ms then 33ms, fourth is 7ms then 50ms.

So, you're getting roughly 20-40ms+ on that hop.

Now look at hops 9-11.

First result is 28-28-31, second is 33-33-39, third is 33-33-40, fourth is 50-50-55.

Basically, your 9th hop (which seems to be *fra21.ip4.tinet.net) is your problem, not Quake Lives. If it was Quake Lives problem, you would see ping spikes on the lines that return from *quakelive-hosted-by.i3d.net.

i know and i dont care, i ping just fine on other games / tests. same as purri, everything else works but QL route is shit as fuck

13 38 ms 39 ms 39 ms hos-bb2.juniper2.fs.hetzner.de [213.239.240.147]
14 43 ms 41 ms 41 ms hos-tr3.ex3k13.rz12.hetzner.de [213.239.228.206]
15 38 ms 38 ms 38 ms static.207.84.63.178.clients.your-server.de [178.63.84.207]
16 38 ms 39 ms 38 ms static.167.223.4.46.clients.your-server.de [46.4.223.167]

12 36 ms 37 ms 36 ms hetzner-gw.lambdanet.net [213.239.247.205]
13 38 ms 38 ms 40 ms hos-bb2.juniper2.fs.hetzner.de [213.239.240.147]
14 39 ms 39 ms 39 ms hos-tr4.ex3k12.rz13.hetzner.de [213.239.224.109]
15 39 ms 40 ms 38 ms mail.imperiale-garde.de [88.198.50.85]

8 22 ms 20 ms 20 ms HAM-4-pos010.de.lambdanet.net [81.209.190.17]
9 20 ms 20 ms 56 ms HAM-1-eth001.de.lambdanet.net [217.71.96.25]
10 28 ms 24 ms 24 ms BER-1-eth010.de.lambdanet.net [217.71.96.93]
11 24 ms 24 ms 24 ms 217.71.104.126
12 32 ms 25 ms 26 ms blog.exhale.de [212.87.33.43]

So what's the point of this post?

whining

Now, with all that money we're paying for QL, id software can bring ten gigabit optics from QL servers to everyone's home, easily. But those bastards will NEVER do ANYTHING for community :(((((((((

dude im sitting on a fibre that can reach 11.5mb/s down or upload, everything else pings fine except QL and im not alone with the problem so

It's like saying "why it's so hard to get to the top of mount Everest if there is perfectly fine highway right outside my town". The traceroute from your post has 11 hops. Your fibre only gets you to hop 2 and not any further. To get to hop 3 from hop 2 your packets have to come off from your fibre and traverse through some other link. Then between hop 3 and hop 4 there's yet another completely different link, etc. Some of those links may actually themselves be multi-hop networks that are logically seen as a single layer 2 link.
The in-game ping is a sum of two things: the actual ping from you to the server, and the additional time that it takes for your PC to generate a packet with current state, QL server to receive and process all those packets, and generate a reply and then your PC to understand that reply. QuakeLive can affect only the second part of the ping, it cannot has any effect on the actual time it takes packets to reach from your PC to QL server and back.
And these traceroute results you've posted actually confirm that it's a problem somewhere on the path from you to QL server, it has nothing to do with QuakeLive itself. Traceroute is not QuakeLive, it's not written by id software, it's an internal OS utility, and if it shows increased ping, then id software has nothing to do with it. Something changed on the path between you and QL server (maybe increased utilization on an interface somewhere, maybe ISP that hosts QL server can't pay for faster channel anymore, a lot of things may happen), and it resulted in a higher ping. Of course you're not alone with the problem, because the problem is somewhere on a network segment very near QL server, so probably, everyone that plays on that server, goes through that segment and has the same problem. But what has id software or QuakeLive to do with the ISP's or data center's network? You're just another stupid whiner that always blames id for anything, without even looking into the problem.

im aware of the basics of networking, i advice you to read the whole thread. id going for stupid centralized server solution and not offering any choices for scandinavian players IS their fault, and directly affects the playability of QL, even if its not directly the QL servers fault.

-frs

and btw your assumption that i always blame id for everything is completely wrong, 99% of the time im on id's side and the only things i've whined about are the ever-increasing FPS drops (might be slightly fixed this patch) and now the ever-worsening ping.

cant blame ql for this, sorry :(.
they definetely picked a pretty bad game provider for .de tho .

yeah i know its not directly QL's fault, but it is id's fault for not having a single server in northern europe (denmark for example, good middle ground for official games) AND only relying on 1 server location for germany. im just pissed as hell >:|

Word, this was the shit in qw, q2, q3 and not ql! :D

Though I don't complain, pinging just fine to germany and netherlands.
But can imagine finland/norway/sweden having a long way to their servers since swe servers are gone.

this is totally right .

Central distribution model ftw!

How can you say it's not QL's fault? There are literary hundreds of people willing to set up QL servers all around the globe, which players would benefit from greatly, and ID is the one making it impossible for them to do it.

we setup a discussion between one of the major ISP's in finland and ttimo from id (he was still working on ql back then) the ISP was willing to DONATE the hardware and bandwidth for free, but they didnt want to give id root access on the server or the server hardware wasnt 100% dedicated to QL, cant remember which. well it turned to shit and never happened cause of that :D

The immenseness of absurdity that surrounds Quake Live is simply stunning.

i keep getting this 150ms ping spikes lasting for 5minutes or so. even browser restart seems to help from time to time. its been happening for last few days. i never had any problems with ping in QL whatsoever. i hope this issue is just temporary.

welcome to my ping for 4 years haha :D gl fixing it man, i know how it feels in quake live!

50 is still somewhat playable but when it goes past 55 and jumps to 60-70 it just gets shit :/

yea, the spikes are what screw the experience for me, but in my case it's actually my internet rather than the ql servers. That said, quake live in it's current state doesn't really aid "our" experience with pings - q3 still feels good with the setup they have in cpma.

In some ways, ID could tip toe around this issue by just giving us bigger hitboxes.

yep welcome to my world aswell, getting whined at 24/7 for warping when theres nothing i can do about it

lol so I guess u have exceptional dodging :P

exactly, these noobs need to realise im just a good dodger i dont warp! ;)

gerppa 2.0

another top dodger

lol, u got no idea, when i started to play quake i had this student inet and many ppl wouldnt even play with me cause i warped, get pretty much banned from pickup etc :D

and also i have never seen u warp, if u move wasd and start teleporting into places then u can call that warp like i had, make rail jump in dm6 just to warp to shards or drop in mid air :D and when watch demo ur demo freeze every 3 sec cause of the warp :D

exactly, you say i dont warp but then i play a pickup and get raged at

/net_restart

what \net_restart has to do with routing?

idk probably nothing but it worked for me once or twice so....

The solution is warsow ;)
Ther you can host your own server and play with friends ;)

then kill yourself ;)

try to play from 60ping to 90 stable on all eu and then come back with ur whine kid

Oh noes, ping 50

The world is a big place deal with it , for every server you ping well to1000 others will have ping 50+.

I'll admit it can be frustrating to not even have the option to play more locally but still, 50 msec for a thousand miles, hard to really complain too much about that.