[outages] TWC outages

Adam Greene maillist at webjogger.net
Thu Aug 30 16:21:00 EDT 2012


Things seem to get bad at hop 8 (107.14.17.173)

traceroute to www.yahoo.com (98.138.253.109), 30 hops max, 60 byte packets
  1  204.8.80.17 (204.8.80.17)  0.912 ms  1.070 ms  1.256 ms
  2  10049.webjogger.net (204.8.80.49)  2.446 ms  2.444 ms  2.432 ms
  3  cpe-24-29-112-25.nyc.res.rr.com (24.29.112.25)  10.993 ms 10.993 
ms  10.982 ms
  4  ten-1-1-5-nycmnytga7750sr099.nyc.rr.com (69.193.225.222)  16.520 
ms  16.531 ms  16.521 ms
  5  bun1-nycmnytg-rtr001.nyc.rr.com (24.29.148.73)  16.486 ms 16.476 
ms  16.465 ms
  6  bun6-nycmnytg-rtr002.nyc.rr.com (24.29.148.250)  18.120 ms 17.039 ms *
  7  ae-4-0.cr0.nyc30.tbone.rr.com (66.109.6.78)  17.742 ms  16.339 ms  
17.506 ms
* 8  107.14.17.173 (107.14.17.173)  71.405 ms  67.471 ms  65.846 ms*
  9  ae-8-0.cr0.chi10.tbone.rr.com (66.109.6.25)  65.914 ms 107.14.19.34 
(107.14.19.34)  61.833 ms  70.927 ms
10  ae-0-0.cr0.chi30.tbone.rr.com (66.109.6.21)  66.835 ms  66.834 ms  
66.441 ms
11  ae-2-0.cr0.dfw10.tbone.rr.com (66.109.6.22)  69.471 ms 
ae15.120.pr0.dfw10.tbone.rr.com (66.109.9.41)  62.811 ms  62.778 ms
12  ae-3-0.pr0.dfw10.tbone.rr.com (66.109.6.209)  101.383 ms 
ae-1-0.pr0.dfw10.tbone.rr.com (66.109.6.179)  101.348 ms  60.769 ms
13  66.109.10.169 (66.109.10.169)  62.555 ms 66.109.9.191 
(66.109.9.191)  62.500 ms 66.109.10.171 (66.109.10.171)  62.524 ms
14  ae-3.pat2.dnx.yahoo.com (216.115.96.58)  98.932 ms  99.981 ms 
ae-9.pat1.dnx.yahoo.com (216.115.96.79)  99.537 ms
15  ae-6.pat1.nez.yahoo.com (216.115.104.118)  107.224 ms 
ae-7.pat2.nez.yahoo.com (216.115.104.126)  149.888 ms 
ae-0.pat2.nez.yahoo.com (216.115.100.10)  104.932 ms
16  xe-5-0-0.msr1.ne1.yahoo.com (216.115.100.1)  122.856 ms 
xe-7-0-0.msr2.ne1.yahoo.com (216.115.100.7)  132.237 ms 
xe-5-0-0.msr2.ne1.yahoo.com (216.115.100.3)  109.687 ms
17  xe-4-0-0.clr1-a-gdc.ne1.yahoo.com (98.138.144.21)  100.303 ms 
xe-7-0-0.clr2-a-gdc.ne1.yahoo.com (98.138.0.27)  112.824 ms 
xe-8-0-0.clr1-a-gdc.ne1.yahoo.com (98.138.144.29)  137.603 ms
18  et-17-1.fab1-1-gdc.ne1.yahoo.com (98.138.0.79)  131.838 ms 
et-18-25.fab3-1-gdc.ne1.yahoo.com (98.138.0.89)  118.462 ms 
et-17-1.fab2-1-gdc.ne1.yahoo.com (98.138.0.81)  139.356 ms
19  po-10.bas2-7-prd.ne1.yahoo.com (98.138.240.22)  112.879 ms 
po-12.bas2-7-prd.ne1.yahoo.com (98.138.240.26)  111.829 ms 
po-11.bas2-7-prd.ne1.yahoo.com (98.138.240.24)  116.293 ms
20  * * *

