View Relay "PrincessPeach"

Fingerprint: C54B65B26EDCFF7695665F85B869CE472F0EA893 | Operator: tor-exit.goodpuppy.space v3 (5 relays) ✓ Validated | Family: 5 relays | email:tor-exit@goodpuppy.space... | AS33915 | Netherlands | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, Valid, V2Dir, Fast (4)
BW Verified
6/7 BW Auths Measured 44 Kbit/s Median
Stability
Overloaded | UP 1d 22h 14m ago | UP 79% (1M)
Reachability
IPv4: 9/9 | v6: 8/8 (Directory Auths)
First Seen
2mo 2w 4d ago
BW Weight
0.00% of Network | 52 Mbit/s Observed By Relay
Version
0.4.9.8 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: WFU below threshold : Weighted Fractional Uptime 77.8% is below 98% requirement
    Suggestion: WFU measures recent uptime (recent downtime weighs more heavily). To improve: 1) Minimize restarts, 2) Use systemd with Restart=always, 3) Monitor for OOM kills, 4) Schedule updates during low-traffic periods.
  • 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.
  • HSDir: WFU below threshold : WFU 77.8% below 98% required for HSDir
    Suggestion: HSDir requires ≥98% WFU, Stable flag, and Time Known ≥25 hours (or ~10 days for moria1). Improve uptime consistency.
  • Write Bandwidth Limit Hit : Write rate limit (50 Mbit/s) was hit 7 times. Relay is throttling outbound traffic.
    Suggestion: Increase RelayBandwidthRate and RelayBandwidthBurst in torrc if your connection has more upload capacity.
  • Read Bandwidth Limit Hit : Read rate limit (50 Mbit/s) was hit 7 times. Relay is throttling inbound traffic.
    Suggestion: Increase RelayBandwidthRate and RelayBandwidthBurst in torrc if your connection has more download capacity.
Notes:
  • Rate Limit Configuration: Configured limits: Rate=50 Mbit/s, Burst=101 Mbit/s. Limits hit: Write=7, Read=7.

Connectivity and Location

