Tor Relays :: cb1tor

View Relay "cb1tor"

Fingerprint: `EE72F8544BC46F6FFCDB47CCDB954E5AC642756C` | Family: 1 relay | supermp3man@protonmail.com | AS60404 | Netherlands | Linux

Health Status

Consensus: Not In Consensus (1/8 Directory Auths, need 5)
Flags: Running, Valid, Fast, Stable, Exit (5)
DNS Health: Not Tested (via exitdnshealth.1aeo.com)
BW Verified: 0/5 BW Auths Measured 80 Kbit/s Median
Stability: Overloaded | DOWN 23h 46m 38s ago | UP 100% (1M)

Reachability: IPv4: 1/9 | v6: 0/8 (Directory Auths)
First Seen: 3w 1d 14h ago
BW Weight: 0.01% of Network | 197 Mbit/s Observed By Relay
Version: 0.4.8.18 Not Recommended

Issues Detected:

Not in consensus : Only 1/8 authorities voted for this relay (need 5)
Suggestion: Verify your relay is reachable from multiple geographic locations. Check firewall rules allow incoming connections on your ORPort from all directory authority IP addresses.
IPv4 reachability issues : Only 1/9 authorities can reach this relay
Suggestion: Authorities that cannot reach you: bastet, dannenberg, faravahar, gabelmoo, longclaw, maatuska, moria1, tor26. Check: 1) Firewall allows incoming TCP on ORPort, 2) No ISP-level blocking, 3) Tor is running and listening. Use 'nc -zv your-ip your-orport' from external hosts to test.
IPv6 not reachable : 0/8 authorities that test IPv6 can reach your IPv6 address
Suggestion: Verify IPv6 is correctly configured: 1) Check ORPort binding includes IPv6 address, 2) Firewall allows IPv6 traffic, 3) IPv6 address is publicly routable. Test with: curl -6 http://ipv6.icanhazip.com/
HSDir: requires V2Dir (tunnelled-dir-server) : HSDir requires the relay to support tunnelled directory requests (V2Dir flag). This relay is missing V2Dir — the descriptor likely does not include tunnelled-dir-server, usually because DirCache 0 is set in torrc.
Suggestion: Remove DirCache 0 from torrc (DirCache is enabled by default in Tor ≥0.3.3). Restart Tor and verify the descriptor includes tunnelled-dir-server. You can check with: grep tunnelled-dir-server /var/lib/tor/cached-descriptors
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.
Tor version not recommended : Running Tor version 0.4.8.18 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.
Write Bandwidth Limit Hit : Write rate limit (84 Mbit/s) was hit 215 times. Relay is throttling outbound traffic.
Suggestion: Increase RelayBandwidthRate and RelayBandwidthBurst in torrc if your connection has more upload capacity.

Notes:

Rate Limit Configuration: Configured limits: Rate=84 Mbit/s, Burst=9 Gbit/s. Limits hit: Write=215, Read=0.

Connectivity and Location

Addresses

OR Address: 5.255.99.147:9001
[2a04:52c0:104:4735::1]:9001
Exit Address: 5.255.99.147

Reachability (Directory Authorities)

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

Location

Country: Netherlands
Interactive Map: View in RouteFluxMap

Autonomous System

AS Number: AS60404
AS Name: The Infrastructure Group B.V. (BGP.tools)
AS Rarity: Rare (score: 2/5, 0.52% consensus weight, 33 operators)

Flags and Eligibility

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

Eligibility Flag Vote Details

Flag	Metric	Status	Relay Value	Threshold Required
Running	IPv4 Reachability	Below (1/8 DA)	1/8 authorities reached relay	≥5/8 DA ORPort reachable
Running	IPv6 Reachability	Below (0/7 DA)	0/7 tested authorities reached relay	≥4/7 tested (majority) (≥4/7 DA)
Valid	Descriptor	Partial (1/8 DA)	1/8 authorities assigned Valid	Not blacklisted + valid descriptor (≥5/8 DA)
V2Dir	DirPort Available	Below (0/8 DA)	No DirPort, no tunnelled-dir-server (R)	Tunnelled directory via ORPort or DirPort (≥5/8 DA)
Fast	Speed	Meets (8/8 DA)	197.8 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: 101.2d (1/8 DA above threshold)	≥16.5d - 58.9d (varies) (≥5/8 DA)
Stable	Uptime	Meets (8/8 DA)	27.8d (R)	≥10.4d - 10.9d (varies) (≥5/8 DA)
HSDir	Prereq: Fast	Below (1/8 DA)	1/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 (1/8 DA)	1/8 DA assigned Stable	≥16.5d - 58.9d (varies) (≥5/8 DA)
	Prereq: V2Dir	Below (0/8 DA)	0/8 DA assigned V2Dir	Tunnelled directory via ORPort or DirPort (≥5/8 DA)
	WFU	Meets (1/8 DA)	Median: 99.8% (1/8 DA above threshold)	≥98.0% (≥5/8 DA)
	Time Known	Below (1/8 DA)	Median: 101.4d (1/8 DA above threshold)	≥1.0d (most) (≥5/8 DA) [Stricter] moria1: ≥9.8d
