Connectivity
Connectivity and managing Your Comcast Business network
Male IT Specialist Holds Laptop and Discusses Work with Female Server Technician. They're Standing in Data Center, Rack Server Cabinet is Open.
jtitley16
Frequent Contributor

Intermitent Packet Loss for all of June with no resolution.

I have been suffering from a High frequency of disconnects from sever host servers located in Los Angeles, and Houston, I have provided traceroutes, Pathpings, WinMTR, and Looking Glass reports as well as the IP addresses of servers where packet loss occurs.  Tier 2 tech support has offered some rather interesting and ignorant feedback thus far.  The following was sent to me by tier 2 in regards to my issue of packet loss: "This is in reference to your Comcast Business high speed internet.  I have verified that all of your Comcast internet services are working correctly.  I am able to login to your gateway and reach websites from within your gateway.  If you are still experiencing connectivity issues, I would recommend that you start with basic troubleshooting, and restart all of your equipment or contact your IT professional.  Additionally I have included several helpful links for your internet service." - jordan-t2-smb@comcast.net.  I am talking about intermittent packet loss that is disconnecting me from my connection with a server, of course I can reach web pages..........How about we get some real help for this issue?  I am providing both links to the official Blizzard Forums where they suggest the connectivity problem exists on your end as well as some of my supporting log files.

 

This is now my 2nd Saturday that you have sent a tech to troubleshoot the issue that is clearly not located at my house, I'm not really thrilled about losing my weekend because I have to sit here and wait for a field tech to look at my logs and say "Oh i don't know anything about that stuff, let me replace your modem for you."  I am also equally displeased with your tier 2 agent that thinks because he can connect to a webpage that my packet loss issue is resolved...........

 

Here is a response from Blizzard Entertainment in which they suggest that this is your problem:

"8. be-11719-cr01.1601milehigh.co.ibone.comcast.net 80.0% 10 33.2 33.2 33.1 33.2 0.0
9. be-10919-cr01.sunnyvale.ca.ibone.comcast.net 40.0% 10 51.9 51.9 51.8 52.1 0.1

8. be-11719-cr01.1601milehigh.co.ibone.comcast.net 90.0% 10 33.1 33.1 33.1 33.1 0.0
9. be-10919-cr01.sunnyvale.ca.ibone.comcast.net 10.0% 10 51.8 51.8 51.8 52.0 0.1

Good call out, I'm sorry I missed those in your first trace. Can you show these to your ISP? It looks like this packet loss is well within their network." 

The URL can be found here: http://us.battle.net/wow/en/forum/topic/20745135510?page=2#23

 

In addition here are some logs which support my claim that this issue is on your end.  I have put in bold the areas with packet loss.

TRACEROUTE:
traceroute to 67.182.25.217 (67.182.25.217), 15 hops max, 60 byte packets
1 Blizzard (Blizzard) 2.124 ms 2.171 ms 2.204 ms
2 * * *
3 37.244.1.100 (37.244.1.100) 2.443 ms 2.655 ms 2.740 ms
4 37.244.1.32 (37.244.1.32) 3.847 ms 3.849 ms 3.849 ms
5 te-0-11-0-0-2-pe01.350ecermak.il.ibone.comcast.net (173.167.56.237) 2.177 ms 2.209 ms 2.243 ms
6 hu-2-4-0-1-cr02.350ecermak.il.ibone.comcast.net (68.86.89.245) 2.076 ms 3.790 ms 3.781 ms
7 be-10517-cr02.denver.co.ibone.comcast.net (68.86.85.170) 35.062 ms 35.088 ms 35.108 ms
8 be-11719-cr01.1601milehigh.co.ibone.comcast.net (68.86.86.78) 31.139 ms 31.405 ms 31.633 ms
9 be-10919-cr01.sunnyvale.ca.ibone.comcast.net (68.86.85.153) 52.128 ms 52.423 ms 51.727 ms
10 ae-79-ar01.sacramento.ca.ccal.comcast.net (68.86.93.26) 54.693 ms 54.717 ms 54.612 ms
11 ae-24-sur03.clovis.ca.ccal.comcast.net (162.151.40.130) 57.113 ms 57.071 ms 57.096 ms
12 te-6-1-acr01.clovis.ca.ccal.comcast.net (162.151.83.118) 59.700 ms 59.745 ms 59.773 ms
13 c-67-182-25-217.hsd1.ca.comcast.net (67.182.25.217) 70.993 ms 73.382 ms 77.632 ms


25/06/2016 16:31:51 UTC
--------------------

TRACEROUTE:
traceroute to 67.182.25.217 (67.182.25.217), 15 hops max, 60 byte packets
1 Blizzard (Blizzard) 0.778 ms 2.029 ms 2.060 ms
2 * * *
3 37.244.1.100 (37.244.1.100) 2.221 ms 2.440 ms 2.448 ms
4 37.244.1.32 (37.244.1.32) 2.249 ms 3.863 ms 3.875 ms
5 te-0-11-0-0-2-pe01.350ecermak.il.ibone.comcast.net (173.167.56.237) 1.962 ms 2.024 ms 2.057 ms
6 hu-2-4-0-1-cr02.350ecermak.il.ibone.comcast.net (68.86.89.245) 2.112 ms 2.848 ms 2.280 ms
7 be-10517-cr02.denver.co.ibone.comcast.net (68.86.85.170) 33.692 ms 33.708 ms 33.712 ms
8 be-11719-cr01.1601milehigh.co.ibone.comcast.net (68.86.86.78) 31.201 ms 31.347 ms 31.455 ms
9 be-10919-cr01.sunnyvale.ca.ibone.comcast.net (68.86.85.153) 51.870 ms 51.945 ms 52.169 ms
10 ae-79-ar01.sacramento.ca.ccal.comcast.net (68.86.93.26) 54.728 ms 54.740 ms 54.589 ms
11 ae-24-sur03.clovis.ca.ccal.comcast.net (162.151.40.130) 57.133 ms 57.120 ms 57.112 ms
12 te-6-1-acr01.clovis.ca.ccal.comcast.net (162.151.83.118) 59.763 ms 59.839 ms 59.869 ms
13 c-67-182-25-217.hsd1.ca.comcast.net (67.182.25.217) 68.179 ms 68.570 ms 73.842 ms


25/06/2016 16:31:51 UTC
--------------------

PING:
PING 67.182.25.217 (67.182.25.217) 56(84) bytes of data.
64 bytes from 67.182.25.217: icmp_seq=1 ttl=50 time=70.5 ms
64 bytes from 67.182.25.217: icmp_seq=2 ttl=50 time=70.6 ms
64 bytes from 67.182.25.217: icmp_seq=3 ttl=50 time=69.3 ms
64 bytes from 67.182.25.217: icmp_seq=4 ttl=50 time=70.5 ms

--- 67.182.25.217 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3069ms
rtt min/avg/max/mdev = 69.339/70.277/70.698/0.545 ms


25/06/2016 16:31:51 UTC
--------------------

PING:
PING 67.182.25.217 (67.182.25.217) 56(84) bytes of data.
64 bytes from 67.182.25.217: icmp_seq=1 ttl=50 time=69.0 ms
64 bytes from 67.182.25.217: icmp_seq=2 ttl=50 time=70.0 ms
64 bytes from 67.182.25.217: icmp_seq=3 ttl=50 time=70.0 ms
64 bytes from 67.182.25.217: icmp_seq=4 ttl=50 time=68.3 ms

--- 67.182.25.217 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3066ms
rtt min/avg/max/mdev = 68.391/69.406/70.089/0.755 ms


25/06/2016 16:31:51 UTC
--------------------

TRACEROUTE:
traceroute to 67.182.25.217 (67.182.25.217), 15 hops max, 60 byte packets
1 Blizzard (Blizzard) 0.469 ms 0.532 ms 0.675 ms
2 * * *
3 37.244.0.102 (37.244.0.102) 3.118 ms 3.160 ms 3.212 ms
4 37.244.0.34 (37.244.0.34) 1.977 ms 2.012 ms 2.058 ms
5 te-0-4-0-9-pe02.600wseventh.ca.ibone.comcast.net (173.167.56.217) 1.923 ms 1.942 ms 1.997 ms
6 hu-1-0-0-1-cr02.losangeles.ca.ibone.comcast.net (68.86.88.13) 4.149 ms hu-0-5-0-3-cr02.losangeles.ca.ibone.comcast.net (68.86.83.29) 2.940 ms hu-0-5-0-2-cr02.losangeles.ca.ibone.comcast.net (68.86.83.25) 2.955 ms
7 ae-79-ar01.fresno.ca.ccal.comcast.net (68.86.93.38) 8.001 ms 7.985 ms 7.984 ms
8 ae-25-sur03.clovis.ca.ccal.comcast.net (162.151.40.134) 14.994 ms 15.029 ms 15.033 ms
9 te-7-1-acr01.clovis.ca.ccal.comcast.net (162.151.83.126) 16.015 ms 16.103 ms 15.973 ms
10 c-67-182-25-217.hsd1.ca.comcast.net (67.182.25.217) 24.522 ms 28.330 ms 25.117 ms


25/06/2016 16:31:53 UTC
--------------------

TRACEROUTE:
traceroute to 67.182.25.217 (67.182.25.217), 15 hops max, 60 byte packets
1 Blizzard (Blizzard) 0.450 ms 0.470 ms 0.568 ms
2 * * *
3 37.244.0.102 (37.244.0.102) 3.296 ms 3.310 ms 3.312 ms
4 37.244.0.34 (37.244.0.34) 1.942 ms 1.969 ms 2.009 ms
5 te-0-4-0-9-pe02.600wseventh.ca.ibone.comcast.net (173.167.56.217) 1.975 ms 1.995 ms 2.013 ms
6 hu-0-5-0-3-cr02.losangeles.ca.ibone.comcast.net (68.86.83.29) 3.688 ms hu-1-0-0-1-cr02.losangeles.ca.ibone.comcast.net (68.86.88.13) 2.968 ms hu-0-5-0-3-cr02.losangeles.ca.ibone.comcast.net (68.86.83.29) 2.416 ms
7 ae-79-ar01.fresno.ca.ccal.comcast.net (68.86.93.38) 7.983 ms 7.994 ms 7.991 ms
8 ae-25-sur03.clovis.ca.ccal.comcast.net (162.151.40.134) 15.051 ms 15.069 ms 15.050 ms
9 te-7-1-acr01.clovis.ca.ccal.comcast.net (162.151.83.126) 16.030 ms 16.107 ms 16.164 ms
10 c-67-182-25-217.hsd1.ca.comcast.net (67.182.25.217) 25.109 ms 29.578 ms *


25/06/2016 16:31:55 UTC
--------------------

PING:
PING 67.182.25.217 (67.182.25.217) 56(84) bytes of data.
64 bytes from 67.182.25.217: icmp_seq=2 ttl=50 time=25.1 ms
64 bytes from 67.182.25.217: icmp_seq=3 ttl=50 time=29.2 ms
64 bytes from 67.182.25.217: icmp_seq=4 ttl=50 time=25.8 ms

--- 67.182.25.217 ping statistics ---
4 packets transmitted, 3 received, 25% packet loss, time 3998ms
rtt min/avg/max/mdev = 25.108/26.720/29.221/1.797 ms


25/06/2016 16:31:54 UTC
--------------------

PING:
PING 67.182.25.217 (67.182.25.217) 56(84) bytes of data.
64 bytes from 67.182.25.217: icmp_seq=1 ttl=50 time=24.8 ms
64 bytes from 67.182.25.217: icmp_seq=2 ttl=50 time=27.0 ms
64 bytes from 67.182.25.217: icmp_seq=3 ttl=50 time=29.6 ms
64 bytes from 67.182.25.217: icmp_seq=4 ttl=50 time=25.4 ms

--- 67.182.25.217 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3024ms
rtt min/avg/max/mdev = 24.882/26.738/29.632/1.857 ms


25/06/2016 16:31:58 UTC
--------------------

MTR:
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
1. Blizzard 0.0% 10 0.5 0.5 0.4 0.7 0.1
2. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
3. 37.244.1.100 0.0% 10 2.1 2.3 2.1 3.6 0.4
4. 37.244.1.32 0.0% 10 2.1 2.2 2.0 3.2 0.4
5. te-0-11-0-0-2-pe01.350ecermak.il.ibone.comcast.net 0.0% 10 1.9 2.0 1.8 2.3 0.2
6. hu-2-4-0-1-cr02.350ecermak.il.ibone.comcast.net 0.0% 10 2.7 3.2 2.3 4.2 0.6
7. be-10517-cr02.denver.co.ibone.comcast.net 0.0% 10 33.7 34.1 33.4 34.7 0.5
8. be-11719-cr01.1601milehigh.co.ibone.comcast.net 0.0% 10 31.0 31.2 31.0 31.5 0.2
9. be-10919-cr01.sunnyvale.ca.ibone.comcast.net 0.0% 10 52.1 52.0 51.8 52.3 0.2
10. ae-79-ar01.sacramento.ca.ccal.comcast.net 0.0% 10 54.8 54.8 54.7 55.4 0.2
11. ae-24-sur03.clovis.ca.ccal.comcast.net 0.0% 10 57.3 57.2 57.2 57.3 0.0
12. te-6-1-acr01.clovis.ca.ccal.comcast.net 0.0% 10 59.8 59.9 59.8 60.1 0.1
13. c-67-182-25-217.hsd1.ca.comcast.net 30.0% 10 74.1 71.4 68.9 74.5 2.6


25/06/2016 16:31:51 UTC
--------------------

MTR:
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
1. Blizzard 0.0% 10 0.5 0.6 0.4 0.7 0.1
2. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
3. 37.244.1.100 0.0% 10 2.2 2.1 1.9 2.2 0.1
4. 37.244.1.32 0.0% 10 2.1 2.1 1.9 3.1 0.3
5. te-0-11-0-0-2-pe01.350ecermak.il.ibone.comcast.net 0.0% 10 1.9 2.0 1.8 2.2 0.1
6. hu-2-4-0-1-cr02.350ecermak.il.ibone.comcast.net 0.0% 10 2.7 3.0 2.2 3.9 0.6
7. be-10517-cr02.denver.co.ibone.comcast.net 0.0% 10 33.7 34.3 33.5 35.3 0.6
8. be-11719-cr01.1601milehigh.co.ibone.comcast.net 0.0% 10 31.2 31.1 31.0 31.4 0.1
9. be-10919-cr01.sunnyvale.ca.ibone.comcast.net 0.0% 10 51.8 51.9 51.7 52.1 0.1
10. ae-79-ar01.sacramento.ca.ccal.comcast.net 0.0% 10 54.8 55.5 54.7 61.6 2.2
11. ae-24-sur03.clovis.ca.ccal.comcast.net 0.0% 10 57.2 57.2 57.1 57.2 0.0
12. te-6-1-acr01.clovis.ca.ccal.comcast.net 0.0% 10 59.9 59.9 59.8 60.5 0.2
13. c-67-182-25-217.hsd1.ca.comcast.net 30.0% 10 69.3 71.1 68.5 74.2 2.7


