Tor Relays :: ChickenParmesan

View Relay "ChickenParmesan"

Fingerprint: `B8EB2223F1B558EE380C114BEA08CDC68DEF3952` | Family: 1 relay | Random Person <czt114@proton.me> | AS5378 | United Kingdom of Great Britain and Northern Ireland | Linux

Health Status

Consensus: In Consensus (7/7 Directory Auths)
Flags: Running, Valid, V2Dir, Fast, Exit (5)
DNS Health: Healthy (15.3s, 45th percentile) (via exitdnshealth.1aeo.com)
BW Verified: 5/6 BW Auths Measured 1120 bit/s Median
Stability: Not Overloaded | UP 4d 16h 1m ago

Reachability: IPv4: 7/7 (Directory Auths)
First Seen: 4d 15h 45m ago
BW Weight: 0.00% of Network | 4 Mbit/s Observed By Relay
Version: 0.4.9.11 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: bandwidth below threshold : Observed bandwidth 4 Mbit/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.6 days is below 8 days requirement (3.4 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.
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: static-90-255-234-132.vodafonexdsl.co.uk
90.255.234.132:5222
Exit Address: 90.255.234.132

Reachability (Directory Authorities)

IPv4: 7/7

Location

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

Autonomous System

AS Number: AS5378
AS Name: Vodafone Limited (BGP.tools)
AS Rarity: Legendary (score: 4/5, <0.05% consensus weight, 8 operators)

Flags and Eligibility

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

Eligibility Flag Vote Details

Flag	Metric	Status	Relay Value	Threshold Required
Running	IPv4 Reachability	Meets (7/7 DA)	7/7 authorities reached relay	≥4/7 DA ORPort reachable
Valid	Descriptor	Meets (7/7 DA)	7/7 authorities assigned Valid	Not blacklisted + valid descriptor (≥4/7 DA)
V2Dir	DirPort Available	Meets (7/7 DA)	Tunnelled: Yes (no DirPort) (R)	Tunnelled directory via ORPort or DirPort (≥4/7 DA)
Fast	Speed	Meets (7/7 DA)	4.0 Mbit/s (R)	≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥4/7 DA) [Stricter] moria1: ≥8.4 Mbit/s
Stable	MTBF	Below (0/7 DA)	Median: 4.6d (0/7 DA above threshold) Min/Max: 4.6d / 4.6d (7/7 DA, Voting / Total Eligible)	≥9.5d - 20.1d (varies) (≥4/7 DA) [Stricter] moria1: ≥7732.8d
Stable	Uptime	Meets (7/7 DA)	4.7d (R)	≥3.8d - 3.9d (varies) (≥4/7 DA)
HSDir	Prereq: Fast	Meets (4/7 DA)	4/7 DA assigned Fast	≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥4/7 DA) [Stricter] moria1: ≥8.4 Mbit/s
	Prereq: Stable	Below (0/7 DA)	0/7 DA assigned Stable	≥9.5d - 20.1d (varies) (≥4/7 DA) [Stricter] moria1: ≥7732.8d
	Prereq: V2Dir	Meets (7/7 DA)	7/7 DA assigned V2Dir	Tunnelled directory via ORPort or DirPort (≥4/7 DA)
	WFU	Meets (7/7 DA)	Majority: 100.0% (7/7 DA)	≥98.0% (≥4/7 DA)
	Time Known	Meets (6/7 DA)	Median: 4.6d (0/7 DA above threshold) Min/Max: 3.6d / 4.6d (7/7 DA, Voting / Total Eligible)	≥1.0d (most) (≥4/7 DA) [Stricter] moria1: ≥9.8d
