Ping & connection
DeviL, Wed Jan 09 2013, 02:30PMIf many different players are on server my ping raises from 150-210.
BK told me why so I have to accept it, but even if there aren't a lot players on server I lose so many packets from server.
Any ideas why?
Don't have that problem on other servers.
Re: Ping & connection
BanMe, Thu Jan 10 2013, 11:30AM
I get 100mb down and about 50mb up on my school internet. I still get red lines. They aren't as big as yours but they're still there. No problem on other servers either. No ping issues.
At home i get thick ones like you have and my ping will jump to 250-300 for 3-4 seconds and go back down for a few more minutes.
It's pretty annoying.
BanMe, Thu Jan 10 2013, 11:30AM
I get 100mb down and about 50mb up on my school internet. I still get red lines. They aren't as big as yours but they're still there. No problem on other servers either. No ping issues.
At home i get thick ones like you have and my ping will jump to 250-300 for 3-4 seconds and go back down for a few more minutes.
It's pretty annoying.
Re: Ping & connection
NoSkylz[Um3], Fri Jan 11 2013, 11:14PM
I almost never see this on sm.fsk405.com - what ISPs are you both using? Maybe something with the peering? I am using Verizon DSL (7m down/1 up theoretically - in practice about 4m down and 512 up)
NoSkylz[Um3], Fri Jan 11 2013, 11:14PM
I almost never see this on sm.fsk405.com - what ISPs are you both using? Maybe something with the peering? I am using Verizon DSL (7m down/1 up theoretically - in practice about 4m down and 512 up)
Re: Ping & connection
Reflux, Thu Jan 17 2013, 04:31PM
What do you guys think? A trace from Chicago and a trace from Denver. I think somebody is filtering packets.
Reflux, Thu Jan 17 2013, 04:31PM
What do you guys think? A trace from Chicago and a trace from Denver. I think somebody is filtering packets.
Re: Ping & connection
wily duck, Thu Jan 17 2013, 04:57PM
Doubt packet filtering. It's hard getting a good trace back to you (and I don't have your IP, only what's in these traces). Mainland USA to Virginia seems fine, oceanic to DE seems ok, but once mainland DE, it gets tough to get a consistent response.
Standard note on traceroutes/ICMP: All routers treat ICMP as low-priority, as packets are generated by the router's CPU. If said router decides it doesn't have the resources (CPU, mem, otherwise), to produce a response ICMP in a reasonable time, it will simply drop the request, resulting in an asterisk on your trace.
What concerns me about the trace from Superman server to Devil, is hops 7 and 8 show drops. If there were drops, but the following routers responded fine, this would indicate the preceding info above.
Based on Reflux's traces, combined traces from my home server, I'd have your residential ISP verify their peering interfaces for errors, or have them open a ticket with Telekom Germany to verify their downstream interfaces, perhaps validating their hops between their mainland oceanic handoff back downstream for anomalies. I agree that something in the path looks dirty, but not intentionally.
p.s. be sure to verify your residential connection to your ISP is clean first! Low db levels or high SNR on your connection is a possibility in this situation.
Keeping the network engineering skills alive,
:V
wily duck, Thu Jan 17 2013, 04:57PM
Doubt packet filtering. It's hard getting a good trace back to you (and I don't have your IP, only what's in these traces). Mainland USA to Virginia seems fine, oceanic to DE seems ok, but once mainland DE, it gets tough to get a consistent response.
Standard note on traceroutes/ICMP: All routers treat ICMP as low-priority, as packets are generated by the router's CPU. If said router decides it doesn't have the resources (CPU, mem, otherwise), to produce a response ICMP in a reasonable time, it will simply drop the request, resulting in an asterisk on your trace.
What concerns me about the trace from Superman server to Devil, is hops 7 and 8 show drops. If there were drops, but the following routers responded fine, this would indicate the preceding info above.
Based on Reflux's traces, combined traces from my home server, I'd have your residential ISP verify their peering interfaces for errors, or have them open a ticket with Telekom Germany to verify their downstream interfaces, perhaps validating their hops between their mainland oceanic handoff back downstream for anomalies. I agree that something in the path looks dirty, but not intentionally.
p.s. be sure to verify your residential connection to your ISP is clean first! Low db levels or high SNR on your connection is a possibility in this situation.
Keeping the network engineering skills alive,
:V
Re: Ping & connection
DeviL, Fri Jan 18 2013, 12:13AM
So right now two people on Superman and I was able to connect - no red lines and no permanent awaiting connection.
DeviL, Fri Jan 18 2013, 12:13AM
So right now two people on Superman and I was able to connect - no red lines and no permanent awaiting connection.
Re: Ping & connection
wily duck, Fri Jan 18 2013, 11:50AM
Solar flares. Probably should check your pattern buffer compensator and de-ionizing stablizers. These things are known to interfere with FUN
wily duck, Fri Jan 18 2013, 11:50AM
Solar flares. Probably should check your pattern buffer compensator and de-ionizing stablizers. These things are known to interfere with FUN
Re: Ping & connection
FSK405|EZ, Sat Jan 19 2013, 11:16AM
I was going to say that!!
FSK405|EZ, Sat Jan 19 2013, 11:16AM
I was going to say that!!
Re: Ping & connection
DeviL, Sun Jan 20 2013, 11:28AM
and... i am blocked again.
DeviL, Sun Jan 20 2013, 11:28AM
and... i am blocked again.
Re: Ping & connection
Reflux, Sun Jan 20 2013, 03:39PM
Devil,
It is whoever is operating this (62.153.177.34) equipment. Everything up to that router is clean and everything beyond it is dirty.
I've checked the route from a variety of other US locations and everything is clean unless it originates from our Chicago location. From Chicago, the interface right before the dirty router is 80.150.168.21. From all of the places I've checked, the interface before the same router belongs to the same TeleComm (Deutsche Telekom AG). You need to contact them and let them know that they might have a faulty interface on a router.
Chicago
Host Loss%
1. 64.94.34.229 0.0%
2. 64.94.32.67 0.0%
3. 208.48.24.185 0.0%
4. 67.16.161.34 0.0%
5. 67.16.142.54 0.0%
6. 80.150.168.21 0.0%
7. 62.153.177.34 50.0%
8. 87.190.191.181 40.0%
9. ???
Denver
Host Loss%
1. 72.5.102.253 0.0%
2. 216.52.40.71 0.0%
3. 65.46.52.189 0.0%
4. 216.156.6.17 0.0%
5. 216.156.0.9 0.0%
6. 207.88.12.58 0.0%
7. 207.88.14.226 0.0%
8. 206.111.6.234 0.0%
9. 62.153.177.34 0.0%
10. 87.190.191.185 0.0%
11. ???
California
Host Loss%
1. 64.58.178.129 0.0%
2. 64.58.133.26 0.0%
3. 68.4.13.158 0.0%
4. 68.4.11.8 0.0%
5. 68.4.11.94 0.0%
6. 68.1.5.137 0.0%
7. 4.53.230.33 0.0%
8. 4.69.144.138 0.0%
9. 217.6.51.245 0.0%
10. 62.153.177.46 0.0%
11. 87.190.191.181 0.0%
12. ???
[Querying whois.ripe.net]
[whois.ripe.net]
% This is the RIPE Database query service.
% The objects are in RPSL format.
%
% The RIPE Database is subject to Terms and Conditions.
% See http://www.ripe.net/db/support/db-terms-conditions.pdf
% Note: this output has been filtered.
% To receive output for a database update, use the "-B" flag.
% Information related to '62.153.176.0 - 62.153.191.255'
inetnum: 62.153.176.0 - 62.153.191.255
netname: DTAG-BB16
descr: Deutsche Telekom AG
country: DE
admin-c: DTIP
tech-c: DTST
status: ASSIGNED PA
remarks: ******************************************************************
remarks: * Abuse Contact: http://www.t-com.de/ip-abuse in case of Spam, *
remarks: * Hack Attacks, Illegal Activity, Violation, Scans, Probes, etc. *
remarks: ******************************************************************
mnt-by: DTAG-NIC
source: RIPE # Filtered
person: DTAG Global IP-Addressing
address: Deutsche Telekom AG
address: D-90492 Nuernberg
address: Germany
phone: +49 180 5334332
fax-no: +49 6151 6809399
nic-hdl: DTIP
mnt-by: DTAG-NIC
source: RIPE # Filtered
person: Security Team
address: Deutsche Telekom AG
address: Germany
phone: +49 180 5334332
fax-no: +49 6151 6809399
nic-hdl: DTST
mnt-by: DTAG-NIC
source: RIPE # Filtered
% Information related to '62.153.0.0/16AS3320'
route: 62.153.0.0/16
descr: Deutsche Telekom AG, Internet service provider
origin: AS3320
member-of: AS3320:RS-PA-TELEKOM
mnt-by: DTAG-RR
source: RIPE # Filtered
% This query was served by the RIPE Database Query Service version 1.50.5 (WHOIS4)
Reflux, Sun Jan 20 2013, 03:39PM
Devil,
It is whoever is operating this (62.153.177.34) equipment. Everything up to that router is clean and everything beyond it is dirty.
I've checked the route from a variety of other US locations and everything is clean unless it originates from our Chicago location. From Chicago, the interface right before the dirty router is 80.150.168.21. From all of the places I've checked, the interface before the same router belongs to the same TeleComm (Deutsche Telekom AG). You need to contact them and let them know that they might have a faulty interface on a router.
Chicago
Host Loss%
1. 64.94.34.229 0.0%
2. 64.94.32.67 0.0%
3. 208.48.24.185 0.0%
4. 67.16.161.34 0.0%
5. 67.16.142.54 0.0%
6. 80.150.168.21 0.0%
7. 62.153.177.34 50.0%
8. 87.190.191.181 40.0%
9. ???
Denver
Host Loss%
1. 72.5.102.253 0.0%
2. 216.52.40.71 0.0%
3. 65.46.52.189 0.0%
4. 216.156.6.17 0.0%
5. 216.156.0.9 0.0%
6. 207.88.12.58 0.0%
7. 207.88.14.226 0.0%
8. 206.111.6.234 0.0%
9. 62.153.177.34 0.0%
10. 87.190.191.185 0.0%
11. ???
California
Host Loss%
1. 64.58.178.129 0.0%
2. 64.58.133.26 0.0%
3. 68.4.13.158 0.0%
4. 68.4.11.8 0.0%
5. 68.4.11.94 0.0%
6. 68.1.5.137 0.0%
7. 4.53.230.33 0.0%
8. 4.69.144.138 0.0%
9. 217.6.51.245 0.0%
10. 62.153.177.46 0.0%
11. 87.190.191.181 0.0%
12. ???
[Querying whois.ripe.net]
[whois.ripe.net]
% This is the RIPE Database query service.
% The objects are in RPSL format.
%
% The RIPE Database is subject to Terms and Conditions.
% See http://www.ripe.net/db/support/db-terms-conditions.pdf
% Note: this output has been filtered.
% To receive output for a database update, use the "-B" flag.
% Information related to '62.153.176.0 - 62.153.191.255'
inetnum: 62.153.176.0 - 62.153.191.255
netname: DTAG-BB16
descr: Deutsche Telekom AG
country: DE
admin-c: DTIP
tech-c: DTST
status: ASSIGNED PA
remarks: ******************************************************************
remarks: * Abuse Contact: http://www.t-com.de/ip-abuse in case of Spam, *
remarks: * Hack Attacks, Illegal Activity, Violation, Scans, Probes, etc. *
remarks: ******************************************************************
mnt-by: DTAG-NIC
source: RIPE # Filtered
person: DTAG Global IP-Addressing
address: Deutsche Telekom AG
address: D-90492 Nuernberg
address: Germany
phone: +49 180 5334332
fax-no: +49 6151 6809399
nic-hdl: DTIP
mnt-by: DTAG-NIC
source: RIPE # Filtered
person: Security Team
address: Deutsche Telekom AG
address: Germany
phone: +49 180 5334332
fax-no: +49 6151 6809399
nic-hdl: DTST
mnt-by: DTAG-NIC
source: RIPE # Filtered
% Information related to '62.153.0.0/16AS3320'
route: 62.153.0.0/16
descr: Deutsche Telekom AG, Internet service provider
origin: AS3320
member-of: AS3320:RS-PA-TELEKOM
mnt-by: DTAG-RR
source: RIPE # Filtered
% This query was served by the RIPE Database Query Service version 1.50.5 (WHOIS4)
Re: Ping & connection
DeviL, Mon Jan 21 2013, 05:05AM
I tried it this morning again and it was working.
Seems like i'm able to connect in the morning but not at noon when everyone else is in the internet as well.
DeviL, Mon Jan 21 2013, 05:05AM
I tried it this morning again and it was working.
Seems like i'm able to connect in the morning but not at noon when everyone else is in the internet as well.
Re: Ping & connection
Moving_Target, Tue Feb 05 2013, 10:10AM
I now got the same problems. Ping >200 and packet loss galore – unplayable the last few days.
Only on Superman...every other US server works perfectly fine.
Also pinged some servers in chicago and got 100-115.
cheers
MT
Moving_Target, Tue Feb 05 2013, 10:10AM
I now got the same problems. Ping >200 and packet loss galore – unplayable the last few days.
Only on Superman...every other US server works perfectly fine.
Also pinged some servers in chicago and got 100-115.
cheers
MT
traceroute to sm.fsk405.com (64.74.97.153), 64 hops max, 52 byte packets
1 fritz.box (192.168.178.1) 2.637 ms 2.017 ms 2.796 ms
2 10.134.192.1 (10.134.192.1) 11.173 ms 17.288 ms 32.441 ms
3 1312a-mx960-02-ae10-2010.bon.unity-media.net (80.69.105.45) 13.448 ms 9.944 ms 11.167 ms
4 1312a-mx960-01-ae0.bon.unity-media.net (80.69.106.142) 16.367 ms 9.124 ms 12.536 ms
5 1311g-mx960-02-xe-1-0-0.hue.unity-media.net (80.69.106.146) 12.562 ms 26.249 ms 9.827 ms
6 1211f-mx960-02-ae7.dtm.unity-media.net (80.69.107.46) 16.058 ms 12.874 ms 19.935 ms
7 7111a-mx960-02-ae9.fra.unity-media.net (80.69.107.22) 48.689 ms 19.819 ms 35.881 ms
8 7111a-mx960-01-ae0.fra.unity-media.net (80.69.107.213) 20.519 ms 17.458 ms 23.363 ms
9 84-116-131-149.aorta.net (84.116.131.149) 18.489 ms 18.743 ms 20.796 ms
10 84.116.132.161 (84.116.132.161) 19.938 ms
de-fra01a-ri2-xe-5-1-1.aorta.net (84.116.133.114) 30.766 ms
84.116.132.169 (84.116.132.169) 23.195 ms
11 84.116.132.190 (84.116.132.190) 21.823 ms
84.116.132.198 (84.116.132.198) 23.842 ms
84.116.132.158 (84.116.132.158) 19.477 ms
12 ge-3-0.ir1.frankfurt-he.de.xo.net (80.81.192.182) 24.536 ms 19.520 ms 25.465 ms
13 ae1d0.cir1.amsterdam2-nh.nl.xo.net (207.88.15.74) 20.836 ms 37.151 ms 21.173 ms
14 ae1d0.cir1.london2-eng.uk.xo.net (207.88.15.70) 39.658 ms 35.876 ms 39.726 ms
15 vb1042.rar3.nyc-ny.us.xo.net (207.88.13.202) 122.553 ms 118.305 ms 119.957 ms
16 207.88.14.62.ptr.us.xo.net (207.88.14.62) 130.271 ms 131.801 ms 135.633 ms
17 207.88.184.146.ptr.us.xo.net (207.88.184.146) 131.826 ms 137.717 ms 128.999 ms
18 border5.po2-bbnet2.chg.pnap.net (64.94.32.74) 129.454 ms 130.528 ms 129.095 ms
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
Re: Ping & connection
DeviL, Tue Feb 05 2013, 02:17PM
Bei der Telekom?
DeviL, Tue Feb 05 2013, 02:17PM
Bei der Telekom?
Re: Ping & connection
Moving_Target, Tue Feb 05 2013, 02:20PM
Nope, UnityMedia 100Mbit down / 5Mbit up
cheers
MT
Moving_Target, Tue Feb 05 2013, 02:20PM
DeviL
Bei der Telekom?
Nope, UnityMedia 100Mbit down / 5Mbit up
cheers
MT
Re: Ping & connection
DeviL, Thu Feb 07 2013, 07:56AM
So my connection is fine atm.
it's not up to our providers I think.
DeviL, Thu Feb 07 2013, 07:56AM
So my connection is fine atm.
it's not up to our providers I think.
Print this page