View Relay "2mplas3"

Fingerprint: 051E2F746BC4A5C571436B2E8F97CB6EB5975B2D | Family: 5 relays | DoNotDisturb AT NoContact NoWarnings | AS53667 | United States of America | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, Valid, Exit (3)
DNS Health
Not Tested (via exitdnshealth.1aeo.com)
BW Verified
4/7 BW Auths Measured 13 Mbit/s Median
Stability
Incomplete | DOWN 6h 45m 41s ago
Reachability
IPv4: 9/9 | v6: 0/8(Directory Auths)
First Seen
6h 45m 41s ago
BW Weight
0.00% of Network | 0 Kbit/s Observed By Relay
Version
0.4.9.15 Recommended
Issues Detected:
  • 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/
  • Not getting the Fast flag : Only 4/9 authorities vote Fast (5 needed). dizum, faravahar, longclaw and maatuska used the relay-reported unknown, below the Fast threshold (816.0 Kbit/s). dannenberg 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 : 2/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). gabelmoo and tor26 measured this relay at 9.6 Mbit/s – 13.6 Mbit/s. dizum, faravahar, longclaw and maatuska used the relay-reported unknown. dannenberg 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%; dizum: ≥97.969%; 5 needed). bastet, dannenberg, dizum, faravahar, gabelmoo, longclaw, maatuska, moria1 and tor26 measured 6.4%–10.7%.
    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 : 1/9 authorities meet Stable (uptime or MTBF at or above their own median; 5 needed). bastet, dannenberg, dizum, faravahar, gabelmoo, longclaw, maatuska 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.
  • 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
  • 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.

Connectivity and Location

