[outages] capitalone.com

[Chris Stone]

Works for me here in Colorado through both CenturyLink and Cogent. Resolves 
to 208.80.48.112 for http://capitalone.com which redirects me to the same IP 
for https://www.capitalone.com.


Chris

On 10/17/2012 10:58 AM, Grant Ridder wrote:
> Down from a TWTC circuit in Milwaukee, wi also.  The 7th hop is different 
> even though the computers are on the same outbound circuit.
>
> WIndows:
> Tracing route to capitalone.com <http://capitalone.com> [208.80.48.112]
> over a maximum of 30 hops:
>
>   1     1 ms    <1 ms    <1 ms  x.x.x.x
>   2     1 ms    <1 ms    <1 ms  x.x.x.x
>   3     1 ms     1 ms     1 ms  x.x.x.x
>   4     1 ms     1 ms     1 ms  x.x.x.x
>   5     7 ms     1 ms     1 ms esc033.escriptconnect.com 
> <http://esc033.escriptconnect.com> [64.132.85.33]
>   6     4 ms     4 ms     4 ms chi2-pr1-xe-2-3-0-0.us.twtelecom.net 
> <http://chi2-pr1-xe-2-3-0-0.us.twtelecom.net> [66.192.250.154]
>   7     5 ms     4 ms     4 ms  12.249.183.5
>   8     8 ms     6 ms     5 ms cr1.cgcil.ip.att.net 
> <http://cr1.cgcil.ip.att.net> [12.122.133.198]
>   9     4 ms     5 ms     6 ms  12.122.80.113
>  10     *        *        *     Request timed out.
>  11     *        *        *     Request timed out.
>  12     *        *        *     Request timed out.
>  13     *        *        *     Request timed out.
>  14     *        *        *     Request timed out.
>  15     *        *        *     Request timed out.
>  16   102 ms   203 ms   207 ms  12.90.2.6
>  17     *        *        *     Request timed out.
>  18     *        *        *     Request timed out.
>  19     *        *        *     Request timed out.
>
> [etc...]
>
>
> Linux:
> traceroute to capitalone.com <http://capitalone.com> (208.80.48.112), 30 
> hops max, 60 byte packets
>  1  x.x.x.x (x.x.x.x)  0.946 ms  0.690 ms  3.195 ms
>  2  x.x.x.x (x.x.x.x)  3.024 ms  2.792 ms  2.624 ms
>  3  x.x.x.x (x.x.x.x)  2.424 ms  2.282 ms  2.124 ms
>  4 esc033.escriptconnect.com <http://esc033.escriptconnect.com> 
> (64.132.85.33)  4.713 ms  4.550 ms  4.382 ms
>  5 chi2-pr1-xe-2-3-0-0.us.twtelecom.net 
> <http://chi2-pr1-xe-2-3-0-0.us.twtelecom.net> (66.192.250.154)  12.795 ms 
>  13.176 ms  13.007 ms
>  6  12.249.183.5 (12.249.183.5)  4.636 ms  4.543 ms  4.509 ms
>  7 cr2.cgcil.ip.att.net <http://cr2.cgcil.ip.att.net> (12.122.132.214) 
>  7.285 ms cr1.cgcil.ip.att.net <http://cr1.cgcil.ip.att.net> 
> (12.122.133.198)  5.742 ms cr2.cgcil.ip.att.net 
> <http://cr2.cgcil.ip.att.net> (12.122.132.214)  5.582 ms
>  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
>  9  * * *
> 10  * * *
> [etc...]
>
>
> -Grant
>
> On Wed, Oct 17, 2012 at 11:44 AM, chris <tknchris at gmail.com 
> <mailto:tknchris at gmail.com>> wrote:
>
>     I have had a few clients point out that capitalone.com
>     <http://capitalone.com> appears to be down
>
>     DNS resolved to 208.80.48.112 <tel:208.80.48.112> on affected clients
>     on comcast in the northeast
>
>     chris
>
>     _______________________________________________
>     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
> https://puck.nether.net/mailman/listinfo/outages

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/outages/attachments/20121017/9e95c9bd/attachment.htm>