View Relay "2mpe2"

Fingerprint: 7FA39E6A58DCC7E007F24D21C41055DBEFA8824B | Family: 1 relay | DoNotDisturb AT NoContact NoWarnings 2 | AS53667 | United States of America | Linux

Consensus
In Consensus (9/9 Directory Auths)
BW Verified
5/7 BW Auths Measured 12 Kbit/s Median
Stability
Overloaded | DOWN 4h 7m 3s ago
Reachability
IPv4: 9/9 | v6: 8/8 (Directory Auths)
BW Weight
0.00% of Network | 17 Mbit/s Observed By Relay
Version
0.4.9.16 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 5.2% 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 5.2% 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.
  • 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.
  • General Overload Active : Relay reported general overload at 2026-11-07 21:00 UTC. This indicates OOM killer invocation, onionskin queue saturation, or TCP port exhaustion.
    Suggestion: Check CPU/memory with htop. Review logs for "out of memory" or "onionskins" warnings. Consider increasing MaxMemInQueues in torrc. Verify TCP ports available.

Addresses
OR Address
198.98.51.249:8443
[2605:6400:10:1ab:2605:6400:10:1ab]:8443
Reachability (Directory Authorities)
IPv4
9/9
IPv6
8/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.43% consensus weight, 34 operators)

Current Flags (6): Running, Valid, V2Dir, Fast, Exit, BadExit
Eligible Flags (5): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 8/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 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) 17.5 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: 0.1d (1/9 DA above threshold)
Min/Max: 0.1d / 20751.0d (9/9 DA, Voting / Total Eligible)
≥3.2d - 11.2d (varies) (≥5/9 DA)
[Stricter] moria1: ≥6577.2d
Uptime Below (0/9 DA) 2.1d (R) ≥3.3d - 3.3d (varies) (≥5/9 DA)
HSDir Prereq: Fast Meets (8/9 DA) 8/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 ≥3.2d - 11.2d (varies) (≥5/9 DA)
[Stricter] moria1: ≥6577.2d
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: 9.5% (0/9 DA above threshold)
Min/Max: 5.2% / 16.0% (9/9 DA, Voting / Total Eligible)
≥98.0% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 16.1d (9/9 DA above threshold)
Min/Max: 9.9d / 17.7d (9/9 DA, Voting / Total Eligible)
≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.9d
Guard Prereq: Fast Meets (8/9 DA) 8/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 ≥3.2d - 11.2d (varies) (≥5/9 DA)
[Stricter] moria1: ≥6577.2d
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: 9.5% (0/9 DA above threshold)
Min/Max: 5.2% / 16.0% (9/9 DA, Voting / Total Eligible)
≥98% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 16.1d (9/9 DA above threshold)
Min/Max: 9.9d / 17.7d (9/9 DA, Voting / Total Eligible)
≥8 days (≥5/9 DA)
Bandwidth Meets (9/9 DA) 17.5 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-280.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)
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 08:01:41).

Capacity (Relay Reported)
Observed Bandwidth
17.46 Mbit/s
Advertised Bandwidth
17.46 Mbit/s
Rate Limit
18.87 Mbit/s
Burst Limit
20.97 Mbit/s
Total Data
27 GB (1 month)
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-11-08 08:01:41

Measured By
5/7 Bandwidth Authorities
Not measured by: faravahar, longclaw
Median Measurement
12.8 Kbit/s
Min / Max
8 bit/s / 17.4 Kbit/s
Deviation
17.4 Kbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0001% of network (9th pctl) | Guard: N/A | Middle: N/A | Exit: N/A

Uptime Metrics
Current Status
DOWN 4h 7m 3s ago
Overall Uptime (1M/6M/1Y/5Y)
0.0%/0.0%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (0.0%/0.0%/0.0%/0.0%)
Hibernating
No
Timestamps
First Seen
2d 2h 7m ago (2026-11-06 06:00:00)
Last Seen
4h 7m 3s ago (2026-11-08 04:00:00)
Last Restarted
2d 3h 10m ago (2026-11-06 04:56:40)
Last Changed Address
2026-11-06 06:00:00
[Warning] OVERLOADED — General overload at 2026-11-07 21:00 UTC
General Overload (from /details)
Status
Reported
When
2026-11-07 21:00 UTC (11 hours ago)

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)

No rate limit data from /bandwidth endpoint.

