View Relay "2NN36745new"

Fingerprint: B03F3F40CEFEC44CEC8376A4127D1111142D3F99 | Family: 1 relay | noc@example.com | AS210083 | Belize | Linux

Health Status

Consensus
In Consensus (8/8 Directory Auths)
Flags
Running, Valid, V2Dir, Exit (4)
DNS Health
Not Tested (via exitdnshealth.1aeo.com)
BW Verified
0/5 BW Auths Measured 1040 bit/s Median
Stability
Not Overloaded | DOWN 5d 8h 45m ago
Reachability
IPv4: 8/9 (Directory Auths)
First Seen
5d 8h 45m ago
BW Weight
1 Mbit/s Observed By Relay
Version
0.4.9.6 Recommended
Issues Detected:
  • Guard: requires Fast flag : Guard flag requires having the Fast flag first
    Suggestion: Get Fast flag by having bandwidth ≥100 KB/s OR in top 7/8ths of network. Most relays get this easily.
  • 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: bandwidth below threshold : Observed bandwidth 0.1 MB/s is below 2 MB/s minimum (AuthDirGuardBWGuarantee)
    Suggestion: Guard requires ≥2 MB/s bandwidth OR being in top 25% of network. To increase bandwidth: 1) Ensure adequate upstream capacity, 2) Check RelayBandwidthRate/RelayBandwidthBurst in torrc, 3) Monitor with Nyx or ARM.
  • Guard: WFU below threshold : Weighted Fractional Uptime 82.3% 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 4.2 days is below 8 days requirement (3.8 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 Fast flag : HSDir flag requires having the Fast flag first
    Suggestion: Get Fast flag by having bandwidth ≥100 KB/s OR in top 7/8ths of network. Most relays get this easily.
  • 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 82.3% 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.
  • Low bandwidth authority measurements : Only 0/5 bandwidth authorities measured this relay. Minimum 3 measurements needed for accurate consensus weight.
    Suggestion: Low measurement count can indicate connectivity issues. Check: 1) Relay is reachable from multiple geographic locations, 2) ORPort accepts connections from bandwidth scanners, 3) RelayBandwidthRate in torrc matches actual capacity. New relays may take 1-2 days to be measured by all authorities.
Notes:
  • Partial IPv4 reachability: 8/9 authorities can reach this relay

Connectivity and Location

Addresses
OR Address
202.181.177.126:9001
[2a07:e01:3:269::1]:9001
Reachability (Directory Authorities)
IPv4
8/9
Location
Country
Belize Belize
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS210083
AS Name
Privex Inc. (BGP.tools)
AS Rarity
Legendary (score: 4/5, <0.05% consensus weight, 5 operators)

Flags and Eligibility

Current Flags (4): Running, Valid, V2Dir, Exit
Eligible Flags (4): Running: 8/8 | Valid: 8/8 | V2Dir: 8/8 | Fast: 3/8 | Stable: 2/8 | HSDir: 0/8 | Guard: 0/8 | Exit: 8/8
Eligibility Flag Vote Details
Flag Metric Status Relay Value Threshold Required
Running IPv4 Reachability Meets (8/8 DA) 8/8 authorities reached relay ≥5/8 DA ORPort reachable
Valid Descriptor Meets (8/8 DA) 8/8 authorities assigned Valid Not blacklisted + valid descriptor (≥5/8 DA)
V2Dir DirPort Available Meets (8/8 DA) Tunnelled: Yes (no DirPort) (R) Tunnelled directory via ORPort or DirPort (≥5/8 DA)
Fast Speed Meets (8/8 DA) 1.0 Mbit/s (R) ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/8 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Stable MTBF Below (1/8 DA) Median: 0.0d (1/8 DA above threshold)
Min/Max: 0.0d / 20555.6d (8/8 DA, Voting / Total Eligible)		 ≥32.5d - 59.1d (varies) (≥5/8 DA)
[Stricter] moria1: ≥313.0d
Uptime Below (0/8 DA) 5.4d (R) ≥7.0d - 7.1d (varies) (≥5/8 DA)
HSDir Prereq: Fast Below (3/8 DA) 3/8 DA assigned Fast ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/8 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Below (2/8 DA) 2/8 DA assigned Stable ≥32.5d - 59.1d (varies) (≥5/8 DA)
[Stricter] moria1: ≥313.0d
Prereq: V2Dir Meets (8/8 DA) 8/8 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/8 DA)
WFU Below (1/8 DA) Median: 82.4% (1/8 DA above threshold)
Min/Max: 82.3% / 100.0% (8/8 DA, Voting / Total Eligible)		 ≥98.0% (≥5/8 DA)
Time Known Meets (7/8 DA) Median: 4.1d (0/8 DA above threshold)
Min/Max: 4.0d / 5.3d (8/8 DA, Voting / Total Eligible)		 ≥1.0d (most) (≥5/8 DA)
[Stricter] moria1: ≥9.8d
Guard Prereq: Fast Below (3/8 DA) 3/8 DA assigned Fast ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/8 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Below (2/8 DA) 2/8 DA assigned Stable ≥32.5d - 59.1d (varies) (≥5/8 DA)
[Stricter] moria1: ≥313.0d
Prereq: V2Dir Meets (8/8 DA) 8/8 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/8 DA)
WFU Below (1/8 DA) Median: 82.4% (1/8 DA above threshold)
Min/Max: 82.3% / 100.0% (8/8 DA, Voting / Total Eligible)		 ≥98% (≥5/8 DA)
Time Known Below (0/8 DA) (need 3.9 more days) Median: 4.1d (0/8 DA above threshold)
Min/Max: 4.0d / 5.3d (8/8 DA, Voting / Total Eligible)		 ≥8 days (≥5/8 DA)
Bandwidth Below (0/8 DA) 1.0 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-304.0 Mbit/s (≥5/8 DA)
Exit Exit Policy Meets (8/8 DA) Port 80: Yes | Port 443: Yes (R) Allows ≥1 /8 on ports 80 AND 443 (≥5/8 DA)

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

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
1.05 Mbit/s
Advertised Bandwidth
1.05 Mbit/s
Rate Limit
8.59 Gbit/s
Burst Limit
8.59 Gbit/s
Total Data
502 MB (1 month)
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-04-15 01:45:03

