Not seeing any issues in East TN, on either business fiber or residential cable.
________________________________
From: "B.J. Ash via Outages"
Sent: Sunday, July 31, 2016 1:23 PM
To: [email protected]
Subject: Re: [outages] Charter Issues


Seeing packet loss (but no high latency) from Manistique, MI area as well:

traceroute to 4.2.2.2 (4.2.2.2), 64 hops max, 52 byte packets
1  192.168.0.1 (192.168.0.1)  2.191 ms  1.976 ms  1.602 ms
2  192.168.44.1 (192.168.44.1)  16.300 ms  13.602 ms  9.166 ms
3  10.143.190.1 (10.143.190.1)  20.660 ms  17.737 ms  14.362 ms
4  acr01escnmi-tge-0-1-1-2.escn.mi.charter.com (96.34.16.6)  12.934 ms  16.123 
ms  20.547 ms
5  dtr02mrqtmi-bue-96.mrqt.mi.charter.com (96.34.17.72)  18.163 ms  33.793 ms  
18.734 ms
6  crr01mrqtmi-bue-100.mrqt.mi.charter.com (96.34.18.50)  17.937 ms  19.060 ms  
19.129 ms
7  crr01stptwi-bue-251.stpt.wi.charter.com (96.34.18.180)  23.567 ms  24.330 ms 
 24.759 ms
8  crr02stptwi-bue-300.stpt.wi.charter.com (96.34.24.73)  29.829 ms  28.973 ms  
28.353 ms
9  dtr01rhnlwi-tge-0-0-0-3.rhnl.wi.charter.com (96.34.16.91)  36.459 ms  37.636 
ms  31.849 ms
10  * * crr01euclwi-bue-8.eucl.wi.charter.com (96.34.16.8)  63.305 ms
11  crr02sgnwmi-tge-0-0-0-4.sgnw.mi.charter.com (96.34.2.153)  39.664 ms *  
47.200 ms
12  * * *
13  b.resolvers.level3.net (4.2.2.2)  51.418 ms *  58.785 ms


traceroute to 8.8.8.8 (8.8.8.8), 64 hops max, 52 byte packets
1  192.168.0.1 (192.168.0.1)  4.277 ms  1.203 ms  1.292 ms
2  192.168.44.1 (192.168.44.1)  11.856 ms  8.399 ms  6.865 ms
3  10.143.190.1 (10.143.190.1)  16.640 ms  16.012 ms  15.860 ms
4  acr01escnmi-tge-0-1-1-2.escn.mi.charter.com (96.34.16.6)  20.192 ms  23.035 
ms  24.092 ms
5  dtr02mrqtmi-bue-96.mrqt.mi.charter.com (96.34.17.72)  18.664 ms  34.144 ms  
23.401 ms
6  crr01mrqtmi-bue-100.mrqt.mi.charter.com (96.34.18.50)  19.943 ms  22.040 ms  
20.303 ms
7  crr01stptwi-bue-251.stpt.wi.charter.com (96.34.18.180)  25.457 ms  32.676 ms 
 36.227 ms
8  crr02stptwi-bue-300.stpt.wi.charter.com (96.34.24.73)  43.562 ms  39.256 ms  
28.513 ms
9  dtr01rhnlwi-tge-0-0-0-3.rhnl.wi.charter.com (96.34.16.91)  36.058 ms  31.472 
ms  31.832 ms
10  crr01euclwi-bue-8.eucl.wi.charter.com (96.34.16.8)  41.324 ms  90.165 ms  
43.941 ms
11  * crr02sgnwmi-tge-0-0-0-4.sgnw.mi.charter.com (96.34.2.153)  59.288 ms  
48.158 ms
12  bbr02euclwi-bue-5.eucl.wi.charter.com (96.34.0.7)  46.453 ms *  44.995 ms
13  bbr01chcgil-bue-1.chcg.il.charter.com (96.34.0.9)  71.346 ms *  62.600 ms
14  prr01chcgil-bue-2.chcg.il.charter.com (96.34.3.9)  52.336 ms  54.285 ms  
50.465 ms
15  * 96-34-152-30.static.unas.mo.charter.com (96.34.152.30)  54.454 ms  49.326 
ms
16  74.125.37.195 (74.125.37.195)  58.656 ms
    66.249.95.231 (66.249.95.231)  48.828 ms  62.371 ms
