[outages] Chase.com not responding

[Ben Bartsch]

it is now loading from Baton Rouge, LA

On Wed, Sep 19, 2012 at 11:57 AM, Otis L. Surratt, Jr. <otis at ocosa.com>wrote:

> I agree. Their Android Mobile App still works as well.
>
> Otis
>
>
> From: outages-bounces at outages.org [mailto:outages-bounces at outages.org] On
> Behalf Of Thomas Mackintosh Jr
> Sent: Wednesday, September 19, 2012 11:50 AM
> To: outages at outages.org
> Subject: Re: [outages] Chase.com not responding
>
> Don't think it's quite that simple -- their account management page (
> chaseonline.chase.com) is on the same subnet and is reachable. Seems to
> be isolated to the homepage.
>
> Tom
> On Sep 19, 2012, at 12:43 PM, "Frank Bulk" <frnkblk at iname.com> wrote:
>
>
> I can't even resolve www.chase.com - looks like the DNS servers for
> chase.com are all located in 159.53.0.0/16 (which belongs to JP Morgan
> Chase)
>
>     ns1.jpmorganchase.com 159.53.46.53
>     ns2.jpmorganchase.com 159.53.78.53
>     ns05.jpmorganchase.com 159.53.110.152
>     ns06.jpmorganchase.com 159.53.110.153
>
> Hint: don't put all your DNS servers in your AS or infrastructure.
>
> Frank
>
> From: outages-bounces at outages.org [mailto:outages-bounces at outages.org] On
> Behalf Of Jake Mertel
> Sent: Wednesday, September 19, 2012 11:32 AM
> To: 'Josh Luthman'; outages at outages.org
> Subject: Re: [outages] Chase.com not responding
>
> I can confirm their site  is unreachable from my site as well. Seems to be
> stopping at their network edge. Trace in case anyone is interested:
>
> Microsoft Windows [Version 6.1.7601]
> Copyright (c) 2009 Microsoft Corporation.  All rights reserved.
>
> C:\Users\jake>tracert chase.com
>
> Tracing route to chase.com [159.53.62.93]
> over a maximum of 30 hops:
>
>   1    <1 ms    <1 ms    13 ms  v403.lax.ubiquity.io [72.37.224.129]
>   2     1 ms     1 ms     4 ms  xe-1-0-3.ar1.lax2.us.nlayer.net[69.31.127.45]
>   3    <1 ms    <1 ms    <1 ms  ae1-60g.cr1.lax1.us.nlayer.net[69.31.127.129]
>  4     3 ms     1 ms     1 ms  ae1-50g.ar1.lax1.us.nlayer.net[69.31.127.138]
>   5    <1 ms    <1 ms    <1 ms  TenGigE0-3-4-0.GW4.LAX15.ALTER.NET[152.179.21.1
>   6     8 ms    26 ms    29 ms  0.ge-6-0-0.XL4.LAX15.ALTER.NET[152.63.112.78]
>   7    67 ms    67 ms    67 ms  0.xe-11-1-1.XL4.NYC1.ALTER.NET[152.63.10.101]
>   8    67 ms   103 ms    68 ms  0.xe-9-3-0.GW13.NYC1.ALTER.NET[152.63.5.5]
>   9    70 ms    70 ms    70 ms  jpmchase-gw.customer.alter.net[157.130.250.190]
> 10     *        *        *     Request timed out.
> 11
>
>
> From: outages-bounces at outages.org [mailto:outages-bounces at outages.org] On
> Behalf Of Josh Luthman
> Sent: Wednesday, September 19, 2012 9:25 AM
> To: outages at outages.org
> Subject: [outages] Chase.com not responding
>
> Doesn't work for me near Dayton, OH or isup.me
>
> http://www.downforeveryoneorjustme.com/chase.com
>
> The home page worked not more than 10 minutes ago...
>
> Josh Luthman
> Office: 937-552-2340
> Direct: 937-552-2343
> 1100 Wayne St
> Suite 1337
> Troy, OH 45373
> _______________________________________________
> Outages mailing list
> 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/20120919/d1a10421/attachment.htm>