traceroute to 204.70.25.234 (204.70.25.234), 30 hops max, 60 byte packets
  1  204.8.80.17 (204.8.80.17)  0.698 ms  1.180 ms  1.372 ms
  2  10049.webjogger.net (204.8.80.49)  2.436 ms  2.435 ms  2.427 ms
  3  cpe-24-29-112-25.nyc.res.rr.com (24.29.112.25)  11.532 ms 11.534 
ms  11.526 ms
  4  ten-1-1-5-nycmnytga7750sr099.nyc.rr.com (69.193.225.222)  14.464 
ms  14.544 ms  14.535 ms
  5  bun1-nycmnytg-rtr001.nyc.rr.com (24.29.148.73)  14.345 ms 14.496 
ms  14.494 ms
  6  bun6-nycmnytg-rtr002.nyc.rr.com (24.29.148.250)  16.343 ms 14.931 
ms  14.892 ms
  7  107.14.19.24 (107.14.19.24)  18.356 ms  17.226 ms  17.211 ms
* 8  107.14.17.173 (107.14.17.173)  67.914 ms 
ae-0-0.cr0.nyc20.tbone.rr.com (66.109.6.27)  65.741 ms 107.14.17.173 
(107.14.17.173)  68.455 ms*
  9  107.14.19.34 (107.14.19.34)  70.470 ms  61.953 ms  69.257 ms
10  ae-0-0.cr0.chi30.tbone.rr.com (66.109.6.21)  62.538 ms  65.612 ms  
67.378 ms
11  ae15.120.pr0.dfw10.tbone.rr.com (66.109.9.41)  60.999 ms 
ae-2-0.cr0.dfw10.tbone.rr.com (66.109.6.22)  68.423 ms  64.736 ms
12  ae-1-0.pr0.dfw10.tbone.rr.com (66.109.6.179)  61.626 ms  61.912 ms 
ae-3-0.pr0.dfw10.tbone.rr.com (66.109.6.209)  61.879 ms
13  107.14.16.30 (107.14.16.30)  62.092 ms  63.696 ms  60.554 ms
14  dpr1-ge-2-0-0.dallasequinix.savvis.net (204.70.204.146)  67.976 ms  
85.239 ms  60.964 ms
15  cr2-tengige0-7-5-0.dallas.savvis.net (204.70.196.29)  63.074 ms 
62.595 ms  62.438 ms
16  cr1-te-0-6-0-1.sfo.savvis.net (206.28.96.86)  106.205 ms 105.637 ms  
105.625 ms
17  ges1-ge-1-1.sanfranciscosfo.savvis.net (206.24.211.90)  106.065 ms  
106.051 ms  106.018 ms
18  ns03.savvis.net (204.70.25.234)  105.284 ms  107.566 ms  104.862 ms



