I was able to access it earlier today, so apparently it's back down rather than still broken.<br><br><div class="gmail_quote">On Thu, Sep 20, 2012 at 3:32 PM, Stefan <span dir="ltr"><<a href="mailto:netfortius@gmail.com" target="_blank">netfortius@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Still down (<a href="http://www.downforeveryoneorjustme.com/www.chase.com" target="_blank">http://www.downforeveryoneorjustme.com/www.chase.com</a> =><br>
It's not just you! <a href="http://www.chase.com" target="_blank">http://www.chase.com</a> looks down from here).<br>
<br>
But this is no surprise, so I am really not sure why this is a network<br>
[outages] subject. Chase's systems are notorious for failing, for days<br>
in a row, every few months.<br>
<br>
***Stefan<br>
<br>
<br>
On Wed, Sep 19, 2012 at 7:19 PM, abe user <<a href="mailto:abused@citynet.net">abused@citynet.net</a>> wrote:<br>
><br>
> Access is still intermittent from Dayton, OH. Only information I've found<br>
> on the issue thus far:<br>
><br>
> JPMorgan Chase spokesman Patrick Linehan said, "We're experiencing<br>
> intermittent issues with Chase.com. We apologize for any inconvenience and<br>
> are working to restore full connectivity.<br>
><br>
> <a href="http://money.msn.com/business-news/article.aspx?feed=OBR&date=20120919&id=15576876" target="_blank">http://money.msn.com/business-news/article.aspx?feed=OBR&date=20120919&id=15576876</a><br>
><br>
><br>
><br>
> On 09/19/2012 01:22 PM, Ben Bartsch wrote:<br>
><br>
> I spoke too soon. sometimes it loads, but won't when you refresh.<br>
> definitely having issues.<br>
><br>
> On Wed, Sep 19, 2012 at 12:13 PM, Grant Ridder <<a href="mailto:shortdudey123@gmail.com">shortdudey123@gmail.com</a>><br>
> wrote:<br>
>><br>
>> Also not accessible from a VPS i have in Germany, however i can resolve<br>
>> <a href="http://chase.com" target="_blank">chase.com</a> via DNS.<br>
>><br>
>><br>
>> On Wed, Sep 19, 2012 at 12:06 PM, Ben Bartsch <<a href="mailto:uwcableguy@gmail.com">uwcableguy@gmail.com</a>><br>
>> wrote:<br>
>>><br>
>>> it is now loading from Baton Rouge, LA<br>
>>><br>
>>><br>
>>> On Wed, Sep 19, 2012 at 11:57 AM, Otis L. Surratt, Jr. <<a href="mailto:otis@ocosa.com">otis@ocosa.com</a>><br>
>>> wrote:<br>
>>>><br>
>>>> I agree. Their Android Mobile App still works as well.<br>
>>>><br>
>>>> Otis<br>
>>>><br>
>>>><br>
>>>> From: <a href="mailto:outages-bounces@outages.org">outages-bounces@outages.org</a> [mailto:<a href="mailto:outages-bounces@outages.org">outages-bounces@outages.org</a>]<br>
>>>> On Behalf Of Thomas Mackintosh Jr<br>
>>>> Sent: Wednesday, September 19, 2012 11:50 AM<br>
>>>> To: <a href="mailto:outages@outages.org">outages@outages.org</a><br>
>>>> Subject: Re: [outages] Chase.com not responding<br>
>>>><br>
>>>> Don't think it's quite that simple -- their account management page<br>
>>>> (<a href="http://chaseonline.chase.com" target="_blank">chaseonline.chase.com</a>) is on the same subnet and is reachable. Seems to be<br>
>>>> isolated to the homepage.<br>
>>>><br>
>>>> Tom<br>
>>>> On Sep 19, 2012, at 12:43 PM, "Frank Bulk" <<a href="mailto:frnkblk@iname.com">frnkblk@iname.com</a>> wrote:<br>
>>>><br>
>>>><br>
>>>> I can't even resolve <a href="http://www.chase.com" target="_blank">www.chase.com</a> - looks like the DNS servers for<br>
>>>> <a href="http://chase.com" target="_blank">chase.com</a> are all located in <a href="http://159.53.0.0/16" target="_blank">159.53.0.0/16</a> (which belongs to JP Morgan<br>
>>>> Chase)<br>
>>>><br>
>>>> <a href="http://ns1.jpmorganchase.com" target="_blank">ns1.jpmorganchase.com</a> 159.53.46.53<br>
>>>> <a href="http://ns2.jpmorganchase.com" target="_blank">ns2.jpmorganchase.com</a> 159.53.78.53<br>
>>>> <a href="http://ns05.jpmorganchase.com" target="_blank">ns05.jpmorganchase.com</a> 159.53.110.152<br>
>>>> <a href="http://ns06.jpmorganchase.com" target="_blank">ns06.jpmorganchase.com</a> 159.53.110.153<br>
>>>><br>
>>>> Hint: don't put all your DNS servers in your AS or infrastructure.<br>
>>>><br>
>>>> Frank<br>
>>>><br>
>>>> From: <a href="mailto:outages-bounces@outages.org">outages-bounces@outages.org</a> [mailto:<a href="mailto:outages-bounces@outages.org">outages-bounces@outages.org</a>]<br>
>>>> On Behalf Of Jake Mertel<br>
>>>> Sent: Wednesday, September 19, 2012 11:32 AM<br>
>>>> To: 'Josh Luthman'; <a href="mailto:outages@outages.org">outages@outages.org</a><br>
>>>> Subject: Re: [outages] Chase.com not responding<br>
>>>><br>
>>>> I can confirm their site is unreachable from my site as well. Seems to<br>
>>>> be stopping at their network edge. Trace in case anyone is interested:<br>
>>>><br>
>>>> Microsoft Windows [Version 6.1.7601]<br>
>>>> Copyright (c) 2009 Microsoft Corporation. All rights reserved.<br>
>>>><br>
>>>> C:\Users\jake>tracert <a href="http://chase.com" target="_blank">chase.com</a><br>
>>>><br>
>>>> Tracing route to <a href="http://chase.com" target="_blank">chase.com</a> [159.53.62.93]<br>
>>>> over a maximum of 30 hops:<br>
>>>><br>
>>>> 1 <1 ms <1 ms 13 ms <a href="http://v403.lax.ubiquity.io" target="_blank">v403.lax.ubiquity.io</a> [72.37.224.129]<br>
>>>> 2 1 ms 1 ms 4 ms <a href="http://xe-1-0-3.ar1.lax2.us.nlayer.net" target="_blank">xe-1-0-3.ar1.lax2.us.nlayer.net</a><br>
>>>> [69.31.127.45]<br>
>>>> 3 <1 ms <1 ms <1 ms <a href="http://ae1-60g.cr1.lax1.us.nlayer.net" target="_blank">ae1-60g.cr1.lax1.us.nlayer.net</a><br>
>>>> [69.31.127.129]<br>
>>>> 4 3 ms 1 ms 1 ms <a href="http://ae1-50g.ar1.lax1.us.nlayer.net" target="_blank">ae1-50g.ar1.lax1.us.nlayer.net</a><br>
>>>> [69.31.127.138]<br>
>>>> 5 <1 ms <1 ms <1 ms <a href="http://TenGigE0-3-4-0.GW4.LAX15.ALTER.NET" target="_blank">TenGigE0-3-4-0.GW4.LAX15.ALTER.NET</a><br>
>>>> [152.179.21.1<br>
>>>> 6 8 ms 26 ms 29 ms <a href="http://0.ge-6-0-0.XL4.LAX15.ALTER.NET" target="_blank">0.ge-6-0-0.XL4.LAX15.ALTER.NET</a><br>
>>>> [152.63.112.78]<br>
>>>> 7 67 ms 67 ms 67 ms <a href="http://0.xe-11-1-1.XL4.NYC1.ALTER.NET" target="_blank">0.xe-11-1-1.XL4.NYC1.ALTER.NET</a><br>
>>>> [152.63.10.101]<br>
>>>> 8 67 ms 103 ms 68 ms <a href="http://0.xe-9-3-0.GW13.NYC1.ALTER.NET" target="_blank">0.xe-9-3-0.GW13.NYC1.ALTER.NET</a><br>
>>>> [152.63.5.5]<br>
>>>> 9 70 ms 70 ms 70 ms <a href="http://jpmchase-gw.customer.alter.net" target="_blank">jpmchase-gw.customer.alter.net</a><br>
>>>> [157.130.250.190]<br>
>>>> 10 * * * Request timed out.<br>
>>>> 11<br>
>>>><br>
>>>><br>
>>>> From: <a href="mailto:outages-bounces@outages.org">outages-bounces@outages.org</a> [mailto:<a href="mailto:outages-bounces@outages.org">outages-bounces@outages.org</a>]<br>
>>>> On Behalf Of Josh Luthman<br>
>>>> Sent: Wednesday, September 19, 2012 9:25 AM<br>
>>>> To: <a href="mailto:outages@outages.org">outages@outages.org</a><br>
>>>> Subject: [outages] Chase.com not responding<br>
>>>><br>
>>>> Doesn't work for me near Dayton, OH or <a href="http://isup.me" target="_blank">isup.me</a><br>
>>>><br>
>>>> <a href="http://www.downforeveryoneorjustme.com/chase.com" target="_blank">http://www.downforeveryoneorjustme.com/chase.com</a><br>
>>>><br>
>>>> The home page worked not more than 10 minutes ago...<br>
>>>><br>
>>>> Josh Luthman<br>
>>>> Office: <a href="tel:937-552-2340" value="+19375522340">937-552-2340</a><br>
>>>> Direct: <a href="tel:937-552-2343" value="+19375522343">937-552-2343</a><br>
>>>> 1100 Wayne St<br>
>>>> Suite 1337<br>
>>>> Troy, OH 45373<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>
>>>><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>
>>><br>
>>><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>
>><br>
><br>
><br>
><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>
><br>
><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>
_______________________________________________<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>
</blockquote></div><br>