View Relay "RealityNews12"

Fingerprint: `90B0ECD82FF66D1F2C27149FBB05162009F86FD6` | Operator: tomorefreedomitis.com v2 (4 relays) ⚠ Misconfigured | Family: 8 relays | email:jingojngo at gmail.com... | AS13285 | United Kingdom of Great Britain and Northern Ireland | Windows

Health Status

Consensus: In Consensus (9/9 Directory Auths)
Flags: Running, Valid, V2Dir, Fast, Stable (5)
BW Verified: 5/7 BW Auths Measured 2 Mbit/s Median
Stability: Not Overloaded | UP 2d 19h 10m ago | UP 99% (1M)

Reachability: IPv4: 9/9 | v6: 8/8(Directory Auths)
First Seen: 1mo 1w 23h ago
BW Weight: 0.00% of Network | 9 Mbit/s Observed By Relay
Version: 0.4.9.15 Recommended

Issues Detected:

Guard: bandwidth below threshold : 0/9 authorities credit this relay with enough bandwidth for Guard (5 needed): at least 16.8 Mbit/s (AuthDirGuardBWGuarantee) or a place in their top 25% (80.0 Mbit/s – 272.0 Mbit/s). bastet, dannenberg, gabelmoo, moria1 and tor26 measured this relay at 1.9 Mbit/s – 5.6 Mbit/s. dizum, faravahar, longclaw and maatuska used the relay-reported 8.4 Mbit/s.
Suggestion: Guard requires a bandwidth of at least AuthDirGuardBWGuarantee (16.8 Mbit/s by default) or one in the top 25% of relays, judged by each authority the same way as for Fast. To increase bandwidth: 1) Ensure adequate upstream capacity, 2) Check RelayBandwidthRate/RelayBandwidthBurst in torrc, 3) Monitor with Nyx.
HSDir: uptime below 96 hours : Only 0/9 authorities voted HSDir, though this relay has Fast, Stable and V2Dir
Suggestion: HSDir needs 96 hours of uptime as each authority sees it (MinUptimeHidServDirectoryV2): the time since your relay restarted, or since that authority last failed to reach it if that is shorter. Keep the relay running and reachable.
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: 92.27.137.133:9003
[2001:470:1f1c:149::2]:9003

Reachability (Directory Authorities)

IPv4: 9/9
IPv6: 8/8 (1 don't test)

Location

Country: United Kingdom of Great Britain and Northern Ireland
Interactive Map: View in RouteFluxMap

Autonomous System

AS Number: AS13285
AS Name: TalkTalk Communications Limited (BGP.tools)
AS Rarity: Legendary (score: 4/5, <0.05% consensus weight, 5 operators)

Flags and Eligibility

Current Flags (5): Running, Valid, V2Dir, Fast, Stable

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
Running	IPv6 Reachability	Meets (8/8 DA)	8/8 tested authorities reached relay	≥5/8 tested (majority) (≥5/8 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	Partial (8/9 DA)	1.9 Mbit/s – 5.6 Mbit/s (5 DA measured) 8.4 Mbit/s (4 DA relay-reported)	≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA) [Stricter] moria1: ≥8.4 Mbit/s
Stable	MTBF	Partial (7/9 DA)	Median: 12.6d (6/9 DA above threshold) Min/Max: 0.8d / 2732.1d (9/9 DA, Voting / Total Eligible)	≥2.4d - 9.3d (varies) (≥5/9 DA) [Stricter] moria1: ≥7607.5d
Stable	Uptime	Below (0/9 DA)	2.8d (R)	≥5.2d - 5.3d (varies) (≥5/9 DA)
HSDir	Prereq: Fast	Meets (8/9 DA)	8/9 DA assigned Fast 1.9 Mbit/s – 5.6 Mbit/s (5 DA measured) 8.4 Mbit/s (4 DA relay-reported)	≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA) [Stricter] moria1: ≥8.4 Mbit/s
	Prereq: Stable	Meets (8/9 DA)	8/9 DA assigned Stable	≥2.4d - 9.3d (varies) (≥5/9 DA) [Stricter] moria1: ≥7607.5d
	Prereq: V2Dir	Meets (9/9 DA)	9/9 DA assigned V2Dir	Tunnelled directory via ORPort or DirPort (≥5/9 DA)
	Uptime	Below (0/9 DA)	2.8d (R)	≥96h as each authority sees it (MinUptimeHidServDirectoryV2) (≥5/9 DA) [Stricter] moria1: ≥98% WFU and ≥9.8d Time Known
