View Relay "DingBerry"

Fingerprint: `0AE156113CAF79C28EDF599F55FABDE03D5416DC` | Family: 1 relay | t(at)randomperson(dot)com | AS53667 | United States of America | Linux

Health Status

Consensus: Not In Consensus (2/9 Directory Auths, need 5)
Flags: Running, Valid, Stable (3)
BW Verified: 1/7 BW Auths Measured 160 Kbit/s Median
Stability: Not Overloaded | DOWN 6d 17h 45m ago | UP 77% (1M)

Reachability: IPv4: 2/9 | v6: 0/7 (Directory Auths)
First Seen: 1y 4mo 3w ago
BW Weight: 0.00% of Network | 679 Kbit/s Observed By Relay
Version: 0.4.9.6 Not Recommended

Issues Detected:

Not in consensus : Only 2/9 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 2/9 authorities can reach this relay
Suggestion: Authorities that cannot reach you: bastet, 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/7 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/
Not getting the Fast flag : Only 0/9 authorities vote Fast (5 needed). dannenberg measured this relay at 672.0 Kbit/s, below the Fast threshold (816.0 Kbit/s). dizum used the relay-reported 672.0 Kbit/s, below the Fast threshold (816.0 Kbit/s).
Suggestion: Fast requires a bandwidth in the top 7/8 of relays or at least AuthDirFastGuarantee (816.0 Kbit/s by default), judged by each authority. Authorities that have a bandwidth-scanner measurement of your relay judge by it, not by the bandwidth your relay reports. A low measurement means the scanners see your relay underperforming compared with other relays that report a similar speed. Clients only build circuits through Fast relays, so a relay near the threshold can gain and lose most of its traffic from one hourly consensus to the next.
Guard: requires Fast flag : Guard flag requires having the Fast flag first
Suggestion: Fast requires a bandwidth in the top 7/8 of relays or at least AuthDirFastGuarantee (816.0 Kbit/s by default), judged by each authority. Authorities that have a bandwidth-scanner measurement of your relay judge by it, not by the bandwidth your relay reports.
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 – 280.0 Mbit/s). dannenberg measured this relay at 672.0 Kbit/s. dizum used the relay-reported 672.0 Kbit/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: requires Fast flag : HSDir flag requires having the Fast flag first
Suggestion: Fast requires a bandwidth in the top 7/8 of relays or at least AuthDirFastGuarantee (816.0 Kbit/s by default), judged by each authority. Authorities that have a bandwidth-scanner measurement of your relay judge by it, not by the bandwidth your relay reports.
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 1/7 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.9.6 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: 198.98.61.60:9001

Reachability (Directory Authorities)