25/06/2016 16:31:51 UTC
--------------------

MTR:
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
1. Blizzard 0.0% 10 0.4 0.5 0.3 0.8 0.1
2. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
3. 37.244.0.102 0.0% 10 5.3 3.5 2.2 5.3 1.2
4. 37.244.0.34 0.0% 10 1.9 2.0 1.9 2.1 0.1
5. te-0-4-0-9-pe02.600wseventh.ca.ibone.comcast.net 0.0% 10 2.0 2.0 1.9 2.3 0.1
6. hu-0-5-0-0-cr02.losangeles.ca.ibone.comcast.net 0.0% 10 2.5 3.3 2.4 4.2 0.6
7. ae-79-ar01.fresno.ca.ccal.comcast.net 0.0% 10 34.9 15.1 8.0 36.3 11.7
8. ae-25-sur03.clovis.ca.ccal.comcast.net 0.0% 10 15.0 15.0 15.0 15.1 0.0
9. te-7-1-acr01.clovis.ca.ccal.comcast.net 0.0% 10 16.1 16.1 16.0 16.4 0.1
10. c-67-182-25-217.hsd1.ca.comcast.net 0.0% 10 30.5 30.0 25.3 36.0 4.0


25/06/2016 16:31:53 UTC
--------------------

MTR:
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
1. Blizzard 0.0% 10 0.5 1.3 0.4 8.6 2.6
2. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
3. 37.244.0.102 0.0% 10 2.9 3.3 2.2 6.1 1.2
4. 37.244.0.34 0.0% 10 2.0 2.0 1.9 2.2 0.1
5. te-0-4-0-9-pe02.600wseventh.ca.ibone.comcast.net 0.0% 10 2.0 2.0 1.9 2.4 0.1
6. hu-0-5-0-0-cr02.losangeles.ca.ibone.comcast.net 0.0% 10 4.2 3.4 2.4 4.3 0.7
7. ae-79-ar01.fresno.ca.ccal.comcast.net 0.0% 10 8.1 8.2 8.0 9.0 0.4
8. ae-25-sur03.clovis.ca.ccal.comcast.net 0.0% 10 15.0 16.3 15.0 26.6 3.6
9. te-7-1-acr01.clovis.ca.ccal.comcast.net 0.0% 10 16.2 16.1 16.0 16.2 0.1
10. c-67-182-25-217.hsd1.ca.comcast.net 30.0% 10 30.4 32.0 28.1 38.7 4.0


25/06/2016 16:31:54 UTC
--------------------

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

Here is another report showing packet loss on your GreatOaks server

 

|------------------------------------------------------------------------------------------|

| WinMTR statistics |

| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |

|------------------------------------------------|------|------|------|------|------|------|

| Linksys05950 - 0 | 202 | 202 | 0 | 0 | 15 | 0 |

| 10.1.10.1 - 0 | 202 | 202 | 1 | 4 | 60 | 6 |

| 96.120.84.61 - 0 | 202 | 202 | 11 | 17 | 128 | 18 |

|xe-1-0-1-sur03.clovis.ca.ccal.comcast.net - 0 | 202 | 202 | 11 | 18 | 115 | 13 |

|ae-24-ar01.sacramento.ca.ccal.comcast.net - 0 | 202 | 202 | 15 | 26 | 136 | 50 |

|be-33667-cr01.sunnyvale.ca.ibone.comcast.net - 0 | 202 | 202 | 17 | 26 | 117 | 30 |

|be-10925-cr01.9greatoaks.ca.ibone.comcast.net - 0 | 202 | 202 | 19 | 27 | 94 | 29 |

|hu-0-17-0-1-pe03.11greatoaks.ca.ibone.comcast.net - 4 | 178 | 172 | 19 | 25 | 70 | 32 |

| 192.205.32.213 - 4 | 178 | 172 | 22 | 34 | 126 | 23 |

| cr1.sffca.ip.att.net - 4 | 178 | 172 | 22 | 30 | 73 | 28 |

| 12.123.254.61 - 4 | 178 | 172 | 21 | 27 | 70 | 23 |

| No response from host - 100 | 41 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 41 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 41 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 41 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 41 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 41 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 41 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 41 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 41 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 41 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 41 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 41 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 41 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 41 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 41 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 41 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 41 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 41 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 41 | 0 | 0 | 0 | 0 | 0 |

|________________________________________________|______|______|______|______|______|______|

WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

 

I have many WINMTR reports showing packet loss at be-33667-cr01.sunnyvale.ca.ibone.comcast.net

That is 14 packets at that server in less than an hour, i suffered 3 discconects during this session.

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| Linksys05950 - 0 | 7670 | 7670 | 0 | 0 | 26 | 0 |
| 10.1.10.1 - 0 | 7664 | 7664 | 1 | 5 | 145 | 1 |
| 96.120.84.61 - 0 | 7669 | 7669 | 9 | 16 | 340 | 19 |
|xe-0-2-1-sur03.clovis.ca.ccal.comcast.net - 1 | 7666 | 7665 | 9 | 17 | 340 | 11 |
|ae-24-ar01.sacramento.ca.ccal.comcast.net - 0 | 7669 | 7669 | 13 | 24 | 226 | 21 |
|be-33667-cr01.sunnyvale.ca.ibone.comcast.net - 1 | 7580 | 7556 | 17 | 27 | 193 | 27 |
|be-10925-cr01.9greatoaks.ca.ibone.comcast.net - 0 | 7669 | 7669 | 19 | 29 | 249 | 22 |
|hu-0-16-0-1-pe03.11greatoaks.ca.ibone.comcast.net - 0 | 7669 | 7669 | 18 | 25 | 343 | 35 |
| 192.205.32.213 - 0 | 7669 | 7669 | 20 | 35 | 242 | 36 |
| cr2.sffca.ip.att.net - 0 | 7669 | 7669 | 20 | 31 | 253 | 38 |
| 12.123.244.65 - 0 | 7669 | 7669 | 19 | 27 | 332 | 31 |
| No response from host - 100 | 1535 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 1535 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 1535 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 1535 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 1535 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 1535 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 1535 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 1535 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 1535 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 1535 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 1535 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 1535 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 1535 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 1535 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 1535 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 1535 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 1535 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 1535 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 1535 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

0 Kudos
Reply
39 REPLIES 39
jtitley16
Frequent Contributor

Re: Intermitent Packet Loss for all of June with no resolution.

So apperently despite the logs showing high packet loss on your backbone the tier 2 agent noted to customer service to immediately close all tickets regarding packet loss from me.  He could reach some webpages from my gateway so my issue must be resolved right, lets not worry about the logs that show otherwise or anything?  Where do you get this level of IT skills from, cooking fries at McDonalds?

jtitley16
Frequent Contributor

Re: Intermitent Packet Loss for all of June with no resolution.

WHy is this marked as solved?  It's not solved, and no one has contacted me about it.

0 Kudos
Reply
jtitley16
Frequent Contributor

Re: Intermitent Packet Loss for all of June with no resolution.

I thought this was sovled....oh it looks like you just clicked solved even though it wasn't....classic move.

 

Here is another log showing packet loss on your network.....you marked it as solved though...

 

Seems to be an issue at this server:

c-67-182-25-217.hsd1.ca.comcast.net 20.0% 10 18.6 21.2 18.6 25.0 2.2

 

 

TRACEROUTE:
traceroute to 67.182.25.217 (67.182.25.217), 15 hops max, 60 byte packets
1 Blizzard (Blizzard) 0.581 ms 0.614 ms 0.740 ms
2 * * *
3 37.244.1.100 (37.244.1.100) 2.200 ms 2.211 ms 2.217 ms
4 37.244.1.32 (37.244.1.32) 1.911 ms 1.974 ms 2.037 ms
5 te-0-11-0-0-2-pe01.350ecermak.il.ibone.comcast.net (173.167.56.237) 1.910 ms 1.930 ms 1.960 ms
6 hu-2-4-0-1-cr02.350ecermak.il.ibone.comcast.net (68.86.89.245) 4.240 ms 3.099 ms 3.080 ms
7 be-10517-cr02.denver.co.ibone.comcast.net (68.86.85.170) 34.602 ms 33.958 ms 33.958 ms
8 be-11719-cr01.1601milehigh.co.ibone.comcast.net (68.86.86.78) 31.073 ms 31.344 ms 31.586 ms
9 be-10919-cr01.sunnyvale.ca.ibone.comcast.net (68.86.85.153) 52.975 ms 53.123 ms 53.387 ms
10 ae-79-ar01.sacramento.ca.ccal.comcast.net (68.86.93.26) 55.866 ms 55.905 ms 55.930 ms
11 ae-24-sur03.clovis.ca.ccal.comcast.net (162.151.40.130) 57.158 ms 57.185 ms 57.952 ms
12 te-6-1-acr01.clovis.ca.ccal.comcast.net (162.151.83.118) 60.715 ms 60.806 ms 60.828 ms
13 c-67-182-25-217.hsd1.ca.comcast.net (67.182.25.217) 75.697 ms 72.263 ms 72.052 ms


05/07/2016 15:23:05 UTC
--------------------

TRACEROUTE:
traceroute to 67.182.25.217 (67.182.25.217), 15 hops max, 60 byte packets
1 Blizzard (Blizzard) 1.076 ms 1.151 ms 1.298 ms
2 * * *
3 37.244.1.100 (37.244.1.100) 2.022 ms 2.092 ms 2.152 ms
4 37.244.1.32 (37.244.1.32) 1.919 ms 1.954 ms 3.260 ms
5 te-0-11-0-0-2-pe01.350ecermak.il.ibone.comcast.net (173.167.56.237) 1.858 ms 1.930 ms 1.967 ms
6 hu-2-4-0-1-cr02.350ecermak.il.ibone.comcast.net (68.86.89.245) 2.776 ms 2.983 ms 3.013 ms
7 be-10517-cr02.denver.co.ibone.comcast.net (68.86.85.170) 34.534 ms 34.568 ms 34.541 ms
8 be-11719-cr01.1601milehigh.co.ibone.comcast.net (68.86.86.78) 31.106 ms 31.372 ms 31.641 ms
9 be-10919-cr01.sunnyvale.ca.ibone.comcast.net (68.86.85.153) 52.972 ms 53.246 ms 53.489 ms
10 ae-79-ar01.sacramento.ca.ccal.comcast.net (68.86.93.26) 55.879 ms 55.865 ms 55.989 ms
11 ae-24-sur03.clovis.ca.ccal.comcast.net (162.151.40.130) 57.086 ms 57.298 ms 58.015 ms
12 te-6-1-acr01.clovis.ca.ccal.comcast.net (162.151.83.118) 60.697 ms 60.660 ms 60.721 ms
13 c-67-182-25-217.hsd1.ca.comcast.net (67.182.25.217) 75.522 ms * *


05/07/2016 15:23:05 UTC
--------------------

PING:
PING 67.182.25.217 (67.182.25.217) 56(84) bytes of data.
64 bytes from 67.182.25.217: icmp_seq=1 ttl=48 time=71.8 ms
64 bytes from 67.182.25.217: icmp_seq=2 ttl=48 time=72.2 ms
64 bytes from 67.182.25.217: icmp_seq=3 ttl=48 time=73.8 ms
64 bytes from 67.182.25.217: icmp_seq=4 ttl=48 time=73.4 ms

--- 67.182.25.217 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3072ms
rtt min/avg/max/mdev = 71.887/72.867/73.841/0.830 ms


05/07/2016 15:23:05 UTC
--------------------

PING:
PING 67.182.25.217 (67.182.25.217) 56(84) bytes of data.
64 bytes from 67.182.25.217: icmp_seq=1 ttl=48 time=71.6 ms
64 bytes from 67.182.25.217: icmp_seq=2 ttl=48 time=72.5 ms
64 bytes from 67.182.25.217: icmp_seq=3 ttl=48 time=73.1 ms
64 bytes from 67.182.25.217: icmp_seq=4 ttl=48 time=74.3 ms

--- 67.182.25.217 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3072ms
rtt min/avg/max/mdev = 71.679/72.931/74.369/0.977 ms


05/07/2016 15:23:05 UTC
--------------------

TRACEROUTE:
traceroute to 67.182.25.217 (67.182.25.217), 15 hops max, 60 byte packets
1 Blizzard (Blizzard) 0.500 ms 0.529 ms 0.617 ms
2 * * *
3 37.244.0.102 (37.244.0.102) 4.258 ms 4.271 ms 4.276 ms
4 37.244.0.34 (37.244.0.34) 2.004 ms 2.027 ms 2.031 ms
5 te-0-4-0-9-pe02.600wseventh.ca.ibone.comcast.net (173.167.56.217) 1.999 ms 2.019 ms 2.063 ms
6 hu-0-5-0-3-cr02.losangeles.ca.ibone.comcast.net (68.86.83.29) 2.554 ms hu-0-5-0-1-cr02.losangeles.ca.ibone.comcast.net (68.86.83.21) 3.348 ms 3.315 ms
7 ae-79-ar01.fresno.ca.ccal.comcast.net (68.86.93.38) 8.018 ms 8.057 ms 8.058 ms
8 ae-25-sur03.clovis.ca.ccal.comcast.net (162.151.40.134) 9.758 ms 9.774 ms 9.761 ms
9 te-7-1-acr01.clovis.ca.ccal.comcast.net (162.151.83.126) 9.991 ms 9.728 ms 9.777 ms
10 c-67-182-25-217.hsd1.ca.comcast.net (67.182.25.217) 19.338 ms 24.029 ms *


05/07/2016 15:23:07 UTC
--------------------

PING:
PING 67.182.25.217 (67.182.25.217) 56(84) bytes of data.
64 bytes from 67.182.25.217: icmp_seq=2 ttl=51 time=24.5 ms
64 bytes from 67.182.25.217: icmp_seq=3 ttl=51 time=24.1 ms
64 bytes from 67.182.25.217: icmp_seq=4 ttl=51 time=26.0 ms

--- 67.182.25.217 ping statistics ---
4 packets transmitted, 3 received, 25% packet loss, time 3999ms
rtt min/avg/max/mdev = 24.154/24.934/26.099/0.839 ms


05/07/2016 15:23:08 UTC
--------------------