Guard	Prereq: Fast	Below (1/8 DA)	1/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 (1/8 DA)	1/8 DA assigned Stable	≥16.5d - 58.9d (varies) (≥5/8 DA)
	Prereq: V2Dir	Below (0/8 DA)	0/8 DA assigned V2Dir	Tunnelled directory via ORPort or DirPort (≥5/8 DA)
	WFU	Meets (1/8 DA)	Median: 99.8% (1/8 DA above threshold)	≥98% (≥5/8 DA)
	Time Known	Meets (1/8 DA)	Median: 101.4d (1/8 DA above threshold)	≥8 days (≥5/8 DA)
	Bandwidth	Meets (8/8 DA)	197.8 Mbit/s (R)	≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-328.0 Mbit/s (≥5/8 DA)
Exit	Exit Policy	Partial (1/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-29 12:45:03).

Bandwidth Metrics

Capacity (Relay Reported)

Observed Bandwidth: 197.79 Mbit/s
Advertised Bandwidth: 83.89 Mbit/s
Rate Limit: 83.89 Mbit/s
Burst Limit: 8.59 Gbit/s
Total Data: 491 TB (5 years)
1mo: 16 TB | 6mo: 109 TB | 1y: 243 TB | 5y: 491 TB

Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-04-29 12:45:03

Measured By: 0/5 Bandwidth Authorities
Not measured by: gabelmoo, longclaw, maatuska, moria1, tor26
Median Measurement: 80.0 Kbit/s
Min / Max: 80.0 Kbit/s / 80.0 Kbit/s

Network Participation: Consensus Weight: 0.0066% of network (55th pctl) | Guard: N/A | Middle: N/A | Exit: N/A

Uptime and Stability

Uptime Metrics

Current Status: DOWN 23h 46m 38s ago
Overall Uptime (1M/6M/1Y/5Y): 100.0%/97.9%/96.1%/97.9%
Flag Uptime (1M/6M/1Y/5Y): Matches Overall Uptime (100.0%/97.9%/96.1%/97.9%)
Hibernating: No

Timestamps

First Seen: 3w 1d 14h ago (2026-04-06 23:00:00)
Last Seen: 23h 46m 38s ago (2026-04-28 14:00:00)
Last Restarted: 3w 6d 19h ago (2026-04-01 18:43:00)
Last Changed Address: 2026-04-06 23:00:00

[Warning] OVERLOADED — Rate limits hit W:215 R:0 (limit: 84 Mbit/s)

General Overload (from /details)

Status: Not Reported

OOM killer, onionskin queue saturation, or TCP port exhaustion. Flag remains 72h after last event (Tor spec 328).

File Descriptor Exhaustion (from /bandwidth)

Status: Not Reported

Rate Limits (from /bandwidth)

Rate Limit: 83.89 Mbit/s
Burst Limit: 8.59 Gbit/s
Write Limit Hit: 215 times
Read Limit Hit: 0 times
Last Reported: 1 days ago

Recommendations

Consider increasing RelayBandwidthRate
Check if ISP is throttling traffic

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-04-29 05:00 UTC

AROI Domain (?): Not specified
Operator Validation: Unvalidated
This Relay: N/A (no AROI configured)
Contact: supermp3man@protonmail.com

Family Configuration

Family Support: None — No family membership configured

Happy Families (family-cert)

Effective Members: 0: none

MyFamily (legacy declarations)

Effective Member: 1

EE72F8544BC46F6FFCDB47CCDB954E5AC642756C (this relay)

Alleged Members: 0

none

Indirect Members: 0

none

Software and Version

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

Exit Health & Policy

DNS Health

Status: Not Tested

Source: exitdnshealth.1aeo.com

IPv4 Exit Policy Summary

IPv6 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 5.255.99.147:*
accept *:53
accept *:443
accept *:20-23
accept *:43
accept *:79-81
accept *:88
accept *:110
accept *:143
accept *:194
accept *:220
accept *:389
accept *:464-465
accept *:531
accept *:543-544
accept *:554
accept *:563
accept *:587
accept *:636
accept *:706
accept *:749
accept *:873
accept *:902-904
accept *:981
accept *:989-995
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 *:6697
accept *:8000
accept *:8008
accept *:8074
accept *:8080
accept *:8082
accept *:8087-8088
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 Wed, 29 Apr 2026 13:46:37 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-04-29 12: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	v6	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)	No	—	—	—	N	No	—	—	—	—	—	—	—	—	—	—	—	—
dizum (NL)	Yes	Yes	Yes	—	N	Yes	—	Valid, Fast, Stable, Exit	197.8 Mbit/s \| 816.0 Kbit/s	197.8 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	99.8% \| 98%	101.4d \| 8d	101.2d \| 42.5d	27.8d \| 10.4d	99.8% \| 98.0%	101.4d \| 1.0d	2026-04-28 09:43:32	80.0 Kbit/s
faravahar (US)	No	—	—	—	N	No	—	—	—	—	—	—	—	—	—	—	—	—
gabelmoo (DE)	No	—	—	—	Y	No	—	—	—	—	—	—	—	—	—	—	—	—
longclaw (US)	No	—	—	—	Y	No	—	—	—	—	—	—	—	—	—	—	—	—
maatuska (SE)	No	—	—	—	Y	No	—	—	—	—	—	—	—	—	—	—	—	—
moria1 (US)	No	—	—	—	Y	No	—	—	—	—	—	—	—	—	—	—	—	—
tor26 (AT)	No	—	—	—	Y	No	—	—	—	—	—	—	—	—	—	—	—	—

— = 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.