Measured By
0/5 Bandwidth Authorities
Not measured by: gabelmoo, longclaw, maatuska, moria1, tor26
Median Measurement
1040.0 bit/s
Min / Max
1040 bit/s / 1040 bit/s
Network Participation: Consensus Weight: N/A | Guard: N/A | Middle: N/A | Exit: N/A

Uptime and Stability

Uptime Metrics
Current Status
DOWN 5d 8h 45m ago
Overall Uptime (1M/6M/1Y/5Y)
0.0%/0.0%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
N/A
Hibernating
No
Timestamps
First Seen
5d 8h 45m ago (2026-04-09 18:00:00)
Last Seen
5d 8h 45m ago (2026-04-09 18:00:00)
Last Restarted
5d 9h 22m ago (2026-04-09 17:22:59)
Last Changed Address
2026-04-09 18:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

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

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

Software and Version

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

Exit Health & Policy

DNS Health
Status
Not Tested
Source: exitdnshealth.1aeo.com
IPv4 Exit Policy Summary
accept: 
  22
  80
  443
IPv6 Exit Policy Summary
None
Full Exit Policy
reject 0.0.0.0/8:*
reject 169.254.0.0/16:*
reject 127.0.0.0/8:*
reject 192.168.0.0/16:*
reject 10.0.0.0/8:*
reject 172.16.0.0/12:*
reject 202.181.177.126:*
accept *:80
accept *:443
accept *:22
reject *:*

Last fetch was at Wed, 15 Apr 2026 02:45:45 GMT.

Consensus Evaluation

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

Per-Authority Details

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 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) No — — — N No — — — — — — — — — — —
dannenberg (DE) Yes Yes Yes — N Yes Valid, V2Dir, Fast, Exit 1.0 Mbit/s | 816.0 Kbit/s 1.0 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 82.3% | 98% 4.2d | 8d 0.0d | 32.5d 5.4d | 7.0d 82.3% | 98.0% 4.2d | 1.0d 2026-04-15 00:16:36 1040 bit/s
dizum (NL) Yes Yes Yes — N Yes Valid, V2Dir, Fast, Exit 1.0 Mbit/s | 816.0 Kbit/s 1.0 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 82.6% | 98% 4.0d | 8d 0.0d | 41.4d 5.4d | 7.0d 82.6% | 98.0% 4.0d | 1.0d 2026-04-15 00:16:36 1040 bit/s
faravahar (US) Yes Yes Yes — N Yes Valid, V2Dir, Fast, Exit 1.0 Mbit/s | 816.0 Kbit/s 1.0 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 82.4% | 98% 4.2d | 8d 0.0d | 59.3d 5.4d | 7.1d 82.4% | 98.0% 4.2d | 1.0d 2026-04-15 00:16:36 1040 bit/s
gabelmoo (DE) Yes Yes Yes — Y Yes Valid, V2Dir, Exit 1.0 Mbit/s | 816.0 Kbit/s 1.0 Mbit/s | 280.0 Mbit/s OR 16.0 Mbit/s 82.3% | 98% 4.0d | 8d 0.0d | 59.0d 5.4d | 7.2d 82.3% | 98.0% 4.0d | 1.0d 2026-04-15 00:16:36 1040 bit/s
longclaw (US) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Stable, Exit 1.0 Mbit/s | 816.0 Kbit/s 1.0 Mbit/s | 232.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 5.3d | 8d 5.3d | 59.1d 5.4d | 7.1d 100.0% | 98.0% 5.3d | 1.0d 2026-04-15 00:16:36 1040 bit/s
maatuska (SE) Yes Yes Yes — Y Yes Valid, V2Dir, Exit 1.0 Mbit/s | 816.0 Kbit/s 1.0 Mbit/s | 304.0 Mbit/s OR 16.0 Mbit/s 82.4% | 98% 4.1d | 8d 0.0d | 59.1d 5.4d | 7.0d 82.4% | 98.0% 4.1d | 1.0d 2026-04-15 00:16:36 1040 bit/s
moria1 (US) Yes Yes Yes — Y Yes Valid, V2Dir, Stable, Exit 1.0 Mbit/s | 8.4 Mbit/s 1.0 Mbit/s | 216.0 Mbit/s OR 16.0 Mbit/s 82.4% | 98% 4.1d | 8d 20555.6d | 313.0d 5.4d | 8.0d 82.4% | 98.0% 4.1d | 9.8d 2026-04-15 00:16:36 1040 bit/s
tor26 (AT) Yes Yes Yes — Y Yes Valid, V2Dir, Exit 1.0 Mbit/s | 816.0 Kbit/s 1.0 Mbit/s | 272.0 Mbit/s OR 16.0 Mbit/s 82.3% | 98% 4.2d | 8d 0.0d | 59.3d 5.4d | 7.5d 82.3% | 98.0% 4.2d | 1.0d 2026-04-15 00:16:36 1040 bit/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.