View Relay "as215248tor3f"
Fingerprint: C4C2BDBC25C97ADAC6B85EE51BD1F87B1C1C31E0 |
Operator: as215248.net v3
(54 relays)
✓ Validated
⚠ this relay: Misconfigured|
Family: 54 relays
|
email:b[]stiaanbr.ink... |
AS215248
|
Netherlands
|
Linux
- Consensus
- In Consensus (8/10 Directory Auths)
- BW Verified
- 0/8 BW Auths Measured
- Stability
- Incomplete | UP 3h 50m 33s ago
- Reachability
- IPv4: 8/10 | v6: 7/7(Directory Auths)
- BW Weight
- 0 Kbit/s Observed By Relay
- Version
- 0.4.9.15 Recommended
Issues Detected:
-
Not getting the Fast flag
: Only 0/10 authorities vote Fast (6 needed). dizum, faravahar, longclaw and maatuska used the relay-reported unknown, below the Fast threshold (816.0 Kbit/s). E30CF7B3, gabelmoo, moria1 and tor26 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/10 authorities credit this relay with enough bandwidth for Guard (6 needed): at least 16.8 Mbit/s (AuthDirGuardBWGuarantee) or a place in their top 25% (80.0 Mbit/s – 256.0 Mbit/s). dizum, faravahar, longclaw and maatuska used the relay-reported unknown. E30CF7B3, 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/10 authorities meet guard-tk (≥8 days; E30CF7B3: ≥15 hours 54 minutes 57 seconds; 6 needed). E30CF7B3, dizum, faravahar, gabelmoo, longclaw, maatuska, moria1 and tor26 have known this relay for 1.9 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/10 authorities meet Stable (uptime or MTBF at or above their own median; 6 needed). E30CF7B3, 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/8 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/10 authorities can reach this relay
Suggestion: Some authorities cannot reach you: 5947BB57, dannenberg. This may be temporary or due to geographic routing issues.
Addresses
- OR Address
-
tor3.as215248.net
103.149.168.187:9006
[2a14:38c0:2::187]:9006
Reachability (Directory Authorities)
- IPv4
- 8/10
- IPv6
- 7/7 (1 don't test)
Location
- Country
-
Netherlands
- Interactive Map
- View in RouteFluxMap
Eligible Flags (3):
Running: 8/10 | Valid: 8/10 | V2Dir: 8/10 | Fast: 0/10 | Stable: 0/10 | HSDir: 0/10 | Guard: 0/10 | Exit: 0/10
Eligibility Flag Vote Details
| Flag | Metric | Status | Relay Value | Threshold Required |
|---|---|---|---|---|
| Running | IPv4 Reachability | Meets (8/10 DA) | 8/10 authorities reached relay | ≥6/10 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/10 DA) | 8/10 authorities assigned Valid | Not blacklisted + valid descriptor (≥6/10 DA) |
| V2Dir | DirPort Available | Meets (8/10 DA) | Tunnelled: Yes (no DirPort) (R) | Tunnelled directory via ORPort or DirPort (≥6/10 DA) |
| Fast | Speed | Below (0/10 DA) | 0 bit/s (4 DA relay-reported) 0 bit/s (4 DA unmeasured, counted as 0) |
≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥6/10 DA) [Stricter] moria1: ≥8.4 Mbit/s |
| Stable | MTBF | Below (0/10 DA) | Median: 0.1d (0/10 DA above threshold) Min/Max: 0.1d / 0.1d (8/10 DA, Voting / Total Eligible) |
≥0.0d - 10.2d (varies) (≥6/10 DA) [Stricter] moria1: ≥10320.8d |
| Uptime | Below (0/10 DA) | 0.2d (R) | ≥5.4d - 5.8d (varies) (≥6/10 DA) | |
| HSDir | Prereq: Fast | Below (0/10 DA) | 0/10 DA assigned Fast 0 bit/s (4 DA relay-reported) 0 bit/s (4 DA unmeasured, counted as 0) |
≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥6/10 DA) [Stricter] moria1: ≥8.4 Mbit/s |
| Prereq: Stable | Below (0/10 DA) | 0/10 DA assigned Stable | ≥0.0d - 10.2d (varies) (≥6/10 DA) [Stricter] moria1: ≥10320.8d |
|
| Prereq: V2Dir | Meets (8/10 DA) | 8/10 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥6/10 DA) | |
| Uptime | Below (0/10 DA) | 0.2d (R) | ≥96h as each authority sees it (MinUptimeHidServDirectoryV2) (≥6/10 DA) [Stricter] moria1: ≥98% WFU and ≥9.7d Time Known |
|
| Guard | Prereq: Fast | Below (0/10 DA) | 0/10 DA assigned Fast 0 bit/s (4 DA relay-reported) 0 bit/s (4 DA unmeasured, counted as 0) |
≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥6/10 DA) [Stricter] moria1: ≥8.4 Mbit/s |
| Prereq: Stable | Below (0/10 DA) | 0/10 DA assigned Stable | ≥0.0d - 10.2d (varies) (≥6/10 DA) [Stricter] moria1: ≥10320.8d |
|
| Prereq: V2Dir | Meets (8/10 DA) | 8/10 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥6/10 DA) | |
| WFU | Partial (8/10 DA) | Majority: 100.0% (8/10 DA above threshold) | ≥98%; maatuska: ≥96.891% (≥6/10 DA) | |
| Time Known | Below (0/10 DA) | Median: 0.1d (0/10 DA above threshold) Min/Max: 0.1d / 0.1d (8/10 DA, Voting / Total Eligible) |
≥8 days; E30CF7B3: ≥15 hours 54 minutes 57 seconds (≥6/10 DA) | |
| Bandwidth | Below (0/10 DA) | 0 bit/s (4 DA relay-reported) 0 bit/s (4 DA unmeasured, counted as 0) |
≥16.8 Mbit/s (AuthDirGuardBWGuarantee) OR top 25% (≥80.0 Mbit/s-272.0 Mbit/s) (≥6/10 DA) | |
| Exit | Exit Policy | Below (0/10 DA) | Port 80: No | Port 443: No (R) | Allows ≥1 /8 on ports 80 AND 443 (≥6/10 DA) |
(DA) = Dir. Auth. Measured |
(R) = Relay Reported
Data from Tor CollecTor (authority votes, fetched 2026-11-13 11:45:06).
Capacity (Relay Reported)
- Observed Bandwidth
- 0.00 Kbit/s
- Advertised Bandwidth
- Unknown
- Rate Limit
- 6.54 Gbit/s
- Burst Limit
- 8.39 Gbit/s
- Total Data
- N/A
Measurement (Directory Authority Verified)
Source: CollecTor — fetched 2026-11-13 11:45:06
- Measured By
-
0/8
Bandwidth Authorities
Not measured by: 5947BB57, E30CF7B3, 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
- UP 3h 50m 33s 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
- 2h 45m 40s ago (2026-11-13 10:00:00)
- Last Seen
- 1h 45m 40s ago (2026-11-13 11:00:00)
- Last Restarted
- 3h 50m 33s ago (2026-11-13 08:55:07)
- Last Changed Address
- 2026-11-13 10:00:00
Overload status:
Incomplete — not every signal could be evaluated.
(No bandwidth record available for this relay)
Evaluated 2026-11-13 12:45 UTC. /details snapshot 2026-11-13 11:00:00 UTC (cached 45s ago). /bandwidth snapshot 2026-11-13 06:00:00 UTC (cached 5h ago).
General Overload (from /details)
- Status
- No general overload report in available 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-11-13 02:00 UTC
- AROI Domain (?)
- as215248.net
- Operator Validation
- Validated (36/54 relays)
- This Relay
-
Unvalidated
Error: Not yet processed by validator (relay may be new) - Contact
- email:b[]stiaanbr.ink url:https://as215248.net proof:uri-familyid-ed25519 hoster:as215248.net virtualization:kvm sandbox:yes ciissversion:3
Family Configuration
- Family Support
- Happy Families (54) — Has family-cert in server descriptor (guide) | View Full Family (54)
Happy Families (family-cert)
- Effective Members: 54
09F96D5FAAE343C80FEA1697D07E1AC9EDEA769D 0AF5663E8DB9BD56FFDF84AACB5B34DEF6F10B33 0B8084D8C3139E57E8B779CDC94D308DC1E91392 0CE9C706B889BA0801A0CBC85BEADB0F3DB7CC02 167FF0B5AD75A03C344281ABB8FE31AA513CC371 2523871B2C01A080964C16E63734B5456D61B804 35505ACF4631118377D29899FB7D92D5B2443D33 3A6543005AEA4FD822B23F45A37099D578CC6AE8 3E6D3021F69D242D4B3735493075BA7856FB1652 407440825CAFBDDF6DDC6BE38EE9DB1DBD319559 46A4E93D8FD4FF441F1F26FCAE9E2906723F2BC3 4DE4B02FCECC4E7B5355C31AC6646C52599C3E12 5EB3217C848421983EE7FF1752B621884DEDC005 5F4DC5FCE20716853ECB767AB754CEE9709E2A91 60F2B927BDC788F3C3F36415F9E2269137FDC4C1 6352FCD836BF4E45B3299246C57425FBEF0BE2C7 71AE831D9E80839B59CF2E27F4CAFAAB130C56CF 739EDA1379B046E2B7D6FECD392315DF448A27F5 740C1284F73E6F64CAD9125986C2BA490C9D0FA7 7ACE74739A492388B6E3ACAE431588C9B16D0FCA 7BF134A23604D07D3B8E38583AF078E9D33BCE7C 7DF2217738F914A19E06D2AE9C42209602CBEB4E 845C04D3D72635D9CFBA365650C3698892AE23B3 860D69BB314EE1522E2FAB93B171BF4995C668EC 8A510A84120CE3A796AB841EE161FC92755BC826 8E7A8D8C19AB1259BD55269267B1721F5EEF557C 8FC561029CE0E042AE3712673CB48DEEAD293F29 94BF2CA488D753812C3DBBF9700459A1A2DBB0F8 96522F6C63A40E0AA4C529E157C08E6128399A02 9C40C9620BCDE1DE227D2013B81F8D1244B605B9 9E308D17764F7782BA7409CAFBEF4649C737E922 A5AF521058559F1C5D4F8A1617913898687E12BC AAA7DA4D258D055780F4EE496D1154238DF75E04 ACC30C76B543276A6579315EBF8FCE89723EA3B5 AE736E5B999AC7C7624F1FE5AE15662AD6BCA9BA BB84721018B3404F0595DA215BE51F67A57164B8 BF9EB7BC5BB039A6FC7F5A0CC124061BB1B8D2D1 C321D0F686F837391CD1B0F5BCE3D55B6B61CB44 C4C2BDBC25C97ADAC6B85EE51BD1F87B1C1C31E0 (this relay) C945C4F2B12B7154AAD28ABFFDF93BF14B301D2D D2B154D3A067877880FC58840428634FCA4357C3 D6447BFDEAD011B5012138DFA00C349983C4982A D738CEEC4D62DDCD2031708685E1F87567F63BA5 D9009317B06AAD18B5AB99CAEC272DDDAE4F4748 DCEAB1ECEA729F19985D9AB6CE5155CB706873F6 DDB9D3384899E42597CCDDCBA411E4456705B69D DFAC8AD8734E9B1C327C9E1AF1C760E6760F4192 E7017A361C44F7403B186E812C48A06916AD5D83 E7984009244A90A016615AF27CC983D692B7FCFA E8BB96C295A8E02A40D7B80CF8B6183BB2A7E4F9 F16EB458D382DE762D005745486390C43F95E64F FD1C534C569B8A6F263C1461021F6F6103C4CBC6 FD5A85785ED438CC485B8FB8615FF16C98ABB27C FE4D1B9CEC5EE3BC92B9BAAC4ECA372B1A63F5D2
MyFamily (legacy declarations) — none
DNS Health
Not an exit relay — DNS health testing does not apply.Last fetch was at Fri, 13 Nov 2026 12:45:39 GMT.
Data from Tor CollecTor (authority votes, fetched 2026-11-13 11: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 | 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) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 5947BB57 | No | — | — | — | Y | No | — | — | — | — | — | — | — | — | — | — |
| E30CF7B3 | Yes | Yes | No | — | Y | Yes | Yes | Running, Valid, V2Dir | 0 bit/s (U) | 816.0 Kbit/s | 0 bit/s (U) | 184.0 Mbit/s OR 16.8 Mbit/s | 100.0% | 98% | 0.1d | 1d | 0.1d | 0.7d | 0.2d | 5.7d | 2026-11-13 08:56:25 | — |
| dannenberg (DE) | No | — | — | — | Y | No | — | — | — | — | — | — | — | — | — | — |
| dizum (NL) | Yes | Yes | No | — | N | Yes | Yes | Running, Valid, V2Dir | 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.1d | 8d | 0.1d | 7.4d | 0.2d | 5.8d | 2026-11-13 08:56:25 | — |
| faravahar (US) | Yes | Yes | No | — | Y | Yes | Yes | Running, Valid, V2Dir | 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.1d | 8d | 0.1d | 7.2d | 0.2d | 5.6d | 2026-11-13 08:56:25 | — |
| gabelmoo (DE) | Yes | Yes | No | — | Y | Yes | Yes | Running, Valid, V2Dir | 0 bit/s (U) | 816.0 Kbit/s | 0 bit/s (U) | 248.0 Mbit/s OR 16.8 Mbit/s | 100.0% | 98% | 0.1d | 8d | 0.1d | 10.2d | 0.2d | 5.8d | 2026-11-13 08:56:25 | — |
| longclaw (US) | Yes | Yes | No | — | Y | Yes | N/T | Running, Valid, V2Dir | 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.1d | 8d | 0.1d | 10.8d | 0.2d | 5.7d | 2026-11-13 08:56:25 | — |
| maatuska (SE) | Yes | Yes | No | — | N | Yes | Yes | Running, Valid, V2Dir | 0 bit/s (R) | 816.0 Kbit/s | 0 bit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 100.0% | 97% | 0.1d | 8d | 0.1d | 1.5d | 0.2d | 5.4d | 2026-11-13 08:56:25 | — |
| moria1 (US) | Yes | Yes | No | — | Y | Yes | Yes | Running, Valid, V2Dir | 0 bit/s (U) | 8.4 Mbit/s | 0 bit/s (U) | 184.0 Mbit/s OR 16.8 Mbit/s | 100.0% | 98% | 0.1d | 8d | 0.1d | 10320.8d | 0.2d | 6.0d | 2026-11-13 08:56:25 | — |
| tor26 (AT) | Yes | Yes | No | — | Y | Yes | Yes | Running, Valid, V2Dir | 0 bit/s (U) | 816.0 Kbit/s | 0 bit/s (U) | 256.0 Mbit/s OR 16.8 Mbit/s | 100.0% | 98% | 0.1d | 8d | 0.1d | 10.2d | 0.2d | 5.8d | 2026-11-13 08:56:25 | — |
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.