4 ms·
Both Fidelity and Schwab were fine for me on devices where I was already logged in, but logging into a new device wasn’t working. This seems like a common issu
by abadpoli 2y ago
Both Fidelity and Schwab were fine for me on devices where I was already logged in, but logging into a new device wasn’t working.
This seems like a common issue - even if backend systems can take the load, login systems all seem to have a lower TPS limit and have a lot of trouble during big surge events like this. It reminds me a lot of when a new video game releases where the issue is often the login servers being overloaded.
- everybodyknows 2y agoMaybe logins are being throttled deliberately, to protect the transaction servers -- to which all institutional clients are already logged in. West Coast retail customers are out of luck.
- dv_dt 2y agoI can't login on a device i always use, so the failure is more complex than your sample
- abadpoli 2y agoI’m not sure how the inability to login is “more complex”. I clearly state in my comment that logging in wasn’t working.
- dv_dt 2y agoRevalidating session data could be a smaller surface area than validating a fresh login. But if logging in existing devices works in some cases, and doesn't in others, the failure case is more complex than just fresh logins don't work.
- abadpoli 2y agoAh, yes, my original comment was a little unclear. I actually wasn’t logging in on new device vs existing device, it was that I had logged in to one device before 9:30est (presumably before the surge began) and just had an existing already-logged-in-session.