Fidelity CC-505 Error on all accounts / Fidelity Reporting Connection Issue error

Mark Wagner · February 21

Transaction download not working at all today for all Fidelity accounts 2/21/26. CC-505 error on all Fidelity accounts.

Quicken Classic for Windows (R66.12) on Windows 11.

Mark Wagner · February 21

[Removed - Duplicate Post]

BSJ · February 21

I also am seeing CC-505 error on all my Fidelity accounts…

Tommy · February 21

CC-505 on all Fidelity Investment accounts.

I then attempted to 'Reset Account' on the 'Online Services' tab, which deactivated the account. 😡

John QW · February 21

FYI, I was getting the same CC-505 this AM on all Fidelity.. A quick search led me to this:

https://www.quicken.com/support/error-when-using-online-services-cc-505/

And, well, thats a new one for me. Selected "update transactions" from the gear options on the account register and that set off an update operation.. which completed without error… but 0 transactions downloaded. An OSU right after this was successful with all the transactions expected.. for all accounts.

Tony Luers · February 21

Same here on all Fidelity accounts.

CC-505 error

jersey42 · February 21

Same here. Will try again later.

jersey42 · February 21

There is now an error message that says the problem should be resolved by 10:00 AM EST.

GermanBlueRam · February 21

https://community.quicken.com/discussion/comment/20539083#Comment_20539083

My message says 9:00 AM MST.

Quicken Anja · February 21

Hello All,

Thank you for taking the time to report this issue.

We will be forwarding this issue to the proper channels to have this further investigated. However, we request that you please navigate to Help > Report a problem within your Quicken program and submit a problem report with log files and screenshots attached in order to contribute to the investigation.

It would also aid the investigation to include a sanitized file when submitting the problem report. A sanitized file is a data file that removes personally identifiable information so you can comfortably share this file with the Quicken team.

While you will not receive a response through this submission, these reports will help our teams in further investigating the issue. The more problem reports we receive, the better.

Please let us know once that is done, and we apologize for any inconvenience in the meantime! Thank you.
(CBT-1044)

Mark Wagner · February 21

@Quicken Anja

Thanks for the follow-up. Based on the latest error message it appears Fidelity is aware of the problem. I'll test again after 11 AM ET which is when the current error message indicates the connection problem should be resolved.

Quicken Anja · February 21

Thanks for the update, @Mark Wagner. Sounds good—please test after the indicated timeframe and let us know if any issues persist.

GermanBlueRam · February 21

Looks like the fix has been pushed by a couple of hours.

Alan C · February 21

Attempted to download Fidelity transactions this morning, Feb. 21, 2026, and while Quicken appeared to process transactions, no transactions were recorded in accounts. Tried resetting account but no success.

Seems some other folks are experiencing issues.

Quicken, please advise asap if there is an issue and if so, please advise when this will be resolved.

Thank you.

Mark Wagner · February 21

Pushed back again till 1 PM ET. Will check back in later this afternoon.

cyberphile · February 21

As of now, Fidelity is showing connections blocked until 10am PST.

Tony Luers · February 21

Time has now extended to 13:00 EST.

Quicken Anja · February 21

Hello All,

Thank you for the updates and for sharing your experiences with the Fidelity connection this morning.

Please be advised that this issue has been confirmed to be on Fidelity’s end. They are aware of the problem, and our teams are monitoring it as well. The connection issue should be resolved between today and tomorrow.

If you continue to experience CC-505 or the “connection issue” error message by Monday morning, please let us know so we can investigate further.

Thank you for your patience!

Mark Wagner · February 21

@Quicken Anja

Just tested and the connection problem seems to be resolved, at least for me. Thanks.

GermanBlueRam · February 21

No connection error messages, but no transactions for February 20, either. 😕 It appears that I will need to manually enter the trades I made that day.

max58 · February 21

https://community.quicken.com/discussion/comment/20539163#Comment_20539163

Same here. It's 11:24 AM PST. Still not resolved yet.

jersey42 · February 21

I just tried for the third time. Connection was successful, but only one of five transactions (from 3 different accounts) downloaded. I manually entered the other four.

The last time I had a connection error with Fidelity, I had similar results. A few transactions did not download, and they never downloaded in future One Step Updates. This happened at the same time of the CvrShrt problem. This is the first Fidelity issue I have had since then.

Tony Luers · February 21

I just updated at 3:50 EST, all updated fine.

Chuck56 · February 21

same here

NotACPA · February 21

@Quicken Anja

I ran l OSU on the file for a club where I'm the Treasurer at 4:02pm CST.

The club's file uses the "Show Cash in a Checking account" feature, and a deposit came down properly, and was reflected in the pseudo-checking account.

BUT, when I accepted the txn in the checking account, the red flag in the associated brokerage account didn't also clear … which is new behavior.

There were no other downloaded txn and it several attempts at "clicking around" to get the flag in the brokerage account to clear.

Business & Personal R66.11

[EDIT] I updated to R66.12 and restored a backup and re-downloaded … the flag in the brokerage account remained stubborn, only clearing after several attempts. [/EDIT]

GermanBlueRam · February 21

I tried another download at 3:30 MST, and this time the transactions for February 20 appeared.

Which is good, because there were about a dozen of them across two accounts. 👍️

Fidelity CC-505 Error on all accounts / Fidelity Reporting Connection Issue error

Comments

Categories