It’s still very slow for me and sometimes I’m unable to authenticate.
So, some updates: The suspicion is one of the NNS nodes running far behind, slowing down the subnet on finalization. There are 2 steps to resolve the issue:
- Remove the problematic node with proposal (
#81002) - Update boundary node config to avoid routing to the problematic node
While both steps are necessary, the 1st step is critical to restore service speed. The 2nd step has been executed but the proposal is not executed yet.
And we are stuck on voting YES because some of us still cannot access NNS to vote?
With command line it is still possible to vote.
Last update:
-
Above mentionned proposal #81002 has been executed now but, its status is not reflected in the dashboard.
-
In addition to what I say above, it actually needs an additional proposal #81403 to remove the problematic node I understand
Once this last proposition executed, will need some checks to see if finally bring everything back in place.
The voting result as of 09-19-2022 5:04AM UTC was 0.473% Yes and 0.006%No.
How did the proposal get executed? Should the dashboard be not trusted?
Like I said in my above message, the status in the dashboard is not reflected - i.e. is not up-to-date.
#81403 has been executed and performance should be improved now!
Let me know if that works for you?
2 Likes
Yes sir,
we are back in action.
Hopefully it can be maintaind to operate.
Thanks for the update 
1 Like
Looks fine from my side, too.
1 Like
My understanding is that node providers cannot currently be slashed due to the contracts originally put in place(I understand this was necessary to bootstrap). What is the long-term thinking about this? We shouldn’t have had to take this action if the node providers were properly incentivized to make sure their nodes kept up.
1 Like
I think there should be quarantine.
If the monitoring system detects a failure on a node, then it moves the node to quarantine for a certain time (depending on the type of failure).
The time spent in quarantine is then subtracted from the node’s reward.
afaik there is no form of slashing planned, only removal from subnet and remuneration penalties.
My nns just keeps loading and will not allow me access it. I have tried on multiple devices.
Hanging in NNS or hanging in II?
If NNS, issue will be resolved with the next version that was proposed.
If II, I’m not aware of an issue but someone mentionned something in another thread which was resolved.
The link you provided did the same thing the issue is still not resolved for me
The proposal has not yet been executed therefore the fix has not been yet rolled out.
Should of specified that logging into the NNS via computer worked for me after a few tries, still no luck with the phone.
I’m not aware of any issue on computer. The unreleased fix is specific for iOS 15.