View Relay "antiregimerelay"

Fingerprint: 31226BB33410BEEA3F48B281DE1E1BC98BFF6E16 | Family: 1 relay | m4ch3t3.jd@gmail.com | AS197540 | Germany | Linux

Consensus
In Consensus (9/9 Directory Auths)
BW Verified
5/6 BW Auths Measured 25 Kbit/s Median
Stability
Not Overloaded | DOWN 3h 15m 41s ago
Reachability
IPv4: 9/9 | v6: 7/7 (Directory Auths)
BW Weight
0.00% of Network | 25 Mbit/s Observed By Relay
Version
0.4.9.5 Recommended
Issues Detected:
  • Guard: requires Stable flag : Guard flag requires having the Stable flag first
    Suggestion: Get Stable flag by maintaining consistent uptime. Stable requires uptime and MTBF at or above network median (typically 2-3 weeks of stable running).
  • Guard: WFU below threshold : Weighted Fractional Uptime 49.1% is below 98% requirement
    Suggestion: WFU measures recent uptime (recent downtime weighs more heavily). To improve: 1) Minimize restarts, 2) Use systemd with Restart=always, 3) Monitor for OOM kills, 4) Schedule updates during low-traffic periods.
  • Guard: Time Known below threshold : Time Known 3.3 days is below 8 days requirement (4.7 more days needed)
    Suggestion: Time Known tracks how long authorities have observed your relay. This resets if: 1) Identity key changes, 2) Long downtime makes authorities forget you. Just keep running stably.
  • Not eligible for Stable flag : Uptime or MTBF below network median for most authorities
    Suggestion: Stable flag requires uptime/MTBF at or above network median. Keep your relay running continuously for 2-3 weeks. Avoid restarts. Use reliable hardware and network connection.
  • HSDir: requires Stable flag : HSDir flag requires having the Stable flag first
    Suggestion: Get Stable flag by maintaining consistent uptime. Stable requires uptime and MTBF at or above network median (typically 2-3 weeks of stable running). Avoid restarts.
  • HSDir: WFU below threshold : WFU 49.1% below 98% required for HSDir
    Suggestion: HSDir requires ≥98% WFU, Stable flag, and Time Known ≥25 hours (or ~10 days for moria1). Improve uptime consistency.
  • High consensus weight deviation : Large variation in Consensus Weight values across authorities (see 'Cons Wt' column in Per-Authority Details below)
    Suggestion: Consensus weight measurements vary significantly between authorities. This can affect traffic distribution. Ensure stable network connection and consistent bandwidth availability.

