View Relay "Void"

Fingerprint: F12CF84EB7D1CE4D33CA710DB1652632AB849896 | Family: 1 relay | AS154633 | United States of America | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, Valid, V2Dir, Exit (4)
DNS Health
Healthy (7.5s, 9th percentile) (via exitdnshealth.1aeo.com)
BW Verified
4/7 BW Auths Measured 3920 bit/s Median
Stability
Not Overloaded | UP 1d 18h 13m ago | UP 100% (1M)
Reachability
IPv4: 9/9 (Directory Auths)
First Seen
1w 2d 9h ago
BW Weight
0.00% of Network | 3 Mbit/s Observed By Relay
Version
0.4.9.9 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.5 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.
  • 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.
  • 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.

Connectivity and Location

Addresses
OR Address
157.254.24.9:443
Exit Address
157.254.24.9
Reachability (Directory Authorities)
IPv4
9/9
Location
Country
United States of America United States of America
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS154633
AS Name
Sparrowhost Technologies Private Limited (BGP.tools)
AS Rarity
Legendary (score: 5/5, <0.05% consensus weight, 1 operator)

Flags and Eligibility

Current Flags (4): Running, Valid, V2Dir, Exit
Eligible Flags (4): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 4/9 | Stable: 4/9 | HSDir: 0/9 | Guard: 0/9 | Exit: 8/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
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) 3.9 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 (0/9 DA) Median: 4.0d (0/9 DA above threshold)
Min/Max: 0.2d / 9.3d (9/9 DA, Voting / Total Eligible)		 ≥10.1d - 48.4d (varies) (≥5/9 DA)
[Stricter] moria1: ≥1364.1d
Uptime Below (0/9 DA) 1.8d (R) ≥4.3d - 5.2d (varies) (≥5/9 DA)
HSDir Prereq: Fast Below (4/9 DA) 4/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 (4/9 DA) 4/9 DA assigned Stable ≥10.1d - 48.4d (varies) (≥5/9 DA)
[Stricter] moria1: ≥1364.1d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Below (4/9 DA) Median: 88.2% (4/9 DA above threshold)
Min/Max: 10.1% / 100.0% (9/9 DA, Voting / Total Eligible)		 ≥98.0% (≥5/9 DA)
Time Known Meets (8/9 DA) Median: 7.1d (4/9 DA above threshold)
Min/Max: 4.2d / 9.3d (9/9 DA, Voting / Total Eligible)		 ≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.8d
Guard Prereq: Fast Below (4/9 DA) 4/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 (4/9 DA) 4/9 DA assigned Stable ≥10.1d - 48.4d (varies) (≥5/9 DA)
[Stricter] moria1: ≥1364.1d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Below (4/9 DA) Median: 88.2% (4/9 DA above threshold)
Min/Max: 10.1% / 100.0% (9/9 DA, Voting / Total Eligible)		 ≥98% (≥5/9 DA)
Time Known Below (4/9 DA) (need 0.9 more days) Median: 7.1d (4/9 DA above threshold)
Min/Max: 4.2d / 9.3d (9/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Below (0/9 DA) 3.9 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-312.0 Mbit/s (≥5/9 DA)
Exit Exit Policy Meets (8/9 DA) Port 80: Yes | Port 443: Yes (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-07-03 03:02:32).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
3.93 Mbit/s
Advertised Bandwidth
3.93 Mbit/s
Rate Limit
419.43 Mbit/s
Burst Limit
503.32 Mbit/s
Total Data
16 GB (1 month)
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-07-03 03:02:32

Measured By
4/7 Bandwidth Authorities
Not measured by: bastet, dannenberg, gabelmoo
Median Measurement
3920 bit/s
Min / Max
88 bit/s / 6112 bit/s
Deviation
6024 bit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0000% of network (5th pctl) | Guard: N/A | Middle: N/A | Exit: 0.0001% (5th pctl)

Uptime and Stability

Uptime Metrics
Current Status
UP 1d 18h 13m ago
Overall Uptime (1M/6M/1Y/5Y)
100.0%/0.0%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (100.0%/0.0%/0.0%/0.0%)
Hibernating
No
Timestamps
First Seen
1w 2d 9h ago (2026-06-23 18:00:00)
Last Seen
2h 11m 26s ago (2026-07-03 01:00:00)
Last Restarted
1d 18h 13m ago (2026-07-01 08:58:14)
Last Changed Address
2026-06-23 18:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-07-02 19:00 UTC

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

Software and Version

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

Exit Health & Policy

DNS Health
Status
Healthy (avg. 7.5s, 9th percentile)
Query Domain
d94d8504e6334c009ea2a38bde363517.f12cf84e.tor.exit.validator.1aeo.com
DNS Result
Resolved to 64.65.4.1
Cross-Validation
4/4 instances succeeded
First Hop
theTorDoor (US) 14F49599D7310B2574830C1345C6C5B139C0E507
Exit Address Used
157.254.24.9
Per-Instance Results
Cross Validation Attempt 1: Success, 8.7s (cv1_w4)
Cross Validation Attempt 2: Success, 7.1s (cv2_w4)
Cross Validation Attempt 3: Success, 6.4s (cv3_w4)
Cross Validation Attempt 4: Success, 7.7s (cv4_w4)
Tested: 2026-07-02 19:20:47 UTC
Source: exitdnshealth.1aeo.com
IPv4 Exit Policy Summary
accept: 
  1-65535
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 157.254.24.9:*
accept *:*

Last fetch was at Fri, 03 Jul 2026 03:11:23 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-07-03 03:02:32).

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) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Stable, Exit 3.9 Mbit/s | 816.0 Kbit/s 3.9 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 9.3d | 8d 9.3d | 48.4d 1.8d | 5.1d 100.0% | 98.0% 9.3d | 1.0d 2026-07-02 21:00:20 3920 bit/s
dannenberg (DE) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Exit 3.9 Mbit/s | 816.0 Kbit/s 3.9 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 82.3% | 98% 6.1d | 8d 0.3d | 10.1d 1.8d | 5.2d 82.3% | 98.0% 6.1d | 1.0d 2026-07-02 21:00:20 3920 bit/s
dizum (NL) Yes Yes Yes — N Yes Running, Valid, V2Dir, Fast, Stable, Exit 3.9 Mbit/s | 816.0 Kbit/s 3.9 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 9.3d | 8d 9.3d | 25.9d 1.8d | 5.2d 100.0% | 98.0% 9.3d | 1.0d 2026-07-02 21:00:20 3920 bit/s
faravahar (US) Yes Yes Yes — N Yes Running, Valid, V2Dir, Fast, Exit 3.9 Mbit/s | 816.0 Kbit/s 3.9 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 88.1% | 98% 8.6d | 8d 4.0d | 28.4d 1.8d | 5.2d 88.1% | 98.0% 8.6d | 1.0d 2026-07-02 21:00:20 3920 bit/s
gabelmoo (DE) Yes Yes No — Y Yes Valid, V2Dir 3.9 Mbit/s | 816.0 Kbit/s 3.9 Mbit/s | 312.0 Mbit/s OR 16.0 Mbit/s 10.1% | 98% 4.2d | 8d 0.2d | 60.1d 1.8d | 4.3d 10.1% | 98.0% 4.2d | 1.0d 2026-06-29 05:36:51 6112 bit/s
longclaw (US) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Exit 3.9 Mbit/s | 816.0 Kbit/s 3.9 Mbit/s | 240.0 Mbit/s OR 16.0 Mbit/s 88.2% | 98% 7.1d | 8d 2.5d | 57.2d 1.8d | 5.4d 88.2% | 98.0% 7.1d | 1.0d 2026-07-02 21:00:20 440 bit/s
maatuska (SE) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Stable, Exit 3.9 Mbit/s | 816.0 Kbit/s 3.9 Mbit/s | 304.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 9.3d | 8d 9.3d | 30.6d 1.8d | 5.3d 100.0% | 98.0% 9.3d | 1.0d 2026-07-02 21:00:20 88 bit/s
moria1 (US) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Stable, Exit 3.9 Mbit/s | 8.4 Mbit/s 3.9 Mbit/s | 248.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 6.1d | 8d 9.3d | 1364.1d 1.8d | 5.4d 100.0% | 98.0% 6.1d | 9.8d 2026-07-02 21:00:20 304 bit/s
tor26 (AT) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Exit 3.9 Mbit/s | 816.0 Kbit/s 3.9 Mbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 87.9% | 98% 7.1d | 8d 2.5d | 53.1d 1.8d | 5.4d 87.9% | 98.0% 7.1d | 1.0d 2026-07-02 21:00:20 800 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.