IPv4: 2/9
IPv6: 0/7 (2 don't test)

Location

Country: United States of America
Interactive Map: View in RouteFluxMap

Autonomous System

AS Number: AS53667
AS Name: FranTech Solutions (BGP.tools)
AS Rarity: Emerging (score: 1/5, 1.48% consensus weight, 54 operators)

Flags and Eligibility

Current Flags (3): Running, Valid, Stable

Eligibility Flag Vote Details

Flag	Metric	Status	Relay Value	Threshold Required
Running	IPv4 Reachability	Below (2/9 DA)	2/9 authorities reached relay	≥5/9 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 (2/9 DA)	2/9 authorities assigned Valid	Not blacklisted + valid descriptor (≥5/9 DA)
V2Dir	DirPort Available	Below (1/9 DA)	No DirPort, no tunnelled-dir-server (R)	Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Fast	Speed	Below (0/9 DA)	672.0 Kbit/s (1 DA measured) 672.0 Kbit/s (1 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	Below (2/9 DA)	Median: 19.9d (2/9 DA above threshold) Min/Max: 18.7d / 21.1d (2/9 DA, Voting / Total Eligible)	≥5.1d - 10.9d (varies) (≥5/9 DA) [Stricter] moria1: ≥8990.4d
Stable	Uptime	Meets (9/9 DA)	5.3d (R)	≥3.2d - 3.2d (varies) (≥5/9 DA)
HSDir	Prereq: Fast	Below (0/9 DA)	0/9 DA assigned Fast 672.0 Kbit/s (1 DA measured) 672.0 Kbit/s (1 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	Below (2/9 DA)	2/9 DA assigned Stable	≥5.1d - 10.9d (varies) (≥5/9 DA) [Stricter] moria1: ≥8990.4d
	Prereq: V2Dir	Below (1/9 DA)	1/9 DA assigned V2Dir	Tunnelled directory via ORPort or DirPort (≥5/9 DA)
	WFU	Meets (2/9 DA)	Median: 100.0% (2/9 DA above threshold) Min/Max: 99.9% / 100.0% (2/9 DA, Voting / Total Eligible)	≥98.0% (≥5/9 DA)
	Time Known	Below (2/9 DA)	Median: 24.7d (2/9 DA above threshold) Min/Max: 24.3d / 25.0d (2/9 DA, Voting / Total Eligible)	≥1.0d (most) (≥5/9 DA) [Stricter] moria1: ≥10.0d
Guard	Prereq: Fast	Below (0/9 DA)	0/9 DA assigned Fast 672.0 Kbit/s (1 DA measured) 672.0 Kbit/s (1 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	Below (2/9 DA)	2/9 DA assigned Stable	≥5.1d - 10.9d (varies) (≥5/9 DA) [Stricter] moria1: ≥8990.4d
	Prereq: V2Dir	Below (1/9 DA)	1/9 DA assigned V2Dir	Tunnelled directory via ORPort or DirPort (≥5/9 DA)
	WFU	Meets (2/9 DA)	Median: 100.0% (2/9 DA above threshold) Min/Max: 99.9% / 100.0% (2/9 DA, Voting / Total Eligible)	≥98% (≥5/9 DA)
	Time Known	Meets (2/9 DA)	Median: 24.7d (2/9 DA above threshold) Min/Max: 24.3d / 25.0d (2/9 DA, Voting / Total Eligible)	≥8 days (≥5/9 DA)
	Bandwidth	Below (0/9 DA)	672.0 Kbit/s (1 DA measured) 672.0 Kbit/s (1 DA relay-reported)	≥16.8 Mbit/s (AuthDirGuardBWGuarantee) OR top 25% (≥80.0 Mbit/s-280.0 Mbit/s) (≥5/9 DA)
Exit	Exit Policy	Partial (1/9 DA)	Port 80: Yes \| Port 443: Yes (R)	Allows ≥1 /8 on ports 80 AND 443 (≥5/9 DA)
MiddleOnly	Restriction (by DA)	Flagged (1/9 DA)	1/9 authorities assigned MiddleOnly	Suspicious behavior, Sybil risk, or policy violation

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

Bandwidth Metrics

Capacity (Relay Reported)

Observed Bandwidth: 679.94 Kbit/s
Advertised Bandwidth: 679.94 Kbit/s
Rate Limit: 6.29 Mbit/s
Burst Limit: 8.39 Mbit/s
Total Data: 11 TB (5 years)
1mo: 2.6 TB | 6mo: 6.1 TB | 1y: 7.3 TB | 5y: 11 TB

Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-10-12 09:45:05

Measured By: 1/7 Bandwidth Authorities
Not measured by: bastet, faravahar, gabelmoo, longclaw, moria1, tor26
Consensus Weight: 160.0 Kbit/s (Unmeasured)
Measured Min / Max: 672.0 Kbit/s / 672.0 Kbit/s

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

Uptime and Stability

Uptime Metrics

Current Status: DOWN 6d 17h 45m ago
Overall Uptime (1M/6M/1Y/5Y): 77.8%/84.4%/62.1%/74.1%
Flag Uptime (1M/6M/1Y/5Y): Matches Overall Uptime (77.8%/84.4%/62.1%/74.1%)
Hibernating: No

Timestamps

First Seen: 1y 4mo 3w ago (2025-05-17 12:00:00)
Last Seen: 6d 17h 45m ago (2026-10-05 16:00:00)
Last Restarted: 5d 6h 3m ago (2026-10-07 03:41:43)
Last Changed Address: 2026-05-03 17:00:00

Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-10-12 02:00 UTC

AROI Domain (?): Not specified
Operator Validation: Unvalidated
This Relay: N/A (no AROI configured)
Contact: t(at)randomperson(dot)com

Family Configuration

Family Support: None — No family membership configured

Happy Families (family-cert)

Effective Members: 0: none

MyFamily (legacy declarations)

Effective Member: 1

0AE156113CAF79C28EDF599F55FABDE03D5416DC (this relay)

Alleged Members: 0

none

Indirect Members: 0

none

Software and Version

Platform: Linux — Tor 0.4.9.13 on Linux
Version: 0.4.9.6 — 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

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 198.98.61.60:*
reject *:25
reject *:465
reject *:587
reject *:993
reject *:995
reject *:119
reject *:135-139
reject *:445
reject *:563
reject *:1214
reject *:4661-4666
reject *:6346-6429
reject *:6699
reject *:6881-6999
accept *:*

Last fetch was at Mon, 12 Oct 2026 09:45:19 GMT.

Consensus Evaluation

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

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)	HSDir WFU (M\|T)	HSDir TK (M\|T)	Desc Published	Cons Wt (Authority)
bastet (US)	No	—	—	—	Y	No	—	—	—	—	—	—	—	—	—	—	—	—
dannenberg (DE)	Yes	Yes	No	Yes	Y	Yes	—	Running, Valid, Stable, MiddleOnly	672.0 Kbit/s (M) \| 816.0 Kbit/s	672.0 Kbit/s (M) \| 280.0 Mbit/s OR 16.8 Mbit/s	99.9% \| 98%	24.3d \| 8d	18.7d \| 5.1d	5.3d \| 3.2d	99.9% \| 98.0%	24.3d \| 1.0d	2026-10-12 07:50:59	672.0 Kbit/s (R)
dizum (NL)	Yes	Yes	Yes	—	N	Yes	—	Running, Valid, V2Dir, Stable, Exit	672.0 Kbit/s (R) \| 816.0 Kbit/s	672.0 Kbit/s (R) \| 80.0 Mbit/s OR 16.8 Mbit/s	100.0% \| 98%	25.0d \| 8d	21.1d \| 10.9d	5.3d \| 3.2d	100.0% \| 98.0%	25.0d \| 1.0d	2026-10-12 07:50:59	672.0 Kbit/s (R)
faravahar (US)	No	—	—	—	Y	No	—	—	—	—	—	—	—	—	—	—	—	—
gabelmoo (DE)	No	—	—	—	Y	No	—	—	—	—	—	—	—	—	—	—	—	—
longclaw (US)	No	—	—	—	Y	No	—	—	—	—	—	—	—	—	—	—	—	—
maatuska (SE)	No	—	—	—	N	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 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.