On 8/30/2012 4:11 PM, Brian Henson wrote:
> Same here in dayton
>
> On Thu, Aug 30, 2012 at 3:49 PM, Josh Luthman 
> <josh at imaginenetworksllc.com <mailto:josh at imaginenetworksllc.com>> wrote:
>
>     Not effecting me near Dayton Ohio going through Cleveland Ohio.
>
>     C:\Users\jluthman>tracert 4.2.2.2
>       1    <1 ms    <1 ms     2 ms router.toobs.com
>     <http://router.toobs.com> [192.168.21.1]
>       2     2 ms     1 ms     4 ms fwb-74-218-208-209.inxnet.net
>     <http://fwb-74-218-208-209.inxnet.net> [74.218.208.209]
>       3     1 ms     1 ms     1 ms fwb-74-218-88-133.inxnet.net
>     <http://fwb-74-218-88-133.inxnet.net> [74.218.88.133]
>       4     3 ms     3 ms     2 ms fwb-74-218-88-129.inxnet.net
>     <http://fwb-74-218-88-129.inxnet.net> [74.218.88.129]
>       5    10 ms    10 ms    11 ms ae1.tr00.clevohek.mwrtn.rr.com
>     <http://ae1.tr00.clevohek.mwrtn.rr.com> [65.189.140.130]
>       6    22 ms    24 ms    20 ms  107.14.19.58
>       7    37 ms    19 ms    18 ms ae-1-0.pr0.dca20.tbone.rr.com
>     <http://ae-1-0.pr0.dca20.tbone.rr.com> [66.109.6.167]
>       8    23 ms    25 ms    18 ms
>     xe-4-3-0.edge2.washington1.level3.net
>     <http://xe-4-3-0.edge2.washington1.level3.net> [4.79.22.49]
>       9    18 ms    19 ms    18 ms
>     ae-21-70.car1.washington1.level3.net
>     <http://ae-21-70.car1.washington1.level3.net> [4.69.149.67]
>      10    19 ms    18 ms    18 ms b.resolvers.level3.net
>     <http://b.resolvers.level3.net> [4.2.2.2]
>
>     C:\Users\jluthman>tracert www.google.com <http://www.google.com>
>       1    <1 ms    <1 ms    <1 ms router.toobs.com
>     <http://router.toobs.com> [192.168.21.1]
>       2     2 ms     3 ms     2 ms fwb-74-218-208-209.inxnet.net
>     <http://fwb-74-218-208-209.inxnet.net> [74.218.208.209]
>       3     1 ms     2 ms     1 ms fwb-74-218-88-133.inxnet.net
>     <http://fwb-74-218-88-133.inxnet.net> [74.218.88.133]
>       4     1 ms     1 ms     1 ms fwb-74-218-88-129.inxnet.net
>     <http://fwb-74-218-88-129.inxnet.net> [74.218.88.129]
>       5    12 ms    11 ms    11 ms ae0.tr00.clevohek.mwrtn.rr.com
>     <http://ae0.tr00.clevohek.mwrtn.rr.com> [65.189.140.144]
>       6    23 ms    23 ms    22 ms ae-3-0.cr0.dca20.tbone.rr.com
>     <http://ae-3-0.cr0.dca20.tbone.rr.com> [66.109.6.70]
>       7    19 ms    20 ms    27 ms ae-1-0.pr0.dca10.tbone.rr.com
>     <http://ae-1-0.pr0.dca10.tbone.rr.com> [66.109.6.165]
>       8    88 ms    85 ms    84 ms  66.109.9.66
>       9    19 ms    20 ms    20 ms 209.85.252.46 <tel:209.85.252.46>
>      10    20 ms    22 ms    21 ms  72.14.236.98
>      11    28 ms    28 ms    27 ms  72.14.235.12
>      12    35 ms    34 ms    34 ms  72.14.239.64
>      13    35 ms    40 ms    34 ms  209.85.254.247
>      14     *        *        *     Request timed out.
>      15    34 ms    34 ms    34 ms gh-in-f104.1e100.net
>     <http://gh-in-f104.1e100.net> [74.125.130.104]
>
>     Josh Luthman
>     Office: 937-552-2340 <tel:937-552-2340>
>     Direct: 937-552-2343 <tel:937-552-2343>
>     1100 Wayne St
>     Suite 1337
>     Troy, OH 45373
>
>
>
>     On Thu, Aug 30, 2012 at 3:42 PM, Adam Greene
>     <maillist at webjogger.net <mailto:maillist at webjogger.net>> wrote:
>
>         Time Warner seems to be having an issue affecting all accounts
>         in the North East, as per their support line.
>
>         >From 14:45 - 15:00 EST we saw packet loss and high latency on
>         our fiber circuit to them. Additionally, phone service
>         provided over coax experienced a total outage.
>
>         As of 15:00 the packet loss has ceased and dial tone is back,
>         however, latency is very high (100ms - 800ms) to locations
>         outside the TWC network.
>
>         FYI.
>         _______________________________________________
>         Outages mailing list
>         Outages at outages.org <mailto:Outages at outages.org>
>         https://puck.nether.net/mailman/listinfo/outages
>
>
>
>     _______________________________________________
>     Outages mailing list
>     Outages at outages.org <mailto:Outages at outages.org>
>     https://puck.nether.net/mailman/listinfo/outages
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/outages/attachments/20120830/311ef9d9/attachment.htm>


More information about the Outages mailing list