TRACEROUTE:
traceroute to 67.182.25.217 (67.182.25.217), 15 hops max, 60 byte packets
1 Blizzard (Blizzard) 0.442 ms 0.456 ms 0.517 ms
2 * * *
3 37.244.0.102 (37.244.0.102) 3.563 ms 3.577 ms 3.584 ms
4 37.244.0.34 (37.244.0.34) 1.959 ms 1.995 ms 2.061 ms
5 te-0-4-0-9-pe02.600wseventh.ca.ibone.comcast.net (173.167.56.217) 1.928 ms 1.978 ms 2.025 ms
6 hu-0-5-0-1-cr02.losangeles.ca.ibone.comcast.net (68.86.83.21) 2.693 ms hu-0-5-0-0-cr02.losangeles.ca.ibone.comcast.net (68.86.83.17) 3.557 ms hu-0-5-0-3-cr02.losangeles.ca.ibone.comcast.net (68.86.83.29) 3.508 ms
7 ae-79-ar01.fresno.ca.ccal.comcast.net (68.86.93.38) 7.953 ms 8.071 ms 8.032 ms
8 ae-25-sur03.clovis.ca.ccal.comcast.net (162.151.40.134) 9.761 ms 9.769 ms 9.766 ms
9 te-7-1-acr01.clovis.ca.ccal.comcast.net (162.151.83.126) 9.787 ms 9.741 ms 9.741 ms
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 c-67-182-25-217.hsd1.ca.comcast.net (67.182.25.217) 19.233 ms 24.005 ms *


05/07/2016 15:23:09 UTC
--------------------

MTR:
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
1. Blizzard 0.0% 10 0.7 0.6 0.5 0.9 0.1
2. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
3. 37.244.1.100 0.0% 10 2.2 2.3 2.1 3.2 0.3
4. 37.244.1.32 0.0% 10 3.4 2.1 1.8 3.4 0.5
5. te-0-11-0-0-2-pe01.350ecermak.il.ibone.comcast.net 0.0% 10 2.2 2.0 1.8 2.2 0.2
6. hu-2-4-0-1-cr02.350ecermak.il.ibone.comcast.net 0.0% 10 3.9 3.5 2.5 4.3 0.6
7. be-10517-cr02.denver.co.ibone.comcast.net 0.0% 10 33.7 34.4 33.3 35.1 0.6
8. be-11719-cr01.1601milehigh.co.ibone.comcast.net 0.0% 10 31.1 31.2 31.0 31.4 0.1
9. be-10919-cr01.sunnyvale.ca.ibone.comcast.net 0.0% 10 53.3 53.2 53.0 53.3 0.1
10. ae-79-ar01.sacramento.ca.ccal.comcast.net 0.0% 10 56.0 56.2 55.9 57.9 0.6
11. ae-24-sur03.clovis.ca.ccal.comcast.net 0.0% 10 57.2 57.2 57.1 57.2 0.0
12. te-6-1-acr01.clovis.ca.ccal.comcast.net 0.0% 10 60.7 60.7 60.7 60.8 0.0
13. c-67-182-25-217.hsd1.ca.comcast.net 30.0% 10 70.0 74.9 69.3 81.6 4.6


05/07/2016 15:23:05 UTC
--------------------

MTR:
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
1. Blizzard 0.0% 10 0.9 0.7 0.5 0.9 0.1
2. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
3. 37.244.1.100 0.0% 10 2.1 2.2 2.1 2.3 0.1
4. 37.244.1.32 0.0% 10 3.3 2.2 2.0 3.3 0.4
5. te-0-11-0-0-2-pe01.350ecermak.il.ibone.comcast.net 0.0% 10 2.2 2.0 1.8 2.3 0.2
6. hu-2-4-0-1-cr02.350ecermak.il.ibone.comcast.net 0.0% 10 3.9 3.4 2.5 4.0 0.6
7. be-10517-cr02.denver.co.ibone.comcast.net 0.0% 10 33.7 34.5 33.3 35.4 0.7
8. be-11719-cr01.1601milehigh.co.ibone.comcast.net 0.0% 10 31.3 31.2 31.1 31.4 0.1
9. be-10919-cr01.sunnyvale.ca.ibone.comcast.net 0.0% 10 53.1 53.1 53.0 53.6 0.2
10. ae-79-ar01.sacramento.ca.ccal.comcast.net 0.0% 10 56.0 56.2 56.0 57.9 0.6
11. ae-24-sur03.clovis.ca.ccal.comcast.net 0.0% 10 57.2 57.2 57.2 57.2 0.0
12. te-6-1-acr01.clovis.ca.ccal.comcast.net 0.0% 10 60.7 60.7 60.7 60.8 0.0
13. c-67-182-25-217.hsd1.ca.comcast.net 10.0% 10 75.2 74.1 69.4 80.3 3.7


05/07/2016 15:23:05 UTC
--------------------

PING:
PING 67.182.25.217 (67.182.25.217) 56(84) bytes of data.
64 bytes from 67.182.25.217: icmp_seq=2 ttl=51 time=25.2 ms
64 bytes from 67.182.25.217: icmp_seq=3 ttl=51 time=18.8 ms
64 bytes from 67.182.25.217: icmp_seq=4 ttl=51 time=29.6 ms

--- 67.182.25.217 ping statistics ---
4 packets transmitted, 3 received, 25% packet loss, time 3998ms
rtt min/avg/max/mdev = 18.814/24.588/29.684/4.463 ms


05/07/2016 15:23:12 UTC
--------------------

MTR:
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
1. Blizzard 0.0% 10 0.4 0.5 0.3 0.7 0.1
2. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
3. 37.244.0.102 0.0% 10 2.3 2.9 2.1 4.5 0.8
4. 37.244.0.34 0.0% 10 2.0 2.0 2.0 2.1 0.0
5. te-0-4-0-9-pe02.600wseventh.ca.ibone.comcast.net 0.0% 10 2.0 2.0 1.8 2.3 0.1
6. hu-0-5-0-0-cr02.losangeles.ca.ibone.comcast.net 0.0% 10 4.1 3.1 2.2 4.2 0.7
7. ae-79-ar01.fresno.ca.ccal.comcast.net 0.0% 10 8.1 9.3 8.0 16.1 2.8
8. ae-25-sur03.clovis.ca.ccal.comcast.net 0.0% 10 9.9 9.8 9.7 9.9 0.1
9. te-7-1-acr01.clovis.ca.ccal.comcast.net 0.0% 10 9.8 10.1 9.8 11.9 0.6
10. c-67-182-25-217.hsd1.ca.comcast.net 0.0% 10 26.2 22.5 18.0 27.9 3.6


05/07/2016 15:23:07 UTC
--------------------

MTR:
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
1. Blizzard 0.0% 10 0.4 0.6 0.4 0.9 0.2
2. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
3. 37.244.0.102 0.0% 10 2.1 3.0 2.1 4.2 0.7
4. 37.244.0.34 0.0% 10 2.0 2.2 2.0 3.4 0.4
5. te-0-4-0-9-pe02.600wseventh.ca.ibone.comcast.net 0.0% 10 2.1 2.2 2.0 3.4 0.4
6. hu-0-5-0-3-cr02.losangeles.ca.ibone.comcast.net 0.0% 10 2.7 3.4 2.4 4.4 0.7
7. ae-79-ar01.fresno.ca.ccal.comcast.net 0.0% 10 8.0 10.2 8.0 24.0 5.2
8. ae-25-sur03.clovis.ca.ccal.comcast.net 0.0% 10 9.8 10.0 9.8 10.5 0.3
9. te-7-1-acr01.clovis.ca.ccal.comcast.net 0.0% 10 9.8 9.8 9.8 9.9 0.0
10. c-67-182-25-217.hsd1.ca.comcast.net 20.0% 10 18.6 21.2 18.6 25.0 2.2


05/07/2016 15:23:08 UTC

0 Kudos
Reply
Internetguy23
Occasional Visitor

Re: Intermitent Packet Loss for all of June with no resolution.

Having a similar issue when trying to play blizzard games, really frustrating 

0 Kudos
Reply
Respected Member

Re: Intermitent Packet Loss for all of June with no resolution.

Sorry to hear about your service issues. Would you please DM your account information so I can investigate for you?

0 Kudos
Reply
jtitley16
Frequent Contributor

Re: Intermitent Packet Loss for all of June with no resolution.

Are you going to help me the original poster?  If so what do you mean by DM my account info, i posted signed in you should have my account info.  This solution that is marked is not a solution it is just my reply to my own post asking for help, please unmark this as solved, because it is not solved.
0 Kudos
Reply
Respected Member

Re: Intermitent Packet Loss for all of June with no resolution.

My apologies for the incorrect term "DM". I meant private message your account information so we can further correspond on the issue. I have also removed the accepted solution as you requested.

0 Kudos
Reply
jtitley16
Frequent Contributor

Re: Intermitent Packet Loss for all of June with no resolution.

still happening.

 

TRACEROUTE:
traceroute to 67.182.25.217 (67.182.25.217), 15 hops max, 60 byte packets
1 Blizzard (Blizzard) 0.798 ms 0.820 ms 0.874 ms
2 * * *
3 37.244.1.100 (37.244.1.100) 2.176 ms 2.243 ms 2.307 ms
4 37.244.1.32 (37.244.1.32) 1.857 ms 1.902 ms 1.952 ms
5 te-0-11-0-0-2-pe01.350ecermak.il.ibone.comcast.net (173.167.56.237) 1.816 ms 1.842 ms 1.891 ms
6 hu-2-4-0-1-cr02.350ecermak.il.ibone.comcast.net (68.86.89.245) 3.996 ms 2.608 ms 2.597 ms
7 be-10517-cr02.denver.co.ibone.comcast.net (68.86.85.170) 33.188 ms 34.861 ms 34.893 ms
8 be-11719-cr01.1601milehigh.co.ibone.comcast.net (68.86.86.78) 30.932 ms 31.157 ms 31.404 ms
9 be-10919-cr01.sunnyvale.ca.ibone.comcast.net (68.86.85.153) 51.880 ms 51.893 ms 52.105 ms
10 ae-79-ar01.sacramento.ca.ccal.comcast.net (68.86.93.26) 54.692 ms 54.706 ms 54.732 ms
11 ae-24-sur03.clovis.ca.ccal.comcast.net (162.151.40.130) 57.203 ms 57.209 ms 57.204 ms
12 te-6-1-acr01.clovis.ca.ccal.comcast.net (162.151.83.118) 59.832 ms 59.809 ms 59.749 ms
13 c-67-182-25-217.hsd1.ca.comcast.net (67.182.25.217) 75.656 ms 70.252 ms 70.118 ms


09/07/2016 02:04:32 UTC
--------------------

TRACEROUTE:
traceroute to 67.182.25.217 (67.182.25.217), 15 hops max, 60 byte packets
1 Blizzard (Blizzard) 0.837 ms 0.842 ms 0.893 ms
2 * * *
3 37.244.1.100 (37.244.1.100) 1.990 ms 2.130 ms 2.227 ms
4 37.244.1.32 (37.244.1.32) 1.979 ms 2.001 ms 2.052 ms
5 te-0-11-0-0-2-pe01.350ecermak.il.ibone.comcast.net (173.167.56.237) 1.799 ms 1.833 ms 1.861 ms
6 hu-2-4-0-1-cr02.350ecermak.il.ibone.comcast.net (68.86.89.245) 2.262 ms 3.090 ms 3.076 ms
7 be-10517-cr02.denver.co.ibone.comcast.net (68.86.85.170) 33.611 ms 33.220 ms 33.208 ms
8 be-11719-cr01.1601milehigh.co.ibone.comcast.net (68.86.86.78) 30.940 ms 31.038 ms 31.264 ms
9 be-10919-cr01.sunnyvale.ca.ibone.comcast.net (68.86.85.153) 51.838 ms 52.157 ms 52.400 ms
10 ae-79-ar01.sacramento.ca.ccal.comcast.net (68.86.93.26) 54.669 ms 54.730 ms 54.696 ms
11 ae-24-sur03.clovis.ca.ccal.comcast.net (162.151.40.130) 57.177 ms 57.201 ms 57.168 ms
12 te-6-1-acr01.clovis.ca.ccal.comcast.net (162.151.83.118) 59.782 ms 59.796 ms 59.837 ms
13 c-67-182-25-217.hsd1.ca.comcast.net (67.182.25.217) 74.179 ms * *


09/07/2016 02:04:32 UTC
--------------------

PING:
PING 67.182.25.217 (67.182.25.217) 56(84) bytes of data.
64 bytes from 67.182.25.217: icmp_seq=1 ttl=50 time=73.5 ms
64 bytes from 67.182.25.217: icmp_seq=2 ttl=50 time=73.2 ms
64 bytes from 67.182.25.217: icmp_seq=3 ttl=50 time=81.8 ms
64 bytes from 67.182.25.217: icmp_seq=4 ttl=50 time=72.4 ms

--- 67.182.25.217 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3071ms
rtt min/avg/max/mdev = 72.475/75.283/81.838/3.805 ms


09/07/2016 02:04:32 UTC
--------------------

PING:
PING 67.182.25.217 (67.182.25.217) 56(84) bytes of data.
64 bytes from 67.182.25.217: icmp_seq=1 ttl=50 time=69.2 ms
64 bytes from 67.182.25.217: icmp_seq=2 ttl=50 time=69.4 ms
64 bytes from 67.182.25.217: icmp_seq=3 ttl=50 time=69.6 ms
64 bytes from 67.182.25.217: icmp_seq=4 ttl=50 time=68.8 ms

--- 67.182.25.217 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3066ms
rtt min/avg/max/mdev = 68.803/69.272/69.640/0.305 ms


09/07/2016 02:04:32 UTC
--------------------

TRACEROUTE:
traceroute to 67.182.25.217 (67.182.25.217), 15 hops max, 60 byte packets
1 Blizzard (Blizzard) 0.421 ms 0.469 ms 0.550 ms
2 * * *
3 37.244.0.102 (37.244.0.102) 3.540 ms 3.555 ms 3.559 ms
4 37.244.0.34 (37.244.0.34) 2.021 ms 2.163 ms 2.170 ms
5 te-0-4-0-9-pe02.600wseventh.ca.ibone.comcast.net (173.167.56.217) 2.976 ms 2.998 ms 3.003 ms
6 hu-0-5-0-0-cr02.losangeles.ca.ibone.comcast.net (68.86.83.17) 2.583 ms hu-0-5-0-2-cr02.losangeles.ca.ibone.comcast.net (68.86.83.25) 3.327 ms hu-1-0-0-0-cr02.losangeles.ca.ibone.comcast.net (68.86.88.9) 2.564 ms
7 ae-79-ar01.fresno.ca.ccal.comcast.net (68.86.93.38) 7.995 ms 8.020 ms 8.020 ms
8 ae-25-sur03.clovis.ca.ccal.comcast.net (162.151.40.134) 16.056 ms 16.008 ms 15.992 ms
9 te-7-1-acr01.clovis.ca.ccal.comcast.net (162.151.83.126) 16.094 ms 16.264 ms 16.244 ms
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *


09/07/2016 02:04:34 UTC
--------------------

