Devs, you owe me 100 M.
The reaction time is very bad I am constantly losing fighter.
Last days playing in the evening is not possible. Did your hamster die in the server room?
I have the same problem every Evening for 1 week, from about 22000 players on the server. And Yes my Provider is âDeutsche Telekomâ.
I noticed since approximately one or two weeks that EVE got very laggy. No reason why as the ping time is good and I havenât changed anything. My provider is 1&1 and I never experienced such lag before.
o7!
Same problems here, though I have up to 30% package loss when pinging Tranquility in the evenings (EU time). My ISP is Telekom as well. The issues have started about 10 days to two weeks ago and keep getting worse.
I suspect routing/peering issues on the side of the provider, but canât know for sure.
Having the same issue as well and also the Deutsche Telekom as provider. Looking on a trace route it appears that the last hop within the GTT network is dropping the packages.
I guess there are many German player affected by this issue.
mh well at last me not alone⊠since days Evil lags evrywhere evrywhen. ping is 8-10 for anything else then eve and same pc as bevore just horrible lags. mh and telekom too as i just saw.
Same here. Login take up to 2 Minutes, new ingame windows like character screen/Assets etc. takes also 10-60 sec to open, hardcore lags when Iâm in space.
My ping is always between 16 up to 20ms and full FPS - no FPS drops.
My provider is also Deutsche Telekom
Seems like thats the problemâŠ
Hello, me and my buddy have same issues, bad ping, massive lags, packet loss if pathping etc etc. Mostl y happens in the evenings. Our ISP is DTAG was well.
hey guys. same problem here, my provider is also Telekom. I Opend a ticket and a gm send me a tool to give him informations about the ping and tracer problem. So i think you all need to open a ticket and send the data to ccp, so if they collect enough i hope they will do something.
1&1 Hier Folgende Traceroute zeigt Probleme fĂŒr mich:
6 20 ms 21 ms 11 ms 52.93.39.118
7 34 ms 11 ms 18 ms 52.93.49.127
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 10 ms 10 ms 10 ms server-99-84-151-128.txl52.r.cloudfront.net [99.84.151.128]
Zweite Woche und immer Hop 7 bis 12 listed Time Out.
Same here(nothern Italy, )
Massive Lags
In J-Space definetly not possible to play with d-scan times about 20 sec.
Routenverfolgung zu d1hoqe10mv32pv.cloudfront.net [99.84.151.41]
Âber maximal 30 Hops:
1 1 ms 1 ms 1 ms 192.168.1.1
2 7 ms 4 ms 3 ms 192.168.2.1
3 * * * ZeitÂberschreitung der Anforderung.
4 66 ms 66 ms 65 ms host237-158-static.36-88-b.business.telecomitalia.it [88.36.158.237]
5 66 ms 69 ms 68 ms host21-193-static.20-80-b.business.telecomitalia.it [80.20.193.21]
6 74 ms 90 ms 72 ms 172.19.184.62
7 75 ms 75 ms 74 ms 172.19.177.26
8 75 ms 75 ms 74 ms etrunk49.milano1.mil.seabone.net [195.22.205.98]
9 74 ms 75 ms 75 ms ae11.milano58.mil.seabone.net [195.22.208.79]
10 74 ms 72 ms 218 ms ae-5.edge1.Milan1.Level3.net [4.68.73.37]
11 320 ms 274 ms 129 ms ae-2-3602.edge3.Berlin1.Level3.net [4.69.159.5]
12 97 ms 96 ms 94 ms 212.162.43.250
13 * * * ZeitÂberschreitung der Anforderung.
14 * * * ZeitÂberschreitung der Anforderung.
15 * * * ZeitÂberschreitung der Anforderung.
16 * * * ZeitÂberschreitung der Anforderung.
17 * * * ZeitÂberschreitung der Anforderung.
18 * * * ZeitÂberschreitung der Anforderung.
19 * * * ZeitÂberschreitung der Anforderung.
20 93 ms 93 ms 95 ms server-99-84-151-41.txl52.r.cloudfront.net [99.84.151.41]
Same here !
Routenverfolgung zu d1hoqe10mv32pv.cloudfront.net [99.84.151.67]
Âber maximal 30 Hops:
1 <1 ms <1 ms <1 ms speedport.ip [192.168.2.1]
2 18 ms 17 ms 18 ms 62.155.247.141
3 21 ms 20 ms 21 ms 217.5.101.58
4 28 ms 20 ms 20 ms 217.5.101.58
5 20 ms 20 ms 20 ms 80.157.207.26
6 28 ms 32 ms 25 ms 52.93.39.84
7 21 ms 22 ms 34 ms 52.93.49.123
8 * * * ZeitÂberschreitung der Anforderung.
9 * * * ZeitÂberschreitung der Anforderung.
10 * * * ZeitÂberschreitung der Anforderung.
11 * * * ZeitÂberschreitung der Anforderung.
12 * * * ZeitÂberschreitung der Anforderung.
13 21 ms 21 ms 21 ms server-99-84-151-67.txl52.r.cloudfront.net [99.84.151.67]
Ablaufverfolgung beendet.
Also having huge issues with massive lags in EU-TZ. Already sent a support ticket. My provider is also Deutsche Telekom.
I have the them problem.
I have the same problem as several others in our Corp.
Has anyone already reached support or received an answer?
Same Problem with Telekom since around 2 Weeks here, creating a Ticket.
Routenverfolgung zu d1hoqe10mv32pv.cloudfront.net [99.84.151.67]
Âber maximal 30 Hops:
1 <1 ms <1 ms <1 ms fritz.box [xxx.xxx.xxx.x]
2 4 ms 4 ms 4 ms 62.155.240.15
3 8 ms 7 ms 8 ms 217.239.60.38
4 8 ms 8 ms 7 ms 217.239.60.38
5 8 ms 7 ms 7 ms 80.157.207.26
6 18 ms 16 ms 13 ms 52.93.39.116
7 8 ms 7 ms 7 ms 52.93.49.127
8 * * * ZeitÂberschreitung der Anforderung.
9 * * * ZeitÂberschreitung der Anforderung.
10 * * * ZeitÂberschreitung der Anforderung.
11 * * * ZeitÂberschreitung der Anforderung.
12 * * * ZeitÂberschreitung der Anforderung.
13 8 ms 9 ms 7 ms server-99-84-151-67.txl52.r.cloudfront.net [99.84.151.67]
Ablaufverfolgung beendet.
also same here since around 1 to 2 weeks here:
ISP: Telekom
Routenverfolgung zu d1hoqe10mv32pv.cloudfront.net [99.84.151.41]
ĂŒber maximal 30 Hops:
1 18 ms 16 ms 27 ms speedport.ip [xxx.xxx.xxx.x]
2 14 ms 10 ms 16 ms 62.155.247.110
3 13 ms 19 ms 17 ms 62.154.46.218
4 25 ms 20 ms 13 ms 62.154.46.218
5 15 ms 23 ms 14 ms 80.156.161.178
6 26 ms 21 ms 20 ms 52.93.39.22
7 21 ms 12 ms 14 ms 52.93.49.115
8 * * * ZeitĂŒberschreitung der Anforderung.
9 * * * ZeitĂŒberschreitung der Anforderung.
10 * * * ZeitĂŒberschreitung der Anforderung.
11 * * * ZeitĂŒberschreitung der Anforderung.
12 * * * ZeitĂŒberschreitung der Anforderung.
13 15 ms 18 ms 16 ms
Ablaufverfolgung beendet.
timing of ping is ok but the bufferbloat is very high, results in massive lagspikes
Same here
1 9 ms 5 ms 4 ms speedport.ip [xxx.xxx.xxx.x]
2 21 ms 21 ms 20 ms 62.155.243.23
3 33 ms 28 ms 27 ms 217.239.60.86
4 109 ms 45 ms 32 ms 217.239.60.86
5 24 ms 25 ms 24 ms 80.156.161.178
6 30 ms 31 ms 30 ms 52.93.39.70
7 28 ms 32 ms 38 ms 52.93.49.121
8 * * * ZeitĂŒberschreitung der Anforderung.
9 * * * ZeitĂŒberschreitung der Anforderung.
10 * * * ZeitĂŒberschreitung der Anforderung.
11 * * * ZeitĂŒberschreitung der Anforderung.
12 * * * ZeitĂŒberschreitung der Anforderung.
13 36 ms 35 ms 32 ms
Ablaufverfolgung beendet.
Unfortunately unplayable in this state for me and many others apparently.
At least any kind of PvP activity isnât feasible unless you like loosingâŠ
I have basically the same problems. Opened a Support Ticket last week but didnât get an answer yetâŠ
tarte tracert fĂŒr binaries.eveonline.com
Routenverfolgung zu d17ueqc3zm9j8o.cloudfront.net [99.84.147.39]
Âber maximal 30 Hops:
1 2 ms <1 ms <1 ms speedport.ip [192.168.2.1]
2 57 ms 46 ms 10 ms 62.155.243.154
3 33 ms 22 ms 22 ms 217.239.60.134
4 25 ms 22 ms 22 ms 217.239.60.134
5 22 ms 30 ms 21 ms 80.156.161.178
6 33 ms 30 ms 27 ms 52.93.39.38
7 22 ms 23 ms 22 ms 52.93.49.117
8 * * * ZeitÂberschreitung der Anforderung.
9 * * * ZeitÂberschreitung der Anforderung.
10 * * * ZeitÂberschreitung der Anforderung.
11 * * * ZeitÂberschreitung der Anforderung.
12 * * * ZeitÂberschreitung der Anforderung.
13 22 ms 22 ms 22 ms server-99-84-147-39.txl52.r.cloudfront.net [99.84.147.39]
Ablaufverfolgung beendet.
Starte tracert fĂŒr resources.eveonline.com
Routenverfolgung zu dm794883twbxj.cloudfront.net [13.32.3.125]
Âber maximal 30 Hops:
1 4 ms <1 ms <1 ms speedport.ip [192.168.2.1]
2 9 ms 8 ms 9 ms 62.155.243.154
3 15 ms 14 ms 14 ms 217.0.200.26
4 15 ms 13 ms 13 ms 217.0.200.26
5 14 ms 14 ms 16 ms 80.157.128.94
6 20 ms 16 ms 18 ms 52.93.41.122
7 16 ms 14 ms 13 ms 52.93.41.125
8 15 ms 14 ms 14 ms 52.93.48.25
9 * * * ZeitÂberschreitung der Anforderung.
10 * * * ZeitÂberschreitung der Anforderung.
11 * * * ZeitÂberschreitung der Anforderung.
12 14 ms 14 ms 14 ms server-13-32-3-125.muc51.r.cloudfront.net [13.32.3.125]
Ablaufverfolgung beendet.
Traceroute-Diagnose abgeschlossen
SSL-Diagnose begonnen