View Relay "Unnamed"

Fingerprint: 0F6A8ABD613A27B79AA637BFBAAFF9EF2E660AFA | Family: 1 relay | AS2856 | United Kingdom of Great Britain and Northern Ireland | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, Valid, V2Dir (3)
BW Verified
5/6 BW Auths Measured 568 bit/s Median
Stability
Not Overloaded | UP 4d 57m 46s ago
Reachability
IPv4: 9/9 (Directory Auths)
First Seen
4d 1h 46m ago
BW Weight
0.00% of Network | 2 Mbit/s Observed By Relay
Version
0.4.8.16 Not 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.3 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: Time Known below threshold : Time Known 4.0 days is below 8 days requirement (4.0 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.
  • 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.
  • Tor version not recommended : Running Tor version 0.4.8.16 which is not on the recommended list.
    Suggestion: Update to the latest stable Tor version. Outdated versions may have security vulnerabilities and could eventually be rejected by the network. See torproject.org/download for latest releases.

Connectivity and Location

Addresses
OR Address
host109-146-237-189.range109-146.btcentralplus.com
109.146.237.189:9001
Reachability (Directory Authorities)
IPv4
9/9
Location
Country
United Kingdom of Great Britain and Northern Ireland United Kingdom of Great Britain and Northern Ireland
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS2856
AS Name
British Telecommunications PLC (BGP.tools)
AS Rarity
Epic (score: 3/5, <0.05% consensus weight, 11 operators)

Flags and Eligibility

Current Flags (3): Running, Valid, V2Dir
Eligible Flags (3): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 4/9 | Stable: 0/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
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) 2.2 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: 4.0d / 4.0d (9/9 DA, Voting / Total Eligible)		 ≥11.5d - 55.6d (varies) (≥5/9 DA)
[Stricter] moria1: ≥356.4d
Uptime Below (0/9 DA) 4.0d (R) ≥13.7d - 14.7d (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 (0/9 DA) 0/9 DA assigned Stable ≥11.5d - 55.6d (varies) (≥5/9 DA)
[Stricter] moria1: ≥356.4d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (9/9 DA) Majority: 100.0% (9/9 DA) ≥98.0% (≥5/9 DA)
Time Known Meets (8/9 DA) Median: 4.0d (0/9 DA above threshold)
Min/Max: 3.2d / 4.0d (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 (0/9 DA) 0/9 DA assigned Stable ≥11.5d - 55.6d (varies) (≥5/9 DA)
[Stricter] moria1: ≥356.4d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (9/9 DA) Majority: 100.0% (9/9 DA) ≥98% (≥5/9 DA)
Time Known Below (0/9 DA) (need 4.0 more days) Median: 4.0d (0/9 DA above threshold)
Min/Max: 3.2d / 4.0d (9/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Below (0/9 DA) 2.2 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-296.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-13 23:45:02).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
2.24 Mbit/s
Advertised Bandwidth
2.05 Mbit/s
Rate Limit
2.05 Mbit/s
Burst Limit
4.10 Mbit/s
Total Data
1.8 GB (1 month)
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-03-13 23:45:02

Measured By
5/6 Bandwidth Authorities
Not measured by: longclaw
Median Measurement
568 bit/s
Min / Max
144 bit/s / 2048 bit/s
Deviation
1904 bit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0000% of network (4th pctl) | Guard: N/A | Middle: 0.0000% (2th pctl) | Exit: N/A

Uptime and Stability

Uptime Metrics
Current Status
UP 4d 57m 46s 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 1h 46m ago (2026-03-09 22:00:00)
Last Seen
5h 46m 38s ago (2026-03-13 18:00:00)
Last Restarted
4d 57m 46s ago (2026-03-09 22:48:52)
Last Changed Address
2026-03-09 22:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-03-13 16: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 
0F6A8ABD613A27B79AA637BFBAAFF9EF2E660AFA (this relay)
Alleged Members: 0
none
Indirect Members: 0
none

Software and Version

Platform
Linux — Tor 0.4.8.16 on Linux
Version
0.4.8.16 — Not Recommended
Version Status
Obsolete — Update urgently. See torproject.org/download

Exit Health & Policy

DNS Health
Not an exit relay — DNS health testing does not apply.
IPv4 Exit Policy Summary
reject: 
  1-65535
IPv6 Exit Policy Summary
None
Full Exit Policy
reject *:*

Last fetch was at Fri, 13 Mar 2026 23:46:37 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-03-13 23:45:02).

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 No — Y Yes Running, Valid, V2Dir 2.2 Mbit/s | 816.0 Kbit/s 2.2 Mbit/s | 208.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 4.0d | 8d 4.0d | 58.0d 4.0d | 14.6d 100.0% | 98.0% 4.0d | 1.0d 2026-03-13 18:11:12 568 bit/s
dannenberg (DE) Yes Yes No — N Yes Running, Valid, V2Dir, Fast 2.2 Mbit/s | 816.0 Kbit/s 2.2 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 4.0d | 8d 4.0d | 11.5d 4.0d | 14.7d 100.0% | 98.0% 4.0d | 1.0d 2026-03-13 18:11:12 2048 bit/s
dizum (NL) Yes Yes No — N Yes Running, Valid, V2Dir, Fast 2.2 Mbit/s | 816.0 Kbit/s 2.2 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 4.0d | 8d 4.0d | 46.2d 4.0d | 13.7d 100.0% | 98.0% 4.0d | 1.0d 2026-03-13 18:11:12 2048 bit/s
faravahar (US) Yes Yes No — N Yes Running, Valid, V2Dir, Fast 2.2 Mbit/s | 816.0 Kbit/s 2.2 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 4.0d | 8d 4.0d | 53.2d 4.0d | 14.7d 100.0% | 98.0% 4.0d | 1.0d 2026-03-13 18:11:12 2048 bit/s
gabelmoo (DE) Yes Yes No — Y Yes Running, Valid, V2Dir 2.2 Mbit/s | 816.0 Kbit/s 2.2 Mbit/s | 288.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 4.0d | 8d 4.0d | 59.7d 4.0d | 14.7d 100.0% | 98.0% 4.0d | 1.0d 2026-03-13 18:11:12 144 bit/s
longclaw (US) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast 2.2 Mbit/s | 816.0 Kbit/s 2.2 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 4.0d | 8d 4.0d | 59.2d 4.0d | 14.7d 100.0% | 98.0% 4.0d | 1.0d 2026-03-13 18:11:12 2048 bit/s
maatuska (SE) Yes Yes No — Y Yes Running, Valid, V2Dir 2.2 Mbit/s | 816.0 Kbit/s 2.2 Mbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 4.0d | 8d 4.0d | 39.2d 4.0d | 14.7d 100.0% | 98.0% 4.0d | 1.0d 2026-03-13 18:11:12 184 bit/s
moria1 (US) Yes Yes No — Y Yes Running, Valid, V2Dir 2.2 Mbit/s | 8.4 Mbit/s 2.2 Mbit/s | 224.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 3.2d | 8d 4.0d | 356.4d 4.0d | 16.6d 100.0% | 98.0% 3.2d | 9.8d 2026-03-13 18:11:12 512 bit/s
tor26 (AT) Yes Yes No — Y Yes Running, Valid, V2Dir 2.2 Mbit/s | 816.0 Kbit/s 2.2 Mbit/s | 272.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 4.0d | 8d 4.0d | 55.6d 4.0d | 15.3d 100.0% | 98.0% 4.0d | 1.0d 2026-03-13 18:11:12 152 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.