Down from a TWTC circuit in Milwaukee, wi also. The 7th hop is different even though the computers are on the same outbound circuit.<div><br></div><div>WIndows:</div><div><div>Tracing route to <a href="http://capitalone.com">capitalone.com</a> [208.80.48.112]</div>
<div>over a maximum of 30 hops:</div><div><br></div><div> 1 1 ms <1 ms <1 ms x.x.x.x</div><div> 2 1 ms <1 ms <1 ms x.x.x.x</div><div> 3 1 ms 1 ms 1 ms x.x.x.x</div><div> 4 1 ms 1 ms 1 ms x.x.x.x</div>
<div> 5 7 ms 1 ms 1 ms <a href="http://esc033.escriptconnect.com">esc033.escriptconnect.com</a> [64.132.85.33]</div><div> 6 4 ms 4 ms 4 ms <a href="http://chi2-pr1-xe-2-3-0-0.us.twtelecom.net">chi2-pr1-xe-2-3-0-0.us.twtelecom.net</a> [66.192.250.154]</div>
<div> 7 5 ms 4 ms 4 ms 12.249.183.5</div><div> 8 8 ms 6 ms 5 ms <a href="http://cr1.cgcil.ip.att.net">cr1.cgcil.ip.att.net</a> [12.122.133.198]</div><div> 9 4 ms 5 ms 6 ms 12.122.80.113</div>
<div> 10 * * * Request timed out.</div><div> 11 * * * Request timed out.</div><div> 12 * * * Request timed out.</div><div> 13 * * * Request timed out.</div>
<div> 14 * * * Request timed out.</div><div> 15 * * * Request timed out.</div><div> 16 102 ms 203 ms 207 ms 12.90.2.6</div><div> 17 * * * Request timed out.</div>
<div> 18 * * * Request timed out.</div><div> 19 * * * Request timed out.</div><div><br></div>[etc...]</div><div><br></div><div><br><div>Linux:</div><div>traceroute to <a href="http://capitalone.com">capitalone.com</a> (208.80.48.112), 30 hops max, 60 byte packets</div>
<div><div> 1 x.x.x.x (x.x.x.x) 0.946 ms 0.690 ms 3.195 ms</div><div> 2 x.x.x.x (x.x.x.x) 3.024 ms 2.792 ms 2.624 ms</div><div> 3 x.x.x.x (x.x.x.x) 2.424 ms 2.282 ms 2.124 ms</div><div> 4 <a href="http://esc033.escriptconnect.com">esc033.escriptconnect.com</a> (64.132.85.33) 4.713 ms 4.550 ms 4.382 ms</div>
<div> 5 <a href="http://chi2-pr1-xe-2-3-0-0.us.twtelecom.net">chi2-pr1-xe-2-3-0-0.us.twtelecom.net</a> (66.192.250.154) 12.795 ms 13.176 ms 13.007 ms</div><div> 6 12.249.183.5 (12.249.183.5) 4.636 ms 4.543 ms 4.509 ms</div>
<div> 7 <a href="http://cr2.cgcil.ip.att.net">cr2.cgcil.ip.att.net</a> (12.122.132.214) 7.285 ms <a href="http://cr1.cgcil.ip.att.net">cr1.cgcil.ip.att.net</a> (12.122.133.198) 5.742 ms <a href="http://cr2.cgcil.ip.att.net">cr2.cgcil.ip.att.net</a> (12.122.132.214) 5.582 ms</div>
<div> 8 12.122.80.77 (12.122.80.77) 4.901 ms 5.131 ms 12.122.80.113 (12.122.80.113) 5.012 ms</div><div> 9 * * *</div><div>10 * * *</div><div>[etc...]</div></div><div><br></div><div><br></div><div>-Grant</div><br><div class="gmail_quote">
On Wed, Oct 17, 2012 at 11:44 AM, chris <span dir="ltr"><<a href="mailto:tknchris@gmail.com" target="_blank">tknchris@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I have had a few clients point out that <a href="http://capitalone.com" target="_blank">capitalone.com</a> appears to be down<div><br></div><div>DNS resolved to <a href="tel:208.80.48.112" value="+12088048112" target="_blank">208.80.48.112</a> on affected clients on comcast in the northeast</div>
<span class="HOEnZb"><font color="#888888"><div><br></div>
<div>chris</div>
</font></span><br>_______________________________________________<br>
Outages mailing list<br>
<a href="mailto:Outages@outages.org">Outages@outages.org</a><br>
<a href="https://puck.nether.net/mailman/listinfo/outages" target="_blank">https://puck.nether.net/mailman/listinfo/outages</a><br>
<br></blockquote></div><br></div>