Working fine for me...fast and response. Smells like a DDoS attack. On 09/20/2012 08:59 AM, Andreas Welch wrote:
I was able to access it earlier today, so apparently it's back down rather than still broken.
On Thu, Sep 20, 2012 at 3:32 PM, Stefan <netfortius@gmail.com <mailto:netfortius@gmail.com>> wrote:
Still down (http://www.downforeveryoneorjustme.com/www.chase.com => It's not just you! http://www.chase.com looks down from here).
But this is no surprise, so I am really not sure why this is a network [outages] subject. Chase's systems are notorious for failing, for days in a row, every few months.
***Stefan
On Wed, Sep 19, 2012 at 7:19 PM, abe user <abused@citynet.net <mailto:abused@citynet.net>> wrote: > > Access is still intermittent from Dayton, OH. Only information I've found > on the issue thus far: > > JPMorgan Chase spokesman Patrick Linehan said, "We're experiencing > intermittent issues with Chase.com. We apologize for any inconvenience and > are working to restore full connectivity. > > http://money.msn.com/business-news/article.aspx?feed=OBR&date=20120919&id=15... > > > > On 09/19/2012 01:22 PM, Ben Bartsch wrote: > > I spoke too soon. sometimes it loads, but won't when you refresh. > definitely having issues. > > On Wed, Sep 19, 2012 at 12:13 PM, Grant Ridder <shortdudey123@gmail.com <mailto:shortdudey123@gmail.com>> > wrote: >> >> Also not accessible from a VPS i have in Germany, however i can resolve >> chase.com <http://chase.com> via DNS. >> >> >> On Wed, Sep 19, 2012 at 12:06 PM, Ben Bartsch <uwcableguy@gmail.com <mailto:uwcableguy@gmail.com>> >> wrote: >>> >>> it is now loading from Baton Rouge, LA >>> >>> >>> On Wed, Sep 19, 2012 at 11:57 AM, Otis L. Surratt, Jr. <otis@ocosa.com <mailto:otis@ocosa.com>> >>> wrote: >>>> >>>> I agree. Their Android Mobile App still works as well. >>>> >>>> Otis >>>> >>>> >>>> From: outages-bounces@outages.org <mailto:outages-bounces@outages.org> [mailto:outages-bounces@outages.org <mailto:outages-bounces@outages.org>] >>>> On Behalf Of Thomas Mackintosh Jr >>>> Sent: Wednesday, September 19, 2012 11:50 AM >>>> To: outages@outages.org <mailto:outages@outages.org> >>>> Subject: Re: [outages] Chase.com not responding >>>> >>>> Don't think it's quite that simple -- their account management page >>>> (chaseonline.chase.com <http://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@iname.com <mailto:frnkblk@iname.com>> wrote: >>>> >>>> >>>> I can't even resolve www.chase.com <http://www.chase.com> - looks like the DNS servers for >>>> chase.com <http://chase.com> are all located in 159.53.0.0/16 <http://159.53.0.0/16> (which belongs to JP Morgan >>>> Chase) >>>> >>>> ns1.jpmorganchase.com <http://ns1.jpmorganchase.com> 159.53.46.53 >>>> ns2.jpmorganchase.com <http://ns2.jpmorganchase.com> 159.53.78.53 >>>> ns05.jpmorganchase.com <http://ns05.jpmorganchase.com> 159.53.110.152 >>>> ns06.jpmorganchase.com <http://ns06.jpmorganchase.com> 159.53.110.153 >>>> >>>> Hint: don't put all your DNS servers in your AS or infrastructure. >>>> >>>> Frank >>>> >>>> From: outages-bounces@outages.org <mailto:outages-bounces@outages.org> [mailto:outages-bounces@outages.org <mailto:outages-bounces@outages.org>] >>>> On Behalf Of Jake Mertel >>>> Sent: Wednesday, September 19, 2012 11:32 AM >>>> To: 'Josh Luthman'; outages@outages.org <mailto:outages@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 <http://chase.com> >>>> >>>> Tracing route to chase.com <http://chase.com> [159.53.62.93] >>>> over a maximum of 30 hops: >>>> >>>> 1 <1 ms <1 ms 13 ms v403.lax.ubiquity.io <http://v403.lax.ubiquity.io> [72.37.224.129] >>>> 2 1 ms 1 ms 4 ms xe-1-0-3.ar1.lax2.us.nlayer.net <http://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 <http://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 <http://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 <http://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 <http://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 <http://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 <http://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 <http://jpmchase-gw.customer.alter.net> >>>> [157.130.250.190] >>>> 10 * * * Request timed out. >>>> 11 >>>> >>>> >>>> From: outages-bounces@outages.org <mailto:outages-bounces@outages.org> [mailto:outages-bounces@outages.org <mailto:outages-bounces@outages.org>] >>>> On Behalf Of Josh Luthman >>>> Sent: Wednesday, September 19, 2012 9:25 AM >>>> To: outages@outages.org <mailto:outages@outages.org> >>>> Subject: [outages] Chase.com not responding >>>> >>>> Doesn't work for me near Dayton, OH or isup.me <http://isup.me> >>>> >>>> http://www.downforeveryoneorjustme.com/chase.com >>>> >>>> The home page worked not more than 10 minutes ago... >>>> >>>> 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 >>>> _______________________________________________ >>>> Outages mailing list >>>> Outages@outages.org <mailto:Outages@outages.org> >>>> https://puck.nether.net/mailman/listinfo/outages >>>> >>>> >>>> _______________________________________________ >>>> Outages mailing list >>>> Outages@outages.org <mailto:Outages@outages.org> >>>> https://puck.nether.net/mailman/listinfo/outages >>> >>> >>> >>> _______________________________________________ >>> Outages mailing list >>> Outages@outages.org <mailto:Outages@outages.org> >>> https://puck.nether.net/mailman/listinfo/outages >>> >> > > > > _______________________________________________ > Outages mailing list > Outages@outages.org <mailto:Outages@outages.org> > https://puck.nether.net/mailman/listinfo/outages > > > > _______________________________________________ > Outages mailing list > Outages@outages.org <mailto:Outages@outages.org> > https://puck.nether.net/mailman/listinfo/outages > _______________________________________________ Outages mailing list Outages@outages.org <mailto:Outages@outages.org> https://puck.nether.net/mailman/listinfo/outages