Addresses
OR Address
178-85-139-57.dynamic.upc.nl
178.85.139.57:33880
[2001:1c00:5608:bc00::b362]:33880
Reachability (Directory Authorities)
IPv4
9/9
IPv6
8/8 (1 don't test)
Location
Country
Netherlands Netherlands
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS33915
AS Name
Vodafone Libertel B.V. (BGP.tools)
AS Rarity
Epic (score: 3/5, 0.05% consensus weight, 15 operators)

Flags and Eligibility

Current Flags (4): Running, Valid, V2Dir, Fast
Eligible Flags (4): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 9/9 | Stable: 1/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
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 Meets (9/9 DA) 52.6 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 (1/9 DA) Median: 3.4d (1/9 DA above threshold)
Min/Max: 2.5d / 13257.9d (9/9 DA, Voting / Total Eligible)		 ≥21.2d - 51.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥340.7d
Uptime Below (0/9 DA) 1.9d (R) ≥13.4d - 13.7d (varies) (≥5/9 DA)
HSDir Prereq: Fast Meets (9/9 DA) 9/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 (1/9 DA) 1/9 DA assigned Stable ≥21.2d - 51.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥340.7d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Below (0/9 DA) Median: 77.8% (0/9 DA above threshold)
Min/Max: 74.8% / 78.3% (9/9 DA, Voting / Total Eligible)		 ≥98.0% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 12.4d (9/9 DA above threshold)
Min/Max: 10.0d / 12.6d (9/9 DA, Voting / Total Eligible)		 ≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.9d
Guard Prereq: Fast Meets (9/9 DA) 9/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 (1/9 DA) 1/9 DA assigned Stable ≥21.2d - 51.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥340.7d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Below (0/9 DA) Median: 77.8% (0/9 DA above threshold)
Min/Max: 74.8% / 78.3% (9/9 DA, Voting / Total Eligible)		 ≥98% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 12.4d (9/9 DA above threshold)
Min/Max: 10.0d / 12.6d (9/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Meets (9/9 DA) 52.6 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-328.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-05-27 10:15:07).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
52.57 Mbit/s
Advertised Bandwidth
41.94 Mbit/s
Rate Limit
41.94 Mbit/s
Burst Limit
100.66 Mbit/s
Total Data
21 TB (6 months)
1mo: 7.2 TB | 6mo: 21 TB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-05-27 10:15:07

Measured By
6/7 Bandwidth Authorities
Not measured by: dannenberg
Median Measurement
44.8 Kbit/s
Min / Max
41.6 Kbit/s / 63.2 Kbit/s
Network Participation: Consensus Weight: 0.0032% of network (41th pctl) | Guard: N/A | Middle: 0.0097% (68th pctl) | Exit: N/A

Uptime and Stability

Uptime Metrics
Current Status
UP 1d 22h 14m ago
Overall Uptime (1M/6M/1Y/5Y)
79.4%/86.0%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
—/85.7%/—/—
Hibernating
No
Timestamps
First Seen
2mo 2w 4d ago (2026-03-09 18:00:00)
Last Seen
1h 15m 38s ago (2026-05-27 09:00:00)
Last Restarted
1d 22h 14m ago (2026-05-25 12:01:17)
Last Changed Address
2026-05-25 13:00:00
[Warning] OVERLOADED — Rate limits hit W:7 R:7 (limit: 50 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
50.33 Mbit/s
Burst Limit
100.66 Mbit/s
Write Limit Hit
7 times
Read Limit Hit
7 times
Last Reported
21 hours ago
Recommendations
  • Consider increasing RelayBandwidthRate
  • Check if ISP is throttling traffic

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-05-27 03:00 UTC

AROI Domain (?)
tor-exit.goodpuppy.space
Operator Validation
Validated (5/5 relays)
This Relay
Validated (uri-familyid-ed25519)
Contact
email:tor-exit@goodpuppy.space url:https://tor-exit.goodpuppy.space proof:uri-familyid-ed25519 dnslocation:local dnsqname:y dnssec:y ciissversion:3
Family Configuration
Family Support
Happy Families (5) — Has family-cert in server descriptor (guide) | View Full Family (5)
MyFamily (legacy declarations) — none

Software and Version

Platform
Linux — Tor 0.4.9.8 on Linux
Version
0.4.9.8 — 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, 27 May 2026 10:15:37 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-05-27 10:15:07).

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) Yes Yes No — Y Yes Yes Running, Valid, V2Dir, Fast 52.6 Mbit/s | 816.0 Kbit/s 52.6 Mbit/s | 224.0 Mbit/s OR 16.0 Mbit/s 77.8% | 98% 12.6d | 8d 3.5d | 50.5d 1.9d | 13.4d 77.8% | 98.0% 12.6d | 1.0d 2026-05-27 00:02:25 49.6 Kbit/s
dannenberg (DE) Yes Yes No — Y Yes Yes Running, Valid, V2Dir, Fast 52.6 Mbit/s | 816.0 Kbit/s 52.6 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 78.0% | 98% 12.4d | 8d 3.2d | 46.6d 1.9d | 13.7d 78.0% | 98.0% 12.4d | 1.0d 2026-05-27 00:02:25 41.9 Kbit/s
dizum (NL) Yes Yes No — N Yes Yes Running, Valid, V2Dir, Fast 52.6 Mbit/s | 816.0 Kbit/s 52.6 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 77.6% | 98% 12.5d | 8d 3.6d | 21.2d 1.9d | 13.7d 77.6% | 98.0% 12.5d | 1.0d 2026-05-27 00:02:25 41.9 Kbit/s
faravahar (US) Yes Yes No — N Yes Yes Running, Valid, V2Dir, Fast 52.6 Mbit/s | 816.0 Kbit/s 52.6 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 78.2% | 98% 12.4d | 8d 3.4d | 51.7d 1.9d | 13.7d 78.2% | 98.0% 12.4d | 1.0d 2026-05-27 00:02:25 41.9 Kbit/s
gabelmoo (DE) Yes Yes No — Y Yes Yes Running, Valid, V2Dir, Fast 52.6 Mbit/s | 816.0 Kbit/s 52.6 Mbit/s | 312.0 Mbit/s OR 16.0 Mbit/s 77.7% | 98% 12.6d | 8d 3.2d | 53.0d 1.9d | 13.8d 77.7% | 98.0% 12.6d | 1.0d 2026-05-27 00:02:25 49.6 Kbit/s
longclaw (US) Yes Yes No — Y Yes — Running, Valid, V2Dir, Fast 52.6 Mbit/s | 816.0 Kbit/s 52.6 Mbit/s | 248.0 Mbit/s OR 16.0 Mbit/s 78.3% | 98% 12.5d | 8d 3.8d | 58.0d 1.9d | 13.7d 78.3% | 98.0% 12.5d | 1.0d 2026-05-27 00:02:25 41.6 Kbit/s
maatuska (SE) Yes Yes No — Y Yes Yes Running, Valid, V2Dir, Fast 52.6 Mbit/s | 816.0 Kbit/s 52.6 Mbit/s | 328.0 Mbit/s OR 16.0 Mbit/s 77.1% | 98% 11.8d | 8d 2.5d | 24.6d 1.9d | 13.5d 77.1% | 98.0% 11.8d | 1.0d 2026-05-27 00:02:25 44.8 Kbit/s
moria1 (US) Yes Yes No — Y Yes Yes Running, Valid, V2Dir, Fast, Stable 52.6 Mbit/s | 8.4 Mbit/s 52.6 Mbit/s | 232.0 Mbit/s OR 16.0 Mbit/s 74.8% | 98% 10.0d | 8d 13257.9d | 340.7d 1.9d | 14.2d 74.8% | 98.0% 10.0d | 9.9d 2026-05-27 00:02:25 63.2 Kbit/s
tor26 (AT) Yes Yes No — Y Yes Yes Running, Valid, V2Dir, Fast 52.6 Mbit/s | 816.0 Kbit/s 52.6 Mbit/s | 312.0 Mbit/s OR 16.0 Mbit/s 78.0% | 98% 12.4d | 8d 3.2d | 54.0d 1.9d | 13.8d 78.0% | 98.0% 12.4d | 1.0d 2026-05-27 00:02:25 54.4 Kbit/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.