View Relay "arrogance"

Fingerprint: 4BE8056BEEB066D4C79FAF6D82CBA14080161037 | Family: 1 relay | Nitroglycerin <8421sophisticated@fldubai.com> | AS47890 | Romania | Linux

Consensus
In Consensus (9/9 Directory Auths)
BW Verified
6/7 BW Auths Measured 8 Kbit/s Median
Stability
Not Overloaded | DOWN 18h 45m 32s ago
Reachability
IPv4: 9/9 | v6: None configured(Directory Auths)
BW Weight
0.00% of Network | 59 Mbit/s Observed By Relay
Version
0.4.9.17 Recommended
Issues Detected:
  • 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: WFU below threshold : 0/9 authorities meet guard-wfu (≥98%; 5 needed). moria1 measured 0% (no uptime history for this relay). E30CF7B3, dannenberg, dizum, faravahar, gabelmoo, longclaw, maatuska and tor26 measured 75.9%–81.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.
  • Guard: Time Known below threshold : 0/9 authorities meet guard-tk (≥8 days; E30CF7B3: ≥5 days 10 hours 41 minutes 56 seconds; 5 needed). moria1 have no time-known history (3 seconds). E30CF7B3, dannenberg, dizum, faravahar, gabelmoo, longclaw, maatuska and tor26 have known this relay for 2.9 days–3.8 days.
    Suggestion: Time Known tracks how long authorities have observed your relay. This resets if: 1) Identity key changes, 2) Long downtime makes authorities forget you. Just keep running stably.
  • Not eligible for Stable flag : 1/9 authorities meet Stable (uptime or MTBF at or above their own median; 5 needed). E30CF7B3, dannenberg, dizum, faravahar, gabelmoo, longclaw, 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.
  • 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.
  • StaleDesc flag assigned : Relay descriptor is older than 18 hours
    Suggestion: Your relay is not publishing fresh descriptors. Check: 1) Tor process is running, 2) Network connectivity, 3) Clock is synchronized (NTP). Restart Tor if needed.
  • 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.
  • MiddleOnly restriction active : This relay has been restricted to middle position only by directory authorities. MiddleOnly removes Guard, Exit, HSDir, and V2Dir flags, and adds BadExit. This significantly limits the relay's role in the network.
    Suggestion: This may indicate suspicious behavior patterns, Sybil risk indicators, or policy violations. Contact bad-relays@lists.torproject.org for more information.

Addresses
OR Address
2.57.122.210:443
Reachability (Directory Authorities)
IPv4
9/9
IPv6
None configured
Location
Country
Romania Romania
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS47890
AS Name
UNMANAGED LTD (BGP.tools)
AS Rarity
Legendary (score: 4/5, <0.05% consensus weight, 4 operators)