PING:
PING 67.182.25.217 (67.182.25.217) 56(84) bytes of data.
64 bytes from 67.182.25.217: icmp_seq=3 ttl=50 time=30.5 ms
64 bytes from 67.182.25.217: icmp_seq=4 ttl=50 time=32.9 ms

--- 67.182.25.217 ping statistics ---
4 packets transmitted, 2 received, 50% packet loss, time 3999ms
rtt min/avg/max/mdev = 30.593/31.749/32.905/1.156 ms


09/07/2016 02:04:35 UTC
--------------------

MTR:
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
1. Blizzard 0.0% 10 0.4 0.6 0.4 0.8 0.1
2. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
3. 37.244.1.100 0.0% 10 2.2 2.3 2.1 3.3 0.4
4. 37.244.1.32 0.0% 10 2.0 3.0 1.9 4.3 1.0
5. te-0-11-0-0-2-pe01.350ecermak.il.ibone.comcast.net 0.0% 10 2.1 2.1 1.8 2.3 0.1
6. hu-2-4-0-1-cr02.350ecermak.il.ibone.comcast.net 0.0% 10 2.3 3.2 2.3 4.3 0.8
7. be-10517-cr02.denver.co.ibone.comcast.net 0.0% 10 34.2 34.3 33.5 35.3 0.5
8. be-11719-cr01.1601milehigh.co.ibone.comcast.net 0.0% 10 31.0 31.0 31.0 31.1 0.0
9. be-10919-cr01.sunnyvale.ca.ibone.comcast.net 0.0% 10 52.0 51.9 51.8 52.0 0.1
10. ae-79-ar01.sacramento.ca.ccal.comcast.net 0.0% 10 54.8 56.4 54.7 70.9 5.1
11. ae-24-sur03.clovis.ca.ccal.comcast.net 0.0% 10 57.2 57.3 57.2 57.4 0.0
12. te-6-1-acr01.clovis.ca.ccal.comcast.net 0.0% 10 59.9 59.9 59.8 60.0 0.1
13. c-67-182-25-217.hsd1.ca.comcast.net 0.0% 10 69.5 77.6 69.0 86.1 7.2


09/07/2016 02:04:32 UTC
--------------------

MTR:
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
1. Blizzard 0.0% 10 0.5 0.6 0.5 1.2 0.2
2. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
3. 37.244.1.100 0.0% 10 2.2 2.4 2.1 3.5 0.5
4. 37.244.1.32 0.0% 10 1.9 2.1 1.9 3.2 0.4
5. te-0-11-0-0-2-pe01.350ecermak.il.ibone.comcast.net 0.0% 10 1.9 2.0 1.7 2.4 0.2
6. hu-2-4-0-1-cr02.350ecermak.il.ibone.comcast.net 0.0% 10 2.1 3.0 2.1 3.8 0.6
7. be-10517-cr02.denver.co.ibone.comcast.net 0.0% 10 34.6 34.5 33.6 35.2 0.5
8. be-11719-cr01.1601milehigh.co.ibone.comcast.net 0.0% 10 31.1 31.0 30.9 31.1 0.1
9. be-10919-cr01.sunnyvale.ca.ibone.comcast.net 0.0% 10 51.9 51.9 51.8 52.0 0.0
10. ae-79-ar01.sacramento.ca.ccal.comcast.net 0.0% 10 54.8 58.1 54.7 85.4 9.6
11. ae-24-sur03.clovis.ca.ccal.comcast.net 0.0% 10 57.3 57.4 57.2 58.3 0.3
12. te-6-1-acr01.clovis.ca.ccal.comcast.net 0.0% 10 59.9 59.9 59.8 60.0 0.0
13. c-67-182-25-217.hsd1.ca.comcast.net 80.0% 10 71.4 70.0 68.7 71.4 1.9


09/07/2016 02:04:32 UTC
--------------------

TRACEROUTE:
traceroute to 67.182.25.217 (67.182.25.217), 15 hops max, 60 byte packets
1 Blizzard (Blizzard) 0.373 ms 0.425 ms 0.562 ms
2 * * *
3 37.244.0.102 (37.244.0.102) 3.224 ms 3.241 ms 3.248 ms
4 37.244.0.34 (37.244.0.34) 1.893 ms 1.912 ms 1.956 ms
5 te-0-4-0-9-pe02.600wseventh.ca.ibone.comcast.net (173.167.56.217) 1.907 ms 3.106 ms 3.125 ms
6 hu-1-0-0-1-cr02.losangeles.ca.ibone.comcast.net (68.86.88.13) 2.957 ms hu-0-5-0-2-cr02.losangeles.ca.ibone.comcast.net (68.86.83.25) 4.478 ms hu-0-5-0-1-cr02.losangeles.ca.ibone.comcast.net (68.86.83.21) 4.469 ms
7 ae-79-ar01.fresno.ca.ccal.comcast.net (68.86.93.38) 7.943 ms 8.010 ms 8.003 ms
8 ae-25-sur03.clovis.ca.ccal.comcast.net (162.151.40.134) 16.045 ms 16.047 ms 16.002 ms
9 te-7-1-acr01.clovis.ca.ccal.comcast.net (162.151.83.126) 15.988 ms 16.092 ms 16.090 ms
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *


09/07/2016 02:04:38 UTC
--------------------

MTR:
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
1. Blizzard 0.0% 10 0.4 0.4 0.3 0.5 0.0
2. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
3. 37.244.0.102 0.0% 10 2.2 3.3 2.1 4.9 0.9
4. 37.244.0.34 0.0% 10 2.1 2.0 1.9 2.4 0.1
5. te-0-4-0-9-pe02.600wseventh.ca.ibone.comcast.net 0.0% 10 2.1 2.1 1.9 2.3 0.1
6. hu-0-5-0-3-cr02.losangeles.ca.ibone.comcast.net 0.0% 10 4.5 3.5 2.3 4.5 0.7
7. ae-79-ar01.fresno.ca.ccal.comcast.net 0.0% 10 10.2 8.3 8.0 10.2 0.7
8. ae-25-sur03.clovis.ca.ccal.comcast.net 0.0% 10 16.2 16.2 16.0 16.6 0.2
9. te-7-1-acr01.clovis.ca.ccal.comcast.net 0.0% 10 16.4 16.5 16.1 19.0 0.9
10. c-67-182-25-217.hsd1.ca.comcast.net 0.0% 10 32.6 30.5 25.6 35.6 4.1


09/07/2016 02:04:34 UTC
--------------------

PING:
PING 67.182.25.217 (67.182.25.217) 56(84) bytes of data.
64 bytes from 67.182.25.217: icmp_seq=4 ttl=50 time=35.2 ms

--- 67.182.25.217 ping statistics ---
4 packets transmitted, 1 received, 75% packet loss, time 5005ms
rtt min/avg/max/mdev = 35.243/35.243/35.243/0.000 ms


09/07/2016 02:04:39 UTC
--------------------

MTR:
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
1. Blizzard 0.0% 10 0.4 0.4 0.3 0.7 0.1
2. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
3. 37.244.0.102 0.0% 10 4.5 3.3 2.1 4.5 0.7
4. 37.244.0.34 0.0% 10 1.9 2.0 1.9 2.1 0.1
5. te-0-4-0-9-pe02.600wseventh.ca.ibone.comcast.net 0.0% 10 4.0 2.3 1.9 4.0 0.7
6. hu-0-5-0-0-cr02.losangeles.ca.ibone.comcast.net 0.0% 10 3.7 3.5 2.6 4.3 0.5
7. ae-79-ar01.fresno.ca.ccal.comcast.net 0.0% 10 8.1 8.1 8.0 8.1 0.0
8. ae-25-sur03.clovis.ca.ccal.comcast.net 0.0% 10 16.0 16.1 16.0 16.4 0.1
9. te-7-1-acr01.clovis.ca.ccal.comcast.net 0.0% 10 16.1 16.1 16.0 16.3 0.1
10. c-67-182-25-217.hsd1.ca.comcast.net 10.0% 10 31.4 30.4 24.9 40.5 4.8


09/07/2016 02:04:35 UTC
--------------------

 

0 Kudos
Reply
jtitley16
Frequent Contributor

Re: Intermitent Packet Loss for all of June with no resolution.

c-67-182-25-217.hsd1.ca.comcast.net 80.0% 10 71.4 70.0 68.7 71.4 1.9

0 Kudos
Reply
Respected Member

Re: Intermitent Packet Loss for all of June with no resolution.

Thank you,

 

When you have a chance will you please test your services again to see it the issue has been resolved?

0 Kudos
Reply
jtitley16
Frequent Contributor

Re: Intermitent Packet Loss for all of June with no resolution.

its been more than 7 weeks and its getting worse.  

 

TRACEROUTE:
traceroute to 67.182.25.217 (67.182.25.217), 15 hops max, 60 byte packets
1 Blizzard (Blizzard) 0.528 ms 0.669 ms 0.808 ms
2 * * *
3 37.244.1.100 (37.244.1.100) 2.199 ms 3.432 ms 3.445 ms
4 37.244.1.32 (37.244.1.32) 2.533 ms 4.082 ms 4.094 ms
5 te-0-11-0-0-2-pe01.350ecermak.il.ibone.comcast.net (173.167.56.237) 1.776 ms 2.026 ms 2.033 ms
6 hu-2-4-0-1-cr02.350ecermak.il.ibone.comcast.net (68.86.89.245) 2.342 ms 3.294 ms 3.371 ms
7 be-10517-cr02.denver.co.ibone.comcast.net (68.86.85.170) 34.741 ms 34.234 ms 33.981 ms
8 * * *
9 be-10919-cr01.sunnyvale.ca.ibone.comcast.net (68.86.85.153) 51.851 ms 51.856 ms 52.297 ms
10 ae-79-ar01.sacramento.ca.ccal.comcast.net (68.86.93.26) 54.774 ms 54.800 ms 54.679 ms
11 ae-24-sur03.clovis.ca.ccal.comcast.net (162.151.40.130) 57.369 ms 57.553 ms 57.527 ms
12 te-6-1-acr01.clovis.ca.ccal.comcast.net (162.151.83.118) 59.905 ms 59.810 ms 59.781 ms
13 c-67-182-25-217.hsd1.ca.comcast.net (67.182.25.217) 69.493 ms 71.443 ms 71.429 ms


16/07/2016 04:08:45 UTC
--------------------

TRACEROUTE:
traceroute to 67.182.25.217 (67.182.25.217), 15 hops max, 60 byte packets
1 Blizzard (Blizzard) 0.903 ms 1.035 ms 1.202 ms
2 * * *
3 37.244.1.100 (37.244.1.100) 3.391 ms 3.394 ms 3.408 ms
4 37.244.1.32 (37.244.1.32) 4.045 ms 4.036 ms 4.049 ms
5 te-0-11-0-0-2-pe01.350ecermak.il.ibone.comcast.net (173.167.56.237) 2.178 ms 2.197 ms 2.247 ms
6 hu-2-4-0-1-cr02.350ecermak.il.ibone.comcast.net (68.86.89.245) 2.277 ms 3.076 ms 3.066 ms
7 be-10517-cr02.denver.co.ibone.comcast.net (68.86.85.170) 34.422 ms 33.755 ms 33.747 ms
8 * * *
9 be-10919-cr01.sunnyvale.ca.ibone.comcast.net (68.86.85.153) 52.057 ms 52.564 ms 52.163 ms
10 ae-79-ar01.sacramento.ca.ccal.comcast.net (68.86.93.26) 54.794 ms 54.797 ms 54.717 ms
11 ae-24-sur03.clovis.ca.ccal.comcast.net (162.151.40.130) 57.369 ms 57.542 ms 57.531 ms
12 te-6-1-acr01.clovis.ca.ccal.comcast.net (162.151.83.118) 59.955 ms 59.761 ms 59.793 ms
13 c-67-182-25-217.hsd1.ca.comcast.net (67.182.25.217) 74.038 ms 71.435 ms 71.466 ms


16/07/2016 04:08:45 UTC
--------------------

PING:
PING 67.182.25.217 (67.182.25.217) 56(84) bytes of data.
64 bytes from 67.182.25.217: icmp_seq=1 ttl=50 time=71.9 ms
64 bytes from 67.182.25.217: icmp_seq=2 ttl=50 time=72.8 ms
64 bytes from 67.182.25.217: icmp_seq=3 ttl=50 time=80.2 ms
64 bytes from 67.182.25.217: icmp_seq=4 ttl=50 time=71.5 ms

--- 67.182.25.217 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3069ms
rtt min/avg/max/mdev = 71.548/74.160/80.287/3.579 ms


16/07/2016 04:08:45 UTC
--------------------

PING:
PING 67.182.25.217 (67.182.25.217) 56(84) bytes of data.
64 bytes from 67.182.25.217: icmp_seq=1 ttl=50 time=72.1 ms
64 bytes from 67.182.25.217: icmp_seq=2 ttl=50 time=70.4 ms
64 bytes from 67.182.25.217: icmp_seq=3 ttl=50 time=71.3 ms
64 bytes from 67.182.25.217: icmp_seq=4 ttl=50 time=78.3 ms

--- 67.182.25.217 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3077ms
rtt min/avg/max/mdev = 70.453/73.054/78.305/3.091 ms


16/07/2016 04:08:45 UTC
--------------------

TRACEROUTE:
traceroute to 67.182.25.217 (67.182.25.217), 15 hops max, 60 byte packets
1 Blizzard (Blizzard) 1.097 ms 1.155 ms 1.256 ms
2 * * *
3 37.244.0.102 (37.244.0.102) 3.027 ms 3.043 ms 3.048 ms
4 37.244.0.34 (37.244.0.34) 1.850 ms 1.896 ms 1.937 ms
5 te-0-4-0-9-pe02.600wseventh.ca.ibone.comcast.net (173.167.56.217) 1.879 ms 1.916 ms 1.960 ms
6 hu-0-5-0-0-cr02.losangeles.ca.ibone.comcast.net (68.86.83.17) 3.543 ms hu-0-5-0-1-cr02.losangeles.ca.ibone.comcast.net (68.86.83.21) 3.787 ms hu-0-5-0-2-cr02.losangeles.ca.ibone.comcast.net (68.86.83.25) 3.766 ms
7 ae-79-ar01.fresno.ca.ccal.comcast.net (68.86.93.38) 8.084 ms 8.087 ms 8.086 ms
8 ae-25-sur03.clovis.ca.ccal.comcast.net (162.151.40.134) 16.111 ms 16.127 ms 16.114 ms
9 te-7-1-acr01.clovis.ca.ccal.comcast.net (162.151.83.126) 16.049 ms 16.153 ms 16.181 ms
10 c-67-182-25-217.hsd1.ca.comcast.net (67.182.25.217) 25.612 ms 30.327 ms *


16/07/2016 04:08:47 UTC
--------------------