Addresses
OR Address
v2202602341181437475.bestsrv.de
152.53.119.177:9001
[2a02:8071:5a71:ab80:b2cd:230f:1b59:ece2]:9001
Reachability (Directory Authorities)
IPv4
9/9
IPv6
7/7 (2 don't test)
Location
Country
Germany Germany
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS197540
AS Name
netcup GmbH (BGP.tools)
AS Rarity
Emerging (score: 1/5, 4.26% consensus weight, 182 operators)

Current Flags (4): Running, Valid, V2Dir, Fast
Eligible Flags (4): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 8/9 | Stable: 1/9 | HSDir: 0/9 | Guard: 0/9 | Exit: 0/9
Eligibility Flag Vote Details
Flag Metric Status Relay Value Threshold Required
Running IPv4 Reachability Meets (9/9 DA) 9/9 authorities reached relay ≥5/9 DA ORPort reachable
IPv6 Reachability Meets (7/7 DA) 7/7 tested authorities reached relay ≥4/7 tested (majority) (≥4/7 DA)
Valid Descriptor Meets (9/9 DA) 9/9 authorities assigned Valid Not blacklisted + valid descriptor (≥5/9 DA)
V2Dir DirPort Available Meets (9/9 DA) Tunnelled: Yes (no DirPort) (R) Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Fast Speed Meets (9/9 DA) 25.3 Mbit/s (R) ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Stable MTBF Below (1/9 DA) Median: 0.1d (1/9 DA above threshold)
Min/Max: 0.0d / 19599.4d (9/9 DA, Voting / Total Eligible)
≥11.8d - 52.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥430.3d
Uptime Below (0/9 DA) 4.5d (R) ≥8.0d - 10.0d (varies) (≥5/9 DA)
HSDir Prereq: Fast Meets (8/9 DA) 8/9 DA assigned Fast ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Below (1/9 DA) 1/9 DA assigned Stable ≥11.8d - 52.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥430.3d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Below (0/9 DA) Median: 45.7% (0/9 DA above threshold)
Min/Max: 32.6% / 53.2% (9/9 DA, Voting / Total Eligible)
≥98.0% (≥5/9 DA)
Time Known Meets (8/9 DA) Median: 3.3d (0/9 DA above threshold)
Min/Max: 3.2d / 3.3d (9/9 DA, Voting / Total Eligible)
≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.9d
Guard Prereq: Fast Meets (8/9 DA) 8/9 DA assigned Fast ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Below (1/9 DA) 1/9 DA assigned Stable ≥11.8d - 52.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥430.3d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Below (0/9 DA) Median: 45.7% (0/9 DA above threshold)
Min/Max: 32.6% / 53.2% (9/9 DA, Voting / Total Eligible)
≥98% (≥5/9 DA)
Time Known Below (0/9 DA) (need 4.7 more days) Median: 3.3d (0/9 DA above threshold)
Min/Max: 3.2d / 3.3d (9/9 DA, Voting / Total Eligible)
≥8 days (≥5/9 DA)
Bandwidth Meets (9/9 DA) 25.3 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-304.0 Mbit/s (≥5/9 DA)
Exit Exit Policy Below (0/9 DA) Port 80: No | Port 443: No (R) Allows ≥1 /8 on ports 80 AND 443 (≥5/9 DA)

(DA) = Dir. Auth. Measured | (R) = Relay Reported
Data from Tor CollecTor (authority votes, fetched 2026-03-04 22:15:08).

Capacity (Relay Reported)
Observed Bandwidth
25.25 Mbit/s
Advertised Bandwidth
25.17 Mbit/s
Rate Limit
25.17 Mbit/s
Burst Limit
41.94 Mbit/s
Total Data
39 GB (1 month)
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-03-04 22:15:08

Measured By
5/6 Bandwidth Authorities
Not measured by: longclaw
Median Measurement
25.2 Kbit/s
Min / Max
1760 bit/s / 26.4 Kbit/s
Deviation
24.6 Kbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0012% of network (26th pctl) | Guard: N/A | Middle: N/A | Exit: N/A

Uptime Metrics
Current Status
DOWN 3h 15m 41s ago
Overall Uptime (1M/6M/1Y/5Y)
0.0%/0.0%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (0.0%/0.0%/0.0%/0.0%)
Hibernating
No
Timestamps
First Seen
4d 11h 15m ago (2026-02-28 12:00:00)
Last Seen
3h 15m 41s ago (2026-03-04 20:00:00)
Last Restarted
4d 12h 16m ago (2026-02-28 10:59:18)
Last Changed Address
2026-02-28 12:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator Identity

Source: AROI Validation API — 2026-03-04 14:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
m4ch3t3.jd@gmail.com
Family Configuration
Family Support
None — No family membership configured
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Member: 1
31226BB33410BEEA3F48B281DE1E1BC98BFF6E16 (this relay)
Alleged Members: 0
none
Indirect Members: 0
none

Platform
Linux — Tor 0.4.9.5 on Linux
Version
0.4.9.5Recommended
Version Status
Recommended

Full Exit Policy
reject *:*

Last fetch was at Wed, 04 Mar 2026 23:15:39 GMT.

Data from Tor CollecTor (authority votes, fetched 2026-03-04 22:15:08).

Each cell shows: your measured value | authority threshold. Green = meets, red = below. Flags: green = all authorities agree, yellow = partial.

Authority Running Valid Exit MiddleOnly BW Scan
(Authority)
v4 v6 Flags Fast (Relay|T) Guard BW (Relay|Threshold) Guard WFU (M|T) Guard TK (M|T) Stable MTBF (M|T) Stable Uptime (Relay|T) HSDir WFU (M|T) HSDir TK (M|T) Desc Published Cons Wt (Authority)
bastet (US) Yes Yes No Y Yes Yes Valid, V2Dir, Fast 25.3 Mbit/s | 816.0 Kbit/s 25.3 Mbit/s | 224.0 Mbit/s OR 16.0 Mbit/s 49.1% | 98% 3.3d | 8d 0.1d | 56.3d 4.5d | 9.6d 49.1% | 98.0% 3.3d | 1.0d 2026-03-04 05:17:41 1760 bit/s
dannenberg (DE) Yes Yes No N Yes Yes Running, Valid, V2Dir, Fast 25.3 Mbit/s | 816.0 Kbit/s 25.3 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 32.6% | 98% 3.2d | 8d 0.0d | 11.8d 4.5d | 8.2d 32.6% | 98.0% 3.2d | 1.0d 2026-03-04 05:17:41 25.2 Kbit/s
dizum (NL) Yes Yes No N Yes Running, Valid, V2Dir, Fast 25.3 Mbit/s | 816.0 Kbit/s 25.3 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 44.4% | 98% 3.3d | 8d 0.1d | 42.7d 4.5d | 8.0d 44.4% | 98.0% 3.3d | 1.0d 2026-03-04 05:17:41 25.2 Kbit/s
faravahar (US) Yes Yes No N Yes Yes Running, Valid, V2Dir, Fast 25.3 Mbit/s | 816.0 Kbit/s 25.3 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 45.7% | 98% 3.2d | 8d 0.1d | 48.6d 4.5d | 10.0d 45.7% | 98.0% 3.2d | 1.0d 2026-03-04 05:17:41 25.2 Kbit/s
gabelmoo (DE) Yes Yes No Y Yes Yes Running, Valid, V2Dir, Fast 25.3 Mbit/s | 816.0 Kbit/s 25.3 Mbit/s | 304.0 Mbit/s OR 16.0 Mbit/s 45.6% | 98% 3.3d | 8d 0.1d | 58.8d 4.5d | 10.1d 45.6% | 98.0% 3.3d | 1.0d 2026-03-04 05:17:41 22.4 Kbit/s
longclaw (US) Yes Yes No Y Yes Running, Valid, V2Dir, Fast 25.3 Mbit/s | 816.0 Kbit/s 25.3 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 53.2% | 98% 3.2d | 8d 0.1d | 59.0d 4.5d | 9.6d 53.2% | 98.0% 3.2d | 1.0d 2026-03-04 05:17:41 25.2 Kbit/s
maatuska (SE) Yes Yes No Y Yes Yes Valid, V2Dir, Fast 25.3 Mbit/s | 816.0 Kbit/s 25.3 Mbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 50.2% | 98% 3.3d | 8d 0.1d | 39.2d 4.5d | 10.1d 50.2% | 98.0% 3.3d | 1.0d 2026-03-04 05:17:41 26.4 Kbit/s
moria1 (US) Yes Yes No Y Yes Yes Running, Valid, V2Dir, Stable 25.3 Mbit/s | 8.4 Mbit/s 25.3 Mbit/s | 232.0 Mbit/s OR 16.0 Mbit/s 39.0% | 98% 3.3d | 8d 19599.4d | 430.3d 4.5d | 10.8d 39.0% | 98.0% 3.3d | 9.9d 2026-03-04 05:17:41 2160 bit/s
tor26 (AT) Yes Yes No Y Yes Yes Running, Valid, V2Dir, Fast 25.3 Mbit/s | 816.0 Kbit/s 25.3 Mbit/s | 304.0 Mbit/s OR 16.0 Mbit/s 49.1% | 98% 3.2d | 8d 0.1d | 52.7d 4.5d | 10.1d 49.1% | 98.0% 3.2d | 1.0d 2026-03-04 05:17:41 25.6 Kbit/s

— = not tested/available • Format: relay value | authority threshold • WFU = Weighted Fractional Uptime • TK = Time Known

Bandwidth Values Explained:
Relay Reported = Your relay's self-reported bandwidth from its descriptor (observed_bandwidth). Used for flag eligibility (Guard, Fast).
Authority Measured = Bandwidth measured by authority's sbws scanner. Used for consensus weight (path selection probability).
Why different? Authorities verify your reported bandwidth independently. 6 of 9 authorities run bandwidth scanners; 3 use relay-reported values directly.
Stable Uptime (Two Data Sources):
Relay Uptime = From Onionoo API (last_restarted field). Self-reported uptime from descriptor. Same value for all authorities.
Authority Threshold = From CollecTor vote files (flag-thresholds stable-uptime). Each authority may have different thresholds.
Why two sources? Vote files contain authority thresholds but not per-relay uptime values. Onionoo aggregates relay descriptors which include uptime.