[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[tor-bugs] #33824 [Core Tor/sbws]: relay measures low / high on same network and same server

To: undisclosed-recipients: ;
Subject: [tor-bugs] #33824 [Core Tor/sbws]: relay measures low / high on same network and same server
From: "Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>
Date: Mon, 06 Apr 2020 01:32:19 -0000
Auto-submitted: auto-generated
Delivered-to: archiver@xxxxxxxx
Delivery-date: Sun, 05 Apr 2020 21:32:29 -0400
List-archive: <http://lists.torproject.org/pipermail/tor-bugs/>
List-help: <mailto:tor-bugs-request@lists.torproject.org?subject=help>
List-id: "auto: Tor bug tracker status mails" <tor-bugs.lists.torproject.org>
List-post: <mailto:tor-bugs@lists.torproject.org>
List-subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs>, <mailto:tor-bugs-request@lists.torproject.org?subject=subscribe>
List-unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-bugs>, <mailto:tor-bugs-request@lists.torproject.org?subject=unsubscribe>
Reply-to: no-reply@xxxxxxxxxxxxxx, blackhole@xxxxxxxxxxxxxx
Sender: "tor-bugs" <tor-bugs-bounces@xxxxxxxxxxxxxxxxxxxx>

#33824: relay measures low / high on same network and same server
------------------------+-------------------------------
 Reporter:  niftybunny  |          Owner:  (none)
     Type:  defect      |         Status:  new
 Priority:  Medium      |      Component:  Core Tor/sbws
  Version:              |       Severity:  Normal
 Keywords:              |  Actual Points:
Parent ID:              |         Points:
 Reviewer:              |        Sponsor:
------------------------+-------------------------------
 Teor told me it would be helpfuI:

 "If you have a relay that measures low, and a relay that measures high,
 on the same network, that would be really helpful."

  185.220.101.199 | niftywabbit         | abuse-contact@to-surf-and-
 protect.net  |     1 |    1 |            56000 |
  185.220.101.245 | niftyguard36      | abuse-contact@to-surf-and-
 protect.net  |     0 |    0 |               27 |

 Same server, same routing, same config  ...

 Here a list I got from nusenu. There are three servers, all in the same
 datacenter, same rack, same 20 gbit connection to the same router, same
 routing, same configuration, same hardware (40 cores, 128 gb ram and 2 ssd
 per server.

 +---------------------+----------------+-----------------+---------------------+----------------------------------------+-------+------+------------------+
 | first_seen          | family members | IP              | nickname
 | contact                                | guard | exit | consensus_weight
 |
 +---------------------+----------------+-----------------+---------------------+----------------------------------------+-------+------+------------------+
 | 2016-09-22 16:00:00 |              1 | 185.220.101.3   | niftyhutia
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     0 |    1 |             7300
 |
 | 2020-03-26 14:00:00 |            186 | 185.220.101.242 | niftyguard33
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     0 |    0 |               16
 |
 | 2020-03-26 14:00:00 |            186 | 185.220.101.224 | niftyguard15
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    1 |               61
 |
 | 2019-01-05 08:00:00 |            186 | 137.74.19.201   |
 niftyflorescaverat  | abuse@xxxxxxxxxxxxxxxxxxxxxxx          |     1 |
 0 |            35000 |
 | 2020-03-26 14:00:00 |            186 | 185.220.101.214 | niftyguard05
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     0 |    1 |              220
 |
 | 2020-03-26 14:00:00 |            186 | 185.220.101.228 | niftyguard19
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     0 |    1 |              150
 |
 | 2019-01-25 21:00:00 |            186 | 185.220.101.133 | niftyboglemming
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    1 |            34000
 |
 | 2019-01-31 03:00:00 |            186 | 185.220.101.146 | niftyhazelmouse
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    1 |            38500
 |
 | 2020-02-02 15:00:00 |            186 | 185.220.101.199 | niftywabbit
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    1 |            56000
 |
 | 2016-08-23 17:00:00 |            186 | 185.220.101.1   | niftyhedgehog
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    1 |            26600
 |
 | 2016-09-18 20:00:00 |            186 | 185.220.101.31  | niftywoodmouse
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    1 |            43900
 |
 | 2020-03-26 20:00:00 |            186 | 185.220.101.244 | niftyguard35
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    0 |               53
 |
 | 2020-03-26 15:00:00 |            186 | 185.220.101.243 | niftywabbit13
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    1 |               75
 |
 | 2020-03-26 14:00:00 |            186 | 185.220.101.245 | niftyguard36
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     0 |    0 |               27
 |
 | 2019-01-26 02:00:00 |            186 | 185.220.101.7   | niftylagurus
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    1 |            19900
 |
 | 2020-03-19 21:00:00 |            186 | 185.220.101.36  | niftyexit
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     0 |    1 |               30
 |
 | 2020-03-26 17:00:00 |            186 | 185.220.101.154 | niftywabbit14
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    1 |               26
 |
 | 2019-01-31 20:00:00 |            186 | 54.38.73.16     | niftymastomys
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    0 |            63000
 |
 | 2016-07-27 13:00:00 |            186 | 185.220.101.10  | niftymouse
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    1 |            16000
 |
 | 2018-01-12 21:00:00 |            186 | 185.220.101.19  | niftyrabbitrat
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    1 |            58700
 |
 | 2019-06-24 14:00:00 |            186 | 51.38.22.252    | wabbitseason4
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    0 |            23800
 |
 | 2016-10-23 21:00:00 |            186 | 185.220.101.137 |
 niftycottonmouse    | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |
 1 |            36100 |
 | 2019-01-05 08:00:00 |            186 | 185.220.101.12  | niftyneochoerus
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    1 |            34200
 |
 | 2020-03-26 17:00:00 |            186 | 185.220.101.153 | niftywabbit13
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    1 |             2700
 |
 | 2020-03-26 15:00:00 |            186 | 185.220.101.150 | niftyguard72
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    0 |             2300
 |
 | 2020-03-19 21:00:00 |            186 | 185.220.101.39  | niftyexit
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    1 |             3100
 |
 | 2020-02-02 14:00:00 |            186 | 185.220.101.194 | niftywabbit2
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    1 |            55000
 |
 | 2020-03-26 20:00:00 |            186 | 185.220.101.157 | niftyguard79
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    0 |             2100
 |
 | 2020-02-02 14:00:00 |            186 | 185.220.101.193 | niftywabbit
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    1 |            41600
 |
 | 2020-03-26 14:00:00 |            186 | 185.220.101.218 | niftyguard09
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     0 |    1 |             1800
 |
 | 2020-03-26 20:00:00 |            186 | 185.220.101.232 | niftyguard23
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     0 |    0 |               30
 |
 | 2020-03-26 20:00:00 |            186 | 185.220.101.155 | niftyguard77
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    0 |               53
 |
 | 2016-09-20 04:00:00 |            186 | 185.220.101.32  | niftysquirrel
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    1 |            34200
 |
 | 2019-10-26 21:00:00 |            186 | 54.38.18.130    |
 niftyleastchipmunk  | abuse@xxxxxxxxxxxxxxxxxxxxxxx          |     1 |
 0 |            25000 |
 | 2020-03-26 20:00:00 |            186 | 185.220.101.248 | niftyguard39
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     0 |    0 |               52
 |
 | 2020-03-26 15:00:00 |            186 | 185.220.101.249 | niftywabbit19
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    1 |            45500
 |
 | 2020-03-26 20:00:00 |            186 | 185.220.101.153 | niftyguard75
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     0 |    0 |               16
 |
 | 2020-03-26 20:00:00 |            186 | 185.220.101.225 | niftyguard16
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     0 |    1 |              130
 |
 | 2020-03-26 14:00:00 |            186 | 185.220.101.240 | niftyguard31
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     0 |    0 |               27
 |
 | 2020-03-26 20:00:00 |            186 | 185.220.101.188 | niftyguard69
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    0 |              840
 |
 | 2019-01-25 21:00:00 |            186 | 185.220.101.30  |
 niftywoodlemming    | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |
 1 |            29600 |
 | 2020-03-26 15:00:00 |            186 | 185.220.101.174 | niftyguard55
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     0 |    1 |               45
 |
 | 2017-12-30 10:00:00 |            186 | 185.220.101.141 |
 niftyeuropeanrabbit | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |
 1 |            51000 |
 | 2020-03-26 14:00:00 |            186 | 185.220.101.250 | niftyguard38
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     0 |    0 |               29
 |
 | 2020-03-26 20:00:00 |            186 | 185.220.101.164 | niftyguard45
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     0 |    1 |              230
 |
 | 2020-03-26 15:00:00 |            186 | 185.220.101.184 | niftyguard65
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    0 |              880
 |
 | 2020-03-26 20:00:00 |            186 | 185.220.101.229 | niftyguard
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     0 |    1 |               26
 |
 | 2020-03-26 15:00:00 |            186 | 185.220.101.250 | niftywabbit20
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     0 |    1 |              120
 |
 | 2016-08-30 19:00:00 |            186 | 185.220.101.24  |
 niftysugarglider    | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |
 1 |            45200 |
 | 2019-01-31 03:00:00 |            186 | 185.220.101.23  |
 niftysteppemarmot   | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |
 1 |            54000 |
 | 2020-03-26 15:00:00 |            186 | 185.220.101.180 | niftyguard61
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     0 |    0 |              120
 |
 | 2020-03-26 15:00:00 |            186 | 185.220.101.160 | niftyguard41
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    1 |             6000
 |
 | 2020-03-26 17:00:00 |            186 | 185.220.101.155 | niftywabbit15
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    1 |            11200
 |
 | 2020-03-26 15:00:00 |            186 | 185.220.101.173 | niftyguard54
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     0 |    1 |               63
 |
 | 2020-03-26 20:00:00 |            186 | 185.220.101.182 | niftyguard63
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    0 |             4810
 |
 | 2020-03-26 15:00:00 |            186 | 185.220.101.185 | niftyguard66
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     0 |    0 |               42
 |
 | 2020-03-26 15:00:00 |            186 | 185.220.101.248 | niftywabbit18
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     0 |    1 |               80
 |
 | 2019-06-24 14:00:00 |            186 | 185.220.101.139 | niftydiatomys
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    1 |            44300
 |
 | 2020-02-02 15:00:00 |            186 | 185.220.101.201 | niftywabbit9
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    1 |            58000
 |
 | 2020-03-26 17:00:00 |            186 | 185.220.101.151 | niftywabbit11
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    1 |             3000
 |
 | 2020-03-26 15:00:00 |            186 | 185.220.101.172 | niftyguard53
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     0 |    1 |               88
 |
 | 2020-02-02 15:00:00 |            186 | 185.220.101.196 | niftywabbit4
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    1 |            22800
 |
 | 2020-03-26 15:00:00 |            186 | 185.220.101.156 | niftyguard78
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    0 |               39
 |
 | 2019-10-26 21:00:00 |            186 | 54.38.18.130    |
 niftyafricagiantrat | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |
 0 |            23000 |
 | 2020-03-26 20:00:00 |            186 | 185.220.101.235 | niftyguard26
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     0 |    0 |               36
 |
 | 2020-03-26 14:00:00 |            186 | 185.220.101.239 | niftyguard
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     0 |    0 |               86
 |
 | 2020-03-26 15:00:00 |            186 | 185.220.101.163 | niftyguard44
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     0 |    1 |               45
 |
 | 2019-01-31 20:00:00 |            186 | 51.38.164.157   | niftylinkrat
 | abuse@xxxxxxxxxxxxxxxxxxxxxxx          |     1 |    0 |            60000
 |
 | 2020-03-26 14:00:00 |            186 | 185.220.101.241 | niftyguard32
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     0 |    0 |               77
 |
 | 2016-08-28 10:00:00 |            186 | 185.220.101.136 | niftychipmunk
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    1 |            30000
 |
 | 2016-10-20 18:00:00 |            186 | 185.220.101.28  | niftytucotuco
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    1 |            30200
 |
 | 2020-03-26 17:00:00 |            186 | 185.220.101.157 | niftywabbit17
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    1 |            21000
 |
 | 2020-03-26 20:00:00 |            186 | 185.220.101.171 | niftyguard52
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     0 |    1 |               24
 |
 | 2020-03-26 14:00:00 |            186 | 185.220.101.213 | niftyguard04
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     0 |    1 |              200
 |
 | 2018-02-03 21:00:00 |            186 | 185.220.101.145 | niftyhare
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    1 |            38400
 |
 | 2020-03-26 14:00:00 |            186 | 185.220.101.236 | niftyguard27
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    0 |             1200
 |
 | 2019-01-05 08:00:00 |            186 | 185.220.101.120 |
 niftyhornedgopher   | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |
 0 |            16600 |
 | 2020-03-26 15:00:00 |            186 | 185.220.101.175 | niftyguard56
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     0 |    1 |              150
 |
 | 2020-03-26 15:00:00 |            186 | 185.220.101.245 | niftywabbit15
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    1 |               25
 |
 | 2020-03-26 20:00:00 |            186 | 185.220.101.231 | niftyguard22
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     0 |    0 |               23
 |
 | 2016-11-23 00:00:00 |            186 | 185.220.101.131 | niftybeaver
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    1 |            39000
 |
 | 2019-01-30 21:00:00 |            186 | 137.74.19.202   |
 niftyleastgerbil    | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |
 0 |            47500 |
 | 2020-03-26 14:00:00 |            186 | 185.220.101.227 | niftyguard18
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     0 |    1 |               29
 |
 | 2016-02-05 18:00:00 |            186 | 185.220.101.138 | niftycottontail
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    1 |            25000
 |
 | 2016-09-22 16:00:00 |            186 | 185.220.101.14  | niftypedetidae
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxx   |     1 |    1 |            51000
 |
 | 2020-03-26 15:00:00 |            186 | 185.220.101.151 | niftyguard73
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     0 |    0 |               92
 |
 | 2020-03-26 14:00:00 |            186 | 185.220.101.230 | niftyguard21
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     0 |    0 |               40
 |
 | 2020-03-26 14:00:00 |            186 | 185.220.101.237 | niftyguard28
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    0 |             2200
 |
 | 2020-03-26 15:00:00 |            186 | 185.220.101.183 | niftyguard64
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     0 |    0 |               18
 |
 | 2020-03-26 20:00:00 |            186 | 185.220.101.233 | niftyguard24
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    0 |               53
 |
 | 2020-03-19 21:00:00 |            186 | 185.220.101.40  | niftyexit
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    1 |              110
 |
 | 2020-02-02 15:00:00 |            186 | 185.220.101.198 | niftywabbit6
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    1 |            33000
 |
 | 2019-08-09 19:00:00 |            186 | 185.220.101.11  | niftymuskrat
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    1 |            37000
 |
 | 2016-12-02 20:00:00 |            186 | 185.220.101.9   | niftyllipika
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    1 |            28000
 |
 | 2016-11-25 21:00:00 |            186 | 185.220.101.16  | niftyporcupine
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    1 |            33500
 |
 | 2020-03-26 14:00:00 |            186 | 185.220.101.211 | niftyguard02
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    1 |             9400
 |
 | 2020-03-26 15:00:00 |            186 | 185.220.101.176 | niftyguard57
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     0 |    1 |               20
 |
 | 2019-01-31 20:00:00 |            186 | 51.38.164.157   |
 niftycongogerbil    | abuse@xxxxxxxxxxxxxxxxxxxxxxx          |     1 |
 0 |            61000 |
 | 2019-01-05 08:00:00 |            186 | 137.74.19.201   | niftyphoberomys
 | abuse@xxxxxxxxxxxxxxxxxxxxxxx          |     1 |    0 |            44000
 |
 | 2020-03-26 15:00:00 |            186 | 185.220.101.168 | niftyguard49
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    1 |             5020
 |
 | 2018-12-16 06:00:00 |            186 | 185.220.101.33  |
 niftytamiasaristus  | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |
 1 |            32000 |
 | 2020-03-26 14:00:00 |            186 | 185.220.101.210 | niftyguard01
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     0 |    1 |               78
 |
 | 2020-03-26 14:00:00 |            186 | 185.220.101.222 | niftyguard13
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    1 |              110
 |
 | 2020-03-26 15:00:00 |            186 | 185.220.101.170 | niftyguard51
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    1 |            14100
 |
 | 2020-03-26 14:00:00 |            186 | 185.220.101.223 | niftyguard14
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     0 |    1 |               23
 |
 | 2016-08-30 17:00:00 |            186 | 185.220.101.25  | niftyjerboa
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    1 |            60000
 |
 | 2020-03-26 15:00:00 |            186 | 185.220.101.242 | niftywabbit12
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    1 |            19200
 |
 | 2016-08-03 12:00:00 |            186 | 185.220.101.18  | niftyquokka
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    1 |            54000
 |
 | 2016-08-24 06:00:00 |            186 | 185.220.101.13  | niftypedetes
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    1 |            26000
 |
 | 2019-01-26 01:00:00 |            186 | 185.220.101.26  |
 niftytamiasatsali   | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |
 1 |            31300 |
 | 2020-03-26 15:00:00 |            186 | 185.220.101.190 | niftyguard71
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    0 |             5010
 |
 | 2020-03-26 17:00:00 |            186 | 185.220.101.156 | niftywabbit16
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    1 |            14000
 |
 | 2019-01-05 09:00:00 |            186 | 54.38.145.211   |
 niftyalloeumyarion  | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |
 0 |            45800 |
 | 2020-03-26 14:00:00 |            186 | 185.220.101.212 | niftyguard03
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     0 |    1 |               18
 |
 | 2019-01-31 03:00:00 |            186 | 185.220.101.22  |
 niftyredsquirrel    | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |
 1 |            54700 |
 | 2019-01-31 20:00:00 |            186 | 5.196.213.57    | niftyspinymouse
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    0 |            18300
 |
 | 2019-10-23 19:00:00 |            186 | 185.220.101.142 |
 niftyfoxsquirrel    | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |
 1 |            32500 |
 | 2017-12-27 01:00:00 |            186 | 185.220.101.17  |
 niftypygmyjerboa    | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |
 1 |            47000 |
 | 2019-01-31 20:00:00 |            186 | 185.220.101.21  | niftyredrockrat
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    1 |            55000
 |
 | 2020-03-26 14:00:00 |            186 | 185.220.101.215 | niftyguard06
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     0 |    1 |               56
 |
 | 2020-03-26 14:00:00 |            186 | 185.220.101.219 | niftyguard10
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     0 |    1 |              110
 |
 | 2019-01-05 08:00:00 |            186 | 185.220.101.121 |
 niftycastoroides    | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |
 0 |            19400 |
 | 2019-01-05 09:00:00 |            186 | 54.38.145.211   | niftydiatomys
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    0 |            45700
 |
 | 2020-03-26 17:00:00 |            186 | 185.220.101.152 | niftywabbit12
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    1 |            14500
 |
 | 2020-02-02 15:00:00 |            186 | 185.220.101.202 | niftywabbit
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    1 |            49700
 |
 | 2019-06-24 14:00:00 |            186 | 51.38.22.252    |
 niftysnowshoehare   | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |
 0 |            26000 |
 | 2019-12-01 00:00:00 |            186 | 54.38.73.16     | niftyshrew
 | abuse-contatct@xxxxxxxxxxxxxxxxxxxxxxx |     1 |    0 |            32000
 |
 | 2020-03-26 20:00:00 |            186 | 185.220.101.154 | niftyguard76
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    0 |               16
 |
 | 2020-03-26 20:00:00 |            186 | 185.220.101.249 | niftyguard40
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     0 |    0 |              260
 |
 | 2020-03-26 15:00:00 |            186 | 185.220.101.167 | niftyguard48
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     0 |    1 |               34
 |
 | 2020-03-26 15:00:00 |            186 | 185.220.101.165 | niftyguard46
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    1 |             7640
 |
 | 2020-03-26 15:00:00 |            186 | 185.220.101.179 | niftyguard60
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    1 |             6100
 |
 | 2020-03-26 15:00:00 |            186 | 185.220.101.177 | niftyguard58
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     0 |    1 |               17
 |
 | 2020-03-26 15:00:00 |            186 | 185.220.101.247 | niftywabbit17
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     0 |    1 |              220
 |
 | 2020-03-19 21:00:00 |            186 | 185.220.101.35  | niftyexit
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     0 |    1 |               22
 |
 | 2019-06-24 14:00:00 |            186 | 185.220.101.129 |
 niftyalloumyraion   | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |
 1 |            31000 |
 | 2020-03-26 14:00:00 |            186 | 185.220.101.221 | niftyguard12
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     0 |    1 |               33
 |
 | 2017-12-27 01:00:00 |            186 | 185.220.101.136 | niftybunny
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    1 |            23000
 |
 | 2016-01-25 23:00:00 |            186 | 185.220.101.15  | niftypika
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    1 |            34600
 |
 | 2020-03-26 15:00:00 |            186 | 185.220.101.178 | niftyguard59
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    1 |             7100
 |
 | 2020-03-26 17:00:00 |            186 | 185.220.101.160 | niftywabbit20
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    1 |             5270
 |
 | 2019-01-25 20:00:00 |            186 | 185.220.101.130 | niftybankvole
 | abuse@xxxxxxxxxxxxxxxxxxxxxxx          |     1 |    1 |             9900
 |
 | 2020-03-19 21:00:00 |            186 | 185.220.101.37  | niftyexit
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     0 |    1 |              350
 |
 | 2016-02-06 17:00:00 |            186 | 185.220.101.29  |
 niftyvolcanorabbit  | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |
 1 |            28400 |
 | 2020-03-19 21:00:00 |            186 | 185.220.101.43  | niftyexit
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     0 |    1 |              150
 |
 | 2020-02-02 15:00:00 |            186 | 185.220.101.195 | niftywabbit3
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    1 |            53500
 |
 | 2020-03-26 17:00:00 |            186 | 185.220.101.159 | niftywabbit19
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    1 |              210
 |
 | 2020-03-26 14:00:00 |            186 | 185.220.101.216 | niftyguard07
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    1 |            12000
 |
 | 2017-12-27 01:00:00 |            186 | 185.220.101.4   | niftyjackrabbit
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    1 |            46000
 |
 | 2020-03-26 17:00:00 |            186 | 185.220.101.158 | niftywabbit18
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    1 |            18400
 |
 | 2019-01-25 21:00:00 |            186 | 185.220.101.135 | niftychionomy
 | abuse@xxxxxxxxxxxxxxxxxxxxxxx          |     0 |    1 |            24600
 |
 | 2016-05-22 05:00:00 |            186 | 185.220.101.143 | niftygerbil
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    1 |            32000
 |
 | 2020-03-26 15:00:00 |            186 | 185.220.101.166 | niftyguard47
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     0 |    1 |              150
 |
 | 2020-03-19 21:00:00 |            186 | 185.220.101.34  | niftyexit
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     0 |    1 |              110
 |
 | 2019-01-05 08:00:00 |            186 | 5.196.213.57    | niftytelicomys
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    0 |            22500
 |
 | 2020-03-26 15:00:00 |            186 | 185.220.101.241 | niftywabbit11
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    1 |             8800
 |
 | 2020-03-26 15:00:00 |            186 | 185.220.101.186 | niftyguard67
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     0 |    0 |              170
 |
 | 2020-03-26 14:00:00 |            186 | 185.220.101.217 | niftyguard08
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     0 |    1 |              138
 |
 | 2020-03-19 21:00:00 |            186 | 185.220.101.38  | niftyexit
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    1 |               14
 |
 | 2020-02-02 15:00:00 |            186 | 185.220.101.197 | niftywabbit5
 | abuse@xxxxxxxxxxxxxxxxxxxxxxx          |     1 |    1 |            37400
 |
 | 2019-01-25 20:00:00 |            186 | 185.220.101.132 | niftyblythsvole
 | abuse@xxxxxxxxxxxxxxxxxxxxxxx          |     1 |    1 |            28000
 |
 | 2020-03-26 20:00:00 |            186 | 185.220.101.234 | niftyguard25
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    0 |              130
 |
 | 2020-03-19 21:00:00 |            186 | 185.220.101.41  | niftyexit
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     0 |    1 |              110
 |
 | 2020-03-26 15:00:00 |            186 | 185.220.101.169 | niftyguard50
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    1 |              160
 |
 | 2019-08-09 19:00:00 |            186 | 185.220.101.2   | niftyhousemouse
 | abuse@xxxxxxxxxxxxxxxxxxxxxxx          |     1 |    1 |            53500
 |
 | 2016-11-25 21:00:00 |            186 | 185.220.101.140 | niftydormouse
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    1 |            31900
 |
 | 2019-01-30 21:00:00 |            186 | 137.74.19.202   |
 niftywatersgerbil   | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |
 0 |            54000 |
 | 2020-03-26 14:00:00 |            186 | 185.220.101.243 | niftyguard34
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    0 |               17
 |
 | 2016-05-25 21:00:00 |            186 | 185.220.101.144 | niftyguineapig
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     0 |    1 |            24100
 |
 | 2019-01-25 21:00:00 |            186 | 185.220.101.6   |
 niftyjunipervole    | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |
 1 |            31000 |
 | 2020-03-20 00:00:00 |            186 | 185.220.101.42  | niftyexit
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    1 |            13600
 |
 | 2020-03-26 15:00:00 |            186 | 185.220.101.187 | niftyguard68
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     0 |    0 |               44
 |
 | 2020-03-26 20:00:00 |            186 | 185.220.101.238 | niftyguard29
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     0 |    0 |               25
 |
 | 2020-03-26 15:00:00 |            186 | 185.220.101.161 | niftyguard42
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     0 |    1 |              596
 |
 | 2019-01-05 08:00:00 |            186 | 185.220.101.8   | niftyleithia
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    1 |            26000
 |
 | 2018-01-11 15:00:00 |            186 | 185.220.101.27  | niftytreerat
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    1 |            39000
 |
 | 2020-03-26 15:00:00 |            186 | 185.220.101.158 | niftyguard80
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    0 |              120
 |
 | 2020-03-26 15:00:00 |            186 | 185.220.101.181 | niftyguard62
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     0 |    0 |               80
 |
 | 2020-03-26 15:00:00 |            186 | 185.220.101.162 | niftyguard43
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    1 |             7000
 |
 | 2020-03-26 15:00:00 |            186 | 185.220.101.244 | niftywabbit11
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     0 |    1 |              330
 |
 | 2020-03-26 14:00:00 |            186 | 185.220.101.247 | niftyguard37
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     0 |    0 |               27
 |
 | 2020-03-26 20:00:00 |            186 | 185.220.101.189 | niftyguard70
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    0 |              140
 |
 | 2016-09-17 13:00:00 |            186 | 185.220.101.20  | niftyrat
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    1 |            40000
 |
 | 2020-03-26 14:00:00 |            186 | 185.220.101.220 | niftyguard11
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    1 |             1500
 |
 | 2020-02-02 15:00:00 |            186 | 185.220.101.200 | niftywabbit8
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    1 |            50000
 |
 | 2020-03-26 20:00:00 |            186 | 185.220.101.226 | niftyguard17
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     0 |    1 |               67
 |
 | 2020-03-26 15:00:00 |            186 | 185.220.101.246 | niftywabbit16
 | abuse-contact@xxxxxxxxxxxxxxxxxxxxxxx  |     1 |    1 |            56000
 |
 +---------------------+----------------+-----------------+---------------------+----------------------------------------+-------+------+------------------+

 so we have from 14 to 60000 everthing.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/33824>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online

_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Follow-Ups:
- Re: [tor-bugs] #33824 [Core Tor/sbws]: relay measures low / high on same network and same server
  - From: Tor Bug Tracker & Wiki
- Re: [tor-bugs] #33824 [Core Tor/sbws]: relay measures low / high on same network and same server
  - From: Tor Bug Tracker & Wiki
- Re: [tor-bugs] #33824 [Core Tor/sbws]: relay measures low / high on same network and same server
  - From: Tor Bug Tracker & Wiki
- Re: [tor-bugs] #33824 [Core Tor/sbws]: relay measures low / high on same network and same server
  - From: Tor Bug Tracker & Wiki
- Re: [tor-bugs] #33824 [Core Tor/sbws]: relay measures low / high on same network and same server
  - From: Tor Bug Tracker & Wiki
- Re: [tor-bugs] #33824 [Core Tor/sbws]: relay measures low / high on same network and same server
  - From: Tor Bug Tracker & Wiki
- Re: [tor-bugs] #33824 [Core Tor/sbws]: relay measures low / high on same network and same server
  - From: Tor Bug Tracker & Wiki
- Re: [tor-bugs] #33824 [Core Tor/sbws]: relay measures low / high on same network and same server
  - From: Tor Bug Tracker & Wiki
- Re: [tor-bugs] #33824 [Core Tor/sbws]: relay measures low / high on same network and same server
  - From: Tor Bug Tracker & Wiki

Prev by Author: Re: [tor-bugs] #33267 [Core Tor/Chutney]: Prop 313: 8.1. Test IPv6 Relay Consensus Counts using Chutney
Next by Author: Re: [tor-bugs] #32198 [Internal Services/Services Admin Team]: upgrade CRM* machines to buster
Previous by thread: Re: [tor-bugs] #33823 [Internal Services/Tor Sysadmin Team]: Can we block phishing emails when forwarding emails?
Next by thread: Re: [tor-bugs] #33824 [Core Tor/sbws]: relay measures low / high on same network and same server
Index(es):
- Author
- Thread