PING:
PING 67.182.25.217 (67.182.25.217) 56(84) bytes of data.
64 bytes from 67.182.25.217: icmp_seq=2 ttl=50 time=31.4 ms
64 bytes from 67.182.25.217: icmp_seq=3 ttl=50 time=28.2 ms
64 bytes from 67.182.25.217: icmp_seq=4 ttl=50 time=38.4 ms

--- 67.182.25.217 ping statistics ---
4 packets transmitted, 3 received, 25% packet loss, time 3997ms
rtt min/avg/max/mdev = 28.266/32.696/38.416/4.242 ms


16/07/2016 04:08:48 UTC
--------------------

TRACEROUTE:
traceroute to 67.182.25.217 (67.182.25.217), 15 hops max, 60 byte packets
1 Blizzard (Blizzard) 0.369 ms 0.419 ms 0.559 ms
2 * * *
3 37.244.0.102 (37.244.0.102) 2.142 ms 2.181 ms 2.258 ms
4 37.244.0.34 (37.244.0.34) 2.034 ms 2.049 ms 2.111 ms
5 te-0-4-0-9-pe02.600wseventh.ca.ibone.comcast.net (173.167.56.217) 1.952 ms 2.007 ms 2.138 ms
6 hu-0-5-0-3-cr02.losangeles.ca.ibone.comcast.net (68.86.83.29) 3.737 ms hu-1-0-0-1-cr02.losangeles.ca.ibone.comcast.net (68.86.88.13) 2.847 ms hu-0-5-0-3-cr02.losangeles.ca.ibone.comcast.net (68.86.83.29) 2.664 ms
7 ae-79-ar01.fresno.ca.ccal.comcast.net (68.86.93.38) 8.525 ms 8.802 ms 8.804 ms
8 ae-25-sur03.clovis.ca.ccal.comcast.net (162.151.40.134) 16.074 ms 16.080 ms 16.011 ms
9 te-7-1-acr01.clovis.ca.ccal.comcast.net (162.151.83.126) 16.115 ms 16.159 ms 16.047 ms
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *


16/07/2016 04:08:49 UTC
--------------------

MTR:
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
1. Blizzard 0.0% 10 0.5 1.6 0.5 10.7 3.2
2. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
3. 37.244.1.100 0.0% 10 3.5 2.7 2.1 3.5 0.7
4. 37.244.1.32 0.0% 10 3.3 2.4 1.9 3.4 0.7
5. te-0-11-0-0-2-pe01.350ecermak.il.ibone.comcast.net 0.0% 10 1.9 1.9 1.8 2.2 0.2
6. hu-2-4-0-1-cr02.350ecermak.il.ibone.comcast.net 0.0% 10 2.4 3.2 2.3 3.9 0.6
7. be-10517-cr02.denver.co.ibone.comcast.net 0.0% 10 35.0 34.3 33.5 35.4 0.7
8. be-11719-cr01.1601milehigh.co.ibone.comcast.net 30.0% 10 31.1 31.2 31.1 31.3 0.1
9. be-10919-cr01.sunnyvale.ca.ibone.comcast.net 0.0% 10 52.1 51.9 51.9 52.1 0.1
10. ae-79-ar01.sacramento.ca.ccal.comcast.net 0.0% 10 54.8 55.0 54.8 55.5 0.3
11. ae-24-sur03.clovis.ca.ccal.comcast.net 0.0% 10 57.5 58.6 57.4 61.6 1.6
12. te-6-1-acr01.clovis.ca.ccal.comcast.net 0.0% 10 59.9 59.9 59.8 60.4 0.2
13. c-67-182-25-217.hsd1.ca.comcast.net 20.0% 10 70.3 71.1 68.9 77.4 2.9


16/07/2016 04:08:45 UTC
--------------------

MTR:
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
1. Blizzard 0.0% 10 0.6 1.5 0.4 10.4 3.1
2. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
3. 37.244.1.100 0.0% 10 2.2 2.6 1.9 4.3 0.8
4. 37.244.1.32 0.0% 10 2.0 2.3 1.9 3.3 0.6
5. te-0-11-0-0-2-pe01.350ecermak.il.ibone.comcast.net 0.0% 10 1.9 2.0 1.8 2.1 0.1
6. hu-2-4-0-1-cr02.350ecermak.il.ibone.comcast.net 0.0% 10 2.5 3.4 2.5 4.0 0.5
7. be-10517-cr02.denver.co.ibone.comcast.net 0.0% 10 35.0 34.5 33.5 35.3 0.7
8. be-11719-cr01.1601milehigh.co.ibone.comcast.net 40.0% 10 31.4 31.2 31.0 31.5 0.2
9. be-10919-cr01.sunnyvale.ca.ibone.comcast.net 0.0% 10 51.9 51.9 51.8 52.1 0.1
10. ae-79-ar01.sacramento.ca.ccal.comcast.net 0.0% 10 54.8 54.9 54.8 55.2 0.1
11. ae-24-sur03.clovis.ca.ccal.comcast.net 0.0% 10 57.4 58.5 57.4 61.2 1.4
12. te-6-1-acr01.clovis.ca.ccal.comcast.net 0.0% 10 59.9 59.9 59.8 60.2 0.1
13. c-67-182-25-217.hsd1.ca.comcast.net 30.0% 10 75.3 74.7 68.7 84.3 5.1


16/07/2016 04:08:45 UTC
--------------------

PING:
PING 67.182.25.217 (67.182.25.217) 56(84) bytes of data.
64 bytes from 67.182.25.217: icmp_seq=1 ttl=50 time=28.9 ms
64 bytes from 67.182.25.217: icmp_seq=2 ttl=50 time=27.3 ms
64 bytes from 67.182.25.217: icmp_seq=3 ttl=50 time=27.8 ms
64 bytes from 67.182.25.217: icmp_seq=4 ttl=50 time=30.3 ms

--- 67.182.25.217 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3029ms
rtt min/avg/max/mdev = 27.341/28.631/30.399/1.187 ms


16/07/2016 04:08:52 UTC
--------------------

MTR:
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
1. Blizzard 0.0% 10 0.5 0.6 0.4 1.0 0.2
2. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
3. 37.244.0.102 0.0% 10 2.6 2.2 2.0 2.6 0.2
4. 37.244.0.34 0.0% 10 1.9 2.0 1.9 2.1 0.1
5. te-0-4-0-9-pe02.600wseventh.ca.ibone.comcast.net 0.0% 10 2.0 2.1 1.9 2.5 0.2
6. hu-1-0-0-0-cr02.losangeles.ca.ibone.comcast.net 0.0% 10 2.5 3.4 2.4 4.2 0.7
7. ae-79-ar01.fresno.ca.ccal.comcast.net 0.0% 10 8.0 10.3 8.0 30.3 7.0
8. ae-25-sur03.clovis.ca.ccal.comcast.net 0.0% 10 16.1 16.1 16.0 16.1 0.0
9. te-7-1-acr01.clovis.ca.ccal.comcast.net 0.0% 10 16.1 16.2 16.0 16.5 0.1
10. c-67-182-25-217.hsd1.ca.comcast.net 0.0% 10 26.4 29.9 24.8 39.6 5.4


16/07/2016 04:08:47 UTC
--------------------

MTR:
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
1. Blizzard 0.0% 10 0.6 0.4 0.4 0.6 0.1
2. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
3. 37.244.0.102 0.0% 10 2.1 2.7 2.1 6.0 1.2
4. 37.244.0.34 0.0% 10 2.0 2.0 1.8 2.1 0.1
5. te-0-4-0-9-pe02.600wseventh.ca.ibone.comcast.net 0.0% 10 2.8 2.1 1.9 2.8 0.3
6. hu-1-0-0-0-cr02.losangeles.ca.ibone.comcast.net 0.0% 10 3.6 3.4 2.4 4.3 0.8
7. ae-79-ar01.fresno.ca.ccal.comcast.net 0.0% 10 8.1 8.4 8.0 9.0 0.4
8. ae-25-sur03.clovis.ca.ccal.comcast.net 0.0% 10 16.1 16.1 16.0 16.1 0.0
9. te-7-1-acr01.clovis.ca.ccal.comcast.net 0.0% 10 16.1 16.2 16.0 17.1 0.3
10. c-67-182-25-217.hsd1.ca.comcast.net 0.0% 10 25.3 30.4 24.9 56.0 9.5


16/07/2016 04:08:48 UTC
--------------------

 

 

BATTLE.NET LOOKING-GLASS 2.0.0
Your IP Address
67.182.25.217
Looking-Glass
Blizzard Network Diagnostic Tool

SELECT THE REGION

SELECT THE SERVICE

SELECT THE REALM

SELECT THE TESTS
MTR
Traceroute
Ping
Run Test Test Result
Copy Result to Clipboard
TRACEROUTE:
traceroute to 67.182.25.217 (67.182.25.217), 15 hops max, 60 byte packets
1 Blizzard (Blizzard) 0.844 ms 0.862 ms 1.042 ms
2 * * *
3 37.244.1.100 (37.244.1.100) 3.368 ms 3.393 ms 3.403 ms
4 37.244.1.32 (37.244.1.32) 1.937 ms 2.095 ms 2.153 ms
5 te-0-11-0-0-2-pe01.350ecermak.il.ibone.comcast.net (173.167.56.237) 2.097 ms 2.193 ms 2.304 ms
6 hu-2-4-0-1-cr02.350ecermak.il.ibone.comcast.net (68.86.89.245) 2.461 ms 2.999 ms 3.000 ms
7 be-10517-cr02.denver.co.ibone.comcast.net (68.86.85.170) 33.499 ms 35.534 ms 35.414 ms
8 be-11719-cr01.1601milehigh.co.ibone.comcast.net (68.86.86.78) 31.087 ms 31.370 ms 31.637 ms
9 be-10919-cr01.sunnyvale.ca.ibone.comcast.net (68.86.85.153) 51.838 ms 51.964 ms 51.786 ms
10 ae-79-ar01.sacramento.ca.ccal.comcast.net (68.86.93.26) 54.732 ms 54.755 ms 54.719 ms
11 ae-24-sur03.clovis.ca.ccal.comcast.net (162.151.40.130) 57.406 ms 57.375 ms 57.360 ms
12 te-6-1-acr01.clovis.ca.ccal.comcast.net (162.151.83.118) 60.287 ms 59.817 ms 61.012 ms
13 c-67-182-25-217.hsd1.ca.comcast.net (67.182.25.217) 69.992 ms 69.494 ms 73.970 ms


16/07/2016 04:07:47 UTC
--------------------

TRACEROUTE:
traceroute to 67.182.25.217 (67.182.25.217), 15 hops max, 60 byte packets
1 Blizzard (Blizzard) 0.645 ms 1.145 ms 1.288 ms
2 * * *
3 37.244.1.100 (37.244.1.100) 3.407 ms 3.420 ms 3.433 ms
4 37.244.1.32 (37.244.1.32) 3.722 ms 3.732 ms 3.735 ms
5 te-0-11-0-0-2-pe01.350ecermak.il.ibone.comcast.net (173.167.56.237) 2.423 ms 2.437 ms 2.518 ms
6 hu-2-4-0-1-cr02.350ecermak.il.ibone.comcast.net (68.86.89.245) 2.463 ms 3.049 ms 3.039 ms
7 be-10517-cr02.denver.co.ibone.comcast.net (68.86.85.170) 33.544 ms 35.044 ms 35.085 ms
8 be-11719-cr01.1601milehigh.co.ibone.comcast.net (68.86.86.78) 31.578 ms 31.682 ms 31.170 ms
9 be-10919-cr01.sunnyvale.ca.ibone.comcast.net (68.86.85.153) 51.970 ms 52.279 ms 52.208 ms
10 ae-79-ar01.sacramento.ca.ccal.comcast.net (68.86.93.26) 54.781 ms 54.797 ms 54.715 ms
11 ae-24-sur03.clovis.ca.ccal.comcast.net (162.151.40.130) 57.385 ms 57.362 ms 57.429 ms
12 te-6-1-acr01.clovis.ca.ccal.comcast.net (162.151.83.118) 59.876 ms 59.761 ms 61.085 ms
13 c-67-182-25-217.hsd1.ca.comcast.net (67.182.25.217) 74.631 ms 73.132 ms 72.816 ms


16/07/2016 04:07:47 UTC
--------------------

PING:
PING 67.182.25.217 (67.182.25.217) 56(84) bytes of data.
64 bytes from 67.182.25.217: icmp_seq=1 ttl=50 time=74.3 ms
64 bytes from 67.182.25.217: icmp_seq=2 ttl=50 time=69.5 ms
64 bytes from 67.182.25.217: icmp_seq=3 ttl=50 time=69.0 ms
64 bytes from 67.182.25.217: icmp_seq=4 ttl=50 time=68.6 ms

--- 67.182.25.217 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3067ms
rtt min/avg/max/mdev = 68.608/70.395/74.362/2.316 ms


16/07/2016 04:07:47 UTC
--------------------

PING:
PING 67.182.25.217 (67.182.25.217) 56(84) bytes of data.
64 bytes from 67.182.25.217: icmp_seq=1 ttl=50 time=69.4 ms
64 bytes from 67.182.25.217: icmp_seq=2 ttl=50 time=74.5 ms
64 bytes from 67.182.25.217: icmp_seq=3 ttl=50 time=73.5 ms
64 bytes from 67.182.25.217: icmp_seq=4 ttl=50 time=73.3 ms

--- 67.182.25.217 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3073ms
rtt min/avg/max/mdev = 69.427/72.704/74.518/1.945 ms


16/07/2016 04:07:47 UTC
--------------------

TRACEROUTE:
traceroute to 67.182.25.217 (67.182.25.217), 15 hops max, 60 byte packets
1 Blizzard (Blizzard) 0.445 ms 0.496 ms 0.610 ms
2 * * *
3 37.244.0.102 (37.244.0.102) 3.340 ms 3.359 ms 3.361 ms
4 37.244.0.34 (37.244.0.34) 2.010 ms 2.028 ms 2.034 ms
5 te-0-4-0-9-pe02.600wseventh.ca.ibone.comcast.net (173.167.56.217) 1.981 ms 2.030 ms 2.068 ms
6 hu-0-5-0-1-cr02.losangeles.ca.ibone.comcast.net (68.86.83.21) 6.061 ms hu-1-0-0-0-cr02.losangeles.ca.ibone.comcast.net (68.86.88.9) 3.071 ms 3.066 ms
7 ae-79-ar01.fresno.ca.ccal.comcast.net (68.86.93.38) 9.200 ms 8.455 ms 8.423 ms
8 ae-25-sur03.clovis.ca.ccal.comcast.net (162.151.40.134) 16.044 ms 16.078 ms 16.079 ms
9 te-7-1-acr01.clovis.ca.ccal.comcast.net (162.151.83.126) 16.017 ms 16.216 ms 16.016 ms
10 c-67-182-25-217.hsd1.ca.comcast.net (67.182.25.217) 26.261 ms 29.860 ms *


