Packet Loss and High Latency to CN

Question

Hi,

we have massive problems connecting to a server in CN. We see a packet loss of > 50% and very high latency which is unusual.

When we use a connection/server outside the Comcast Network we don't have this issues.

Please advise.

Best regards

smargasy · Accepted Answer

Here is the outbound trace

Host Loss% Snt Last Avg Best Wrst StDev
1. 121.199.27.249 0.0% 1043 0.5 1.2 0.3 19.2 2.5
2. 10.132.126.194 0.0% 1043 0.8 33.3 0.6 208.4 38.1
3. 42.120.244.233 0.0% 1043 0.7 0.7 0.6 24.4 1.9
4. 42.120.244.181 0.0% 1043 1.2 1.3 1.0 65.3 3.8
5. 122.224.213.198 0.0% 1043 1.0 6.0 0.9 89.8 12.9
6. 220.191.135.161 0.0% 1043 2.7 4.3 1.8 30.3 1.7
7. 202.97.68.141 0.0% 1043 5.0 6.9 4.9 31.3 1.6
8. 202.97.33.162 99.6% 1043 5.3 5.9 5.2 7.6 1.2
9. 202.97.33.154 83.9% 1042 7.8 7.3 4.9 92.9 10.6
10. 202.97.58.166 5.7% 1042 270.6 270.2 203.7 307.5 9.2
202.97.58.162
202.97.58.182
202.97.58.178
202.97.58.174
11. 202.97.50.26 9.5% 1042 285.8 282.9 180.4 294.4 7.8
12. 218.30.54.50 1.3% 1042 292.6 289.3 200.1 349.2 11.1
13. te-2-0-0-13-cr01.losangeles.ca.ibone.comcast.net 15.1% 1042 268.8 266.2 210.2 282.4 8.6
14. be-11115-cr02.losangeles.ca.ibone.comcast.net 15.3% 1042 297.2 293.6 221.5 425.0 17.0
15. be-11315-cr01.dallas.tx.ibone.comcast.net 11.9% 1042 314.0 313.7 220.2 325.9 7.9
16. be-11213-cr01.56marietta.ga.ibone.comcast.net 9.0% 1042 346.4 344.1 270.4 358.8 12.3
17. be-7922-ar03.venice.fl.westfl.comcast.net 19.4% 1042 329.4 324.7 282.5 337.5 6.1
18. te-0-0-0-1-ur04.beaudr.fl.naples.comcast.net 11.6% 1042 334.2 330.8 244.1 343.6 9.2
19. te-6-0-acr01.beaudr.fl.naples.comcast.net 3.6% 1042 332.0 332.1 260.8 531.7 12.4
20. ???
21. wall.smargasy.com 6.5% 1041 364.0 378.8 289.4 915.2 22.5

kraze · Accepted Answer

Well the loss is definitely starting within China. Your best bet here would be to contact your provider in China and ask if they can adjust the outbound path to get you around the issue there.

Alternatively, you can try to wait it out. Issues like this normally don't stay around for too long and will eventually get fixed.

VBSSP-RICH · Answer

Hello smargasy and welcome,

Could you provide some of your network structure info as follows:

a.) What Comcast Gateway (CG) are you using?

b.) What Internet Tier speed are you running?

c.) Are you using Comcast StaticIP?

d.) Are you using a FW or any such controlling / security router device?

e.) Is your server directly connected to the CG?

f.) Can you log into your CG using 10.1.10.1, cusadmin/highspeed, go to gateway summary, cable and provide your downstream/upstream power levels?

Look forward to hearing from you to further assist......

smargasy · Answer

Hi,

We use the Comcast delivered Modem and our own firewall, but thats not the problem because every other connection does not have performance issues. One of the routers on the way to the CN Server creates huges packet-losses.

ATTENTION: we talk about OUTGOING Connections, the server we want to connect to is in CN (a customer of us)

We have 120MB and using static ip's.

This is a trace done with mtr where you can see that beginning with host 14 the connection is going bad - 90% packet loss makes any remote work impossible (doesnt matter what protocol)

---------------

Host Loss% Snt Last Avg Best Wrst StDev
1. 192.168.5.1 0.0% 1318 0.4 0.4 0.4 2.0 0.1
2. 50.251.99.190 0.0% 1318 2.0 6.6 1.5 96.0 6.5
3. 73.23.14.1 0.0% 1318 17.7 21.1 10.0 208.5 11.9
4. te-0-0-0-18-ur03.beaudr.fl.naples.comcast.net 0.0% 1318 38.3 19.8 10.4 86.6 9.2
5. te-0-7-0-0-ur04.beaudr.fl.naples.comcast.net 0.0% 1318 18.7 19.6 10.4 149.8 10.5
te-0-7-0-1-ur04.beaudr.fl.naples.comcast.net
6. te-0-5-0-13-ar03.venice.fl.westfl.comcast.net 0.0% 1318 25.7 26.8 14.5 170.1 12.5
te-0-9-0-2-ar03.venice.fl.westfl.comcast.net
te-0-9-0-10-ar03.venice.fl.westfl.comcast.net
7. be-33661-cr01.56marietta.ga.ibone.comcast.net 0.0% 1318 53.6 38.6 25.9 145.8 11.0
8. be-11213-cr01.dallas.tx.ibone.comcast.net 0.0% 1318 46.6 58.0 45.1 145.4 10.6
9. be-11315-cr02.losangeles.ca.ibone.comcast.net 0.0% 1318 82.2 87.6 76.8 165.6 9.5
10. be-11115-cr01.losangeles.ca.ibone.comcast.net 0.0% 1318 80.2 89.0 76.2 159.7 9.6
11. xe-2-0-2-0-pe01.onewilshire.ca.ibone.comcast.net 0.0% 1317 77.0 88.9 75.8 242.0 14.4
12. 218.30.54.21 0.0% 1317 83.2 88.6 76.7 198.6 10.8
13. ???
14. 202.97.50.5 8.5% 1317 349.0 345.5 245.3 455.0 24.9
15. 202.97.35.33 89.8% 1317 342.6 373.4 249.7 440.4 30.4
16. 202.97.50.241 13.0% 1317 337.2 364.0 262.3 477.6 24.9
17. ???
18. 61.164.31.162 14.0% 1317 429.0 412.3 289.6 544.4 35.9
19. 122.224.187.157 12.9% 1317 402.0 413.6 305.7 650.8 41.4
20. 42.120.244.182 13.1% 1315 371.5 374.7 274.8 480.0 28.6
21. 42.120.244.234 13.4% 1315 347.1 341.0 240.1 461.9 26.0
22. ???
23. 121.199.33.21 11.3% 1314 385.9 372.9 270.6 464.6 24.9

kraze · Answer

That loss is starting after the Comcast network and after it's within the Chinanet network. This generally means it isn't a Comcast problem and more of a peering issue. Using an outside connection to bypass this issue makes sense as the routing is likely different. You can try contacting Comcast to see if they'd be willing to fiddle with it and see if they could suggest a different route, but it's unlikely. You could also try contacting your provider and see if they'd be willing to reach out and see if changing the route is feasible.

Also are you able to get us an outbound that we can look at?

train_wreck · Answer

As well as kraze's request, possibly provide a traceroute from the working connection? Perhaps inbound traffic to the CN site is entering at a different handoff IP/location when accessed on that ISP versus on Comcast?

smargasy

Packet Loss and High Latency to CN

smargasy

kraze

VBSSP-RICH

smargasy

kraze

train_wreck