View Relay "BingChaling"
Fingerprint: 57F5F24FC8DCDE6FA51D8F067FFED78D754D18A9 |
Family: 1 relay
|
AS11232
|
United States of America
|
Linux
- Consensus
- Not In Consensus (2/9 Directory Auths, need 5)
- DNS Health
- Not Tested (via exitdnshealth.1aeo.com)
- BW Verified
- 0/7 BW Auths Measured
- Stability
- Not Overloaded | DOWN 1d 3h 45m ago
- Reachability
- IPv4: 2/9 | v6: None configured(Directory Auths)
- BW Weight
- 0 Kbit/s Observed By Relay
- Version
- 0.4.9.15 Recommended
Issues Detected:
-
Not in consensus
: Only 2/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 2/9 authorities can reach this relay
Suggestion: Authorities that cannot reach you: dannenberg, dizum, faravahar, gabelmoo, longclaw, 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. -
Not getting the Fast flag
: Only 0/9 authorities vote Fast (5 needed). maatuska used the relay-reported unknown, below the Fast threshold (816.0 Kbit/s). bastet 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
: 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% (80.0 Mbit/s – 192.0 Mbit/s). maatuska used the relay-reported unknown. bastet 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%; 5 needed). bastet and maatuska measured 4.6%–8.0%.
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; 5 needed). bastet and maatuska have known this relay for 8.5 hours–13.5 hours.
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
: 0/9 authorities meet Stable (uptime or MTBF at or above their own median; 5 needed). bastet and maatuska 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. -
Low bandwidth authority measurements
: Only 0/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
-
24-220-75-227-dynamic.midco.net
24.220.75.227:9001
Reachability (Directory Authorities)
- IPv4
- 2/9
- IPv6
- None configured
Location
- Country
-
United States of America
- Interactive Map
- View in RouteFluxMap
Eligible Flags (0):
Running: 2/9 | Valid: 2/9 | V2Dir: 2/9 | Fast: 0/9 | Stable: 0/9 | HSDir: 0/9 | Guard: 0/9 | Exit: 2/9
Eligibility Flag Vote Details
| Flag | Metric | Status | Relay Value | Threshold Required |
|---|---|---|---|---|
| Running | IPv4 Reachability | Below (2/9 DA) | 2/9 authorities reached relay | ≥5/9 DA ORPort reachable |
| Valid | Descriptor | Partial (2/9 DA) | 2/9 authorities assigned Valid | Not blacklisted + valid descriptor (≥5/9 DA) |
| V2Dir | DirPort Available | Meets (2/9 DA) | Tunnelled: Yes (no DirPort) (R) | Tunnelled directory via ORPort or DirPort (≥5/9 DA) |
| Fast | Speed | Below (0/9 DA) | 0 bit/s (1 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 (0/9 DA) | Median: 0.0d (0/9 DA above threshold) Min/Max: 0.0d / 0.0d (2/9 DA, Voting / Total Eligible) |
≥2.5d - 8.5d (varies) (≥5/9 DA) [Stricter] moria1: ≥8467.5d |
| Uptime | Below (0/9 DA) | 1.2d (R) | ≥3.2d - 4.0d (varies) (≥5/9 DA) | |
| HSDir | Prereq: Fast | Below (0/9 DA) | 0/9 DA assigned Fast 0 bit/s (1 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 (0/9 DA) | 0/9 DA assigned Stable | ≥2.5d - 8.5d (varies) (≥5/9 DA) [Stricter] moria1: ≥8467.5d |
|
| Prereq: V2Dir | Below (2/9 DA) | 2/9 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥5/9 DA) | |
| Uptime | Below (0/9 DA) | 1.2d (R) | ≥96h as each authority sees it (MinUptimeHidServDirectoryV2) (≥5/9 DA) [Stricter] moria1: ≥98% WFU and ≥9.9d Time Known |
|
| Guard | Prereq: Fast | Below (0/9 DA) | 0/9 DA assigned Fast 0 bit/s (1 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 (0/9 DA) | 0/9 DA assigned Stable | ≥2.5d - 8.5d (varies) (≥5/9 DA) [Stricter] moria1: ≥8467.5d |
|
| Prereq: V2Dir | Below (2/9 DA) | 2/9 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥5/9 DA) | |
| WFU | Below (0/9 DA) | Median: 6.3% (0/9 DA above threshold) Min/Max: 4.6% / 8.0% (2/9 DA, Voting / Total Eligible) |
≥98% (≥5/9 DA) | |
| Time Known | Below (0/9 DA) | Median: 0.5d (0/9 DA above threshold) Min/Max: 0.4d / 0.6d (2/9 DA, Voting / Total Eligible) |
≥8 days (≥5/9 DA) | |
| Bandwidth | Below (0/9 DA) | 0 bit/s (1 DA relay-reported) 0 bit/s (1 DA unmeasured, counted as 0) |
≥16.8 Mbit/s (AuthDirGuardBWGuarantee) OR top 25% (≥80.0 Mbit/s-288.0 Mbit/s) (≥5/9 DA) | |
| Exit | Exit Policy | Partial (2/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-02 07:45:06).
Capacity (Relay Reported)
- Observed Bandwidth
- 0.00 Kbit/s
- Advertised Bandwidth
- Unknown
- Rate Limit
- 81.92 Mbit/s
- Burst Limit
- 163.84 Mbit/s
- Total Data
- N/A
Measurement (Directory Authority Verified)
Source: CollecTor — fetched 2026-11-02 07:45:06
- Measured By
-
0/7
Bandwidth Authorities
Not measured by: bastet, dannenberg, faravahar, gabelmoo, longclaw, moria1, tor26 - Consensus Weight
- 0 bit/s (Unmeasured)
- Measured Min / Max
- N/A / N/A
Network Participation:
Consensus Weight:
N/A
|
Guard:
N/A |
Middle:
N/A |
Exit:
N/A
Uptime Metrics
- Current Status
- DOWN 1d 3h 45m 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
- 1d 3h 45m ago (2026-11-01 04:00:00)
- Last Seen
- 1d 3h 45m ago (2026-11-01 04:00:00)
- Last Restarted
- 1d 4h 46m ago (2026-11-01 02:58:40)
- Last Changed Address
- 2026-11-01 04:00:00
Overload Status:
Not Overloaded — No overload conditions reported.
Evaluated 2026-11-02 07:45 UTC. /details snapshot 2026-11-02 06:00:00 UTC (cached 24s ago). /bandwidth snapshot 2026-11-02 05:00:00 UTC (cached 1h 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
Operator Identity
Source: AROI Validation API — 2026-11-01 22:00 UTC
Family Configuration
- Family Support
- None — No family membership configured
Happy Families (family-cert)
- Effective Members: 0
- none
MyFamily (legacy declarations)
- Effective Member: 1
57F5F24FC8DCDE6FA51D8F067FFED78D754D18A9 (this relay)
- Alleged Members: 0
- none
- Indirect Members: 0
- none
IPv4 Exit Policy Summary
reject: 25 119 135-139 445 563 1214 4661-4666 6346-6429 6699 6881-6999
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 24.220.75.227:* reject *:25 reject *:119 reject *:135-139 reject *:445 reject *:563 reject *:1214 reject *:4661-4666 reject *:6346-6429 reject *:6699 reject *:6881-6999 accept *:*
Last fetch was at Mon, 02 Nov 2026 07:45:27 GMT.
Data from Tor CollecTor (authority votes, fetched 2026-11-02 07:45:06).
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 | Yes | — | Y | Yes | Valid, V2Dir, Exit | 0 bit/s (U) | 816.0 Kbit/s | 0 bit/s (U) | 192.0 Mbit/s OR 16.8 Mbit/s | 4.6% | 98% | 0.6d | 8d | 0.0d | 7.1d | 1.2d | 3.4d | 2026-11-01 03:18:41 | — |
| 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) | Yes | Yes | Yes | — | N | Yes | Valid, V2Dir, Exit | 0 bit/s (R) | 816.0 Kbit/s | 0 bit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 8.0% | 98% | 0.4d | 8d | 0.0d | 2.5d | 1.2d | 3.2d | 2026-11-01 03:18:41 | — |
| 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
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.