Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • S sbws
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 5
    • Issues 5
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Network Health
  • sbws
  • Issues
  • #40119
Closed
Open
Created Jan 11, 2022 by juga@jugaMaintainer

gabelmoo's sbws weight sum is greater than the 50% of the consensus

As explained at #40115 (closed) gabelmoo's sbws is reporting this warning.

It looks like gabelmoo's had always greatest consensus weight sum (see for instance the total consensus weight graph back in 2018 when the log was created: https://metrics.torproject.org/totalcw.png?start=2018-10-01&end=2018-10-31), what it probably due gabelmoo's location (Germany). What i'm not sure is whether it was as much as the 50% before because relays were getting stuck in bandwidth partitions with torflow or we just didn't notice cause torflow wasn't logging that.

This issue is to investigate why this is happening.

Assignee
Assign to
Time tracking