Guard	Prereq: Fast	Meets (4/7 DA)	4/7 DA assigned Fast	≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥4/7 DA) [Stricter] moria1: ≥8.4 Mbit/s
	Prereq: Stable	Below (0/7 DA)	0/7 DA assigned Stable	≥9.5d - 20.1d (varies) (≥4/7 DA) [Stricter] moria1: ≥7732.8d
	Prereq: V2Dir	Meets (7/7 DA)	7/7 DA assigned V2Dir	Tunnelled directory via ORPort or DirPort (≥4/7 DA)
	WFU	Meets (7/7 DA)	Majority: 100.0% (7/7 DA)	≥98% (≥4/7 DA)
	Time Known	Below (0/7 DA) (need 3.4 more days)	Median: 4.6d (0/7 DA above threshold) Min/Max: 3.6d / 4.6d (7/7 DA, Voting / Total Eligible)	≥8 days (≥4/7 DA)
	Bandwidth	Below (0/7 DA)	4.0 Mbit/s (R)	≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-288.0 Mbit/s (≥4/7 DA)
Exit	Exit Policy	Meets (7/7 DA)	Port 80: Yes \| Port 443: Yes (R)	Allows ≥1 /8 on ports 80 AND 443 (≥4/7 DA)

(DA) = Dir. Auth. Measured | (R) = Relay Reported
Data from Tor CollecTor (authority votes, fetched 2026-07-14 02:45:10).

Bandwidth Metrics

Capacity (Relay Reported)

Observed Bandwidth: 4.00 Mbit/s
Advertised Bandwidth: 4.00 Mbit/s
Rate Limit: 4.10 Mbit/s
Burst Limit: 4.10 Mbit/s
Total Data: 11 GB (1 month)

Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-07-14 02:45:10

Measured By: 5/6 Bandwidth Authorities
Not measured by: bastet
Median Measurement: 1120 bit/s
Min / Max: 680 bit/s / 4000 bit/s
Deviation: 3320 bit/s [Warning] High variation

Network Participation: Consensus Weight: 0.0001% of network (4th pctl) | Guard: N/A | Middle: N/A | Exit: 0.0002% (1th pctl)

Uptime and Stability

Uptime Metrics

Current Status: UP 4d 16h 1m 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 15h 45m ago (2026-07-09 11:00:00)
Last Seen: 1h 45m 57s ago (2026-07-14 01:00:00)
Last Restarted: 4d 16h 1m ago (2026-07-09 10:44:35)
Last Changed Address: 2026-07-09 11:00:00

Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

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

AROI Domain (?): Not specified
Operator Validation: Unvalidated
This Relay: N/A (no AROI configured)
Contact: Random Person <czt114@proton.me>

Family Configuration

Family Support: None — No family membership configured

Happy Families (family-cert)

Effective Members: 0: none

MyFamily (legacy declarations)

Effective Member: 1

B8EB2223F1B558EE380C114BEA08CDC68DEF3952 (this relay)

Alleged Members: 0

none

Indirect Members: 0

none

Software and Version

Platform: Linux — Tor 0.4.9.11 on Linux
Version: 0.4.9.11 — Recommended
Version Status: Recommended

Exit Health & Policy

DNS Health

Status

Healthy (avg. 15.3s, 45th percentile)

Query Domain

d19cd7f4eceb4e4292bd742fb98a98e1.b8eb2223.tor.exit.validator.1aeo.com

DNS Result

Resolved to 64.65.4.1

Cross-Validation

4/4 instances succeeded

First Hop

tornode1 (PL) BD30E1532EE061CA7825FC929D765FFB55C8B889

Exit Address Used

90.255.234.132

Per-Instance Results

Cross Validation Attempt 1:	Success, 18.6s	(cv1_w3)
Cross Validation Attempt 2:	Success, 13.7s	(cv2_w3)
Cross Validation Attempt 3:	Success, 14.1s	(cv3_w3)
Cross Validation Attempt 4:	Success, 15.0s	(cv4_w3)

Tested: 2026-07-13 19:15:14 UTC

Source: exitdnshealth.1aeo.com

