View Relay "Michal212"
Fingerprint: 67F4C46CC831F30B050CB29B068E8AD3915CBC02 |
Family: 1 relay
|
Michal212 <torsafe777@gmail.com> |
AS211507
|
Hong Kong
|
Linux
- Consensus
- In Consensus (9/9 Directory Auths)
- DNS Health
- Healthy (16.5s, 72nd percentile) (via exitdnshealth.1aeo.com)
- BW Verified
- 5/7 BW Auths Measured 41 Mbit/s Median
- Stability
- Overloaded | UP 6d 11h 9m ago | UP 99% (1M)
- Reachability
- IPv4: 9/9 | v6: 8/8(Directory Auths)
- BW Weight
- 0.00% of Network | 79 Mbit/s Observed By Relay
- Version
- 0.4.9.15 Recommended
Issues Detected:
-
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. -
General Overload Active
: Relay reported general overload at 2026-11-03 12:00 UTC. Reported timestamps use hour precision, so the displayed minute is not an exact incident time. The flag does not identify which trigger fired. Investigation paths are Tor's internal OOM handling, dropped ntor onionskins, and TCP port exhaustion.
Suggestion: Inspect CPU and memory with htop, Tor service logs, host or container memory headroom, and the effective MaxMemInQueues. When the process was killed or restarted, check kernel OOM logs separately. A kernel OOM kill is a different mechanism from Tor freeing memory itself. MetricsPort: tor_relay_load_oom_bytes_total. Broken down by subsys. An increase measures bytes freed by Tor’s internal OOM handling. It is not an invocation count and it is not proof of a kernel OOM kill. Review Tor’s onionskin and drop messages, and whether the CPU is saturated or contended. The general-overload flag does not say this trigger fired. MetricsPort: tor_relay_load_onionskins_total{type="ntor",action="dropped"} and {type="ntor_v3",action="dropped"}. Compare each with the matching action="processed" series. Inspect both supported handshake types. Review Tor logs, socket usage, and the host’s ephemeral-port allocation. On Linux, ss -s and reading net.ipv4.ip_local_port_range are useful starting checks. MetricsPort: tor_relay_load_tcp_exhaustion_total. An increase records additional exhaustion events. See the Tor overload troubleshooting guide.
Addresses
- OR Address
-
45.133.73.28:9001
[2a14:c380:d70:16::a]:9001 - Exit Address
- 45.133.73.28
Reachability (Directory Authorities)
- IPv4
- 9/9
- IPv6
- 8/8 (1 don't test)
Location
- Country
-
Hong Kong
- Interactive Map
- View in RouteFluxMap
Eligible Flags (8):
Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 9/9 | Stable: 8/9 | HSDir: 8/9 | Guard: 8/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) | 21.6 Mbit/s – 76.0 Mbit/s (5 DA measured) 79.3 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 | Partial (8/9 DA) | Median: 13.2d (7/9 DA above threshold) Min/Max: 0.0d / 22.5d (9/9 DA, Voting / Total Eligible) |
≥2.4d - 9.4d (varies) (≥5/9 DA) [Stricter] moria1: ≥7616.8d |
| Uptime | Meets (9/9 DA) | 6.5d (R) | ≥5.2d - 5.5d (varies) (≥5/9 DA) | |
| HSDir | Prereq: Fast | Meets (9/9 DA) | 9/9 DA assigned Fast 21.6 Mbit/s – 76.0 Mbit/s (5 DA measured) 79.3 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.4d - 9.4d (varies) (≥5/9 DA) [Stricter] moria1: ≥7616.8d |
|
| Prereq: V2Dir | Meets (9/9 DA) | 9/9 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥5/9 DA) | |
| Uptime | Partial (8/9 DA) | 6.5d (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 21.6 Mbit/s – 76.0 Mbit/s (5 DA measured) 79.3 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.4d - 9.4d (varies) (≥5/9 DA) [Stricter] moria1: ≥7616.8d |
|
| 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.9% (8/9 DA above threshold) Min/Max: 0.0% / 100.0% (9/9 DA, Voting / Total Eligible) |
≥98%; dizum: ≥97.86% (≥5/9 DA) | |
| Time Known | Partial (8/9 DA) | Median: 18.1d (8/9 DA above threshold) Min/Max: 0.0d / 24.8d (9/9 DA, Voting / Total Eligible) |
≥8 days (≥5/9 DA) | |
| Bandwidth | Meets (9/9 DA) | 21.6 Mbit/s – 76.0 Mbit/s (5 DA measured) 79.3 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-04 17:15:06).
Capacity (Relay Reported)
- Observed Bandwidth
- 79.32 Mbit/s
- Advertised Bandwidth
- 79.32 Mbit/s
- Rate Limit
- 8.59 Gbit/s
- Burst Limit
- 8.59 Gbit/s
- Total Data
-
25 TB
(6 months)
1mo: 20 TB | 6mo: 25 TB
Measurement (Directory Authority Verified)
Source: CollecTor — fetched 2026-11-04 17:15:06
- Measured By
-
5/7
Bandwidth Authorities
Not measured by: faravahar, longclaw - Consensus Weight
- 41.6 Mbit/s (median of 5 measurements)
- Measured Min / Max
- 21.6 Mbit/s / 76.0 Mbit/s
- Deviation
- 54.4 Mbit/s [Warning] High variation
Network Participation:
Consensus Weight:
0.0016% of network
(27th pctl)
|
Guard:
N/A |
Middle:
N/A |
Exit:
0.0050% (6th pctl)
History
Uptime Metrics
- Current Status
- UP 6d 11h 9m ago
- Overall Uptime (1M/6M/1Y/5Y)
- 99.6%/99.7%/0.0%/0.0%
- Flag Uptime (1M/6M/1Y/5Y)
- Matches Overall Uptime (99.6%/99.7%/0.0%/0.0%)
- Hibernating
- No
Timestamps
- First Seen
- 1mo 2w 3d ago (2026-09-18 15:00:00)
- Last Seen
- 2h 15m 39s ago (2026-11-04 15:00:00)
- Last Restarted
- 6d 11h 9m ago (2026-10-29 06:06:31)
- Last Changed Address
- 2026-09-18 15:00:00
[Warning] OVERLOADED
— General overload at 2026-11-03 12:00 UTC
Evaluated 2026-11-04 17:15 UTC. /details snapshot 2026-11-04 15:00:00 UTC (cached 33s ago). /bandwidth snapshot 2026-11-04 05: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
- Reported
- When
- 2026-11-03 12:00 UTC (1 day ago)
The general-overload flag does not say which trigger fired. Possible paths are Tor’s internal memory handling, dropped ntor handshakes, and TCP port exhaustion. Allium treats a valid report as eligible for 72 hours; that cutoff is not proof the relay recovered then.
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
- —
What to check
-
Tor internal memory pressure
Inspect CPU and memory with htop, Tor service logs, host or container memory headroom, and the effective MaxMemInQueues. When the process was killed or restarted, check kernel OOM logs separately. A kernel OOM kill is a different mechanism from Tor freeing memory itself.MetricsPort:
tor_relay_load_oom_bytes_total— Broken down by subsys. An increase measures bytes freed by Tor’s internal OOM handling. It is not an invocation count and it is not proof of a kernel OOM kill. -
ntor handshake pressure
Review Tor’s onionskin and drop messages, and whether the CPU is saturated or contended. The general-overload flag does not say this trigger fired.MetricsPort:
tor_relay_load_onionskins_total{type="ntor",action="dropped"} and {type="ntor_v3",action="dropped"}— Compare each with the matching action="processed" series. Inspect both supported handshake types. -
TCP port exhaustion
Review Tor logs, socket usage, and the host’s ephemeral-port allocation. On Linux, ss -s and reading net.ipv4.ip_local_port_range are useful starting checks.MetricsPort:
tor_relay_load_tcp_exhaustion_total— An increase records additional exhaustion events.
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-04 08:00 UTC
- AROI Domain (?)
- Not specified
- Operator Validation
- Unvalidated
- This Relay
- N/A (no AROI configured)
- Contact
- Michal212 <torsafe777@gmail.com>
Family Configuration
- Family Support
- None — No family membership configured
Happy Families (family-cert)
- Effective Members: 0
- none
MyFamily (legacy declarations)
- Effective Member: 1
67F4C46CC831F30B050CB29B068E8AD3915CBC02 (this relay)
- Alleged Members: 0
- none
- Indirect Members: 0
- none
DNS Health
- Status
- Healthy (avg. 16.5s, 72nd percentile)
- Query Domain
455ace6caf5e4c448805390d87259aa0.67f4c46c.tor.exit.validator.1aeo.com- DNS Result
-
Resolved to
64.65.4.1 - Upstream Resolver
-
Google
(public resolver)
Google 100% (~51 estimated queries) - Cross-Validation
- 4/4 instances succeeded
- First Hop
- Unnamed (PL) 9C4F2F5770AF9428C927C27E6233E1B5A355A4B5
- Exit Address Used
45.133.73.28- Per-Instance Results
-
Cross Validation Attempt 1: Success, 21.6s (cv1_w2) Cross Validation Attempt 2: Success, 15.0s (cv2_w2) Cross Validation Attempt 3: Success, 11.6s (cv3_w2) Cross Validation Attempt 4: Success, 18.0s (cv4_w2)
Tested: 2026-11-03 20:09:56 UTC
Source: exitdnshealth.1aeo.com
IPv4 Exit Policy Summary
reject: 25 119 135-139 445 563 1214 4661-4666 6346-6429 6699 6881-6999
IPv6 Exit Policy Summary
reject: 25 119 135-139 445 563 1214 4661-4666 6346-6429 6699 6881-6999
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 45.133.73.28:* reject 45.137.201.54:* 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 Wed, 04 Nov 2026 17:15:39 GMT.
Data from Tor CollecTor (authority votes, fetched 2026-11-04 17:15: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 | 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 | 72.0 Mbit/s (M) | 816.0 Kbit/s | 72.0 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s | 99.8% | 98% | 18.1d | 8d | 13.2d | 8.4d | 6.5d | 5.2d | 2026-11-04 06:06:58 | 72.0 Mbit/s (M) |
| dannenberg (DE) | Yes | Yes | Yes | — | Y | Yes | Yes | Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit | 21.6 Mbit/s (M) | 816.0 Kbit/s | 21.6 Mbit/s (M) | 272.0 Mbit/s OR 16.8 Mbit/s | 100.0% | 98% | 24.8d | 8d | 22.5d | 9.4d | 6.5d | 5.5d | 2026-11-04 06:06:58 | 21.6 Mbit/s (M) |
| dizum (NL) | Yes | Yes | Yes | — | N | Yes | Yes | Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit | 79.3 Mbit/s (R) | 816.0 Kbit/s | 79.3 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 98.5% | 98% | 16.7d | 8d | 10.5d | 6.8d | 6.5d | 5.5d | 2026-11-04 06:06:58 | 79.3 Mbit/s (R) |
| faravahar (US) | Yes | Yes | Yes | — | Y | Yes | Yes | Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit | 79.3 Mbit/s (R) | 816.0 Kbit/s | 79.3 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 99.9% | 98% | 17.8d | 8d | 10.4d | 6.5d | 6.5d | 5.5d | 2026-11-04 06:06:58 | 79.3 Mbit/s (R) |
| gabelmoo (DE) | Yes | Yes | Yes | — | Y | Yes | Yes | Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit | 28.0 Mbit/s (M) | 816.0 Kbit/s | 28.0 Mbit/s (M) | 248.0 Mbit/s OR 16.8 Mbit/s | 100.0% | 98% | 24.8d | 8d | 22.5d | 10.8d | 6.5d | 5.5d | 2026-11-04 06:06:58 | 28.0 Mbit/s (M) |
| longclaw (US) | Yes | Yes | Yes | — | Y | Yes | N/T | Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit | 79.3 Mbit/s (R) | 816.0 Kbit/s | 79.3 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 100.0% | 98% | 24.6d | 8d | 22.3d | 10.9d | 6.5d | 5.3d | 2026-11-04 06:06:58 | 79.3 Mbit/s (R) |
| maatuska (SE) | Yes | Yes | Yes | — | N | Yes | Yes | Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit | 79.3 Mbit/s (R) | 816.0 Kbit/s | 79.3 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 99.0% | 98% | 17.0d | 8d | 2.9d | 2.4d | 6.5d | 5.5d | 2026-11-04 06:06:58 | 79.3 Mbit/s (R) |
| moria1 (US) | Yes | Yes | Yes | — | Y | Yes | Yes | Valid, V2Dir, Fast, Exit | 76.0 Mbit/s (M) | 8.4 Mbit/s | 76.0 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s | 0.0% | 98% | 0.0d | 8d | 0.0d | 7616.8d | 6.5d | 5.5d | 2026-11-04 06:06:58 | 76.0 Mbit/s (M) |
| tor26 (AT) | Yes | Yes | Yes | — | Y | Yes | Yes | Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit | 41.6 Mbit/s (M) | 816.0 Kbit/s | 41.6 Mbit/s (M) | 256.0 Mbit/s OR 16.8 Mbit/s | 100.0% | 98% | 24.8d | 8d | 22.5d | 10.7d | 6.5d | 5.5d | 2026-11-04 06:06:58 | 41.6 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.