View Relay "torexiteu06"
Fingerprint: C87D32683EC034188E7FF78610FAA00C6939AA4D |
Family: 31 relays
|
NextServ NOC <noc@nextserv.eu> |
AS204464
|
Germany
|
Linux
- Consensus
- In Consensus (9/9 Directory Auths)
- BW Verified
- 5/7 BW Auths Measured 8 Kbit/s Median
- Stability
- Not Overloaded | UP 13h 39m 36s ago
- Reachability
- IPv4: 9/9 | v6: 8/8 (Directory Auths)
- BW Weight
- 0.00% of Network | 49 Mbit/s Observed By Relay
- Version
- 0.4.9.14 Recommended
Issues Detected:
-
Not getting the Fast flag
: Only 3/9 authorities vote Fast (5 needed). bastet, dannenberg, gabelmoo, moria1 and tor26 measured this relay at 8.0 Kbit/s, below the Fast threshold (816.0 Kbit/s; moria1: 8.4 Mbit/s). faravahar judged it by bandwidth not shown in the votes. Its consensus weight, the median of the 5 bandwidth-scanner measurements, is 8.0 Kbit/s.
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
: 3/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). bastet, dannenberg, gabelmoo, moria1 and tor26 measured this relay at 8.0 Kbit/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: Time Known below threshold
: 0/9 authorities meet guard-tk (≥8 days; 5 needed). bastet, dannenberg, dizum, faravahar, gabelmoo, longclaw, maatuska, moria1 and tor26 have known this relay for 1.1 days–1.2 days.
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, 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.
Addresses
- OR Address
-
torexit.eu
62.144.62.6:9105
[2a14:7581:5080::1105]:9105
Reachability (Directory Authorities)
- IPv4
- 9/9
- IPv6
- 8/8 (1 don't test)
Location
- Country
-
Germany
- Interactive Map
- View in RouteFluxMap
Eligible Flags (3):
Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 3/9 | Stable: 1/9 | HSDir: 0/9 | Guard: 0/9 | Exit: 0/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 | Below (3/9 DA) | 8.0 Kbit/s (5 DA measured) 49.6 Mbit/s (3 DA relay-reported) 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: 1.2d (1/9 DA above threshold) Min/Max: 0.6d / 10374.8d (9/9 DA, Voting / Total Eligible) |
≥4.8d - 7.7d (varies) (≥5/9 DA) [Stricter] moria1: ≥10819.8d |
| Uptime | Below (0/9 DA) | 0.6d (R) | ≥6.2d - 6.5d (varies) (≥5/9 DA) | |
| HSDir | Prereq: Fast | Below (3/9 DA) | 3/9 DA assigned Fast 8.0 Kbit/s (5 DA measured) 49.6 Mbit/s (3 DA relay-reported) 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 (1/9 DA) | 1/9 DA assigned Stable | ≥4.8d - 7.7d (varies) (≥5/9 DA) [Stricter] moria1: ≥10819.8d |
|
| Prereq: V2Dir | Meets (9/9 DA) | 9/9 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥5/9 DA) | |
| Uptime | Below (0/9 DA) | 0.6d (R) | ≥96h as each authority sees it (MinUptimeHidServDirectoryV2) (≥5/9 DA) [Stricter] moria1: ≥98% WFU and ≥9.9d Time Known |
|
| Guard | Prereq: Fast | Below (3/9 DA) | 3/9 DA assigned Fast 8.0 Kbit/s (5 DA measured) 49.6 Mbit/s (3 DA relay-reported) 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 (1/9 DA) | 1/9 DA assigned Stable | ≥4.8d - 7.7d (varies) (≥5/9 DA) [Stricter] moria1: ≥10819.8d |
|
| Prereq: V2Dir | Meets (9/9 DA) | 9/9 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥5/9 DA) | |
| WFU | Partial (7/9 DA) | Majority: 100.0% (7/9 DA above threshold) Min/Med/Max: 96.1% / 100.0% / 100.0% (9/9 DA, Voting / Total Eligible) |
≥98% (≥5/9 DA) | |
| Time Known | Below (0/9 DA) | Median: 1.2d (0/9 DA above threshold) Min/Max: 1.1d / 1.2d (9/9 DA, Voting / Total Eligible) |
≥8 days (≥5/9 DA) | |
| Bandwidth | Below (3/9 DA) | 8.0 Kbit/s (5 DA measured) 49.6 Mbit/s (3 DA relay-reported) 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 | 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-10-23 16:45:07).
Capacity (Relay Reported)
- Observed Bandwidth
- 49.63 Mbit/s
- Advertised Bandwidth
- 49.63 Mbit/s
- Rate Limit
- 838.86 Mbit/s
- Burst Limit
- 1.05 Gbit/s
- Total Data
- N/A
Measurement (Directory Authority Verified)
Source: CollecTor — fetched 2026-10-23 16:45:07
- Measured By
-
5/7
Bandwidth Authorities
Not measured by: faravahar, longclaw - Consensus Weight
- 8.0 Kbit/s (median of 5 measurements)
- Measured Min / Max
- 8.0 Kbit/s / 8.0 Kbit/s
Network Participation:
Consensus Weight:
0.0000% of network
(0th pctl)
|
Guard:
N/A |
Middle:
0.0000% (0th pctl) |
Exit:
N/A
Uptime Metrics
- Current Status
- UP 13h 39m 36s ago
- Overall Uptime (1M/6M/1Y/5Y)
- 0.0%/0.0%/0.0%/0.0%
- Flag Uptime (1M/6M/1Y/5Y)
- Matches Overall Uptime (0.0%/0.0%/0.0%/0.0%)
- Hibernating
- No
Timestamps
- First Seen
- 1d 4h 45m ago (2026-10-22 12:00:00)
- Last Seen
- 1h 45m 16s ago (2026-10-23 15:00:00)
- Last Restarted
- 13h 39m 36s ago (2026-10-23 03:05:40)
- Last Changed Address
- 2026-10-22 12:00:00
Overload Status:
Not Overloaded — No overload conditions reported.
Evaluated 2026-10-23 16:45 UTC. /details snapshot 2026-10-23 15:00:00 UTC (cached 19s ago). /bandwidth snapshot 2026-10-23 13:00:00 UTC (cached 2h 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
History
Operator Identity
Source: AROI Validation API — 2026-10-23 08:00 UTC
- AROI Domain (?)
- Not specified
- Operator Validation
- Unvalidated
- This Relay
- N/A (no AROI configured)
- Contact
- NextServ NOC <noc@nextserv.eu>
Family Configuration
- Family Support
- Happy Families (31) — Has family-cert in server descriptor (guide) | View Full Family (31)
Happy Families (family-cert)
- Effective Members: 31
04F31F4D801284C31D13DDE255F98A3184012710 066D2DD0156291D749D726478DF4F824E8A681B1 1658CCB43F2B028D9D5DDB69837264AF64EA0A43 2A153AF19E78F91EE8EB6A0E368BC41ABAEE1F2A 326D7BFCDF900C6ECE94B4C0FA2DFF657BCAD480 379C3A3551611A5E558D2CC48BDFA6536A688D2A 3D5E480AC65769912BC9A32ED134F3827ACD20F3 4842EB63705E861D1FABACC8851BBB579258BA60 4E2B541C30D4B03E290F728281D187F85F5B4A3B 55E29BEB592C1AEF492489155AEBAC8111465C33 5909F7AE6D97C24CAEF8CE909B143B6AB2BBC0C5 5F4C24A25CB83802FEFE135FE3B080ECA275CA21 60281386E18309923F76126144AE001BF5B6BBC7 6192EAE141ABA1E43C18CD18F829B3C434ACC8DF 6A5E70DE22BA452E97AF91FE5AB97A1508AA059F 782B602DF3B6CEF97A6E2D6D1D52885337ABD4DE 7FB586F3856828FDAD40667783AFDBD03F44A682 849CDDA3BC052D43D012A0753E119B8D7E2AAA85 856C818C61F5F0EBB8C5902DA76F4EF220627878 8D66E017A677FF4B630A9B9CF56F68268F71E1EB 947CF83FDB76A12F83AD82D6A9537FEA2D93F501 9DBA1CF5314F86894BEC29C4C38C66DBAB0BF260 A1776DF62C44F4B393D479A830CFBED01FA9E368 C712A9CB690BE476E97DEF07F545D0117D3A196D C87D32683EC034188E7FF78610FAA00C6939AA4D (this relay) CC0552FBDB78EA87E66F36DF7E282A821B622BE8 DB2E82F0D14A72E6BFCA0E19AFF73C1833DE84AA DB4DA81FF69D5DBE85F3B67B8FF8E2EA59A04801 E8AA9327ACACF3D354AF2A66FE3850F64AEF6745 F1239D60A468B2803EFD0C167EA84A5AD9400C62 FC51377F580C3320D510D692F5918F54A4556837
MyFamily (legacy declarations) — none
DNS Health
Not an exit relay — DNS health testing does not apply.Last fetch was at Fri, 23 Oct 2026 16:45:16 GMT.
Data from Tor CollecTor (authority votes, fetched 2026-10-23 16:45:07).
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 | No | — | Y | Yes | Yes | Running, Valid, V2Dir | 8.0 Kbit/s (M) | 816.0 Kbit/s | 8.0 Kbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s | 100.0% | 98% | 1.2d | 8d | 1.2d | 4.8d | 0.6d | 6.5d | 2026-10-23 11:35:44 | 8.0 Kbit/s (M) |
| dannenberg (DE) | Yes | Yes | No | — | Y | Yes | Yes | Running, Valid, V2Dir | 8.0 Kbit/s (M) | 816.0 Kbit/s | 8.0 Kbit/s (M) | 296.0 Mbit/s OR 16.8 Mbit/s | 100.0% | 98% | 1.2d | 8d | 1.2d | 5.8d | 0.6d | 6.6d | 2026-10-23 11:35:44 | 8.0 Kbit/s (M) |
| dizum (NL) | Yes | Yes | No | — | N | Yes | Yes | Running, Valid, V2Dir, Fast | 49.6 Mbit/s (R) | 816.0 Kbit/s | 49.6 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 100.0% | 98% | 1.2d | 8d | 1.2d | 7.5d | 0.6d | 6.5d | 2026-10-23 11:35:44 | 49.6 Mbit/s (R) |
| faravahar (US) | Yes | Yes | No | — | Y | Yes | Yes | Running, Valid, V2Dir | not published | 816.0 Kbit/s | not published | 280.0 Mbit/s OR 16.8 Mbit/s | 97.5% | 98% | 1.1d | 8d | 0.6d | 7.9d | 0.6d | 6.9d | 2026-10-23 11:35:44 | 49.6 Mbit/s (R) |
| gabelmoo (DE) | Yes | Yes | No | — | Y | Yes | Yes | Running, Valid, V2Dir | 8.0 Kbit/s (M) | 816.0 Kbit/s | 8.0 Kbit/s (M) | 264.0 Mbit/s OR 16.8 Mbit/s | 100.0% | 98% | 1.2d | 8d | 1.2d | 7.7d | 0.6d | 6.5d | 2026-10-23 11:35:44 | 8.0 Kbit/s (M) |
| longclaw (US) | Yes | Yes | No | — | Y | Yes | — | Running, Valid, V2Dir, Fast | 49.6 Mbit/s (R) | 816.0 Kbit/s | 49.6 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 100.0% | 98% | 1.2d | 8d | 1.2d | 7.8d | 0.6d | 6.5d | 2026-10-23 11:35:44 | 49.6 Mbit/s (R) |
| maatuska (SE) | Yes | Yes | No | — | N | Yes | Yes | Running, Valid, V2Dir, Fast | 49.6 Mbit/s (R) | 816.0 Kbit/s | 49.6 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 100.0% | 98% | 1.2d | 8d | 1.2d | 7.6d | 0.6d | 6.4d | 2026-10-23 11:35:44 | 49.6 Mbit/s (R) |
| moria1 (US) | Yes | Yes | No | — | Y | Yes | Yes | Running, Valid, V2Dir, Stable | 8.0 Kbit/s (M) | 8.4 Mbit/s | 8.0 Kbit/s (M) | 200.0 Mbit/s OR 16.8 Mbit/s | 96.1% | 98% | 1.2d | 8d | 10374.8d | 10819.8d | 0.6d | 6.2d | 2026-10-23 11:35:44 | 8.0 Kbit/s (M) |
| tor26 (AT) | Yes | Yes | No | — | Y | Yes | Yes | Running, Valid, V2Dir | 8.0 Kbit/s (M) | 816.0 Kbit/s | 8.0 Kbit/s (M) | 272.0 Mbit/s OR 16.8 Mbit/s | 100.0% | 98% | 1.2d | 8d | 1.2d | 7.7d | 0.6d | 6.8d | 2026-10-23 11:35:44 | 8.0 Kbit/s (M) |
— = not tested/available • 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.