View Relay "NCExit01"
Fingerprint: ED3C3B5CF8C524F23A476EC4FB363F55F01B070D |
Family: 1 relay
|
abh0rr3nt@proton.me |
AS27284
|
United States of America
|
Linux
- Consensus
- In Consensus (9/9 Directory Auths)
- DNS Health
- Healthy (7.8s, 3rd percentile) (via exitdnshealth.1aeo.com)
- BW Verified
- 5/7 BW Auths Measured 6 Mbit/s Median
- Stability
- Not Overloaded | UP 4d 20h 15m ago | UP 99% (1M)
- Reachability
- IPv4: 9/9 | v6: 7/8(Directory Auths)
- BW Weight
- 0.00% of Network | 16 Mbit/s Observed By Relay
- Version
- 0.4.9.15 Recommended
Issues Detected:
-
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). dannenberg, gabelmoo and tor26 measured this relay at 4.9 Mbit/s – 6.7 Mbit/s. dizum, faravahar, longclaw and maatuska used the relay-reported 16.0 Mbit/s.
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. -
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
-
147.90.234.167:9001
[2602:f6f6:2:597e::1]:9001 - Exit Address
- 147.90.234.167
Reachability (Directory Authorities)
- IPv4
- 9/9
- IPv6
- 7/8 (1 don't test)
Location
- Country
-
United States of America
- Interactive Map
- View in RouteFluxMap
Eligible Flags (7):
Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 9/9 | Stable: 8/9 | HSDir: 7/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 (7/8 DA) | 7/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) | 4.9 Mbit/s – 24.8 Mbit/s (5 DA measured) 16.0 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 (1/9 DA) | Median: 7.8d (1/9 DA above threshold) Min/Max: 0.6d / 13719.4d (9/9 DA, Voting / Total Eligible) |
≥2.7d - 12.0d (varies) (≥5/9 DA) [Stricter] moria1: ≥6041.4d |
| Uptime | Below (0/9 DA) | 4.8d (R) | ≥4.9d - 4.9d (varies) (≥5/9 DA) | |
| HSDir | Prereq: Fast | Meets (9/9 DA) | 9/9 DA assigned Fast 4.9 Mbit/s – 24.8 Mbit/s (5 DA measured) 16.0 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 (8/9 DA) | 8/9 DA assigned Stable | ≥2.7d - 12.0d (varies) (≥5/9 DA) [Stricter] moria1: ≥6041.4d |
|
| Prereq: V2Dir | Meets (9/9 DA) | 9/9 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥5/9 DA) | |
| Uptime | Partial (7/9 DA) | 4.8d (R) | ≥96h as each authority sees it (MinUptimeHidServDirectoryV2) (≥5/9 DA) [Stricter] moria1: ≥98% WFU and ≥9.8d Time Known |
|
| Guard | Prereq: Fast | Meets (9/9 DA) | 9/9 DA assigned Fast 4.9 Mbit/s – 24.8 Mbit/s (5 DA measured) 16.0 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 (8/9 DA) | 8/9 DA assigned Stable | ≥2.7d - 12.0d (varies) (≥5/9 DA) [Stricter] moria1: ≥6041.4d |
|
| Prereq: V2Dir | Meets (9/9 DA) | 9/9 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥5/9 DA) | |
| WFU | Partial (8/9 DA) | Median: 99.1% (8/9 DA above threshold) Min/Max: 95.6% / 99.6% (9/9 DA, Voting / Total Eligible) |
≥98%; maatuska: ≥96.88599999999999% (≥5/9 DA) | |
| Time Known | Meets (9/9 DA) | Median: 16.3d (9/9 DA above threshold) Min/Max: 9.6d / 17.5d (9/9 DA, Voting / Total Eligible) |
≥8 days (≥5/9 DA) | |
| Bandwidth | Below (2/9 DA) | 4.9 Mbit/s – 24.8 Mbit/s (5 DA measured) 16.0 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-10 11:45:05).
Capacity (Relay Reported)
- Observed Bandwidth
- 16.93 Mbit/s
- Advertised Bandwidth
- 16.00 Mbit/s
- Rate Limit
- 16.00 Mbit/s
- Burst Limit
- 32.00 Mbit/s
- Total Data
-
13 TB
(6 months)
1mo: 3.7 TB | 6mo: 13 TB
Measurement (Directory Authority Verified)
Source: CollecTor — fetched 2026-11-10 11:45:05
- Measured By
-
5/7
Bandwidth Authorities
Not measured by: faravahar, longclaw - Consensus Weight
- 6.7 Mbit/s (median of 5 measurements)
- Measured Min / Max
- 4.9 Mbit/s / 24.8 Mbit/s
- Deviation
- 19.9 Mbit/s [Warning] High variation
Network Participation:
Consensus Weight:
0.0004% of network
(13th pctl)
|
Guard:
N/A |
Middle:
N/A |
Exit:
0.0012% (3th pctl)
History
Uptime Metrics
- Current Status
- UP 4d 20h 15m ago
- Overall Uptime (1M/6M/1Y/5Y)
- 99.5%/99.5%/0.0%/0.0%
- Flag Uptime (1M/6M/1Y/5Y)
- Matches Overall Uptime (99.5%/99.5%/0.0%/0.0%)
- Hibernating
- No
Timestamps
- First Seen
- 4mo 2w 5d ago (2026-06-24 03:00:00)
- Last Seen
- 1h 45m 39s ago (2026-11-10 10:00:00)
- Last Restarted
- 4d 20h 15m ago (2026-11-05 15:30:38)
- Last Changed Address
- 2026-06-24 03:00:00
Overload Status:
Not Overloaded.
Historical rate-limit report outside the 24-hour window
Evaluated 2026-11-10 11:45 UTC. /details snapshot 2026-11-10 10:00:00 UTC (cached 16s ago). /bandwidth snapshot 2026-11-10 01:00:00 UTC (cached 9h 30m ago).
Reported timestamps use hour precision, so the displayed minute is not an exact incident time.
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
- Historical report — outside the 24-hour window
- Rate Limit
- 16.00 Mbit/s
- Burst Limit
- 4.0 MB
- Write counter
- 147
- Read counter
- 246
- Reported
- 2026-11-09 11:00 UTC (1 day ago)
Read and write counters increment at most once per minute per direction. They are not a count of blocked connections, the duration of throttling, or necessarily the number of events in the last 24 hours. Rate is BandwidthRate and follows this site’s bits/bytes setting. Burst is BandwidthBurst, already a byte quantity. RelayBandwidthRate and RelayBandwidthBurst are extra torrc caps, not the names of these values. A hit stays eligible for 24 hours.
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-10 03:00 UTC
- AROI Domain (?)
- Not specified
- Operator Validation
- Unvalidated
- This Relay
- N/A (no AROI configured)
- Contact
- abh0rr3nt@proton.me
Family Configuration
- Family Support
- None — No family membership configured
Happy Families (family-cert)
- Effective Members: 0
- none
MyFamily (legacy declarations)
- Effective Member: 1
ED3C3B5CF8C524F23A476EC4FB363F55F01B070D (this relay)
- Alleged Members: 0
- none
- Indirect Members: 0
- none
DNS Health
- Status
- Healthy (avg. 7.8s, 3rd percentile)
- Query Domain
799453c274e34a7b8f74ddc3cdc3c5de.ed3c3b5c.tor.exit.validator.1aeo.com- DNS Result
-
Resolved to
64.65.4.1 - Upstream Resolver
-
Cloudflare
(public resolver)
Cloudflare 100% (~38 estimated queries) - Cross-Validation
- 3/3 instances succeeded
- First Hop
- marvinmartian (NL) 5F3981B8E05F5594740B4CC56E8C958403A42C76
- Exit Address Used
147.90.234.167- Per-Instance Results
-
Cross Validation Attempt 1: Success, 10.6s (cv1_w4) Cross Validation Attempt 2: Success, 3.1s (cv2_w4) Cross Validation Attempt 3: Success, 9.7s (cv4_w4)
Tested: 2026-11-09 20:18:19 UTC
Source: exitdnshealth.1aeo.com
IPv4 Exit Policy Summary
accept: 53 80 443 8080
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 147.90.234.167:* accept *:53 accept *:80 accept *:443 accept *:8080 reject *:*
Last fetch was at Tue, 10 Nov 2026 11:45:38 GMT.
Data from Tor CollecTor (authority votes, fetched 2026-11-10 11: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 | 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, Stable, HSDir, Guard, Exit | 24.8 Mbit/s (M) | 816.0 Kbit/s | 24.8 Mbit/s (M) | 184.0 Mbit/s OR 16.8 Mbit/s | 99.6% | 98% | 15.4d | 8d | 9.2d | 9.7d | 4.8d | 5.9d | 2026-11-05 13:22:40 | 24.8 Mbit/s (M) |
| dannenberg (DE) | Yes | Yes | Yes | — | Y | Yes | Yes | Running, Valid, V2Dir, Fast, Stable, HSDir, Exit | 4.9 Mbit/s (M) | 816.0 Kbit/s | 4.9 Mbit/s (M) | 272.0 Mbit/s OR 16.8 Mbit/s | 99.2% | 98% | 17.5d | 8d | 7.3d | 12.0d | 4.8d | 4.9d | 2026-11-10 06:05:56 | 4.9 Mbit/s (M) |
| dizum (NL) | Yes | Yes | Yes | — | N | Yes | Yes | Running, Valid, V2Dir, Fast, Stable, HSDir, Exit | 16.0 Mbit/s (R) | 816.0 Kbit/s | 16.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 98.3% | 98% | 16.3d | 8d | 6.7d | 10.0d | 4.8d | 4.9d | 2026-11-10 06:05:56 | 16.0 Mbit/s (R) |
| faravahar (US) | Yes | Yes | Yes | — | Y | Yes | Yes | Running, Valid, V2Dir, Fast, Stable, HSDir, Exit | 16.0 Mbit/s (R) | 816.0 Kbit/s | 16.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 99.0% | 98% | 15.9d | 8d | 6.2d | 9.2d | 4.8d | 4.9d | 2026-11-10 06:05:56 | 16.0 Mbit/s (R) |
| gabelmoo (DE) | Yes | Yes | Yes | — | Y | Yes | Yes | Running, Valid, V2Dir, Fast, Stable, HSDir, Exit | 5.8 Mbit/s (M) | 816.0 Kbit/s | 5.8 Mbit/s (M) | 248.0 Mbit/s OR 16.8 Mbit/s | 99.1% | 98% | 16.7d | 8d | 7.9d | 13.6d | 4.8d | 4.9d | 2026-11-10 06:05:56 | 5.8 Mbit/s (M) |
| longclaw (US) | Yes | Yes | Yes | — | Y | Yes | N/T | Running, Valid, V2Dir, Fast, Stable, HSDir, Exit | 16.0 Mbit/s (R) | 816.0 Kbit/s | 16.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 99.2% | 98% | 17.5d | 8d | 8.1d | 13.9d | 4.8d | 4.9d | 2026-11-10 06:05:56 | 16.0 Mbit/s (R) |
| maatuska (SE) | Yes | Yes | Yes | — | N | Yes | No | Valid, V2Dir, Fast, Exit | 16.0 Mbit/s (R) | 816.0 Kbit/s | 16.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 95.6% | 97% | 13.7d | 8d | 0.6d | 2.7d | 4.8d | 6.8d | 2026-11-10 06:05:56 | 16.0 Mbit/s (R) |
| moria1 (US) | Yes | Yes | Yes | — | Y | Yes | Yes | Running, Valid, V2Dir, Fast, Stable, Guard, Exit | 18.4 Mbit/s (M) | 8.4 Mbit/s | 18.4 Mbit/s (M) | 184.0 Mbit/s OR 16.8 Mbit/s | 98.6% | 98% | 9.6d | 8d | 13719.4d | 6041.4d | 4.8d | 4.9d | 2026-11-10 06:05:56 | 18.4 Mbit/s (M) |
| tor26 (AT) | Yes | Yes | Yes | — | Y | Yes | Yes | Running, Valid, V2Dir, Fast, Stable, HSDir, Exit | 6.7 Mbit/s (M) | 816.0 Kbit/s | 6.7 Mbit/s (M) | 256.0 Mbit/s OR 16.8 Mbit/s | 99.1% | 98% | 17.4d | 8d | 7.8d | 13.5d | 4.8d | 4.9d | 2026-11-10 06:05:56 | 6.7 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.