16/07/2016 04:07:49 UTC
--------------------

PING:
PING 67.182.25.217 (67.182.25.217) 56(84) bytes of data.
64 bytes from 67.182.25.217: icmp_seq=1 ttl=50 time=25.6 ms
64 bytes from 67.182.25.217: icmp_seq=2 ttl=50 time=29.1 ms
64 bytes from 67.182.25.217: icmp_seq=3 ttl=50 time=28.8 ms
64 bytes from 67.182.25.217: icmp_seq=4 ttl=50 time=30.3 ms

--- 67.182.25.217 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3029ms
rtt min/avg/max/mdev = 25.624/28.494/30.305/1.746 ms


16/07/2016 04:07:50 UTC
--------------------

TRACEROUTE:
traceroute to 67.182.25.217 (67.182.25.217), 15 hops max, 60 byte packets
1 Blizzard (Blizzard) 0.333 ms 0.388 ms 0.552 ms
2 * * *
3 37.244.0.102 (37.244.0.102) 2.452 ms 2.479 ms 2.514 ms
4 37.244.0.34 (37.244.0.34) 2.044 ms 2.076 ms 2.114 ms
5 te-0-4-0-9-pe02.600wseventh.ca.ibone.comcast.net (173.167.56.217) 3.127 ms 3.148 ms 3.155 ms
6 hu-1-0-0-0-cr02.losangeles.ca.ibone.comcast.net (68.86.88.9) 3.802 ms hu-0-5-0-2-cr02.losangeles.ca.ibone.comcast.net (68.86.83.25) 3.812 ms hu-1-0-0-1-cr02.losangeles.ca.ibone.comcast.net (68.86.88.13) 2.724 ms
7 ae-79-ar01.fresno.ca.ccal.comcast.net (68.86.93.38) 8.038 ms 8.216 ms 8.217 ms
8 ae-25-sur03.clovis.ca.ccal.comcast.net (162.151.40.134) 16.646 ms 16.366 ms 16.345 ms
9 te-7-1-acr01.clovis.ca.ccal.comcast.net (162.151.83.126) 16.048 ms 16.278 ms 16.221 ms
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *


16/07/2016 04:07:52 UTC
--------------------

MTR:
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
1. Blizzard 0.0% 10 0.7 0.8 0.5 1.3 0.2
2. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
3. 37.244.1.100 0.0% 10 3.4 2.5 1.9 3.5 0.6
4. 37.244.1.32 0.0% 10 3.4 2.5 2.0 3.8 0.7
5. te-0-11-0-0-2-pe01.350ecermak.il.ibone.comcast.net 0.0% 10 2.0 2.0 1.9 2.3 0.2
6. hu-2-4-0-1-cr02.350ecermak.il.ibone.comcast.net 0.0% 10 4.2 3.1 2.3 4.2 0.7
7. be-10517-cr02.denver.co.ibone.comcast.net 0.0% 10 33.6 35.2 33.4 43.2 2.9
8. be-11719-cr01.1601milehigh.co.ibone.comcast.net 90.0% 10 31.2 31.2 31.2 31.2 0.0
9. be-10919-cr01.sunnyvale.ca.ibone.comcast.net 70.0% 10 51.9 52.0 51.9 52.0 0.1
10. ae-79-ar01.sacramento.ca.ccal.comcast.net 0.0% 10 55.1 61.0 54.8 114.4 18.8
11. ae-24-sur03.clovis.ca.ccal.comcast.net 0.0% 10 57.4 59.7 57.4 77.8 6.4
12. te-6-1-acr01.clovis.ca.ccal.comcast.net 0.0% 10 59.9 59.9 59.8 60.2 0.1
13. c-67-182-25-217.hsd1.ca.comcast.net 0.0% 10 73.4 75.3 69.1 115.1 14.1


16/07/2016 04:07:47 UTC
--------------------

MTR:
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
1. Blizzard 0.0% 10 0.6 0.8 0.6 1.0 0.1
2. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
3. 37.244.1.100 0.0% 10 3.5 2.6 1.9 3.5 0.7
4. 37.244.1.32 0.0% 10 2.0 2.4 2.0 3.8 0.6
5. te-0-11-0-0-2-pe01.350ecermak.il.ibone.comcast.net 0.0% 10 2.1 2.0 1.8 2.3 0.2
6. hu-2-4-0-1-cr02.350ecermak.il.ibone.comcast.net 0.0% 10 4.3 3.1 2.3 4.3 0.7
7. be-10517-cr02.denver.co.ibone.comcast.net 0.0% 10 33.6 35.2 33.4 43.2 2.9
8. be-11719-cr01.1601milehigh.co.ibone.comcast.net 90.0% 10 31.4 31.4 31.4 31.4 0.0
9. be-10919-cr01.sunnyvale.ca.ibone.comcast.net 70.0% 10 52.1 52.2 52.1 52.2 0.1
10. ae-79-ar01.sacramento.ca.ccal.comcast.net 0.0% 10 55.1 61.0 54.8 114.4 18.8
11. ae-24-sur03.clovis.ca.ccal.comcast.net 0.0% 10 57.4 59.7 57.4 77.7 6.3
12. te-6-1-acr01.clovis.ca.ccal.comcast.net 0.0% 10 59.9 60.0 59.9 60.4 0.2
13. c-67-182-25-217.hsd1.ca.comcast.net 10.0% 10 68.9 73.7 68.9 81.6 4.0


16/07/2016 04:07:47 UTC
--------------------

PING:
PING 67.182.25.217 (67.182.25.217) 56(84) bytes of data.

--- 67.182.25.217 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 5000ms

 

16/07/2016 04:07:54 UTC
--------------------

MTR:
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
1. Blizzard 0.0% 10 0.4 0.4 0.3 0.6 0.1
2. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
3. 37.244.0.102 0.0% 10 2.2 2.2 2.0 2.7 0.2
4. 37.244.0.34 0.0% 10 2.1 2.0 1.9 2.1 0.1
5. te-0-4-0-9-pe02.600wseventh.ca.ibone.comcast.net 0.0% 10 2.0 2.1 1.9 2.7 0.2
6. hu-0-5-0-1-cr02.losangeles.ca.ibone.comcast.net 0.0% 10 3.1 3.0 2.5 4.0 0.5
7. ae-79-ar01.fresno.ca.ccal.comcast.net 0.0% 10 8.0 8.1 8.0 8.3 0.1
8. ae-25-sur03.clovis.ca.ccal.comcast.net 0.0% 10 16.3 16.3 16.0 17.4 0.4
9. te-7-1-acr01.clovis.ca.ccal.comcast.net 0.0% 10 16.8 16.3 16.0 17.0 0.3
10. c-67-182-25-217.hsd1.ca.comcast.net 0.0% 10 40.4 33.6 24.3 53.5 8.9


16/07/2016 04:07:49 UTC
--------------------

MTR:
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
1. Blizzard 0.0% 10 0.3 0.4 0.3 0.5 0.1
2. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
3. 37.244.0.102 0.0% 10 2.7 2.2 2.1 2.7 0.2
4. 37.244.0.34 0.0% 10 2.1 2.0 1.9 2.1 0.0
5. te-0-4-0-9-pe02.600wseventh.ca.ibone.comcast.net 0.0% 10 2.0 2.0 1.9 2.1 0.1
6. hu-0-5-0-3-cr02.losangeles.ca.ibone.comcast.net 0.0% 10 4.2 3.5 2.4 4.3 0.6
7. ae-79-ar01.fresno.ca.ccal.comcast.net 0.0% 10 8.0 8.1 8.0 8.1 0.0
8. ae-25-sur03.clovis.ca.ccal.comcast.net 0.0% 10 16.1 16.1 16.0 16.1 0.0
9. te-7-1-acr01.clovis.ca.ccal.comcast.net 0.0% 10 16.1 16.3 16.0 17.9 0.6
10. c-67-182-25-217.hsd1.ca.comcast.net 0.0% 10 34.2 30.9 25.6 53.5 8.5


16/07/2016 04:07:50 UTC
--------------------


SELECT THE LANGUAGE

©2015 BLIZZARD ENTERTAINMENT, INC. ALL RIGHTS RESERVED.
Blizzard® Entertainment

0 Kudos
Reply
jtitley16
Frequent Contributor

Re: Intermitent Packet Loss for all of June with no resolution.

Fix coming soon?  multiple disconnects per hour Sunday morning.......

 

10. c-67-182-25-217.hsd1.ca.comcast.net 80.0% 10 26.9 27.3 26.9 27.7 0.6

^ this server seems to be lossing packets alot in all of these logs.....

 

You do plan to look into crediting me some money at some point, ya?

 

 

TRACEROUTE:
traceroute to 67.182.25.217 (67.182.25.217), 15 hops max, 60 byte packets
1 Blizzard (Blizzard) 0.561 ms 0.667 ms 0.894 ms
2 * * *
3 37.244.1.100 (37.244.1.100) 2.210 ms 2.228 ms 2.284 ms
4 37.244.1.32 (37.244.1.32) 3.293 ms 3.305 ms 3.308 ms
5 te-0-11-0-0-2-pe01.350ecermak.il.ibone.comcast.net (173.167.56.237) 1.792 ms 1.834 ms 1.852 ms
6 hu-2-4-0-1-cr02.350ecermak.il.ibone.comcast.net (68.86.89.245) 3.734 ms 2.531 ms 2.521 ms
7 be-10517-cr02.denver.co.ibone.comcast.net (68.86.85.170) 34.365 ms 33.886 ms 33.853 ms
8 be-11719-cr01.1601milehigh.co.ibone.comcast.net (68.86.86.78) 31.044 ms 31.059 ms 31.297 ms
9 be-10919-cr01.sunnyvale.ca.ibone.comcast.net (68.86.85.153) 51.821 ms 51.816 ms 52.046 ms
10 ae-79-ar01.sacramento.ca.ccal.comcast.net (68.86.93.26) 55.637 ms 55.228 ms 55.231 ms
11 ae-24-sur03.clovis.ca.ccal.comcast.net (162.151.40.130) 57.372 ms 58.087 ms 57.709 ms
12 te-6-1-acr01.clovis.ca.ccal.comcast.net (162.151.83.118) 59.883 ms 59.827 ms 59.896 ms
13 c-67-182-25-217.hsd1.ca.comcast.net (67.182.25.217) 72.826 ms 69.044 ms 72.719 ms


17/07/2016 19:38:05 UTC
--------------------

TRACEROUTE:
traceroute to 67.182.25.217 (67.182.25.217), 15 hops max, 60 byte packets
1 Blizzard (Blizzard) 0.406 ms 0.522 ms 0.746 ms
2 * * *
3 37.244.1.100 (37.244.1.100) 2.043 ms 2.195 ms 2.201 ms
4 37.244.1.32 (37.244.1.32) 4.278 ms 4.284 ms 4.296 ms
5 te-0-11-0-0-2-pe01.350ecermak.il.ibone.comcast.net (173.167.56.237) 2.177 ms 2.193 ms 2.223 ms
6 hu-2-4-0-1-cr02.350ecermak.il.ibone.comcast.net (68.86.89.245) 3.103 ms 2.204 ms 2.190 ms
7 be-10517-cr02.denver.co.ibone.comcast.net (68.86.85.170) 34.030 ms 34.898 ms 34.796 ms
8 be-11719-cr01.1601milehigh.co.ibone.comcast.net (68.86.86.78) 31.059 ms 31.359 ms 31.769 ms
9 be-10919-cr01.sunnyvale.ca.ibone.comcast.net (68.86.85.153) 51.783 ms 51.876 ms 52.128 ms
10 ae-79-ar01.sacramento.ca.ccal.comcast.net (68.86.93.26) 55.231 ms 63.895 ms 63.898 ms
11 ae-24-sur03.clovis.ca.ccal.comcast.net (162.151.40.130) 57.377 ms 58.187 ms 57.810 ms
12 te-6-1-acr01.clovis.ca.ccal.comcast.net (162.151.83.118) 59.784 ms 59.785 ms 59.778 ms
13 c-67-182-25-217.hsd1.ca.comcast.net (67.182.25.217) 75.739 ms 73.181 ms 72.262 ms


17/07/2016 19:38:05 UTC
--------------------

PING:
PING 67.182.25.217 (67.182.25.217) 56(84) bytes of data.
64 bytes from 67.182.25.217: icmp_seq=1 ttl=50 time=69.2 ms
64 bytes from 67.182.25.217: icmp_seq=2 ttl=50 time=68.5 ms
64 bytes from 67.182.25.217: icmp_seq=3 ttl=50 time=77.8 ms
64 bytes from 67.182.25.217: icmp_seq=4 ttl=50 time=78.2 ms

--- 67.182.25.217 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3078ms
rtt min/avg/max/mdev = 68.555/73.486/78.292/4.582 ms


17/07/2016 19:38:05 UTC
--------------------

PING:
PING 67.182.25.217 (67.182.25.217) 56(84) bytes of data.
64 bytes from 67.182.25.217: icmp_seq=1 ttl=50 time=69.9 ms
64 bytes from 67.182.25.217: icmp_seq=2 ttl=50 time=74.7 ms
64 bytes from 67.182.25.217: icmp_seq=3 ttl=50 time=75.0 ms
64 bytes from 67.182.25.217: icmp_seq=4 ttl=50 time=74.7 ms

--- 67.182.25.217 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3074ms
rtt min/avg/max/mdev = 69.927/73.603/75.006/2.151 ms


17/07/2016 19:38:05 UTC
--------------------

PING:
PING 67.182.25.217 (67.182.25.217) 56(84) bytes of data.
64 bytes from 67.182.25.217: icmp_seq=1 ttl=50 time=24.9 ms
64 bytes from 67.182.25.217: icmp_seq=2 ttl=50 time=29.0 ms
64 bytes from 67.182.25.217: icmp_seq=3 ttl=50 time=26.0 ms
64 bytes from 67.182.25.217: icmp_seq=4 ttl=50 time=30.0 ms

--- 67.182.25.217 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3029ms
rtt min/avg/max/mdev = 24.904/27.519/30.068/2.132 ms


17/07/2016 19:38:09 UTC
--------------------

