View Relay "110"
Fingerprint: 4BFF9632363B6E0F66FBCE2313477BA309AC7C7E |
Family: 1 relay
|
110@2140.lol |
AS36352
|
United States of America
|
Linux
- Consensus
- Not In Consensus (1/9 Directory Auths, need 5)
- BW Verified
- 1/7 BW Auths Measured 160 Kbit/s Median
- Stability
- Not Overloaded | DOWN 2d 12h 16m ago | UP 56% (1M)
- Reachability
- IPv4: 1/9 | v6: None configured(Directory Auths)
- BW Weight
- 0.00% of Network | 8 Mbit/s Observed By Relay
- Version
- 0.4.9.16 Recommended
-
Not in consensus
: Only 1/9 authorities voted for this relay (need 5)
Suggestion: Verify your relay is reachable from multiple geographic locations. Check firewall rules allow incoming connections on your ORPort from all directory authority IP addresses. -
IPv4 reachability issues
: Only 1/9 authorities can reach this relay
Suggestion: Authorities that cannot reach you: dannenberg, dizum, faravahar, gabelmoo, longclaw, maatuska, moria1, tor26. Check: 1) Firewall allows incoming TCP on ORPort, 2) No ISP-level blocking, 3) Tor is running and listening. Use 'nc -zv your-ip your-orport' from external hosts to test. -
Guard: bandwidth below threshold
: 0/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% (184.0 Mbit/s). bastet measured this relay at 5.7 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. -
Guard: WFU below threshold
: 0/9 authorities meet guard-wfu (≥98%; 5 needed). bastet measured 70.1%.
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
: 1/9 authorities meet guard-tk (≥8 days; 5 needed).
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. -
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 becauseDirCache 0is set in torrc.
Suggestion: RemoveDirCache 0from torrc (DirCache is enabled by default in Tor ≥0.3.3). Restart Tor and verify the descriptor includestunnelled-dir-server. You can check with:grep tunnelled-dir-server /var/lib/tor/cached-descriptors -
Low bandwidth authority measurements
: Only 1/7 bandwidth authorities measured this relay. Minimum 3 measurements needed for accurate consensus weight.
Suggestion: Low measurement count can indicate connectivity issues. Check: 1) Relay is reachable from multiple geographic locations, 2) ORPort accepts connections from bandwidth scanners, 3) RelayBandwidthRate in torrc matches actual capacity. New relays may take 1-2 days to be measured by all authorities.
Addresses
- OR Address
- 23.94.101.188:443
Reachability (Directory Authorities)
- IPv4
- 1/9
- IPv6
- None configured
Location
- Country
-
United States of America
- Interactive Map
- View in RouteFluxMap
Eligibility Flag Vote Details
| Flag | Metric | Status | Relay Value | Threshold Required |
|---|---|---|---|---|
| Running | IPv4 Reachability | Below (1/9 DA) | 1/9 authorities reached relay | ≥5/9 DA ORPort reachable |
| Valid | Descriptor | Partial (1/9 DA) | 1/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 (1/9 DA) | 5.7 Mbit/s (1 DA measured) | ≥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 (0/9 DA) | Median: 6.8d (0/9 DA above threshold) | ≥2.6d - 11.8d (varies) (≥5/9 DA) [Stricter] moria1: ≥6126.3d |
| Uptime | Partial (7/9 DA) | 4.6d (R) | ≥4.4d - 4.5d (varies) (≥5/9 DA) | |
| HSDir | Prereq: Fast | Below (1/9 DA) | 1/9 DA assigned Fast 5.7 Mbit/s (1 DA measured) |
≥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.6d - 11.8d (varies) (≥5/9 DA) [Stricter] moria1: ≥6126.3d |
|
| Prereq: V2Dir | Below (0/9 DA) | 0/9 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥5/9 DA) | |
| Uptime | Below (1/9 DA) | 4.6d (R) | ≥96h as each authority sees it (MinUptimeHidServDirectoryV2) (≥5/9 DA) [Stricter] moria1: ≥98% WFU and ≥9.8d Time Known |
|
| Guard | Prereq: Fast | Below (1/9 DA) | 1/9 DA assigned Fast 5.7 Mbit/s (1 DA measured) |
≥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.6d - 11.8d (varies) (≥5/9 DA) [Stricter] moria1: ≥6126.3d |
|
| 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: 70.1% (0/9 DA above threshold) | ≥98% (≥5/9 DA) | |
| Time Known | Below (1/9 DA) | Median: 14.4d (1/9 DA above threshold) | ≥8 days (≥5/9 DA) | |
| Bandwidth | Below (0/9 DA) | 5.7 Mbit/s (1 DA measured) | ≥16.8 Mbit/s (AuthDirGuardBWGuarantee) OR top 25% (≥80.0 Mbit/s-272.0 Mbit/s) (≥5/9 DA) | |
| Exit | Exit Policy | Below (0/9 DA) | Port 80: No | Port 443: No (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-09 23:15:08).
Capacity (Relay Reported)
- Observed Bandwidth
- 8.81 Mbit/s
- Advertised Bandwidth
- 8.39 Mbit/s
- Rate Limit
- 8.39 Mbit/s
- Burst Limit
- 16.78 Mbit/s
- Total Data
-
6.1 TB
(6 months)
1mo: 1.5 TB | 6mo: 6.1 TB
Measurement (Directory Authority Verified)
Source: CollecTor — fetched 2026-11-09 23:15:08
- Measured By
-
1/7
Bandwidth Authorities
Not measured by: dannenberg, faravahar, gabelmoo, longclaw, moria1, tor26 - Consensus Weight
- 160.0 Kbit/s (Unmeasured)
- Measured Min / Max
- 5.7 Mbit/s / 5.7 Mbit/s
History
Uptime Metrics
- Current Status
- DOWN 2d 12h 16m ago
- Overall Uptime (1M/6M/1Y/5Y)
- 56.9%/80.0%/0.0%/0.0%
- Flag Uptime (1M/6M/1Y/5Y)
- 55.2%/79.4%/—/—
- Hibernating
- No
Timestamps
- First Seen
- 3mo 1w 3d ago (2026-08-01 04:00:00)
- Last Seen
- 2d 12h 16m ago (2026-11-07 12:00:00)
- Last Restarted
- 4d 15h 4m ago (2026-11-05 09:11:41)
- Last Changed Address
- 2026-08-01 04:00:00
Evaluated 2026-11-10 00:16 UTC. /details snapshot 2026-11-09 22:00:00 UTC (cached 31m ago). /bandwidth snapshot 2026-11-09 12:00:00 UTC (cached 10h 31m 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
- 8.39 Mbit/s
- Burst Limit
- 2.1 MB
- Write counter
- 94
- Read counter
- 117
- Reported
- 2026-11-06 21:00 UTC (3 days 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-09 15:00 UTC
- AROI Domain (?)
- Not specified
- Operator Validation
- Unvalidated
- This Relay
- N/A (no AROI configured)
- Contact
- 110@2140.lol
Family Configuration
- Family Support
- None — No family membership configured
- Effective Members: 0
- none
- Effective Member: 1
4BFF9632363B6E0F66FBCE2313477BA309AC7C7E (this relay)
- Alleged Members: 0
- none
- Indirect Members: 0
- none
DNS Health
Not an exit relay — DNS health testing does not apply.Last fetch was at Tue, 10 Nov 2026 00:16:38 GMT.
Data from Tor CollecTor (authority votes, fetched 2026-11-09 23:15:08).
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) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| bastet (US) | Yes | Yes | No | — | Y | Yes | Running, Valid, Fast, Stable | 5.7 Mbit/s (M) | 816.0 Kbit/s | 5.7 Mbit/s (M) | 184.0 Mbit/s OR 16.8 Mbit/s | 70.1% | 98% | 14.4d | 8d | 6.8d | 9.7d | 4.6d | 5.7d | 2026-11-06 03:11:49 | 8.4 Mbit/s (R) |
| dannenberg (DE) | No | — | — | — | Y | No | — | — | — | — | — | — | — | — | — |
| dizum (NL) | No | — | — | — | N | No | — | — | — | — | — | — | — | — | — |
| faravahar (US) | No | — | — | — | Y | No | — | — | — | — | — | — | — | — | — |
| gabelmoo (DE) | No | — | — | — | Y | No | — | — | — | — | — | — | — | — | — |
| longclaw (US) | No | — | — | — | Y | No | — | — | — | — | — | — | — | — | — |
| maatuska (SE) | No | — | — | — | N | No | — | — | — | — | — | — | — | — | — |
| moria1 (US) | No | — | — | — | Y | No | — | — | — | — | — | — | — | — | — |
| tor26 (AT) | No | — | — | — | Y | No | — | — | — | — | — | — | — | — | — |
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
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.
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.