Guard	Prereq: Fast	Meets (8/9 DA)	8/9 DA assigned Fast 1.9 Mbit/s – 5.6 Mbit/s (5 DA measured) 8.4 Mbit/s (4 DA relay-reported)	≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA) [Stricter] moria1: ≥8.4 Mbit/s
	Prereq: Stable	Meets (8/9 DA)	8/9 DA assigned Stable	≥2.4d - 9.3d (varies) (≥5/9 DA) [Stricter] moria1: ≥7607.5d
	Prereq: V2Dir	Meets (9/9 DA)	9/9 DA assigned V2Dir	Tunnelled directory via ORPort or DirPort (≥5/9 DA)
	WFU	Partial (8/9 DA)	Median: 98.9% (8/9 DA above threshold) Min/Max: 94.7% / 99.3% (9/9 DA, Voting / Total Eligible)	≥98%; dizum: ≥97.84099999999999% (≥5/9 DA)
	Time Known	Meets (9/9 DA)	Median: 22.6d (9/9 DA above threshold) Min/Max: 9.9d / 33.4d (9/9 DA, Voting / Total Eligible)	≥8 days (≥5/9 DA)
	Bandwidth	Below (0/9 DA)	1.9 Mbit/s – 5.6 Mbit/s (5 DA measured) 8.4 Mbit/s (4 DA relay-reported)	≥16.8 Mbit/s (AuthDirGuardBWGuarantee) OR top 25% (≥80.0 Mbit/s-272.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-11-04 12:45:10).

Bandwidth Metrics

Capacity (Relay Reported)

Observed Bandwidth: 9.80 Mbit/s
Advertised Bandwidth: 8.39 Mbit/s
Rate Limit: 8.39 Mbit/s
Burst Limit: 8.59 Gbit/s
Total Data: 1.7 TB (6 months)
1mo: 1.6 TB | 6mo: 1.7 TB

Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-11-04 12:45:10

Measured By: 5/7 Bandwidth Authorities
Not measured by: faravahar, longclaw
Consensus Weight: 2.7 Mbit/s (median of 5 measurements)
Measured Min / Max: 1.9 Mbit/s / 5.6 Mbit/s
Deviation: 3.7 Mbit/s [Warning] High variation

Network Participation: Consensus Weight: 0.0001% of network (9th pctl) | Guard: N/A | Middle: 0.0004% (10th pctl) | Exit: N/A

History

Throughput and write/read, last 6 months

Uptime and Stability

Uptime Metrics

Current Status: UP 2d 19h 10m ago
Overall Uptime (1M/6M/1Y/5Y): 99.8%/97.0%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y): Matches Overall Uptime (99.8%/97.0%/0.0%/0.0%)
Hibernating: No

Timestamps

First Seen: 1mo 1w 23h ago (2026-09-27 14:00:00)
Last Seen: 2h 45m 39s ago (2026-11-04 11:00:00)
Last Restarted: 2d 19h 10m ago (2026-11-01 18:34:48)
Last Changed Address: 2026-09-27 14:00:00

Overload Status: Not Overloaded — No overload conditions reported.

Evaluated 2026-11-04 13:45 UTC. /details snapshot 2026-11-04 11:00:00 UTC (cached 42s ago). /bandwidth snapshot 2026-11-04 05:00:00 UTC (cached 6h ago).

General Overload (from /details)

Status: No general overload report in available data

File Descriptor Exhaustion (from /bandwidth)

Status: No file-descriptor exhaustion report in available data

Rate Limits (from /bandwidth)

Status: No rate-limit report in available data
Rate Limit: —
Burst Limit: —
Write counter: —
Read counter: —

About these reports and MetricsPort

Allium’s eligibility windows are applied to the reported timestamps: 72 hours for general overload and file-descriptor exhaustion, 24 hours for a rate-limit hit. A report at the cutoff is historical. An older report can remain visible after Onionoo or Allium’s cache still has it. The cutoff does not prove the relay recovered at that moment. Allium caches the bandwidth document for 12 hours by default. The snapshot time is when Onionoo published that document. It is not the relay’s event time, and it is not necessarily the extra-info publication time. Cache age is how old Allium’s copy is.

MetricsPort counters are cumulative. Compare samples, and account for process restarts. A nonzero total alone does not show ongoing activity. Gauges describe current values. An unavailable metric is unknown, not zero. Allium does not have this relay’s MetricsPort readings and does not invent them.

The port below is an example for an endpoint you have already configured. MetricsPort must be enabled with restricted access and must not be exposed publicly. Setup stays in the Tor overload troubleshooting guide.

curl http://127.0.0.1:9035/metrics

History

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-11-04 04:00 UTC