Current Flags (4): Running, Valid, MiddleOnly, BadExit
Eligible Flags (4): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 5/9 | Stable: 1/9 | HSDir: 0/9 | Guard: 0/9 | Exit: 3/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
Valid Descriptor Meets (9/9 DA) 9/9 authorities assigned Valid Not blacklisted + valid descriptor (≥5/9 DA)
V2Dir DirPort Available Below (3/9 DA) No DirPort, no tunnelled-dir-server (R) Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Fast Speed Partial (5/9 DA) 8.0 Kbit/s – 32.0 Mbit/s (6 DA measured)
59.4 Mbit/s (3 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 (1/9 DA) Median: 3.3d (0/9 DA above threshold)
Min/Max: 0.0d / 3.3d (9/9 DA, Voting / Total Eligible)
≥2.3d - 8.2d (varies) (≥5/9 DA)
[Stricter] moria1: ≥12669.7d
Uptime Below (0/9 DA) 4.1d (R) ≥5.0d - 5.1d (varies) (≥5/9 DA)
HSDir Prereq: Fast Meets (5/9 DA) 5/9 DA assigned Fast
8.0 Kbit/s – 32.0 Mbit/s (6 DA measured)
59.4 Mbit/s (3 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 Below (1/9 DA) 1/9 DA assigned Stable ≥2.3d - 8.2d (varies) (≥5/9 DA)
[Stricter] moria1: ≥12669.7d
Prereq: V2Dir Below (3/9 DA) 3/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Uptime Below (0/9 DA) 4.1d (R) ≥96h as each authority sees it (MinUptimeHidServDirectoryV2) (≥5/9 DA)
[Stricter] moria1: ≥98% WFU and ≥9.7d Time Known
Guard Prereq: Fast Meets (5/9 DA) 5/9 DA assigned Fast
8.0 Kbit/s – 32.0 Mbit/s (6 DA measured)
59.4 Mbit/s (3 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 Below (1/9 DA) 1/9 DA assigned Stable ≥2.3d - 8.2d (varies) (≥5/9 DA)
[Stricter] moria1: ≥12669.7d
Prereq: V2Dir Below (3/9 DA) 3/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Below (0/9 DA) Median: 81.3% (0/9 DA above threshold)
Min/Max: 0.0% / 81.5% (9/9 DA, Voting / Total Eligible)
≥98% (≥5/9 DA)
Time Known Below (0/9 DA) Median: 3.8d (0/9 DA above threshold)
Min/Max: 0.0d / 3.8d (9/9 DA, Voting / Total Eligible)
≥8 days; E30CF7B3: ≥5 days 10 hours 41 minutes 56 seconds (≥5/9 DA)
Bandwidth Partial (5/9 DA) 8.0 Kbit/s – 32.0 Mbit/s (6 DA measured)
59.4 Mbit/s (3 DA relay-reported)
≥16.8 Mbit/s (AuthDirGuardBWGuarantee) OR top 25% (≥80.0 Mbit/s-248.0 Mbit/s) (≥5/9 DA)
Exit Exit Policy Partial (3/9 DA) Port 80: Yes | Port 443: Yes (R) Allows ≥1 /8 on ports 80 AND 443 (≥5/9 DA)
MiddleOnly Restriction (by DA) Flagged (6/9 DA) 6/9 authorities assigned MiddleOnly Suspicious behavior, Sybil risk, or policy violation
BadExit Restriction (by DA) Flagged (4/9 DA) 4/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-20 08:45:05).

Capacity (Relay Reported)
Observed Bandwidth
59.39 Mbit/s
Advertised Bandwidth
59.39 Mbit/s
Rate Limit
209.72 Mbit/s
Burst Limit
251.66 Mbit/s
Total Data
23 GB (1 month)
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-11-20 08:45:05

Measured By
6/7 Bandwidth Authorities
Not measured by: faravahar
Consensus Weight
8.0 Kbit/s (median of 6 measurements)
Measured Min / Max
8.0 Kbit/s / 32.0 Mbit/s
Deviation
32.0 Mbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0000% of network (0th pctl) | Guard: N/A | Middle: N/A | Exit: N/A
History
Throughput and write/read, last 30 days

Uptime Metrics
Current Status
DOWN 18h 45m 32s 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
4d 45m 32s ago (2026-11-16 09:00:00)
Last Seen
18h 45m 32s ago (2026-11-19 15:00:00)
Last Restarted
4d 1h 28m ago (2026-11-16 08:16:38)
Last Changed Address
2026-11-16 09:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Evaluated 2026-11-20 09:45 UTC. /details snapshot 2026-11-20 08:00:00 UTC (cached 37s ago). /bandwidth snapshot 2026-11-20 02: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 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
Uptime, last 30 days

Operator Identity

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

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
Nitroglycerin <8421sophisticated@fldubai.com>
Family Configuration
Family Support
None — No family membership configured
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Member: 1
4BE8056BEEB066D4C79FAF6D82CBA14080161037 (this relay)
Alleged Members: 0
none
Indirect Members: 0
none

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

DNS Health
Not an exit relay — DNS health testing does not apply.
IPv4 Exit Policy Summary
reject: 
  25
  135-139
  445
  465
  587
  4661-4666
  6881-6999
IPv6 Exit Policy Summary
None
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 2.57.122.210:*
reject *:25
reject *:135-139
reject *:445
reject *:465
reject *:587
reject *:4661-4666
reject *:6881-6999
accept *:*

Last fetch was at Fri, 20 Nov 2026 09:45:32 GMT.

Data from Tor CollecTor (authority votes, fetched 2026-11-20 08:45: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 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)
E30CF7B3 Yes Yes Yes — Y Yes Valid, V2Dir, Fast, Exit, StaleDesc 32.0 Mbit/s (M) | 816.0 Kbit/s 32.0 Mbit/s (M) | 184.0 Mbit/s OR 16.8 Mbit/s 75.9% | 98% 2.9d | 5d 2.5d | 3.9d 4.1d | 5.1d 2026-11-19 09:10:26 [Stale] 32.0 Mbit/s (M)
dannenberg (DE) Yes Yes No Yes Y Yes Valid, MiddleOnly, StaleDesc 8.0 Kbit/s (M) | 816.0 Kbit/s 8.0 Kbit/s (M) | 248.0 Mbit/s OR 16.8 Mbit/s 81.5% | 98% 3.8d | 8d 3.3d | 8.2d 4.1d | 5.1d 2026-11-19 09:10:26 [Stale] 8.0 Kbit/s (M)
dizum (NL) Yes Yes Yes — N Yes Valid, V2Dir, Fast, Exit, StaleDesc 59.4 Mbit/s (R) | 816.0 Kbit/s 59.4 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 81.3% | 98% 3.8d | 8d 3.3d | 6.8d 4.1d | 5.1d 2026-11-19 09:10:26 [Stale] 59.4 Mbit/s (R)
faravahar (US) Yes Yes No Yes Y Yes Valid, Fast, MiddleOnly, BadExit, StaleDesc 59.4 Mbit/s (R) | 816.0 Kbit/s 59.4 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 81.5% | 98% 3.8d | 8d 3.3d | 7.0d 4.1d | 5.1d 2026-11-19 09:10:26 [Stale] 59.4 Mbit/s (R)
gabelmoo (DE) Yes Yes No Yes Y Yes Valid, MiddleOnly, BadExit, StaleDesc 8.0 Kbit/s (M) | 816.0 Kbit/s 8.0 Kbit/s (M) | 240.0 Mbit/s OR 16.8 Mbit/s 81.3% | 98% 3.8d | 8d 3.3d | 8.3d 4.1d | 5.1d 2026-11-19 09:10:26 [Stale] 8.0 Kbit/s (M)
longclaw (US) Yes Yes No Yes Y Yes Valid, MiddleOnly, BadExit, StaleDesc 8.0 Kbit/s (M) | 816.0 Kbit/s 8.0 Kbit/s (M) | 240.0 Mbit/s OR 16.8 Mbit/s 81.1% | 98% 3.8d | 8d 3.2d | 9.1d 4.1d | 5.1d 2026-11-19 09:10:26 [Stale] 8.0 Kbit/s (M)
maatuska (SE) Yes Yes No Yes N Yes Valid, Fast, Stable, MiddleOnly, StaleDesc 59.4 Mbit/s (R) | 816.0 Kbit/s 59.4 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 81.3% | 98% 3.8d | 8d 3.3d | 2.3d 4.1d | 5.1d 2026-11-19 09:10:26 [Stale] 59.4 Mbit/s (R)
moria1 (US) Yes Yes No Yes Y Yes Valid, Fast, MiddleOnly, BadExit, StaleDesc 28.8 Mbit/s (M) | 8.4 Mbit/s 28.8 Mbit/s (M) | 184.0 Mbit/s OR 16.8 Mbit/s 0.0% | 98% 0.0d | 8d 0.0d | 12669.7d 4.1d | 5.0d 2026-11-19 09:10:26 [Stale] 28.8 Mbit/s (M)
tor26 (AT) Yes Yes Yes — Y Yes Valid, V2Dir, Exit, StaleDesc 8.0 Kbit/s (M) | 816.0 Kbit/s 8.0 Kbit/s (M) | 240.0 Mbit/s OR 16.8 Mbit/s 81.2% | 98% 3.8d | 8d 3.3d | 8.2d 4.1d | 5.1d 2026-11-19 09:10:26 [Stale] 8.0 Kbit/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.