Re: [tor-relays] Previous Guard not getting Guard flag back
While I understand that my relay lost the guard flag because of a weekend of downtime, I would expect that it would get it back after a while of stable again? Anyone able to shed some light on when it will get the flag back? https://metrics.torproject.org/rs.html#details/924B24AFA7F075D059E8EEB284CC4...
Guard flag calculation is somewhat involved (due to several get-out-jail promotions/bypasses), but the essential part is weighted uptime in excess of the median uptime of guard candidates, or 98% whichever is lower. Presently the authorities have it somewhere around 96% (they do not publish the value). Your relay is at about 91% and will be back as a Guard in less than five days when it will hit 97%. The attached XLS shows it roughly, left side today and right side as-of 3/26. Uptime data came from the "1_month" section of https://onionoo.torproject.org/uptime?search=NSDFreedom Built this sheet for myself recently and simply stuffed in data for your relay. Enjoy. P.S. If anyone spots flaws in the approach, please comment.
What might not be directly obvious is the calculation bases on 12-hour intervals where on each interval the previous uptime is down-weighted to 95% of the next-most-recent. OnionOO uptime intervals are four hours, so each set of three OO intervals are averaged as a single 12-hour interval and then weighted. This only approximates logic of rephist.c which keeps track of uptime with compact records indicating the start and end of relay-is-up span. At 00:34 3/21/2018 -0500, starlight.2017q4@binnacle.cx wrote:
While I understand that my relay lost the guard flag because of a weekend of downtime, I would expect that it would get it back after a while of stable again? Anyone able to shed some light on when it will get the flag back? https://metrics.torproject.org/rs.html#details/924B24AFA7F075D059E8EEB284CC4...
Guard flag calculation is somewhat involved (due to several get-out-jail promotions/bypasses), but the essential part is weighted uptime in excess of the median uptime of guard candidates, or 98% whichever is lower. Presently the authorities have it somewhere around 96% (they do not publish the value). Your relay is at about 91% and will be back as a Guard in less than five days when it will hit 97%. The attached XLS shows it roughly, left side today and right side as-of 3/26. Uptime data came from the "1_month" section of
https://onionoo.torproject.org/uptime?search=NSDFreedom
Built this sheet for myself recently and simply stuffed in data for your relay. Enjoy.
P.S. If anyone spots flaws in the approach, please comment.
Flubbed a date paste on the right-side (visual aid only) but calc is correct. Fix is to copy I3, paste it to I4:I8.
Actually I badly munged the entire right-side. Should have written a perl script or C program to do this--spread-sheet is a terrible hack. Fixup attached here. Your relay should be a guard again by the end of next Wednesday on 3/28, allowing the auths are in a nice mood and 96.2 is adequate. Worst case should be Thursday.
Can't win! Lesson here is never hack a spread-sheet for someone else's relay ;-) Data elements were reverse-order relative to the sheet and I forgot to reverse them. I _think_ this is correct. . .Guard flag comes back Saturday 3/24. I'll have to write a perl or python script sometime to pull data from OnionOO and run the calc. . .
Came in a day early with six authorities voting yea and three voting nay. Implies the median uptime percentage for guard candidates is slightly under 95.8.
participants (1)
-
starlight.2017q4＠binnacle.cx