TRACEROUTE:
traceroute to 67.182.25.217 (67.182.25.217), 15 hops max, 60 byte packets
1 Blizzard (Blizzard) 0.417 ms 0.451 ms 0.596 ms
2 * * *
3 37.244.0.102 (37.244.0.102) 2.140 ms 2.202 ms 2.243 ms
4 37.244.0.34 (37.244.0.34) 1.990 ms 2.011 ms 2.056 ms
5 te-0-4-0-9-pe02.600wseventh.ca.ibone.comcast.net (173.167.56.217) 2.129 ms 2.147 ms 2.148 ms
6 hu-1-0-0-1-cr02.losangeles.ca.ibone.comcast.net (68.86.88.13) 3.399 ms hu-0-5-0-3-cr02.losangeles.ca.ibone.comcast.net (68.86.83.29) 3.793 ms hu-1-0-0-0-cr02.losangeles.ca.ibone.comcast.net (68.86.88.9) 3.992 ms
7 ae-79-ar01.fresno.ca.ccal.comcast.net (68.86.93.38) 8.035 ms 8.007 ms 7.965 ms
8 ae-25-sur03.clovis.ca.ccal.comcast.net (162.151.40.134) 16.729 ms 16.673 ms 16.663 ms
9 te-7-1-acr01.clovis.ca.ccal.comcast.net (162.151.83.126) 16.896 ms 17.068 ms 16.928 ms
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *


17/07/2016 19:38:08 UTC
--------------------

MTR:
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
1. Blizzard 0.0% 10 0.6 0.6 0.5 0.8 0.1
2. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
3. 37.244.1.100 0.0% 10 2.1 2.3 2.1 3.4 0.4
4. 37.244.1.32 0.0% 10 2.0 2.1 1.9 3.1 0.4
5. te-0-11-0-0-2-pe01.350ecermak.il.ibone.comcast.net 0.0% 10 1.7 2.0 1.7 2.2 0.2
6. hu-2-4-0-1-cr02.350ecermak.il.ibone.comcast.net 0.0% 10 4.3 3.4 2.2 4.5 0.8
7. be-10517-cr02.denver.co.ibone.comcast.net 0.0% 10 35.1 34.3 33.3 35.1 0.7
8. be-11719-cr01.1601milehigh.co.ibone.comcast.net 0.0% 10 31.3 31.2 31.1 31.3 0.1
9. be-10919-cr01.sunnyvale.ca.ibone.comcast.net 0.0% 10 51.9 51.9 51.8 52.1 0.1
10. ae-79-ar01.sacramento.ca.ccal.comcast.net 0.0% 10 94.2 59.1 54.8 94.2 12.3
11. ae-24-sur03.clovis.ca.ccal.comcast.net 0.0% 10 57.4 60.0 57.4 83.0 8.1
12. te-6-1-acr01.clovis.ca.ccal.comcast.net 0.0% 10 60.1 59.9 59.8 60.1 0.1
13. c-67-182-25-217.hsd1.ca.comcast.net 0.0% 10 76.4 72.7 68.5 79.3 4.4


17/07/2016 19:38:05 UTC
--------------------

MTR:
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
1. Blizzard 0.0% 10 0.6 0.6 0.4 1.0 0.2
2. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
3. 37.244.1.100 0.0% 10 2.2 2.2 1.9 3.4 0.4
4. 37.244.1.32 0.0% 10 2.0 2.1 1.8 3.1 0.4
5. te-0-11-0-0-2-pe01.350ecermak.il.ibone.comcast.net 0.0% 10 1.8 2.0 1.7 2.2 0.2
6. hu-2-4-0-1-cr02.350ecermak.il.ibone.comcast.net 0.0% 10 4.4 3.1 2.2 4.4 0.7
7. be-10517-cr02.denver.co.ibone.comcast.net 0.0% 10 35.1 34.4 33.3 35.3 0.7
8. be-11719-cr01.1601milehigh.co.ibone.comcast.net 0.0% 10 31.1 31.2 31.1 31.6 0.2
9. be-10919-cr01.sunnyvale.ca.ibone.comcast.net 0.0% 10 52.1 52.0 51.8 52.1 0.1
10. ae-79-ar01.sacramento.ca.ccal.comcast.net 0.0% 10 94.2 59.1 54.8 94.2 12.3
11. ae-24-sur03.clovis.ca.ccal.comcast.net 0.0% 10 57.5 60.0 57.4 83.0 8.1
12. te-6-1-acr01.clovis.ca.ccal.comcast.net 0.0% 10 60.0 59.9 59.8 60.3 0.1
13. c-67-182-25-217.hsd1.ca.comcast.net 10.0% 10 75.0 75.9 70.3 83.9 4.6


17/07/2016 19:38:05 UTC
--------------------

TRACEROUTE:
traceroute to 67.182.25.217 (67.182.25.217), 15 hops max, 60 byte packets
1 Blizzard (Blizzard) 1.250 ms 1.254 ms 1.350 ms
2 * * *
3 37.244.0.102 (37.244.0.102) 2.021 ms 2.144 ms 2.163 ms
4 37.244.0.34 (37.244.0.34) 2.040 ms 2.060 ms 2.066 ms
5 te-0-4-0-9-pe02.600wseventh.ca.ibone.comcast.net (173.167.56.217) 1.959 ms 1.982 ms 1.988 ms
6 hu-0-5-0-2-cr02.losangeles.ca.ibone.comcast.net (68.86.83.25) 3.204 ms hu-0-5-0-3-cr02.losangeles.ca.ibone.comcast.net (68.86.83.29) 3.333 ms hu-1-0-0-1-cr02.losangeles.ca.ibone.comcast.net (68.86.88.13) 2.572 ms
7 ae-79-ar01.fresno.ca.ccal.comcast.net (68.86.93.38) 8.070 ms 8.078 ms 8.080 ms
8 ae-25-sur03.clovis.ca.ccal.comcast.net (162.151.40.134) 16.089 ms 16.096 ms 16.097 ms
9 te-7-1-acr01.clovis.ca.ccal.comcast.net (162.151.83.126) 16.022 ms 16.059 ms 16.027 ms
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *


17/07/2016 19:38:12 UTC
--------------------

PING:
PING 67.182.25.217 (67.182.25.217) 56(84) bytes of data.

--- 67.182.25.217 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 4999ms

 

17/07/2016 19:38:12 UTC
--------------------

MTR:
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
1. Blizzard 0.0% 10 0.4 0.6 0.4 1.1 0.3
2. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
3. 37.244.0.102 0.0% 10 2.6 2.3 2.1 2.8 0.2
4. 37.244.0.34 0.0% 10 2.1 2.0 1.9 2.1 0.1
5. te-0-4-0-9-pe02.600wseventh.ca.ibone.comcast.net 0.0% 10 2.0 2.1 1.9 2.2 0.1
6. hu-0-5-0-3-cr02.losangeles.ca.ibone.comcast.net 0.0% 10 4.1 3.3 2.2 4.2 0.7
7. ae-79-ar01.fresno.ca.ccal.comcast.net 0.0% 10 8.0 8.0 7.9 8.2 0.1
8. ae-25-sur03.clovis.ca.ccal.comcast.net 0.0% 10 16.1 16.1 16.0 16.2 0.0
9. te-7-1-acr01.clovis.ca.ccal.comcast.net 0.0% 10 16.5 16.2 16.1 16.5 0.2
10. c-67-182-25-217.hsd1.ca.comcast.net 80.0% 10 26.9 27.3 26.9 27.7 0.6


17/07/2016 19:38:08 UTC
--------------------

MTR:
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
1. Blizzard 0.0% 10 0.5 0.6 0.3 1.1 0.2
2. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
3. 37.244.0.102 0.0% 10 2.1 2.1 2.0 2.3 0.1
4. 37.244.0.34 0.0% 10 2.0 2.0 1.9 2.1 0.1
5. te-0-4-0-9-pe02.600wseventh.ca.ibone.comcast.net 0.0% 10 2.5 2.3 2.0 3.9 0.6
6. hu-0-5-0-0-cr02.losangeles.ca.ibone.comcast.net 0.0% 10 3.4 3.5 2.4 4.5 0.7
7. ae-79-ar01.fresno.ca.ccal.comcast.net 0.0% 10 8.1 8.7 8.1 14.3 2.0
8. ae-25-sur03.clovis.ca.ccal.comcast.net 0.0% 10 16.0 16.1 16.0 16.3 0.1
9. te-7-1-acr01.clovis.ca.ccal.comcast.net 0.0% 10 16.1 16.4 16.0 18.9 0.9
10. c-67-182-25-217.hsd1.ca.comcast.net 0.0% 10 28.0 30.3 24.4 40.0 4.9


17/07/2016 19:38:09 UTC
--------------------

 

0 Kudos
Reply
jtitley16
Frequent Contributor

Re: Intermitent Packet Loss for all of June with no resolution.