17  216.239.50.234 (216.239.50.234)  55.533 ms *
    209.85.243.163 (209.85.243.163)  52.199 ms
18  * * 216.239.47.45 (216.239.47.45)  71.972 ms
19  * 72.14.234.81 (72.14.234.81)  82.344 ms
    209.85.248.209 (209.85.248.209)  67.783 ms
20  * * *
21  google-public-dns-a.google.com (8.8.8.8)  61.296 ms  61.255 ms *



Not seeing any issues from a Kalamazoo, MI Charter account though:


Tracing route to b.resolvers.level3.net [4.2.2.2]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  192.168.0.1
  2     4 ms     3 ms     3 ms  75-134-85-237.static.aldl.mi.charter.com 
[75.134.85.237]
  3     *        *        *     Request timed out.
  4    19 ms     8 ms     9 ms  dtr02klmzmi-tge-0-3-0-6.klmz.mi.charter.com 
[96.34.38.49]
  5    19 ms    12 ms    18 ms  crr01aldlmi-bue-20.aldl.mi.charter.com 
[96.34.36.62]
  6    50 ms    14 ms    15 ms  bbr01aldlmi-bue-1.aldl.mi.charter.com 
[96.34.2.8]
  7     *       24 ms    42 ms  lag-200.ear3.chicago2.level3.net [4.35.108.149]
  8    37 ms    18 ms    18 ms  ae-17-3605.ear1.chicago2.level3.net 
[4.69.133.90]
  9    30 ms    30 ms    24 ms  b.resolvers.level3.net [4.2.2.2]

Trace complete.


Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

  1     1 ms     1 ms     2 ms  192.168.0.1
  2     2 ms     1 ms     1 ms  75-134-85-237.static.aldl.mi.charter.com 
[75.134.85.237]
  3     *        *        *     Request timed out.
  4    17 ms     8 ms     9 ms  dtr02klmzmi-tge-0-3-0-6.klmz.mi.charter.com 
[96.34.38.49]
  5    15 ms    12 ms    13 ms  crr01aldlmi-bue-20.aldl.mi.charter.com 
[96.34.36.62]
  6    13 ms    23 ms    15 ms  bbr01aldlmi-bue-1.aldl.mi.charter.com 
[96.34.2.8]
  7    16 ms    27 ms    23 ms  bbr01chcgil-bue-805.chcg.il.charter.com 
[96.34.0.139]
  8    20 ms    19 ms    18 ms  prr01chcgil-bue-2.chcg.il.charter.com 
[96.34.3.9]
  9    18 ms    16 ms    16 ms  96-34-152-30.static.unas.mo.charter.com 
[96.34.152.30]
10    17 ms    19 ms    18 ms  74.125.37.195
11    26 ms    24 ms    37 ms  72.14.233.68
12    28 ms    41 ms    55 ms  209.85.244.209
13    33 ms    44 ms    31 ms  216.239.49.133
14     *        *        *     Request timed out.
15    26 ms    25 ms    25 ms  google-public-dns-a.google.com [8.8.8.8]

Trace complete.


--
B.J.



From: Outages <[email protected]> on behalf of "Ryan K. Brooks via 
Outages" <[email protected]>
Reply-To: "Ryan K. Brooks" <[email protected]>
Date: Sunday, July 31, 2016 at 13:02
To: "[email protected]" <[email protected]>
Subject: Re: [outages] Charter Issues


Same in Wisconsin.  High latency and packet loss after a few hops into their 
network.

On 7/31/16 11:54 AM, Matt Freitag via Outages wrote:
Is anyone else experiencing 20% or greater packet loss on their Charter 
connection or is it just local to my area? Coworkers have already confirmed 
it's not just me. We're in the Upper Peninsula of Michigan.

Matt Freitag
Network Engineer I
Information Technology
Michigan Technological University
(906) 487-3696<tel:%28906%29%20487-3696>
https://www.mtu.edu/
https://www.it.mtu.edu/


Disclaimer: This email and its attachments may be confidential and are intended 
solely for the use of the individual to whom it is addressed. Any views or 
opinions expressed are solely those of the author and do not necessarily 
represent those of Kent Record Management Inc. If you are not the intended 
recipient of this email and its attachments, you must take no action based upon 
them, nor must you copy or show them to anyone. Please contact the sender if 
you believe you have received this email in error.
_______________________________________________
Outages mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/outages

Reply via email to