No further updates from storj on the issue?
I wouldn’t have expected any updates during the weekend.
Update
They are back with a vengeance this time.
The vengeance started exactly at 07:00 UTC, 30K errors so far.
Yep they are back back back
It’s not weekend any more.
We are not there yet
I will update the thread when the problem would be solved.
No actions are needed.
The issue should be resolved now.
Thanks for the awesome work on a quick resolution! Everything looks fine on my end now.
My curiosity is peaked, If anyone has the time I’d love to hear a bit about what happened that caused this?
We removed consequences. The root issue is not solved yet.
no issues for approximately over 36 hours, ill say thats a win…
The investigation in progress, I have no updates so far.
I can only say that in normal circumstances it’s not reproduced.
Thank you for the update.
Thanks for the update again. If we can help by providing more info or logs or anything else on our end, please don’t hesitate to ask!
Thank you, but not needed at the moment.
I would like to step up to queue waiting for explanation of root cause ;).
But I agree, problem was “patched” on my side too, thank you very much for fast support.
The Team was aware a day before the post appear on the forum.
That makes me angry not happy
Why?
Shouldn’t they have restored the reputation of the affected nodes?
This post helped to mitigate an issue much faster than if our Community did not provide information and logs. So, I think this post was helpful and I would ask our Community to post any problems in the future too.