Chase.com is returning errors like "Server too busy" and "500: Server Error [%s]" -- causing folks from this Cleveland Pop Culture Examiner to those taking to Twitter to voice their concerns about the down-time.
"Yeah, mine just hangs there when I try to logon," said an Akron-area man who attempted to login to his Chase.com personal checking account on Friday, February 15, 2013.
He's not alone -- the Chase Bank website downtime has apparently been going on since at least 9:30 a.m. ET, the approximate time period when Matthew Warren Cole tweeted a message saying, "Chase website fail: 500: Server Error [%s]."
Srinath Kota smartly asked Chase Support if Chase.com is indeed down, perhaps alerting the support team initially to the error.
"I can't login into my account. It keeps throwing server is busy error after login," Kota tweeted at approximately 10:00 a.m. ET.
The Chase Support team at https://twitter.com/ChaseSupport has replied to customers concerns about the issue on their official Twitter account, stating, "*ALERT* Chase Online is experiencing intermittent issues. We are working to resolve and will keep you updated."
Judging from the history of this 'Server too busy' error, this is not the first time Chase.com has experienced this type of melee -- although it may be the first instance of it happening in 2013 -- I uncovered evidence of this occurring previously, on March 26, 2012.
With the type of talk about cyber warfare and potential attacks on online banking institutions a topic recently addressed in President Obama's State of the Union speech, we will all breathe a sigh of relief once we're back in our checking accounts and paying bills as normal.
Comments