View Relay "mcdonald"
Fingerprint: BDE695953B5D8BAB45691E9A754340112C18FEA5 |
Family: 2 relays
|
nico@pfcloud.io |
AS51396
|
Netherlands
|
Linux
- Consensus
- In Consensus (8/9 Directory Auths)
- DNS Health
- Not Tested (via exitdnshealth.1aeo.com)
- BW Verified
- 3/7 BW Auths Measured 272 Mbit/s Median
- Stability
- Incomplete | UP 3h 33m 31s ago
- Reachability
- IPv4: 8/9 | v6: None configured(Directory Auths)
- BW Weight
- 0.02% of Network | 0 Kbit/s Observed By Relay
- Version
- 0.4.9.6 Not Recommended
Issues Detected:
-
Not getting the Fast flag
: Only 3/9 authorities vote Fast (5 needed). dizum, faravahar, longclaw and maatuska used the relay-reported unknown, below the Fast threshold (816.0 Kbit/s). moria1 counted this relay as 0 (no measurement, relay-reported bandwidth ignored).
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: 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
: 3/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). dizum, faravahar, longclaw and maatuska used the relay-reported unknown. moria1 counted this relay as 0 (no measurement, relay-reported bandwidth ignored).
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. -
Guard: WFU below threshold
: 0/9 authorities meet guard-wfu (≥98%; 5 needed). moria1 measured 0% (no uptime history for this relay). dannenberg, dizum, faravahar, gabelmoo, longclaw, maatuska and tor26 measured 19.6%–20.2%.
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
: 0/9 authorities meet Stable (uptime or MTBF at or above their own median; 5 needed). dannenberg, dizum, faravahar, gabelmoo, longclaw, maatuska, moria1 and tor26 do not.
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 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 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. -
BadExit flag assigned
: This relay has been flagged as a bad exit by directory authorities. BadExit means authorities detected malicious behavior (traffic modification, SSL stripping, etc.).
Suggestion: Contact bad-relays@lists.torproject.org to understand and resolve this issue. -
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.
Notes:
- Partial IPv4 reachability: 8/9 authorities can reach this relay
Suggestion: Some authorities cannot reach you: bastet. This may be temporary or due to geographic routing issues. - Bandwidth authority measurements below majority: 3/7 bandwidth authorities measured this relay (majority is 4).
Suggestion: Some bandwidth authorities cannot measure your relay. This may be temporary or due to geographic routing. Monitor over 24-48 hours. If persistent, check firewall rules and ensure ORPort is accessible from various locations.
Addresses
- OR Address
-
176.65.149.105.ptr.pfcloud.network
176.65.149.105:12040
Reachability (Directory Authorities)
- IPv4
- 8/9
- IPv6
- None configured
Location
- Country
-
Netherlands
- Interactive Map
- View in RouteFluxMap
Eligible Flags (4):
Running: 8/9 | Valid: 8/9 | V2Dir: 8/9 | Fast: 3/9 | Stable: 0/9 | HSDir: 0/9 | Guard: 0/9 | Exit: 8/9
Eligibility Flag Vote Details
| Flag | Metric | Status | Relay Value | Threshold Required |
|---|---|---|---|---|
| Running | IPv4 Reachability | Meets (8/9 DA) | 8/9 authorities reached relay | ≥5/9 DA ORPort reachable |
| Valid | Descriptor | Meets (8/9 DA) | 8/9 authorities assigned Valid | Not blacklisted + valid descriptor (≥5/9 DA) |
| V2Dir | DirPort Available | Meets (8/9 DA) | Tunnelled: Yes (no DirPort) (R) | Tunnelled directory via ORPort or DirPort (≥5/9 DA) |
| Fast | Speed | Below (3/9 DA) | 160.0 Mbit/s – 328.0 Mbit/s (3 DA measured) 0 bit/s (4 DA relay-reported) 0 bit/s (1 DA unmeasured, counted as 0) |
≥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 (0/9 DA) | Median: 2.2d (0/9 DA above threshold) Min/Max: 0.0d / 2.2d (8/9 DA, Voting / Total Eligible) |
≥3.3d - 11.4d (varies) (≥5/9 DA) [Stricter] moria1: ≥6459.8d |
| Uptime | Below (0/9 DA) | 0.1d (R) | ≥3.5d - 3.5d (varies) (≥5/9 DA) | |
| HSDir | Prereq: Fast | Below (3/9 DA) | 3/9 DA assigned Fast 160.0 Mbit/s – 328.0 Mbit/s (3 DA measured) 0 bit/s (4 DA relay-reported) 0 bit/s (1 DA unmeasured, counted as 0) |
≥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 (0/9 DA) | 0/9 DA assigned Stable | ≥3.3d - 11.4d (varies) (≥5/9 DA) [Stricter] moria1: ≥6459.8d |
|
| Prereq: V2Dir | Meets (8/9 DA) | 8/9 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥5/9 DA) | |
| Uptime | Below (0/9 DA) | 0.1d (R) | ≥96h as each authority sees it (MinUptimeHidServDirectoryV2) (≥5/9 DA) [Stricter] moria1: ≥98% WFU and ≥9.8d Time Known |
|
| Guard | Prereq: Fast | Below (3/9 DA) | 3/9 DA assigned Fast 160.0 Mbit/s – 328.0 Mbit/s (3 DA measured) 0 bit/s (4 DA relay-reported) 0 bit/s (1 DA unmeasured, counted as 0) |
≥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 (0/9 DA) | 0/9 DA assigned Stable | ≥3.3d - 11.4d (varies) (≥5/9 DA) [Stricter] moria1: ≥6459.8d |
|
| Prereq: V2Dir | Meets (8/9 DA) | 8/9 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥5/9 DA) | |
| WFU | Below (0/9 DA) | Median: 19.8% (0/9 DA above threshold) Min/Max: 0.0% / 20.2% (8/9 DA, Voting / Total Eligible) |
≥98% (≥5/9 DA) | |
| Time Known | Partial (7/9 DA) | Median: 16.9d (7/9 DA above threshold) Min/Max: 0.0d / 17.2d (8/9 DA, Voting / Total Eligible) |
≥8 days (≥5/9 DA) | |
| Bandwidth | Below (3/9 DA) | 160.0 Mbit/s – 328.0 Mbit/s (3 DA measured) 0 bit/s (4 DA relay-reported) 0 bit/s (1 DA unmeasured, counted as 0) |
≥16.8 Mbit/s (AuthDirGuardBWGuarantee) OR top 25% (≥80.0 Mbit/s-272.0 Mbit/s) (≥5/9 DA) | |
| Exit | Exit Policy | Meets (8/9 DA) | Port 80: Yes | Port 443: Yes (R) | Allows ≥1 /8 on ports 80 AND 443 (≥5/9 DA) |
| BadExit | Restriction (by DA) | Flagged (5/9 DA) | 5/9 authorities assigned BadExit | Exit traffic manipulation, SSL stripping, or policy violation |
(DA) = Dir. Auth. Measured |
(R) = Relay Reported
Data from Tor CollecTor (authority votes, fetched 2026-11-08 16:45:06).
Capacity (Relay Reported)
- Observed Bandwidth
- 0.00 Kbit/s
- Advertised Bandwidth
- Unknown
- Rate Limit
- 8.59 Gbit/s
- Burst Limit
- 8.59 Gbit/s
- Total Data
- N/A
Measurement (Directory Authority Verified)
Source: CollecTor — fetched 2026-11-08 16:45:06
- Measured By
-
3/7
Bandwidth Authorities
Not measured by: bastet, faravahar, longclaw, moria1 - Consensus Weight
- 272.0 Mbit/s (median of 3 measurements)
- Measured Min / Max
- 160.0 Mbit/s / 328.0 Mbit/s
- Deviation
- 168.0 Mbit/s [Warning] High variation
Network Participation:
Consensus Weight:
0.0176% of network
(79th pctl)
|
Guard:
N/A |
Middle:
0.0523% (93th pctl) |
Exit:
N/A
Uptime Metrics
- Current Status
- UP 3h 33m 31s ago
- Overall Uptime (1M/6M/1Y/5Y)
- 0.0%/0.0%/0.0%/0.0%
- Flag Uptime (1M/6M/1Y/5Y)
- N/A
- Hibernating
- No
Timestamps
- First Seen
- 3h 15m 38s ago (2026-11-08 14:00:00)
- Last Seen
- 1h 15m 38s ago (2026-11-08 16:00:00)
- Last Restarted
- 3h 33m 31s ago (2026-11-08 13:42:07)
- Last Changed Address
- 2026-11-08 14:00:00
Overload status:
Incomplete — not every signal could be evaluated.
(No bandwidth record available for this relay)
Evaluated 2026-11-08 17:15 UTC. /details snapshot 2026-11-08 16:00:00 UTC (cached 34s ago). /bandwidth snapshot 2026-11-08 11:00:00 UTC (cached 5h ago).
General Overload (from /details)
- Status
- No general overload report in available data
File Descriptor Exhaustion (from /bandwidth)
- Status
- No bandwidth record available for this relay
Rate Limits (from /bandwidth)
- Status
- No bandwidth record available for this relay
- 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
Operator Identity
Source: AROI Validation API — 2026-11-08 07:00 UTC
- AROI Domain (?)
- Not specified
- Operator Validation
- Unvalidated
- This Relay
- N/A (no AROI configured)
- Contact
- nico@pfcloud.io
Family Configuration
- Family Support
- MyFamily Only (2) — Legacy only. Consider migrating to Happy Families. | View Full Family (2)
Happy Families (family-cert)
- Effective Members: 0
- none
MyFamily (legacy declarations)
- Effective Members: 2
BDE695953B5D8BAB45691E9A754340112C18FEA5 (this relay) E3919227ADC9DF4DE451740AB93C22DF96FFD5A0
- Alleged Members: 0
- none
- Indirect Members: 0
- none
- Platform
- Linux — Tor 0.4.9.6 on Linux
- Version
- 0.4.9.6 — Not Recommended
- Version Status
- Obsolete — Update urgently. See torproject.org/download
IPv4 Exit Policy Summary
reject: 25 194 465 587 994 6657 6660-6670 6697 7000-7005 7070 8000-8004 9000-9001 9998-9999
IPv6 Exit Policy Summary
NoneFull 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 176.65.149.105:* reject *:25 reject *:194 reject *:465 reject *:587 reject *:994 reject *:6657 reject *:6660 reject *:6661 reject *:6662 reject *:6663 reject *:6664 reject *:6665 reject *:6666 reject *:6667 reject *:6668 reject *:6669 reject *:6670 reject *:6697 reject *:7000 reject *:7001 reject *:7002 reject *:7003 reject *:7004 reject *:7005 reject *:7070 reject *:8000 reject *:8001 reject *:8002 reject *:8003 reject *:8004 reject *:9000 reject *:9001 reject *:9998 reject *:9999 accept *:*
Last fetch was at Sun, 08 Nov 2026 17:15:37 GMT.
Data from Tor CollecTor (authority votes, fetched 2026-11-08 16:45:06).
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 (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) | No | — | — | — | Y | No | — | — | — | — | — | — | — | — | — |
| dannenberg (DE) | Yes | Yes | Yes | — | Y | Yes | Running, Valid, V2Dir, Fast, Exit | 160.0 Mbit/s (M) | 816.0 Kbit/s | 160.0 Mbit/s (M) | 272.0 Mbit/s OR 16.8 Mbit/s | 19.7% | 98% | 17.2d | 8d | 2.2d | 11.4d | 0.1d | 3.6d | 2026-11-08 13:42:37 | 160.0 Mbit/s (M) |
| dizum (NL) | Yes | Yes | Yes | — | N | Yes | Running, Valid, V2Dir, Exit | 0 bit/s (R) | 816.0 Kbit/s | 0 bit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 19.6% | 98% | 17.2d | 8d | 2.2d | 8.8d | 0.1d | 3.5d | 2026-11-08 13:42:37 | — |
| faravahar (US) | Yes | Yes | Yes | — | Y | Yes | Running, Valid, V2Dir, Exit, BadExit | 0 bit/s (R) | 816.0 Kbit/s | 0 bit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 20.1% | 98% | 16.6d | 8d | 2.1d | 8.3d | 0.1d | 3.5d | 2026-11-08 13:42:37 | — |
| gabelmoo (DE) | Yes | Yes | Yes | — | Y | Yes | Running, Valid, V2Dir, Fast, Exit, BadExit | 272.0 Mbit/s (M) | 816.0 Kbit/s | 272.0 Mbit/s (M) | 248.0 Mbit/s OR 16.8 Mbit/s | 19.7% | 98% | 17.2d | 8d | 2.2d | 13.1d | 0.1d | 3.5d | 2026-11-08 13:42:37 | 272.0 Mbit/s (M) |
| longclaw (US) | Yes | Yes | Yes | — | Y | Yes | Running, Valid, V2Dir, Exit, BadExit | 0 bit/s (R) | 816.0 Kbit/s | 0 bit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 20.1% | 98% | 16.6d | 8d | 2.2d | 13.3d | 0.1d | 3.5d | 2026-11-08 13:42:37 | — |
| maatuska (SE) | Yes | Yes | Yes | — | N | Yes | Running, Valid, V2Dir, Exit | 0 bit/s (R) | 816.0 Kbit/s | 0 bit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 20.0% | 98% | 17.1d | 8d | 2.2d | 3.3d | 0.1d | 3.5d | 2026-11-08 13:42:37 | — |
| moria1 (US) | Yes | Yes | Yes | — | Y | Yes | Valid, V2Dir, Exit, BadExit | 0 bit/s (U) | 8.4 Mbit/s | 0 bit/s (U) | 184.0 Mbit/s OR 16.8 Mbit/s | 0.0% | 98% | 0.0d | 8d | 0.0d | 6459.8d | 0.1d | 3.5d | 2026-11-08 13:42:37 | — |
| tor26 (AT) | Yes | Yes | Yes | — | Y | Yes | Running, Valid, V2Dir, Fast, Exit, BadExit | 328.0 Mbit/s (M) | 816.0 Kbit/s | 328.0 Mbit/s (M) | 256.0 Mbit/s OR 16.8 Mbit/s | 20.2% | 98% | 16.6d | 8d | 2.2d | 13.1d | 0.1d | 3.6d | 2026-11-08 13:42:37 | 328.0 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 (
Relay-reported (R) = The bandwidth your relay advertises: the lower of its observed bandwidth and its rate limit, capped at 10 MB/s (
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.
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.
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.