View Relay "torexiteu10a"
Fingerprint: 604914F297CC96523A630B5CF336AE25EE115105 |
Family: 73 relays
|
AS204464
|
Germany
|
Platform: unknown
- Consensus
- In Consensus (8/9 Directory Auths)
- DNS Health
- Not Tested (via exitdnshealth.1aeo.com)
- BW Verified
- 0/7 BW Auths Measured
- Stability
- Incomplete | Unknown
- Reachability
- IPv4: 8/9 | v6: 7/7(Directory Auths)
- BW Weight
- 0 Kbit/s Observed By Relay
- Version
- 0.4.9.14 Recommended
Issues Detected:
-
Not getting the Fast flag
: Only 0/9 authorities vote Fast (5 needed). dizum, longclaw and maatuska used the relay-reported unknown, below the Fast threshold (816.0 Kbit/s). dannenberg, gabelmoo, moria1 and tor26 counted this relay as 0 (no measurement, relay-reported bandwidth ignored). faravahar judged it by bandwidth not shown in the votes.
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 – 296.0 Mbit/s). dizum, longclaw and maatuska used the relay-reported unknown. dannenberg, gabelmoo, moria1 and tor26 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: Time Known below threshold
: 0/9 authorities meet guard-tk (≥8 days; 5 needed). dannenberg, dizum, faravahar, gabelmoo, longclaw, maatuska, moria1 and tor26 have no time-known history (2054 seconds–2057 seconds).
Suggestion: Time Known stays near zero until an authority has observed the relay. Keep it running with the same identity key so those authorities accumulate history. -
Not eligible for Stable flag
: 0/9 authorities meet Stable (uptime or MTBF at or above their own median; 5 needed). dannenberg, dizum, faravahar, gabelmoo, longclaw, maatuska, 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. -
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.
Notes:
- Partial IPv4 reachability: 8/9 authorities can reach this relay
Suggestion: Some authorities cannot reach you: bastet. This may be temporary or due to geographic routing issues.
Addresses
- OR Address
-
62.144.62.10:9002
[2a14:7581:5080::1501]:9002
Reachability (Directory Authorities)
- IPv4
- 8/9
- IPv6
- 7/7 (1 don't test)
Location
- Country
-
Germany
- Interactive Map
- View in RouteFluxMap
Eligible Flags (4):
Running: 8/9 | Valid: 8/9 | V2Dir: 8/9 | Fast: 0/9 | Stable: 0/9 | HSDir: 0/9 | Guard: 0/9 | Exit: 8/9
Eligibility Flag Vote Details
| Flag | Metric | Status | Relay Value | Threshold Required |
|---|---|---|---|---|
| Running | IPv4 Reachability | Meets (8/9 DA) | 8/9 authorities reached relay | ≥5/9 DA ORPort reachable |
| IPv6 Reachability | Meets (7/7 DA) | 7/7 tested authorities reached relay | ≥4/7 tested (majority) (≥4/7 DA) | |
| Valid | Descriptor | Meets (8/9 DA) | 8/9 authorities assigned Valid | Not blacklisted + valid descriptor (≥5/9 DA) |
| V2Dir | DirPort Available | Meets (8/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 (3 DA relay-reported) 0 bit/s (4 DA unmeasured, counted as 0) faravahar: not published |
≥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 (8/9 DA, Voting / Total Eligible) |
≥4.9d - 7.8d (varies) (≥5/9 DA) [Stricter] moria1: ≥10444.8d |
| Uptime | Below (0/9 DA) | N/A (R) | ≥6.8d - 6.8d (varies) (≥5/9 DA) | |
| HSDir | Prereq: Fast | Below (0/9 DA) | 0/9 DA assigned Fast 0 bit/s (3 DA relay-reported) 0 bit/s (4 DA unmeasured, counted as 0) faravahar: not published |
≥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 | ≥4.9d - 7.8d (varies) (≥5/9 DA) [Stricter] moria1: ≥10444.8d |
|
| Prereq: V2Dir | Meets (8/9 DA) | 8/9 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥5/9 DA) | |
| Uptime | Below (0/9 DA) | N/A (R) | ≥96h as each authority sees it (MinUptimeHidServDirectoryV2) (≥5/9 DA) [Stricter] moria1: ≥98% WFU and ≥9.8d Time Known |
|
| Guard | Prereq: Fast | Below (0/9 DA) | 0/9 DA assigned Fast 0 bit/s (3 DA relay-reported) 0 bit/s (4 DA unmeasured, counted as 0) faravahar: not published |
≥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 | ≥4.9d - 7.8d (varies) (≥5/9 DA) [Stricter] moria1: ≥10444.8d |
|
| Prereq: V2Dir | Meets (8/9 DA) | 8/9 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥5/9 DA) | |
| WFU | Partial (8/9 DA) | Majority: 100.0% (8/9 DA above threshold) | ≥98% (≥5/9 DA) | |
| Time Known | Below (0/9 DA) | Median: 0.0d (0/9 DA above threshold) Min/Max: 0.0d / 0.0d (8/9 DA, Voting / Total Eligible) |
≥8 days (≥5/9 DA) | |
| Bandwidth | Below (0/9 DA) | 0 bit/s (3 DA relay-reported) 0 bit/s (4 DA unmeasured, counted as 0) faravahar: not published |
≥16.8 Mbit/s (AuthDirGuardBWGuarantee) OR top 25% (≥80.0 Mbit/s-296.0 Mbit/s) (≥5/9 DA) | |
| Exit | Exit Policy | Meets (8/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-10-25 02:15:06).
Capacity (Relay Reported)
- Observed Bandwidth
- 0.00 Kbit/s
- Advertised Bandwidth
- Unknown
- Rate Limit
- Not set
- Burst Limit
- Not set
- Total Data
- N/A
Measurement (Directory Authority Verified)
Source: CollecTor — fetched 2026-10-25 02:15: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
- Unknown
- 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
- 1h 45m 10s ago (2026-10-25 01:00:00)
- Last Seen
- 1h 45m 10s ago (2026-10-25 01:00:00)
- Last Restarted
- Unknown
- Last Changed Address
- 2026-10-25 01:00:00
Overload status:
Incomplete — not every signal could be evaluated.
(Invalid overload data; No bandwidth record available for this relay)
Evaluated 2026-10-25 02:45 UTC. /details snapshot 2026-10-25 01:00:00 UTC (cached 10s ago). /bandwidth snapshot 2026-10-24 14:00:00 UTC (cached 11h 30m ago).
General Overload (from /details)
- Status
- Invalid overload data
File Descriptor Exhaustion (from /bandwidth)
- Status
- No bandwidth record available for this relay
Rate Limits (from /bandwidth)
- Status
- No bandwidth record available for this relay
- 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-10-24 18:00 UTC
Family Configuration
- Family Support
- MyFamily Only (42) — Legacy only. Consider migrating to Happy Families. | View Full Family (73)
Happy Families (family-cert)
- Effective Members: 0
- none
MyFamily (legacy declarations)
- Effective Members: 42
20A20ECCB4C9C292CCF603DB4C4995F9681C64C0 2C33944BBF18BF973D1C2A1F522448AE8587360F 2CA5A24915B5D465DBBBB32FFE61D7DA0D78A07E 2F7EE80ABDDFF1623409FC29214CC30452EFDE2E 3242E811B599620156000362FA8930230ADF6CE8 3CDE8DDBB3A31EE467590C1D888E7761242E4F17 4093E2559E3BC96BF3023482FC01E5F20980581F 4259F2FD8D3A76BE32AB55E6A0F34A87FE3E5998 44D0C889C001CE1F5BF7257A233F64271404F41C 4AB9C4C2BE4E104AFF2F73F7B7C314FBC4A647B0 4DA23B33228E09D42CBD126694F53DFC0C90429D 4EDE09110232E9D38ACD654C8367CBB8DB12DC00 51E59563E05FFE8C3FCDF53316B804518F47B688 5E876698BAE3F335EDABED5BE30C6329E59CC6C7 5E9883EA533EEB1135F47D5C8A7D06981AEB1979 5EBF883A3D9933294276A4C5436CFCBB8E132C18 604914F297CC96523A630B5CF336AE25EE115105 (this relay) 632DD60E4AEB46B9255057C3786D7C2E58504953 65F297D859AE0C3DE41A9C26F38AA5C25F0B61F7 674C97E78F6E1BCA620B15B2F5F149F31E5EBE9A 698AEF7FB9B0FBA7D0DB35B9A712D5CCC95C5206 6AE3E82AE777B4EB05707D2A74991927AA78409D 6B56BC2F71E7A4227FC48D3FB9D1AACA5967F44E 7D187DC4733D4F353700582D99FA24200905557D 8BBC317A51068066AC68732B287C3462CE60D7F5 8DB2B9E42E49DDA88D5E2D3059E592262E150592 980B0D492D0EF690DB6ADA4E353330EE56F4DC2E 9B91418F4DE75D5B5EEECCF9840600E920D3A642 9CC32255D902A7235F6ABA81101E485242B14A3E A1162EC41791389B8ECDA8FE693029409207EF6D AC03C60EF623919FAB455151CD233F8B941F3ED1 B0EB3EB681C200EB0C5478D71A2FA4921983E654 B3A436DFCA8AE7254CA0F85127BE1D52ACC7ACCD BB893C0B68FE783DF3A3FD29121B94F03E72D1A7 BEB9C9DB6F36B2F768FFAF075EDF0D4340B202D5 C1F8794D9E56CFF5F4FA6612B5F74C2844482BB7 D00845137FCB20CCFEDCB3BD270C5ADE8A31A716 D2EC18164E68DBB7C9389ABC73AFBA58FE25882F D3D4F49E21BA74E2EFB4147CFCC1B08D04FA88EE E9C1E0539226B439D1CEA6081C4832A6066C59AF F0EA0F4F081BCF94D23E806BACE231EE3B22E338 FE11A8AFEC5F6B719DAB8ACCC49845E3678D3DC9
- Alleged Members: 0
- none
- Indirect Members: 0
- none
IPv4 Exit Policy Summary
reject: 22 25 135-139 445 465 587
IPv6 Exit Policy Summary
NoneFull Exit Policy
Last fetch was at Sun, 25 Oct 2026 02:45:09 GMT.
Data from Tor CollecTor (authority votes, fetched 2026-10-25 02: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) | No | — | — | — | Y | No | — | — | — | — | — | — | — | — | — | — |
| dannenberg (DE) | Yes | Yes | Yes | — | Y | Yes | Yes | Running, Valid, V2Dir, Exit | 0 bit/s (U) | 816.0 Kbit/s | 0 bit/s (U) | 296.0 Mbit/s OR 16.8 Mbit/s | 100.0% | 98% | 0.0d | 8d | 0.0d | 6.0d | N/A | 6.9d | 2026-10-25 00:15:48 | — |
| dizum (NL) | Yes | Yes | Yes | — | N | Yes | Yes | Running, Valid, V2Dir, Exit | 0 bit/s (R) | 816.0 Kbit/s | 0 bit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 100.0% | 98% | 0.0d | 8d | 0.0d | 7.7d | N/A | 6.8d | 2026-10-25 00:15:48 | — |
| faravahar (US) | Yes | Yes | Yes | — | Y | Yes | Yes | Running, Valid, V2Dir, Exit | not published | 816.0 Kbit/s | not published | 280.0 Mbit/s OR 16.8 Mbit/s | 100.0% | 98% | 0.0d | 8d | 0.0d | 8.0d | N/A | 6.9d | 2026-10-25 00:15:48 | — |
| gabelmoo (DE) | Yes | Yes | Yes | — | Y | Yes | Yes | Running, Valid, V2Dir, Exit | 0 bit/s (U) | 816.0 Kbit/s | 0 bit/s (U) | 264.0 Mbit/s OR 16.8 Mbit/s | 100.0% | 98% | 0.0d | 8d | 0.0d | 7.8d | N/A | 6.8d | 2026-10-25 00:15:48 | — |
| longclaw (US) | Yes | Yes | Yes | — | Y | Yes | N/T | Running, Valid, V2Dir, Exit | 0 bit/s (R) | 816.0 Kbit/s | 0 bit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 100.0% | 98% | 0.0d | 8d | 0.0d | 8.0d | N/A | 6.8d | 2026-10-25 00:15:48 | — |
| maatuska (SE) | Yes | Yes | Yes | — | N | Yes | Yes | Running, Valid, V2Dir, Exit | 0 bit/s (R) | 816.0 Kbit/s | 0 bit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 100.0% | 98% | 0.0d | 8d | 0.0d | 7.8d | N/A | 6.8d | 2026-10-25 00:15:48 | — |
| moria1 (US) | Yes | Yes | Yes | — | Y | Yes | Yes | Running, Valid, V2Dir, Exit | 0 bit/s (U) | 8.4 Mbit/s | 0 bit/s (U) | 200.0 Mbit/s OR 16.8 Mbit/s | 100.0% | 98% | 0.0d | 8d | 0.0d | 10444.8d | N/A | 6.9d | 2026-10-25 00:15:48 | — |
| tor26 (AT) | Yes | Yes | Yes | — | Y | Yes | Yes | Running, Valid, V2Dir, Exit | 0 bit/s (U) | 816.0 Kbit/s | 0 bit/s (U) | 272.0 Mbit/s OR 16.8 Mbit/s | 100.0% | 98% | 0.0d | 8d | 0.0d | 8.0d | N/A | 6.8d | 2026-10-25 00:15:48 | — |
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.