Points accumulating and uptime problem

Hi, I have a question about accumulating points in the desktop node. I joined in the middle of april and I feel like there is no record of accumulating points during many days in that period. For example my online uptime is 1904hours and I think it is much more. 1904hours is 79 full (24h) days of being online. That is impossible because my computer was running online much more.

There is also other common problem. Sometimes when I check my Hyperspace node I see this number (1904 hours, Tier 3, Mulitplier 3 etc ) and after a while those number are randomly changed to for example (444hours, Tier1, Multiplier 1) and then again to different numbers. I think this issue can have influence on system of accumulating points. Is it common problem in Hyperspace node?

as long as points is accumulating then it is fine, the tier/uptime number is fluctuating lately but network is much more stabilizer than before.

1 Like

Yes, it is accumulating but there are weeks when points are not accumulating at all. So if tier/uptime is fluctuating… probably that can have influence on number accumulated points

points can only goes up or it doesn’t. if It stops, try to reset your node simple as that.

Currently my points are not accumulating at all, and I already provided my public key in the tagged topic.

I tried to reset my node multiple times but sometimes node just stops accumulating points for a few days :slight_smile:

this is what i would do : reset my node and wait 1 day to see if the problem persists and repeat the process if needed.

This happened to me too, had been on 24 since early feb 2024.

Reach the team several times and found out that they have some infra issues that what causes my glitch/bug (and yours too possibly), but don’t worry your point and uptime hrs is safe. Including the 1.0x despite connecting a full 24h since 1 year ago bug.

For the fluctuating uptime hrs and multiplier is caused by a slight bug due to current patch update, rest assured team is improving it and fixing it.

Mostly just a visual bug, on the back-end it reflects the correct ones so you won’t miss a point/uptime hours in reality.