Recommendations
  • Check CPU/memory: htop
  • Review MaxMemInQueues in torrc

Operator Identity

Source: AROI Validation API — 2026-11-07 23:00 UTC

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

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

DNS Health
Status
Not Tested
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 198.98.51.249:*
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 Sun, 08 Nov 2026 08:06:52 GMT.

Data from Tor CollecTor (authority votes, fetched 2026-11-08 08:01:41).

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 Yes — Y Yes Yes Running, Valid, V2Dir, Fast, Exit 17.5 Mbit/s | 816.0 Kbit/s 17.5 Mbit/s | 184.0 Mbit/s OR 16.0 Mbit/s 5.2% | 98% 17.7d | 8d 0.1d | 9.7d 2.1d | 5.7d 5.2% | 98.0% 17.7d | 1.0d 2026-11-06 04:56:44 5040 bit/s
dannenberg (DE) Yes Yes Yes — Y Yes Yes Valid, V2Dir, Fast, Exit 17.5 Mbit/s | 816.0 Kbit/s 17.5 Mbit/s | 280.0 Mbit/s OR 16.0 Mbit/s 9.3% | 98% 16.1d | 8d 0.1d | 11.2d 2.1d | 3.4d 9.3% | 98.0% 16.1d | 1.0d 2026-11-08 02:38:24 12.8 Kbit/s
dizum (NL) Yes Yes Yes — N Yes Yes Valid, V2Dir, Fast, Exit 17.5 Mbit/s | 816.0 Kbit/s 17.5 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 9.6% | 98% 16.1d | 8d 0.1d | 8.6d 2.1d | 3.4d 9.6% | 98.0% 16.1d | 1.0d 2026-11-08 02:38:24 17.4 Kbit/s
faravahar (US) Yes Yes Yes — Y Yes Yes Valid, V2Dir, Fast, Exit, BadExit 17.5 Mbit/s | 816.0 Kbit/s 17.5 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 9.4% | 98% 16.1d | 8d 0.1d | 8.0d 2.1d | 3.3d 9.4% | 98.0% 16.1d | 1.0d 2026-11-08 02:38:24 17.4 Kbit/s
gabelmoo (DE) Yes Yes Yes — Y Yes Yes Valid, V2Dir, Fast, Exit, BadExit 17.5 Mbit/s | 816.0 Kbit/s 17.5 Mbit/s | 264.0 Mbit/s OR 16.0 Mbit/s 9.2% | 98% 16.2d | 8d 0.1d | 12.9d 2.1d | 3.3d 9.2% | 98.0% 16.2d | 1.0d 2026-11-08 02:38:24 2160 bit/s
longclaw (US) Yes Yes Yes — Y Yes — Running, Valid, V2Dir, Fast, Exit, BadExit 17.5 Mbit/s | 816.0 Kbit/s 17.5 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 9.5% | 98% 16.1d | 8d 0.1d | 13.2d 2.1d | 3.3d 9.5% | 98.0% 16.1d | 1.0d 2026-11-08 02:38:24 17.4 Kbit/s
maatuska (SE) Yes Yes Yes — N Yes Yes Running, Valid, V2Dir, Fast, Exit 17.5 Mbit/s | 816.0 Kbit/s 17.5 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 9.7% | 98% 16.2d | 8d 0.1d | 3.2d 2.1d | 3.3d 9.7% | 98.0% 16.2d | 1.0d 2026-11-08 02:38:24 17.4 Kbit/s
moria1 (US) Yes Yes Yes — Y Yes Yes Valid, V2Dir, Stable, Exit, BadExit 17.5 Mbit/s | 8.4 Mbit/s 17.5 Mbit/s | 184.0 Mbit/s OR 16.0 Mbit/s 16.0% | 98% 9.9d | 8d 20751.0d | 6577.2d 2.1d | 3.3d 16.0% | 98.0% 9.93d | 9.89d 2026-11-08 02:38:24 8 bit/s
tor26 (AT) Yes Yes Yes — Y Yes Yes Valid, V2Dir, Fast, Exit, BadExit 17.5 Mbit/s | 816.0 Kbit/s 17.5 Mbit/s | 256.0 Mbit/s OR 16.0 Mbit/s 9.8% | 98% 16.1d | 8d 0.1d | 13.0d 2.1d | 3.4d 9.8% | 98.0% 16.1d | 1.0d 2026-11-08 02:38:24 5280 bit/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.