IPv4 Exit Policy Summary

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 90.255.234.132:*
accept *:43
accept *:53
accept *:79-81
accept *:88
accept *:194
accept *:389
accept *:443
accept *:464
accept *:531
accept *:543-544
accept *:554
accept *:563
accept *:636
accept *:706
accept *:749
accept *:853
accept *:873
accept *:902-904
accept *:981
accept *:989-992
accept *:994
accept *:1194
accept *:1220
accept *:1293
accept *:1500
accept *:1533
accept *:1677
accept *:1723
accept *:1755
accept *:1863
accept *:2082-2083
accept *:2086-2087
accept *:2095-2096
accept *:2102-2104
accept *:3128
accept *:3389
accept *:3690
accept *:4321
accept *:4643
accept *:5050
accept *:5190
accept *:5222-5223
accept *:5228
accept *:5900
accept *:6660-6669
accept *:6679
accept *:8000
accept *:8008
accept *:8074
accept *:8080
accept *:8082
accept *:8087-8088
accept *:8232-8233
accept *:8332-8333
accept *:8443
accept *:8888
accept *:9418
accept *:9999-10000
accept *:11371
accept *:19294
accept *:19638
accept *:50002
accept *:64738
reject *:*

Last fetch was at Tue, 14 Jul 2026 02:45:56 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-07-14 02: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	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, Exit	4.0 Mbit/s \| 816.0 Kbit/s	4.0 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	4.6d \| 8d	4.6d \| 29.6d	4.7d \| 4.2d	100.0% \| 98.0%	4.6d \| 1.0d	2026-07-13 22:46:57	4000 bit/s
dannenberg (DE)	Yes	Yes	Yes	—	Y	Yes	Running, Valid, V2Dir, Fast, Exit	4.0 Mbit/s \| 816.0 Kbit/s	4.0 Mbit/s \| 248.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	4.6d \| 8d	4.6d \| 9.5d	4.7d \| 3.9d	100.0% \| 98.0%	4.6d \| 1.0d	2026-07-13 22:46:57	1120 bit/s
dizum (NL)	Yes	Yes	Yes	—	N	Yes	Running, Valid, V2Dir, Fast, Exit	4.0 Mbit/s \| 816.0 Kbit/s	4.0 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	4.6d \| 8d	4.6d \| 18.6d	4.7d \| 3.9d	100.0% \| 98.0%	4.6d \| 1.0d	2026-07-13 22:46:57	4000 bit/s
faravahar (US)	Yes	Yes	Yes	—	Y	Yes	Running, Valid, V2Dir, Fast, Exit	4.0 Mbit/s \| 816.0 Kbit/s	4.0 Mbit/s \| 288.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	4.6d \| 8d	4.6d \| 16.3d	4.7d \| 3.9d	100.0% \| 98.0%	4.6d \| 1.0d	2026-07-13 22:46:57	960 bit/s
maatuska (SE)	Yes	Yes	Yes	—	Y	Yes	Running, Valid, V2Dir, Exit	4.0 Mbit/s \| 816.0 Kbit/s	4.0 Mbit/s \| 280.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	4.6d \| 8d	4.6d \| 20.1d	4.7d \| 3.9d	100.0% \| 98.0%	4.6d \| 1.0d	2026-07-13 22:46:57	792 bit/s
moria1 (US)	Yes	Yes	Yes	—	Y	Yes	Running, Valid, V2Dir, Exit	4.0 Mbit/s \| 8.4 Mbit/s	4.0 Mbit/s \| 232.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	3.6d \| 8d	4.6d \| 7732.8d	4.7d \| 4.2d	100.0% \| 98.0%	3.6d \| 9.8d	2026-07-13 22:46:57	1200 bit/s
tor26 (AT)	Yes	Yes	Yes	—	Y	Yes	Running, Valid, V2Dir, Exit	4.0 Mbit/s \| 816.0 Kbit/s	4.0 Mbit/s \| 264.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	4.6d \| 8d	4.6d \| 30.3d	4.7d \| 3.8d	100.0% \| 98.0%	4.6d \| 1.0d	2026-07-13 22:46:57	680 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.