Addresses
OR Address
205.185.113.210:5061
[2605:6400:20:3b6:2605:6400:20:3b6]:5061
Reachability (Directory Authorities)
IPv4
9/9
IPv6
0/8 (1 don't test)
Location
Country
United States of America United States of America
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS53667
AS Name
FranTech Solutions (BGP.tools)
AS Rarity
Rare (score: 2/5, 0.41% consensus weight, 32 operators)

Flags and Eligibility

Current Flags (3): Running, Valid, Exit
Eligible Flags (4): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 4/9 | Stable: 1/9 | HSDir: 0/9 | Guard: 0/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 Below (0/8 DA) 0/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 Below (0/9 DA) No DirPort, no tunnelled-dir-server (R) Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Fast Speed Below (4/9 DA) 9.6 Mbit/s – 21.6 Mbit/s (4 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 (1/9 DA) Median: 0.1d (1/9 DA above threshold)
Min/Max: 0.1d / 20742.5d (9/9 DA, Voting / Total Eligible)		 ≥2.5d - 9.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥7441.7d
Uptime Below (0/9 DA) 0.3d (R) ≥5.7d - 5.8d (varies) (≥5/9 DA)
HSDir Prereq: Fast Below (4/9 DA) 4/9 DA assigned Fast
9.6 Mbit/s – 21.6 Mbit/s (4 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 (1/9 DA) 1/9 DA assigned Stable ≥2.5d - 9.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥7441.7d
Prereq: V2Dir Below (0/9 DA) 0/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Uptime Below (0/9 DA) 0.3d (R) ≥96h as each authority sees it (MinUptimeHidServDirectoryV2) (≥5/9 DA)
[Stricter] moria1: ≥98% WFU and ≥9.8d Time Known
Guard Prereq: Fast Below (4/9 DA) 4/9 DA assigned Fast
9.6 Mbit/s – 21.6 Mbit/s (4 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 (1/9 DA) 1/9 DA assigned Stable ≥2.5d - 9.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥7441.7d
Prereq: V2Dir Below (0/9 DA) 0/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Below (0/9 DA) Median: 6.8% (0/9 DA above threshold)
Min/Max: 6.4% / 10.7% (9/9 DA, Voting / Total Eligible)		 ≥98%; dizum: ≥97.969% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 15.9d (9/9 DA above threshold)
Min/Max: 9.6d / 16.7d (9/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Below (2/9 DA) 9.6 Mbit/s – 21.6 Mbit/s (4 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 (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-05 02:45:05).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
0.00 Kbit/s
Advertised Bandwidth
Unknown
Rate Limit
20.97 Mbit/s
Burst Limit
25.17 Mbit/s
Total Data
N/A
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-11-05 02:45:05

Measured By
4/7 Bandwidth Authorities
Not measured by: dannenberg, faravahar, longclaw
Consensus Weight
13.6 Mbit/s (median of 4 measurements)
Measured Min / Max
9.6 Mbit/s / 21.6 Mbit/s
Deviation
12.0 Mbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0008% of network (19th pctl) | Guard: N/A | Middle: N/A | Exit: N/A

Uptime and Stability

Uptime Metrics
Current Status
DOWN 6h 45m 41s 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
6h 45m 41s ago (2026-11-04 20:00:00)
Last Seen
6h 45m 41s ago (2026-11-04 20:00:00)
Last Restarted
7h 17m 59s ago (2026-11-04 19:27:42)
Last Changed Address
2026-11-04 20:00:00
Overload status: Incomplete — not every signal could be evaluated. (No bandwidth record available for this relay)

Evaluated 2026-11-05 02:45 UTC. /details snapshot 2026-11-05 01:00:00 UTC (cached 45s ago). /bandwidth snapshot 2026-11-04 19:00:00 UTC (cached 6h 30m 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 and Family

Operator Identity

Source: AROI Validation API — 2026-11-04 18:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
DoNotDisturb AT NoContact NoWarnings
Family Configuration
Family Support
Happy Families (6) — Has family-cert in server descriptor (guide) | View Full Family (5)
MyFamily (legacy declarations) — none

Software and Version

Platform
Linux — Tor 0.4.9.15 on Linux
Version
0.4.9.15 — Recommended
Version Status
Recommended

Exit Health & Policy

DNS Health
Status
Not Tested
Source: exitdnshealth.1aeo.com
IPv4 Exit Policy Summary
accept: 
  53
  80-81
  443
  531
  554
  873
  989-990
  993
  995
  1194
  1755
  1863
  2083
  2086-2087
  2095-2096
  2102-2104
  5050
  5190
  5222-5223
  5228
  8008
  8232-8233
  8332-8333
  8443
  8888
  9418
  11371
  19294
  50002
  64738
IPv6 Exit Policy Summary
accept: 
  53
  80-81
  443
  531
  554
  873
  989-990
  993
  995
  1194
  1755
  1863
  2083
  2086-2087
  2095-2096
  2102-2104
  5050
  5190
  5222-5223
  5228
  8008
  8232-8233
  8332-8333
  8443
  8888
  9418
  11371
  19294
  50002
  64738
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 205.185.113.210:*
accept *:53
accept *:80-81
accept *:443
accept *:531
accept *:554
accept *:873
accept *:989-990
accept *:993
accept *:995
accept *:1194
accept *:1755
accept *:1863
accept *:2083
accept *:2086-2087
accept *:2095-2096
accept *:2102-2104
accept *:5050
accept *:5190
accept *:5222-5223
accept *:5228
accept *:8008
accept *:8232-8233
accept *:8332-8333
accept *:8443
accept *:8888
accept *:9418
accept *:11371
accept *:19294
accept *:50002
accept *:64738
reject *:*

Last fetch was at Thu, 05 Nov 2026 02:45:40 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-11-05 02: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) Desc Published Cons Wt (Authority)
bastet (US) Yes Yes Yes — Y Yes No Valid, Fast, Exit 21.6 Mbit/s (M) | 816.0 Kbit/s 21.6 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s 6.7% | 98% 16.6d | 8d 0.1d | 8.8d 0.3d | 5.7d 2026-11-04 19:27:49 21.6 Mbit/s (M)
dannenberg (DE) Yes Yes Yes — Y Yes No Valid, Exit 0 bit/s (U) | 816.0 Kbit/s 0 bit/s (U) | 272.0 Mbit/s OR 16.8 Mbit/s 6.4% | 98% 15.9d | 8d 0.1d | 9.7d 0.3d | 5.8d 2026-11-04 19:27:49 —
dizum (NL) Yes Yes Yes — N Yes No Valid, Exit 0 bit/s (R) | 816.0 Kbit/s 0 bit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 7.0% | 98% 15.9d | 8d 0.1d | 7.0d 0.3d | 5.8d 2026-11-04 19:27:49 —
faravahar (US) Yes Yes Yes — Y Yes No Valid, Exit 0 bit/s (R) | 816.0 Kbit/s 0 bit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 6.4% | 98% 16.7d | 8d 0.1d | 6.7d 0.3d | 5.8d 2026-11-04 19:27:49 —
gabelmoo (DE) Yes Yes Yes — Y Yes No Valid, Fast, Exit 9.6 Mbit/s (M) | 816.0 Kbit/s 9.6 Mbit/s (M) | 248.0 Mbit/s OR 16.8 Mbit/s 6.5% | 98% 15.9d | 8d 0.1d | 11.1d 0.3d | 5.8d 2026-11-04 19:27:49 9.6 Mbit/s (M)
longclaw (US) Yes Yes Yes — Y Yes N/T Valid, Exit 0 bit/s (R) | 816.0 Kbit/s 0 bit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 6.8% | 98% 16.7d | 8d 0.1d | 11.3d 0.3d | 5.8d 2026-11-04 19:27:49 —
maatuska (SE) Yes Yes Yes — N Yes No Valid, Exit 0 bit/s (R) | 816.0 Kbit/s 0 bit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 6.8% | 98% 15.9d | 8d 0.1d | 2.5d 0.3d | 5.8d 2026-11-04 19:27:49 —
moria1 (US) Yes Yes Yes — Y Yes No Valid, Fast, Stable, Exit 18.4 Mbit/s (M) | 8.4 Mbit/s 18.4 Mbit/s (M) | 184.0 Mbit/s OR 16.8 Mbit/s 10.7% | 98% 9.6d | 8d 20742.5d | 7441.7d 0.3d | 5.8d 2026-11-04 19:27:49 18.4 Mbit/s (M)
tor26 (AT) Yes Yes Yes — Y Yes No Valid, Fast, Exit 13.6 Mbit/s (M) | 816.0 Kbit/s 13.6 Mbit/s (M) | 248.0 Mbit/s OR 16.8 Mbit/s 7.1% | 98% 16.7d | 8d 0.1d | 11.1d 0.3d | 5.8d 2026-11-04 19:27:49 13.6 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 (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.