Why is it when I call tier 1 tells me they can only escalate me to tier 2, because tier 2 put in a note that my packet loss issue is not on Comcasts network?(I'm pretty sure the logs prove them wrong, its clearly a COmcast network issue!)  THen when I get to tier 2 they tell me all they can do is send a truck.  THen when the truck arrives they tell me they can't do anyhting except replace teh modem and lines they just replaced a few weeks ago, and to call tier 1 back.  Thisis assanine!  I am disconecting several times an hour for more than a month and a half.  Someonesomewhere must have the knowledge coupled with the authority to fix this, lol they probably work at Charter, what am I thinking??????

0 Kudos
Reply
jtitley16
Frequent Contributor

Re: Intermitent Packet Loss for all of June with no resolution.

Any plans to work on this?  its been almost 2 months now.....

0 Kudos
Reply
jtitley16
Frequent Contributor

Re: Intermitent Packet Loss for all of June with no resolution.

Updates coming soon?  anything?

0 Kudos
Reply
jtitley16
Frequent Contributor

Re: Intermitent Packet Loss for all of June with no resolution.

on thephone with tier 1 support, they want to roll a truck out to fix my packet loss.......

 

this will be teh 3rd truck!  They already replaced all teh lines and modem.....the packet loss is clearly from host to client over COmcast backbone...how is a truck going to help me???

0 Kudos
Reply
jtitley16
Frequent Contributor

Re: Intermitent Packet Loss for all of June with no resolution.

It's been 10 days since you last responded.  I have answered your question, do you plan to answer mine?

0 Kudos
Reply
jtitley16
Frequent Contributor

Re: Intermitent Packet Loss for all of June with no resolution.

I called tier 1 last night I was told tier 2 would call me within a 4 hour window starting form the start of the business day.  No such call ever occurred.  I called tier 1 to inquire 5 hours after the start of teh business day and was informed that - All further tickets on packet loss will be closed going forward as they see no packet loss when they ran a test from client to host.  The packet loss is clearly host to client......and I have provided the logs.

 

Why would a tier 2 tech be allowed to put a note that says "i didnt see any issues, immediately close all further tickets on this issue"?  Clearly if this gets fixed, it could happen again, and from now until the end of time all my tickets would just get closed becuase someone lacking any forsight or care made an absolute statement that was clearly irresponsible, and ignorant.

0 Kudos
Reply
jtitley16
Frequent Contributor

Re: Intermitent Packet Loss for all of June with no resolution.

Any new ideas?  Still occurring deveral times an hour.....

0 Kudos
Reply
jtitley16
Frequent Contributor

Re: Intermitent Packet Loss for all of June with no resolution.

still happening in August.....

0 Kudos
Reply
Respected Member

Re: Intermitent Packet Loss for all of June with no resolution.

Sorry for the delayed response jtitley16,

 

I was looking over your account and didn't see any signal issue that would cause that much packet loss. I did find some interesting information concerning other peoples experiences connecting to Blizzard Servers. (Including non-Comcast customers) Beyond that information the only other thought I have on a solution is swapping the modem. I can send a tech out to swap the modem but if they find that their is not an issue with our equipment there will be a charge associated with the visit.

0 Kudos
Reply
jtitley16
Frequent Contributor

Re: Intermitent Packet Loss for all of June with no resolution.

Why would you look at my account?  I already showed you the logs where it shows the packet loss is occurring from the Host (Blizzard) to the client (me) over your network.  Blizzard Tech support highlighted where the issue was located for you already, in the original post both a link to that post and a copy of its contents can be found.  My miodem was already swapped out, how will a 3rd modem help?

 

"8. be-11719-cr01.1601milehigh.co.ibone.comcast.net 80.0% 10 33.2 33.2 33.1 33.2 0.0
9. be-10919-cr01.sunnyvale.ca.ibone.comcast.net 40.0% 10 51.9 51.9 51.8 52.1 0.1

8. be-11719-cr01.1601milehigh.co.ibone.comcast.net 90.0% 10 33.1 33.1 33.1 33.1 0.0
9. be-10919-cr01.sunnyvale.ca.ibone.comcast.net 10.0% 10 51.8 51.8 51.8 52.0 0.1

Good call out, I'm sorry I missed those in your first trace. Can you show these to your ISP? It looks like this packet loss is well within their network." 

The URL can be found here: http://us.battle.net/wow/en/forum/topic/20745135510?page=2#23

0 Kudos
Reply
jtitley16
Frequent Contributor

Re: Intermitent Packet Loss for all of June with no resolution.

2 months and going......Bliizard's official response is that it is "well within Comcast network".  If you cannot offer any strong evidence to the contrary I suggest you fix it.

0 Kudos
Reply
Internetguy23
Occasional Visitor

Re: Intermitent Packet Loss for all of June with no resolution.

Comcasts idea of support so far seems to be them saying they'll do something and then ignoring you until you go away it would seem.

0 Kudos
Reply
Forum Contributor

Re: Intermitent Packet Loss for all of June with no resolution.

I''ll take a crack at this one.

 

Here's MY winmtr output - this is from Portland OR:

 

|------------------------------------------------------------------------------------------|

|                                      WinMTR statistics                                   |

|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |

|------------------------------------------------|------|------|------|------|------|------|

|                              172.16.1.1 -    0 |  123 |  123 |    0 |    1 |    9 |    1 |

|50-198-160-190-static.hfc.comcastbusiness.net -    0 |  123 |  123 |    1 |    1 |   11 |    1 |

|                            96.120.60.29 -    0 |  123 |  123 |    3 |    8 |   15 |    9 |

|xe-3-2-2-sur04.troutdale.or.bverton.comcast.net -    0 |  123 |  123 |    5 |    9 |   26 |    7 |

|ae-52-ar01.troutdale.or.bverton.comcast.net -    1 |  119 |  118 |    5 |    9 |   33 |    8 |

|ae-2-ar01.beaverton.or.bverton.comcast.net -    0 |  123 |  123 |    6 |   12 |   97 |   19 |

|be-33490-cr01.sunnyvale.ca.ibone.comcast.net -    0 |  123 |  123 |   19 |   24 |   39 |   26 |

|ae-79-ar01.sacramento.ca.ccal.comcast.net -    0 |  123 |  123 |   21 |   30 |  115 |   60 |

|  ae-24-sur03.clovis.ca.ccal.comcast.net -    0 |  123 |  123 |   29 |   35 |   64 |   34 |

| te-6-1-acr01.clovis.ca.ccal.comcast.net -    0 |  123 |  123 |   26 |   30 |   41 |   31 |

|     c-67-182-25-217.hsd1.ca.comcast.net -    0 |  123 |  123 |   35 |   45 |   77 |   40 |

|________________________________________________|______|______|______|______|______|______|

   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

 

As you can see - no problem.

 

A couple things that might help with the diagnosis:

 

A lot of people don't understand how traceroutes (or pings or any other network testing) works in Real Life and how it can be screwed up.

 

There is this perception that "If I ping some server 1 to 3 hops away and it works great, and I do an FTP transfer to another server and it works great - that's proof that MY network is not suffering packet loss"

 

This is incorrect.  Let me explain how packet loss works in IP traffic.

 

You send 100 packets, 1 gets dropped.   The recipient stack sees a missing packet, requests a resend, your stack gets the request, sends the packet out.  Recipient gets the packet, it's all happy.

 

if the recipient is a short distance away (physically and in terms of hops) and your packets take maybe 1 millisecond to travel from you to them - then you will NEVER notice a problem.  Why?  Because it is so fast.

 

In fact you can have maybe 25% packet loss and you still won't notice.

 

but let's assume that the delay from you to them is 30ms    Now, a lost packet will consume 90ms for a replacement to arrive at the destination.   That's still fast, though.

 

Now let's assume the delay is 120ms.   The delay for replacement will be 360ms    Now, do you understand a bit on packet travel?

 

So let's apply this to your traceroute.   Let's say you have a marginal connection and you are losing 10 of your packets.  You run a trace to  1.1.1.1

 

To get to 1.1.1.1  you need to go thorough

 

3.3.3.3

4.4.4.4

5.5.5.5

 

3.3.3.3 is 10ms away.   4.4.4.4  is 80ms away.  5.5.5.5 is 150ms away   1.1.1.1  is 230ms away

 

Your sliding window in your TCP stack is 600ms   Anything taking longer than that will be dropped.

 

So you run your trace.  Your packet loss is happening between you and 3.3.3.3

 

You will get a response from 3.3.3.3 - no problem.  Lost packets and the resend for them will only take 30ms

 

You will get a response from 4.4.4.4   Lost packets and the resend will take 240ms

 

You will get a response from 5.5.5.5   Lost packets and the resend will take 450ms

 

You will NOT get a response from 1.1.1.1 because the lost packet round trip will be 690ms and your window is only 600ms - your stack will drop the response.

 

You will then conclude that the problem MUST be between 5.5.5.5 and 1.1.1.1 and then proceed to scream at the admin.   The admin - who has no losses - runs a trace - sees nothing in between 5.5.5.5 and 1.1.1.1 - and concludes you don't know what the heck you are talking about.  Or, the admin is a bit clever - deduces you are off the deep end - checks your connection from you to 3.3.3.3 - sees packet loss and tells you maybe your equipment is buggered up - and you tell him to ef himself because you are absolutely positively sure you are right - because some network tool that you don't really understand how to use told you so.

 

I see this kind of thing ALL THE TIME.   And the WORST part of the problem is that modern consumer grade networking products try to be very helpful - and conceal errors.

 

I had a customer with what he thought was a buggered up switch a couple months ago and he was practically crying because every single thing he saw - netstat under Windows, various packet counters and error counters in his switch, etc. etc. etc - all of them showed ZERO packet errors.

 

I dropped a Pentascanner on his network and checked about 6 cable runs and 4 of them were showing errors.   The switch and windows showed no errors.   I tested several others - some were OK some were bad.   Eventually I convinced him to drop $6,000 into a recable (fortunately it was not a large office) put in all new CAT-6 and whala - problems vanished.  Then he shamfully admitted to me that he had dropped $2K on other network "consultants" who had come in and told him it must be his server/clients/sunspots/blah blah blah.

 

There's a line in one of the Star Trek movies - "You have to learn WHY things work on a starship"  Take it to heart.    ping, traceroute and so on are good tools  - but if you don't know WHY things work on a network - they will steer you down a blind rabbit hole.   Every time.

0 Kudos
Reply
Forum Contributor

Re: Intermitent Packet Loss for all of June with no resolution.

Now, here's what you want to do when troubleshooting Comcast packet loss (or what you think might be packet loss)

 

First, you gotta be using a CLEAN pc.  I'm NOT talking about your desktop PC that might have a bunch of baloney loaded on it.   I'm talking about a laptop that you carefully and lovingly wiped and loaded from virgin windows install media then dropped into a golden can - this laptop is ONLY used for network troubleshooting.

 

I use an older Core2 laptop that shipped from Dell with XP preloaded.  It's a POS for win 7 so I wiped and relaoded it with Linux but Windows will work just as well.

 

Next you need to look at your cable modem.  If your cable modem is 3rd party then you need a DOCSIS3 with as many channels as you can.  If it's a Comcast-supplied one then get a Cisco BWG.  The SMC and Netgear ones have fewer channels even though they are DOCSIS3 which means you will be competing with a million other custeomrs on your cable segment.  With the BWG you will have access to channels that the SMC customers don't have so out of the box you will have less contention.

 

Next, you need to test your local network.  Setup a local server.  This can be a second laptop or a second windows system or something like that.   You need to plug your virgin PC into one of the modem ports and your local server into the other.   You should then copy files back and forth to that server at the same time.  If you DO NOT get close to 100Mbt and your systems have 100BaseT interfaces then you are NOT running full duplex.  Stop one of the copies.  If you still don't get it - you have an ethernet chip incompatability and you are dropping packets.   If both systems are gigabit AND THEY ARE FAST you should get well above 100Mbt but probably not 1 GB (unless you have superfast disks)

 

NOW if you find this server thing to be kludgy there is a much better way to test your local network and that is with packet flooding.

 

Under Linux you become root and use ping -f

 

Under Windows 7 you load winpcap and run a flooder program from Netscan tools Pro, or you dig around on the Internet and find an old udp flooding program that is written to use raw sockets and you run this under Windows XP - NOT windows XP service pack 1 (where that capability was disabled by Microsoft)

 

Under windows 8 or 10 you cannot use a packet driver to flood.   Thanks Microsoft.

 

You can learn about packet flooding by googling for it.  This is how professionals test networks.  Flooding will quickly reveal  ethernet incompatabilities and problems with cabling.  I wrote a flooder for Android and use it on my cell phone to test wifi networks.  It is quite easy to knock crummy wifi routers offline with it.

 

Now, take your virgin system and run a trace to your destination.   Next use a tool called pingplotter (if you are are on windows) and run it to ALL the hops  (use the pro trial)   If on Linux then write a script to run ping in parallel to all the hops and feed the results into gnuplot.    Run it for a day or so. Packet loss is not predictible so you need a few days to gather data.

 

Now compare your graphs.  Averaging the graphs to a hop will give you the distance to that hop.  Look for periods that the last destination is offline or not responding and compare those to the graphs of the other hops.  If all graphs show a spike then the loss is nearer to you.  If only the next graph to the failing hop shows a spike then the loss is further away.

 

lastly, remember  - traceroute was written to test routing protocols.  Not bandwidth testing.  And if you think you can do this with a local wifi network then here's a nickle go buy a real computer, son.

0 Kudos
Reply
jtitley16
Frequent Contributor

Re: Intermitent Packet Loss for all of June with no resolution.

The packet loss which seems the most severe is from Host to Client as it passes through Colorado, Comcast is only checking my connection in one direction.  As the logs suggest the packet loss is the host reposne as it goes through their network.  If it was on a different ISP backbone I'd not be at Comcast about it, but it is on their network.

 

Testing my Hardware is just going to prove the following: that the packet loss I am suffering from is not on the client to host route.  The series of tubes called the internet is a 2 way communication system, it just so happens that the return trip is also over the Comcast network, and I happen to be a Comcast customer, which allows me to cry tears of pain and frustration on the forums until someone in Colorado fixes it.  

0 Kudos
Reply
Respected Member

Re: Intermitent Packet Loss for all of June with no resolution.

Hello jtitley16,

 

After going over a few of the options available to me I have temporarily disabled the IPv6 access to your modem to see if this helps with the connection. Please message back to let me know your status.

0 Kudos
Reply
jtitley16
Frequent Contributor

Re: Intermitent Packet Loss for all of June with no resolution.

You disabled ipv6 on 7-7-16 and I messaged you back that there was no change.  Why are we doing this again?

I am also discconecting multiple times an hour from several voip sites, using ventrillo and teamspeak as well now.  

 

Re: Intermitent Packet Loss for all of June with no resolution.
Sent: ‎07-07-2016 08:53 PM
 

hello jtitley16,

 

I made a few changes on your modem configuration to stop routing IPv6 addresses to see if this temporarily resolves the routing issue. Please let me know how your connection is moving forward.

 
 

 

0 Kudos
Reply
Forum Contributor

Re: Intermitent Packet Loss for all of June with no resolution.

"...Testing my Hardware is just going to prove the following..."

 

And there we have the answer as to why you have no resolution.   Ignore the fact that other people are not seeing this (such as the trace I posted).   It's so much easier to logically prove that there's no problem on your end than to get your hands dirty actually verifying it with a real test with real equipment.

 

You may have read my entire post but you still don't understand how things work and how easy it is for a failure or misconfiguration in a piece of gear to cause symptoms in another section of a system that is ASSSUMED to be unrelated.

 

Before casting stones on other people's networks you need to have iron in your own windows.  You have not tested your internal network for packet loss and yet it is so easy to do it with a ping flood or with copies of large files and a stopwatch, there is no defensible excuse for not doing it.

 

You are just lucky that no comcast tech has shown up at your site who really understands network troubleshooting, and if that day ever comes you have a high probability of being caught with your pants down. (although I will readily admit with the shortage of such people within Comcast you have an even higher probability of never seeing such a tech)

0 Kudos
Reply
jtitley16
Frequent Contributor

Re: Intermitent Packet Loss for all of June with no resolution.

Yes Packets coming from Los Angeles through Denver losing packets before they reach my network, which are shown on the traceroute given to me by the server are likely related to my network.  That makes sense if you don't think about it.

 

Anyways I am still having issues staying connected to various FTP, VOIP and MMO servers.  You have disabled my ipv6 twice now without succesfully solving the issue, any more ideas?

0 Kudos
Reply
jtitley16
Frequent Contributor

Re: Intermitent Packet Loss for all of June with no resolution.

I am still disconnecting from the mmo server and voip server several times an hour.  They are completely unrelated servers in very different locations.  its now been 3 months with no improvements on any of my machines with and without my router...............

0 Kudos
Reply
jtitley16
Frequent Contributor

Re: Intermitent Packet Loss for all of June with no resolution.

Disconnecting from several unrelated servers with 30 seconds intervals at this point, my internet connection is not currently of any use towards my business needs.  ANy plans of helping me resolve this?

0 Kudos
Reply
jtitley16
Frequent Contributor

Re: Intermitent Packet Loss for all of June with no resolution.

I ma losing connections to multiple voip, ftp, and mmo servers, so unless they have all had ongoing problems since I started service with Comcast, clearly this is your issue.......how long as it been since a comcast agent has even responded?  In the almost 4 months this post has been here you have offered one solution, twice and it didn't help.  disabling ipv6 hardly counts as doing your best to resolve an issue of this duration.

 

--- 67.182.25.217 ping statistics ---
4 packets transmitted, 3 received, 25% packet loss, time 3998ms
rtt min/avg/max/mdev = 33.139/38.134/45.052/5.054 ms

 

MTR:
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
1. Blizzard 0.0% 10 0.5 0.5 0.5 0.6 0.0
2. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
3. 37.244.1.100 0.0% 10 2.2 2.3 2.0 3.2 0.3
4. 37.244.1.32 0.0% 10 1.9 2.1 1.8 3.3 0.4
5. te-0-11-0-0-2-pe01.350ecermak.il.ibone.comcast.net 0.0% 10 2.0 2.1 1.8 2.3 0.2
6. hu-2-3-0-4-cr02.350ecermak.il.ibone.comcast.net 0.0% 10 3.5 3.4 2.4 4.9 0.9
7. be-10517-cr02.denver.co.ibone.comcast.net 0.0% 10 34.2 34.3 33.4 35.4 0.7
8. be-11719-cr01.1601milehigh.co.ibone.comcast.net 0.0% 10 33.1 33.1 33.0 33.2 0.0
9. be-10919-cr01.sunnyvale.ca.ibone.comcast.net 60.0% 10 52.2 52.2 52.2 52.3 0.0
10. ae-79-ar01.sacramento.ca.ccal.comcast.net 0.0% 10 58.4 57.4 55.1 70.7 4.9
11. ae-24-sur03.clovis.ca.ccal.comcast.net 0.0% 10 59.3 59.3 59.3 59.4 0.0
12. te-6-1-acr01.clovis.ca.ccal.comcast.net 0.0% 10 57.0 57.0 56.9 57.4 0.1
13. c-67-182-25-217.hsd1.ca.comcast.net 30.0% 10 67.1 71.5 66.2 79.6 4.9

 

 

0 Kudos
Reply
GadgetPig
New Member

Re: Intermitent Packet Loss for all of June with no resolution.

@jtitley16 

Out of curiosity, what brand/model modem are you using? And have you tried connecting your PC directly to a port on the gateway/modem,bypassing any switches on your network?

0 Kudos
Reply
Highlighted
GadgetPig
New Member

Re: Intermitent Packet Loss for all of June with no resolution.

@jtitley16 

Out of curiosity, what brand/model modem are you using? And have you tried connecting your PC directly to a port on the gateway/modem,bypassing any switches on your network?

Tags (1)
0 Kudos
Reply
Trusted Forum Contributor

Re: Intermitent Packet Loss for all of June with no resolution.

From Michigan

 

--- c-67-182-25-217.hsd1.ca.comcast.net ping statistics ---
53 packets transmitted, 53 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 84.244/91.086/110.091/5.559 ms

0 Kudos
Reply
jtitley16
Frequent Contributor

Re: Intermitent Packet Loss for all of June with no resolution.

Comcast gave me a Cisco DPC3941B. Yes thePC is plugged into the modem currently without the router.  I have also used multiple pc's and cat6 cables form the pc's to the modem.  None of this helped in any way.  I have however started using a mobile hotspot form AT&T and it resolved my packet loss and dc issues from all the different servers I connect to.  I will post the logs when I get time.  To me I am using the same network and on AT&T I have no packet loss and on Comcast I do have packet loss, its a no brainer.

 

My Network is having packet loss and connection issues with multiple mmo, ftp, and voip servers on Comcast's network but not AT&T.  At this point it is going to be pretty hard for Comcast to claim it isn't there network.

0 Kudos
Reply
Trusted Forum Contributor

Re: Intermitent Packet Loss for all of June with no resolution.

From Michigan:

--- c-67-182-25-217.hsd1.ca.comcast.net ping statistics ---
104 packets transmitted, 104 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 83.390/91.256/119.195/6.038 ms

0 Kudos
Reply