We shared a detailed note here –
We had also shared this note on the a while ago.
Hi thank you, but I think as you have said in the answer that your investigation is ongoing so will wait for the exact reason for the malfunction. Some doubts are there, just curious to know.
-
Only people who were not logging in frequently faced issues or did other people also face the issue?
-
During our investigation, we discovered that there were an unusual number of password reset requests being generated which was causing login issues.
Whether the user request this or was the system malfunctioned and an auto request for resets sent?
- Does this have any connection with election result volatility?
I am also puzzled, because one a/c had all the issues and in another one it worked fine from open.
1 Like
Hi @Chirag1
Our tech infrastructure is designed in such a way that in case of any issue, it doesn’t affect every user. Thereby mitigating the risk to a large extent
1 Like
Woah I thought every users accounts are on different mirrors to mitigate the risks. Never knew it was for chosen ones or random ones. Hope I on a relatively safe server
Hi @AlgoEye
Here’s the RCA for November 6th related issue
+1 … Kite android update was horrendus last night . Logged me out automatically and then enforced 2FA to access it back. In addition back n forth failures of 503 page unavailable errors.
@Meher_Smaran the issue is not from 6th Nov, as we interacted in the other thread the issue persists today and I don’t think its linked to exchange. although an update on the same would be very kind.
We have made some changes in the way our app starts up. Now, we fetch data in the background while you’re on the login screen. This means we directly take you to the bioauth page, and most users won’t see the loading symbol on their screen. Only if the data hasn’t fully loaded while you’re doing the bioauth user will see this loading symbol. We made this change to make the app faster and give you a better experience.