AROI Domain (?): tomorefreedomitis.com
Operator Validation: Unvalidated
This Relay: Unvalidated
Error: URI-RSA: HTTP error 404 for tomorefreedomitis.com at URL: https://tomorefreedomitis.com/.well-known/tor-relay/rsa-fingerprint.txt; URI-RSA: HTTP SSL hostname mismatch, certificate is not valid for www.tomorefreedomitis.com at URL: https://www.tomorefreedomitis.com/.well-known/tor-relay/rsa-fingerprint.txt
Contact: email:jingojngo at gmail.com url:https://tomorefreedomitis.com proof:uri-rsa pgp:F8A61A2F cost:70GBP uplinkbw:80 memory:64000 cpu:985K btc:bc1q64s3540s42uyuvdcnsyaukmr0dkwp7w26450rj offlinemasterkey:n sandbox:n os:Window/11/Pro/25H2 tls:openssl autoupdate:y confmgmt:manual ciissversion:2 trafficacct:unmetered

Family Configuration

Family Support: Happy Families (8) — Has family-cert in server descriptor (guide) | View Full Family (8)

Happy Families (family-cert)

Effective Members: 8

16C4EB200957606BE8E5F07BBE0E523C31ABBCDC
448B98E456E6E8AA2F2F332D7E3EDC68233E11D7
506600D9FBACE4D2D559C869D8516D4A74DBBD22
90B0ECD82FF66D1F2C27149FBB05162009F86FD6 (this relay)
9F2C36D8BDD29A25DCBE0B9CFBC7FE1EC6F4CED3
BEEEB7C935E314EBE8C9BA77EE4DF0C52844440E
C7865D58EEFE96B92333E3C8BE3C0AAAA0000EEF
E37485E32D38E703319A4D737ABB53253EDB2E02

MyFamily (legacy declarations) — none

Software and Version

Platform: Windows — Tor 0.4.9.15 on Windows 8 [or later]
Version: 0.4.9.15 — Recommended
Version Status: Recommended

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 Wed, 04 Nov 2026 13:45:39 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-11-04 12:45:10).

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	v6	Flags	Fast (BW\|T)	Guard BW (BW\|Threshold)	Guard WFU (M\|T)	Guard TK (M\|T)	Stable MTBF (M\|T)	Stable Uptime (Relay\|T)	Desc Published	Cons Wt (Authority)
bastet (US)	Yes	Yes	No	—	Y	Yes	Yes	Running, Valid, V2Dir, Fast, Stable	5.5 Mbit/s (M) \| 816.0 Kbit/s	5.5 Mbit/s (M) \| 192.0 Mbit/s OR 16.8 Mbit/s	98.5% \| 98%	18.1d \| 8d	10.3d \| 8.4d	2.8d \| 5.2d	2026-11-03 20:34:50	5.5 Mbit/s (M)
dannenberg (DE)	Yes	Yes	No	—	Y	Yes	Yes	Running, Valid, V2Dir, Fast, Stable	1.9 Mbit/s (M) \| 816.0 Kbit/s	1.9 Mbit/s (M) \| 272.0 Mbit/s OR 16.8 Mbit/s	99.2% \| 98%	33.4d \| 8d	12.6d \| 9.3d	2.8d \| 5.3d	2026-11-03 20:34:50	1.9 Mbit/s (M)
dizum (NL)	Yes	Yes	No	—	N	Yes	Yes	Running, Valid, V2Dir, Fast	8.4 Mbit/s (R) \| 816.0 Kbit/s	8.4 Mbit/s (R) \| 80.0 Mbit/s OR 16.8 Mbit/s	94.7% \| 98%	10.3d \| 8d	0.8d \| 6.7d	2.8d \| 5.3d	2026-11-03 20:34:50	8.4 Mbit/s (R)
faravahar (US)	Yes	Yes	No	—	Y	Yes	Yes	Running, Valid, V2Dir, Fast, Stable	8.4 Mbit/s (R) \| 816.0 Kbit/s	8.4 Mbit/s (R) \| 80.0 Mbit/s OR 16.8 Mbit/s	98.9% \| 98%	22.6d \| 8d	8.9d \| 6.5d	2.8d \| 5.3d	2026-11-03 20:34:50	8.4 Mbit/s (R)
gabelmoo (DE)	Yes	Yes	No	—	Y	Yes	Yes	Running, Valid, V2Dir, Fast, Stable	2.7 Mbit/s (M) \| 816.0 Kbit/s	2.7 Mbit/s (M) \| 248.0 Mbit/s OR 16.8 Mbit/s	99.3% \| 98%	33.4d \| 8d	28.5d \| 10.8d	2.8d \| 5.3d	2026-11-03 20:34:50	2.7 Mbit/s (M)
longclaw (US)	Yes	Yes	No	—	Y	Yes	N/T	Running, Valid, V2Dir, Fast, Stable	8.4 Mbit/s (R) \| 816.0 Kbit/s	8.4 Mbit/s (R) \| 80.0 Mbit/s OR 16.8 Mbit/s	99.3% \| 98%	33.3d \| 8d	28.6d \| 10.9d	2.8d \| 5.3d	2026-11-03 20:34:50	8.4 Mbit/s (R)
maatuska (SE)	Yes	Yes	No	—	N	Yes	Yes	Running, Valid, V2Dir, Fast, Stable	8.4 Mbit/s (R) \| 816.0 Kbit/s	8.4 Mbit/s (R) \| 80.0 Mbit/s OR 16.8 Mbit/s	98.2% \| 98%	21.3d \| 8d	3.6d \| 2.4d	2.8d \| 5.3d	2026-11-03 20:34:50	8.4 Mbit/s (R)
moria1 (US)	Yes	Yes	No	—	Y	Yes	Yes	Running, Valid, V2Dir, Stable	5.6 Mbit/s (M) \| 8.4 Mbit/s	5.6 Mbit/s (M) \| 192.0 Mbit/s OR 16.8 Mbit/s	98.3% \| 98%	9.9d \| 8d	2732.1d \| 7607.5d	2.8d \| 5.3d	2026-11-03 20:34:50	5.6 Mbit/s (M)
tor26 (AT)	Yes	Yes	No	—	Y	Yes	Yes	Running, Valid, V2Dir, Fast, Stable	2.3 Mbit/s (M) \| 816.0 Kbit/s	2.3 Mbit/s (M) \| 256.0 Mbit/s OR 16.8 Mbit/s	99.2% \| 98%	30.3d \| 8d	24.9d \| 10.6d	2.8d \| 5.3d	2026-11-03 20:34:50	2.3 Mbit/s (M)

