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
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@outages.org [mailto:outages-bounces@outages.org] On Behalf Of Josh Luthman Sent: Wednesday, September 19, 2012 9:25 AM To: 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 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373
On Sep 19, 2012, at 9:31 AM, Jake Mertel <jake@nobistech.net> wrote:
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:
A few weeks back they changed their web server from (I believe) Sun Webserver over to IIS. Rumor has it from notices they've posted that a new site is forthcoming; guess we'll find out? -- Corey
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@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 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@outages.org [mailto:outages-bounces@outages.org] On Behalf Of Josh Luthman Sent: Wednesday, September 19, 2012 9:25 AM To: outages@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
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@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@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 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@outages.org [mailto:outages-bounces@outages.org] On Behalf Of Josh Luthman Sent: Wednesday, September 19, 2012 9:25 AM To: outages@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@outages.org https://puck.nether.net/mailman/listinfo/outages
I agree. Their Android Mobile App still works as well. Otis From: 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 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@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@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 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@outages.org [mailto:outages-bounces@outages.org] On Behalf Of Josh Luthman Sent: Wednesday, September 19, 2012 9:25 AM To: outages@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@outages.org https://puck.nether.net/mailman/listinfo/outages
it is now loading from Baton Rouge, LA On Wed, Sep 19, 2012 at 11:57 AM, Otis L. Surratt, Jr. <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] On Behalf Of Thomas Mackintosh Jr Sent: Wednesday, September 19, 2012 11:50 AM To: 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) 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> 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@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 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@outages.org [mailto:outages-bounces@outages.org] On Behalf Of Josh Luthman Sent: Wednesday, September 19, 2012 9:25 AM To: outages@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@outages.org https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
Also not accessible from a VPS i have in Germany, however i can resolve chase.com via DNS. On Wed, Sep 19, 2012 at 12:06 PM, Ben Bartsch <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>wrote:
I agree. Their Android Mobile App still works as well.
Otis
From: 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 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@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@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 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@outages.org [mailto:outages-bounces@outages.org] On Behalf Of Josh Luthman Sent: Wednesday, September 19, 2012 9:25 AM To: outages@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@outages.org https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
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>wrote:
Also not accessible from a VPS i have in Germany, however i can resolve chase.com via DNS.
On Wed, Sep 19, 2012 at 12:06 PM, Ben Bartsch <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>wrote:
I agree. Their Android Mobile App still works as well.
Otis
From: 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 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@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@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 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@outages.org [mailto:outages-bounces@outages.org] On Behalf Of Josh Luthman Sent: Wednesday, September 19, 2012 9:25 AM To: outages@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@outages.org https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
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 https://puck.nether.net/mailman/listinfo/outages
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> 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> wrote:
Also not accessible from a VPS i have in Germany, however i can resolve chase.com via DNS.
On Wed, Sep 19, 2012 at 12:06 PM, Ben Bartsch <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> wrote:
I agree. Their Android Mobile App still works as well.
Otis
From: 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 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@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@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 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@outages.org [mailto:outages-bounces@outages.org] On Behalf Of Josh Luthman Sent: Wednesday, September 19, 2012 9:25 AM To: outages@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@outages.org https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
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> 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> 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> wrote:
Also not accessible from a VPS i have in Germany, however i can resolve chase.com via DNS.
On Wed, Sep 19, 2012 at 12:06 PM, Ben Bartsch <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
wrote:
I agree. Their Android Mobile App still works as well.
Otis
From: 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 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@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@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 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@outages.org [mailto:outages-bounces@outages.org ] On Behalf Of Josh Luthman Sent: Wednesday, September 19, 2012 9:25 AM To: outages@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@outages.org https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
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
Working for me from Miami Hernan On Sep 20, 2012, at 8:32 AM, Stefan <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> 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> wrote:
Also not accessible from a VPS i have in Germany, however i can resolve chase.com via DNS.
On Wed, Sep 19, 2012 at 12:06 PM, Ben Bartsch <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> wrote:
I agree. Their Android Mobile App still works as well.
Otis
From: 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 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@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@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 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@outages.org [mailto:outages-bounces@outages.org] On Behalf Of Josh Luthman Sent: Wednesday, September 19, 2012 9:25 AM To: outages@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@outages.org https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
Slow in NY -----Original Message----- From: outages-bounces@outages.org [mailto:outages-bounces@outages.org] On Behalf Of Hernan Banato Sent: Thursday, September 20, 2012 9:35 AM To: Stefan Cc: outages@outages.org Subject: Re: [outages] Chase.com not responding Working for me from Miami Hernan On Sep 20, 2012, at 8:32 AM, Stefan <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> 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=2012091 9&id=15576876
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> wrote:
Also not accessible from a VPS i have in Germany, however i can resolve chase.com via DNS.
On Wed, Sep 19, 2012 at 12:06 PM, Ben Bartsch <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> wrote:
I agree. Their Android Mobile App still works as well.
Otis
From: 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 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@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@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 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@outages.org [mailto:outages-bounces@outages.org] On Behalf Of Josh Luthman Sent: Wednesday, September 19, 2012 9:25 AM To: outages@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@outages.org https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages YES Network, Proprietary & Confidential. The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination, or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer. (c) YES Network, Proprietary & Confidential. The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination, or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.
Down for me too. I am in Milwaukee on a TWTC circuit. On Wed, Sep 19, 2012 at 11:24 AM, Josh Luthman <josh@imaginenetworksllc.com>wrote:
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@outages.org https://puck.nether.net/mailman/listinfo/outages
Same here in NYC over VZB From: outages-bounces@outages.org [mailto:outages-bounces@outages.org] On Behalf Of Grant Ridder Sent: Wednesday, September 19, 2012 12:38 PM To: Josh Luthman Cc: outages@outages.org Subject: Re: [outages] Chase.com not responding Down for me too. I am in Milwaukee on a TWTC circuit. On Wed, Sep 19, 2012 at 11:24 AM, Josh Luthman <josh@imaginenetworksllc.com<mailto:josh@imaginenetworksllc.com>> wrote: 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
Down from Cancun, Mexico Hernan On Sep 19, 2012, at 12:24 PM, Josh Luthman <josh@imaginenetworksllc.com> wrote:
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@outages.org https://puck.nether.net/mailman/listinfo/outages
Same from the 3 locations I am remotely connected to right now. All in Northern Colorado. Blake Pfankuch Cisco, Microsoft, Adtran and VMware Certification Information available upon request. From: outages-bounces@outages.org [mailto:outages-bounces@outages.org] On Behalf Of Josh Luthman Sent: Wednesday, September 19, 2012 10:25 AM To: 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 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373
6 31 ms 40 ms 32 ms v113.core1.lax2.he.net [64.71.131.173] 7 40 ms 30 ms 32 ms las-b3-link.telia.net [213.248.101.29] 8 37 ms 32 ms 42 ms las-bb1-link.telia.net [213.155.130.124] 9 32 ms 30 ms 28 ms att-ic-153025-las-bb1.c.telia.net [80.239.193.214] 10 85 ms 87 ms 85 ms cr2.la2ca.ip.att.net [12.123.30.150] 11 114 ms 103 ms 83 ms cr1.slkut.ip.att.net [12.122.30.29] 12 83 ms 84 ms 84 ms cr2.dvmco.ip.att.net [12.122.30.26] 13 87 ms 98 ms 85 ms cr1.cgcil.ip.att.net [12.122.31.86] 14 83 ms 81 ms 81 ms 12.123.7.21 15 * * * Request timed out. 16 * * * Request timed out. 17 * * From: outages-bounces@outages.org [mailto:outages-bounces@outages.org] On Behalf Of Blake Pfankuch Sent: Wednesday, September 19, 2012 9:39 AM To: Josh Luthman; outages@outages.org Subject: Re: [outages] Chase.com not responding Same from the 3 locations I am remotely connected to right now. All in Northern Colorado. Blake Pfankuch Cisco, Microsoft, Adtran and VMware Certification Information available upon request. From: outages-bounces@outages.org [mailto:outages-bounces@outages.org] On Behalf Of Josh Luthman Sent: Wednesday, September 19, 2012 10:25 AM To: 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 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373
# dig @a.gtld-servers.net. ns chase.com. ;; QUESTION SECTION: ;chase.com. IN NS ;; AUTHORITY SECTION: chase.com. 172800 IN NS ns1.jpmorganchase.com. chase.com. 172800 IN NS ns2.jpmorganchase.com. chase.com. 172800 IN NS ns05.jpmorganchase.com. chase.com. 172800 IN NS ns06.jpmorganchase.com. ;; ADDITIONAL SECTION: ns1.jpmorganchase.com. 172800 IN A 159.53.46.53 ns2.jpmorganchase.com. 172800 IN A 159.53.78.53 ns05.jpmorganchase.com. 172800 IN A 159.53.110.152 ns06.jpmorganchase.com. 172800 IN A 159.53.110.153 Relevant netblocks: 159.53.32.0/19 159.53.64.0/19 159.53.96.0/19 Anyone checked BGP announcements/denouncements, etc.? -- | Jeremy Chadwick jdc@koitsu.org | | UNIX Systems Administrator http://jdc.koitsu.org/ | | Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB | On Wed, Sep 19, 2012 at 12:24:53PM -0400, Josh Luthman wrote:
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@outages.org https://puck.nether.net/mailman/listinfo/outages
Working for me (SF Bay, Comcast). DNS resolves and page loads. www.chase.com is a CNAME for wwwbcchase.gslb.bankone.com. downforeveryoneorjustme.com says it's up now too. Scott On Wed, Sep 19, 2012 at 9:46 AM, Jeremy Chadwick <jdc@koitsu.org> wrote:
# dig @a.gtld-servers.net. ns chase.com.
;; QUESTION SECTION: ;chase.com. IN NS
;; AUTHORITY SECTION: chase.com. 172800 IN NS ns1.jpmorganchase.com. chase.com. 172800 IN NS ns2.jpmorganchase.com. chase.com. 172800 IN NS ns05.jpmorganchase.com. chase.com. 172800 IN NS ns06.jpmorganchase.com.
;; ADDITIONAL SECTION: ns1.jpmorganchase.com. 172800 IN A 159.53.46.53 ns2.jpmorganchase.com. 172800 IN A 159.53.78.53 ns05.jpmorganchase.com. 172800 IN A 159.53.110.152 ns06.jpmorganchase.com. 172800 IN A 159.53.110.153
Relevant netblocks:
159.53.32.0/19 159.53.64.0/19 159.53.96.0/19
Anyone checked BGP announcements/denouncements, etc.?
-- | Jeremy Chadwick jdc@koitsu.org | | UNIX Systems Administrator http://jdc.koitsu.org/ | | Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB |
On Wed, Sep 19, 2012 at 12:24:53PM -0400, Josh Luthman wrote:
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@outages.org https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
participants (19)
-
abe user -
Andreas Welch -
Ben Bartsch -
Blake Pfankuch -
Bret Clark -
Corey Quinn -
Frank Bulk -
Grant Ridder -
Hernan Banato -
Jake Mertel -
Jeremy Chadwick -
Josh Luthman -
Lonnie Bozeman -
Nick D'Attilo -
Otis L. Surratt, Jr. -
Reji Mathew -
Scott Howard -
Stefan -
Thomas Mackintosh Jr