View Relay "fumo"
Fingerprint: CA57276E7F354AB94BFDEE0CFDA8AE6201BDDED9 |
Family: 7 relays
|
fumonion [] protonmail (dot) com |
AS44382
|
Turkey
|
Linux
- Consensus
- In Consensus (9/9 Directory Auths)
- DNS Health
- Healthy (15.0s, 47th percentile) (via exitdnshealth.1aeo.com)
- BW Verified
- 5/7 BW Auths Measured 13 Mbit/s Median
- Stability
- Not Overloaded | UP 6d 14h 53m ago | UP 99% (1M)
- Reachability
- IPv4: 9/9 | v6: 8/8(Directory Auths)
- BW Weight
- 0.00% of Network | 25 Mbit/s Observed By Relay
- Version
- 0.4.9.15 Recommended
Issues Detected:
-
Guard: WFU below threshold
: 4/9 authorities meet guard-wfu (≥98%; dizum: ≥97.879%; 5 needed). bastet, dizum, gabelmoo, moria1 and tor26 measured 77.1%–96.5%.
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. -
HSDir: uptime below 96 hours
: Only 4/9 authorities voted HSDir, though this relay has Fast, Stable and V2Dir
Suggestion: HSDir needs 96 hours of uptime as each authority sees it (MinUptimeHidServDirectoryV2): the time since your relay restarted, or since that authority last failed to reach it if that is shorter. Keep the relay running and reachable. -
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.
Addresses
- OR Address
-
203.202.232.160:443
[2602:fa5d::38c]:443 - Exit Address
- 203.202.232.160
Reachability (Directory Authorities)
- IPv4
- 9/9
- IPv6
- 8/8 (1 don't test)
Location
- Country
-
Turkey
- Interactive Map
- View in RouteFluxMap
Eligible Flags (6):
Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 9/9 | Stable: 5/9 | HSDir: 4/9 | Guard: 2/9 | Exit: 9/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) | 12.0 Mbit/s – 52.8 Mbit/s (5 DA measured) 25.2 Mbit/s (4 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 (3/9 DA) | Median: 7.2d (3/9 DA above threshold) Min/Max: 0.2d / 20756.2d (9/9 DA, Voting / Total Eligible) |
≥2.4d - 9.5d (varies) (≥5/9 DA) [Stricter] moria1: ≥7613.3d |
| Uptime | Meets (9/9 DA) | 6.6d (R) | ≥5.2d - 5.5d (varies) (≥5/9 DA) | |
| HSDir | Prereq: Fast | Meets (9/9 DA) | 9/9 DA assigned Fast 12.0 Mbit/s – 52.8 Mbit/s (5 DA measured) 25.2 Mbit/s (4 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 | Meets (5/9 DA) | 5/9 DA assigned Stable | ≥2.4d - 9.5d (varies) (≥5/9 DA) [Stricter] moria1: ≥7613.3d |
|
| Prereq: V2Dir | Meets (9/9 DA) | 9/9 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥5/9 DA) | |
| Uptime | Partial (8/9 DA) | 6.6d (R) | ≥96h as each authority sees it (MinUptimeHidServDirectoryV2) (≥5/9 DA) [Stricter] moria1: ≥98% WFU and ≥9.9d Time Known |
|
| Guard | Prereq: Fast | Meets (9/9 DA) | 9/9 DA assigned Fast 12.0 Mbit/s – 52.8 Mbit/s (5 DA measured) 25.2 Mbit/s (4 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 | Meets (5/9 DA) | 5/9 DA assigned Stable | ≥2.4d - 9.5d (varies) (≥5/9 DA) [Stricter] moria1: ≥7613.3d |
|
| Prereq: V2Dir | Meets (9/9 DA) | 9/9 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥5/9 DA) | |
| WFU | Below (4/9 DA) | Median: 96.5% (4/9 DA above threshold) Min/Max: 77.1% / 99.7% (9/9 DA, Voting / Total Eligible) |
≥98%; dizum: ≥97.879% (≥5/9 DA) | |
| Time Known | Meets (9/9 DA) | Median: 14.9d (9/9 DA above threshold) Min/Max: 9.9d / 18.0d (9/9 DA, Voting / Total Eligible) |
≥8 days (≥5/9 DA) | |
| Bandwidth | Partial (6/9 DA) | 12.0 Mbit/s – 52.8 Mbit/s (5 DA measured) 25.2 Mbit/s (4 DA relay-reported) |
≥16.8 Mbit/s (AuthDirGuardBWGuarantee) OR top 25% (≥80.0 Mbit/s-272.0 Mbit/s) (≥5/9 DA) | |
| Exit | Exit Policy | Meets (9/9 DA) | Port 80: Yes | Port 443: Yes (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-11-04 20:15:05).
Capacity (Relay Reported)
- Observed Bandwidth
- 25.25 Mbit/s
- Advertised Bandwidth
- 25.25 Mbit/s
- Rate Limit
- 8.59 Gbit/s
- Burst Limit
- 8.59 Gbit/s
- Total Data
-
63 TB
(1 year)
1mo: 7.0 TB | 6mo: 62 TB | 1y: 63 TB
Measurement (Directory Authority Verified)
Source: CollecTor — fetched 2026-11-04 20:15:05
- Measured By
-
5/7
Bandwidth Authorities
Not measured by: faravahar, longclaw - Consensus Weight
- 13.6 Mbit/s (median of 5 measurements)
- Measured Min / Max
- 12.0 Mbit/s / 52.8 Mbit/s
- Deviation
- 40.8 Mbit/s [Warning] High variation
Network Participation:
Consensus Weight:
0.0008% of network
(18th pctl)
|
Guard:
N/A |
Middle:
N/A |
Exit:
0.0025% (3th pctl)
History
Uptime Metrics
- Current Status
- UP 6d 14h 53m ago
- Overall Uptime (1M/6M/1Y/5Y)
- 99.3%/99.0%/99.1%/0.0%
- Flag Uptime (1M/6M/1Y/5Y)
- Matches Overall Uptime (99.3%/99.0%/99.1%/0.0%)
- Hibernating
- No
Timestamps
- First Seen
- 6mo 2w 4d ago (2026-04-20 20:00:00)
- Last Seen
- 1h 15m 36s ago (2026-11-04 19:00:00)
- Last Restarted
- 6d 14h 53m ago (2026-10-29 05:22:01)
- Last Changed Address
- 2026-04-20 20:00:00
Overload Status:
Not Overloaded — No overload conditions reported.
Evaluated 2026-11-04 20:15 UTC. /details snapshot 2026-11-04 19:00:00 UTC (cached 32s ago). /bandwidth snapshot 2026-11-04 19:00:00 UTC (cached 35s ago).
General Overload (from /details)
- Status
- No general overload report in available data
File Descriptor Exhaustion (from /bandwidth)
- Status
- No file-descriptor exhaustion report in available data
Rate Limits (from /bandwidth)
- Status
- No rate-limit report in available data
- 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
History
Operator Identity
Source: AROI Validation API — 2026-11-04 12:00 UTC
- AROI Domain (?)
- Not specified
- Operator Validation
- Unvalidated
- This Relay
- N/A (no AROI configured)
- Contact
- fumonion [] protonmail (dot) com
Family Configuration
- Family Support
- Happy Families (7) — Has family-cert in server descriptor (guide) | View Full Family (7)
Happy Families (family-cert)
- Effective Members: 7
14958ED8C5F9285C4305288E1DC47AF4529C9239 193298316F39F95F001E5BB33142188FDC3FEA0C 48F164863CEBEC45B931A281FAF2CADAD4B1A1AD 4BB511B9DAF4B19CB26DC3AE5B964E10F9941710 873FE511D2C51F65E266F2B550595D6B5E9226FA 9EBE43353D6A53AD8C3F6DE46CF99758AF72A2B1 CA57276E7F354AB94BFDEE0CFDA8AE6201BDDED9 (this relay)
MyFamily (legacy declarations) — none
DNS Health
- Status
- Healthy (avg. 15.0s, 47th percentile)
- Query Domain
ae3fbc87d92141c39d7fd933ee6fc998.ca57276e.tor.exit.validator.1aeo.com- DNS Result
-
Resolved to
64.65.4.1 - Upstream Resolver
-
Other
Other >99% (~82 estimated queries) - Cross-Validation
- 4/4 instances succeeded
- First Hop
- server001 (MD) 03C794401A92F2F033AD5DFB2FC005D445910654
- Exit Address Used
203.202.232.160- Per-Instance Results
-
Cross Validation Attempt 1: Success, 15.6s (cv1_w3) Cross Validation Attempt 2: Success, 14.4s (cv2_w3) Cross Validation Attempt 3: Success, 15.2s (cv3_w3) Cross Validation Attempt 4: Success, 14.7s (cv4_w3)
Tested: 2026-11-04 08:15:50 UTC
Source: exitdnshealth.1aeo.com
IPv4 Exit Policy Summary
reject: 25 465 587
IPv6 Exit Policy Summary
reject: 25 465 587
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 203.202.232.160:* reject *:25 reject *:465 reject *:587 accept *:*
Last fetch was at Wed, 04 Nov 2026 20:15:35 GMT.
Data from Tor CollecTor (authority votes, fetched 2026-11-04 20:15:05).
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) | Desc Published | Cons Wt (Authority) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| bastet (US) | Yes | Yes | Yes | — | Y | Yes | Yes | Running, Valid, V2Dir, Fast, Exit | 32.8 Mbit/s (M) | 816.0 Kbit/s | 32.8 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s | 84.5% | 98% | 12.5d | 8d | 0.2d | 8.4d | 6.6d | 5.2d | 2026-11-03 15:22:20 | 32.8 Mbit/s (M) |
| dannenberg (DE) | Yes | Yes | Yes | — | Y | Yes | Yes | Running, Valid, V2Dir, Fast, Stable, HSDir, Exit | 12.0 Mbit/s (M) | 816.0 Kbit/s | 12.0 Mbit/s (M) | 272.0 Mbit/s OR 16.8 Mbit/s | 99.7% | 98% | 17.4d | 8d | 9.3d | 9.5d | 6.6d | 5.5d | 2026-11-04 09:22:25 | 12.0 Mbit/s (M) |
| dizum (NL) | Yes | Yes | Yes | — | N | Yes | Yes | Running, Valid, V2Dir, Fast, Exit | 25.2 Mbit/s (R) | 816.0 Kbit/s | 25.2 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 96.5% | 98% | 14.9d | 8d | 0.4d | 6.8d | 6.6d | 5.5d | 2026-11-04 09:22:25 | 25.2 Mbit/s (R) |
| faravahar (US) | Yes | Yes | Yes | — | Y | Yes | Yes | Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit | 25.2 Mbit/s (R) | 816.0 Kbit/s | 25.2 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 99.6% | 98% | 14.9d | 8d | 7.2d | 6.6d | 6.6d | 5.5d | 2026-11-04 09:22:25 | 25.2 Mbit/s (R) |
| gabelmoo (DE) | Yes | Yes | Yes | — | Y | Yes | Yes | Running, Valid, V2Dir, Fast, Stable, HSDir, Exit | 13.6 Mbit/s (M) | 816.0 Kbit/s | 13.6 Mbit/s (M) | 248.0 Mbit/s OR 16.8 Mbit/s | 77.1% | 98% | 18.0d | 8d | 9.5d | 10.9d | 6.6d | 5.5d | 2026-11-04 09:22:25 | 13.6 Mbit/s (M) |
| longclaw (US) | Yes | Yes | Yes | — | Y | Yes | N/T | Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit | 25.2 Mbit/s (R) | 816.0 Kbit/s | 25.2 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 99.7% | 98% | 17.3d | 8d | 11.8d | 11.1d | 6.6d | 5.5d | 2026-11-04 09:22:25 | 25.2 Mbit/s (R) |
| maatuska (SE) | Yes | Yes | Yes | — | N | Yes | Yes | Running, Valid, V2Dir, Fast, Exit | 25.2 Mbit/s (R) | 816.0 Kbit/s | 25.2 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 98.0% | 98% | 14.3d | 8d | 2.0d | 2.4d | 6.6d | 5.5d | 2026-11-04 09:22:25 | 25.2 Mbit/s (R) |
| moria1 (US) | Yes | Yes | Yes | — | Y | Yes | Yes | Valid, V2Dir, Fast, Stable, Exit | 52.8 Mbit/s (M) | 8.4 Mbit/s | 52.8 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s | 90.4% | 98% | 9.9d | 8d | 20756.2d | 7613.3d | 6.6d | 5.5d | 2026-11-04 09:22:25 | 52.8 Mbit/s (M) |
| tor26 (AT) | Yes | Yes | Yes | — | Y | Yes | Yes | Running, Valid, V2Dir, Fast, Exit | 12.0 Mbit/s (M) | 816.0 Kbit/s | 12.0 Mbit/s (M) | 256.0 Mbit/s OR 16.8 Mbit/s | 95.9% | 98% | 13.7d | 8d | 0.2d | 10.9d | 6.6d | 5.5d | 2026-11-04 09:22:25 | 12.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.