N/T = this authority does not test IPv6 • — = not in this vote • Format: relay value | authority threshold • WFU = Weighted Fractional Uptime • TK = Time Known • Bandwidth source: (M) bandwidth-scanner measurement, (R) relay-reported, (U) unmeasured, counted as 0

Bandwidth Values Explained:
Measured (M) = An authority's bandwidth-scanner measurement of your relay (Measured= in its vote). An authority that has one uses it for the Fast and Guard flags, and the consensus weight is the median of these measurements when 3 or more authorities have one.
Relay-reported (R) = The bandwidth your relay advertises: the lower of its observed bandwidth and its rate limit, capped at 10 MB/s (Bandwidth= in every vote). An authority without a measurement uses it for flags, unless it has measurements for enough other relays (ignoring-advertised-bws=1); then your relay counts as 0 (U). It sets the consensus weight only when fewer than 3 authorities measured the relay, capped at 20 KB/s (maxunmeasuredbw) while 3 or more authorities publish measurements.
Not published = The authority has no measurement of your relay in its vote and ignores relay-reported bandwidth, yet it voted Fast or its vote has no measurements at all: it judges your relay by a measurement kept from an earlier bandwidth file (0 if none), which its vote doesn't show.
Why different? A low measurement means the bandwidth scanners see your relay underperforming compared with other relays that report a similar speed. Votes list both values in kilobytes per second. Rules: Assigning flags in a vote, Computing a consensus.

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.

View Relay "RealityNews12"

Fingerprint: 90B0ECD82FF66D1F2C27149FBB05162009F86FD6 | Operator: tomorefreedomitis.com v2 (4 relays) ⚠ Misconfigured | Family: 8 relays | email:jingojngo at gmail.com... | AS13285 | United Kingdom of Great Britain and Northern Ireland | Windows

Addresses

Reachability (Directory Authorities)

Location

Autonomous System

Eligibility Flag Vote Details

Capacity (Relay Reported)

Measurement (Directory Authority Verified)

History

Uptime Metrics

Timestamps

General Overload (from /details)

File Descriptor Exhaustion (from /bandwidth)

Rate Limits (from /bandwidth)

History

Operator Identity

Family Configuration

Full Exit Policy

Fingerprint: `90B0ECD82FF66D1F2C27149FBB05162009F86FD6` | Operator: tomorefreedomitis.com v2 (4 relays) ⚠ Misconfigured | Family: 8 relays | email:jingojngo at gmail.com... | AS13285 | United Kingdom of Great Britain and Northern Ireland | Windows