Tor Relays :: Kalemegdan

View Relay "Kalemegdan"

Family: 18 relays | [email protected] | AS205007 | Serbia | Linux

Health Status

Consensus: In Consensus (9/9 Directory Auths)
Flags: Fast, Running, V2Dir, Valid (4)
BW Verified: 5/6 BW Auths Measured 47 Kbit/s Median
Stability: Not Overloaded | UP 4d 15h 42m ago | UP 72% (1M)

Reachability: IPv4: 9/9 (Directory Auths)
First Seen: 1w 6d 5h ago
BW Weight: 0.00% of Network | 47 Mbit/s Observed By Relay
Version: 0.4.8.21 Recommended

Issues Detected:

Guard: WFU below threshold : Weighted Fractional Uptime 61.2% is below 98% requirement
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 : Time Known 7.1 days is below 8 days requirement (0.9 more days needed)
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.
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).
Not eligible for Stable flag : Uptime or MTBF below network median for most authorities
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: WFU below threshold : WFU 61.2% below 98% required for HSDir
Suggestion: HSDir requires ≥98% WFU, Stable flag, and Time Known ≥25 hours (or ~10 days for moria1). Improve uptime consistency.
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.

Connectivity and Location

Addresses

OR Address: 185.48.250.157:443
[2a04:b540:3000:1::ac]:443

Reachability (Directory Authorities)

IPv4: 9/9

Location

Country: Serbia
Interactive Map: View on Interactive Map

Autonomous System

AS Number: AS205007
AS Name: Maxim Azarov trading as eServer (BGP.tools)

Flags and Eligibility

Current Flags (4): Running, Valid, V2Dir, Fast

Eligibility Flag Vote Details

Flag	Metric	Status	Relay Value	Threshold Required
Fast	Speed	Meets (≥100 KB/s)	47.9 Mbit/s (R)	≥800.0 Kbit/s (guarantee) OR top 7/8 [Stricter] moria1: ≥8.4 Mbit/s
Stable	MTBF	Below	Median: 0.2d (1/9 DA above threshold) Min/Max: 0.1d / 20478.1d (9/9 DA, Voting / Total Eligible)	≥22.2d - 53.8d (varies) [Stricter] moria1: ≥406.4d
Stable	Uptime	Below	4.7d (R)	≥10.0d - 11.0d (varies)
HSDir	Prereq: Stable	Below	1/9 authorities assigned Stable flag	≥5/9 authorities
	Prereq: Fast	Meets	9/9 authorities assigned Fast flag	≥5/9 authorities
	WFU	Below	Median: 72.7% (0/9 DA above threshold) Min/Max: 61.1% / 80.0% (9/9 DA, Voting / Total Eligible)	≥98.0%
	Time Known	Below	Median: 7.4d (0/9 DA above threshold) Min/Max: 7.1d / 7.5d (9/9 DA, Voting / Total Eligible)	≥1.0d (most) [Stricter] moria1: ≥9.9d
Guard	Prereq: Fast	Meets	9/9 authorities assigned Fast flag	≥5/9 authorities
	Prereq: Stable	Below	1/9 authorities assigned Stable flag	≥5/9 authorities
	Prereq: V2Dir	Meets	9/9 authorities assigned V2Dir flag	≥5/9 authorities
	WFU	Below	Median: 72.7% (0/9 DA above threshold) Min/Max: 61.1% / 80.0% (9/9 DA, Voting / Total Eligible)	≥98% (all authorities)
	Time Known	Below (need 0.6 more days)	Median: 7.4d (0/9 DA above threshold) Min/Max: 7.1d / 7.5d (9/9 DA, Voting / Total Eligible)	≥8 days (all authorities)
	Bandwidth	Meets (≥2 MB/s)	47.9 Mbit/s (R)	≥16.0 Mbit/s OR ≥80.0 Mbit/s-312.0 Mbit/s

(DA) = Dir. Auth. Measured | (R) = Relay Reported
Data from Tor CollecTor (authority votes, fetched 2026-01-29 10:15:07).

Last fetch was at Thu, 29 Jan 2026 10:15:43 GMT.

Nickname

Kalemegdan

Fingerprint

2B6FBBA678C38EF7DF374BD44B76C26B55A8641B

AROI (?)

none

Contact

[email protected]

IPv4 Exit Policy Summary

reject: 
  1-65535

IPv6 Exit Policy Summary

none

Exit Policy

reject *:*

Effective Family Members: 18 (View)

0C1384BD0ABBC06E25B3CAADA4D31EB6D6256532
149266A3EC0986A43BC2C0C5EC50F91622270E66
1721F504E4581C4A218173562EDEBC38BF48774B
25DCFDAF83FC42292CA3CCEFD5B11A9DEED0C987
2B6FBBA678C38EF7DF374BD44B76C26B55A8641B
34AFA4DF32394385C182D9B3BEBD4967F33B43C8
477A080784134FEC0D242047ABB39459F852F44D
7A011DE06AEDB840ECB01F6E5653B214342325FF
A1D0A2B517B8078CE9840875D9E7455F991FAB3E
A6F3B90879F95EF4C8D51438AB88802D9475C366
BCFD389EB6D6E01C581BB221BA7F597D9BD16FAF
CF2C63AF47595B96CCF5CFC23C8C95826F9B9B53
D01049AC9178252D23EADF2323BB44CE2647774A
D3639E6F2E188229E9ED91020C0043D4DB267A0F
E339970C7021BB066F033083DC7F402FC95CFCFC
E85A2E8BF9A35A6FC5F31F9E208B0462AFAF151E
FB6D60C8B414A3FAE729D7EB34DC3BFC09020069
FC7373EC8E1AFAA56F53A9A1A68F1063DCBC42F9

Alleged Family Members: 0

none

Indirect Family Members: 0

none

Bandwidth Capacity (Observed | Advertised | Rate Limit | Burst Limit): 47.92 Mbit/s | 47.92 Mbit/s| 8.59 Gbit/s| 8.59 Gbit/s Measured
Network Participation (Consensus Weight | Guard | Middle | Exit): 0.00% | N/A | 0.01% | N/A
OR Address: 185.48.250.157:443, [2a04:b540:3000:1::ac]:443
Exit Address: none
Dir Address: none
Country: Serbia
Interactive Map: View on Interactive Map
Autonomous System (AS Number | AS Name): AS205007 | Maxim Azarov trading as eServer (BGP.tools)
Flags: 4: Fast Running V2Dir Valid
Flag Uptime (1M/6M/1Y/5Y): 69.9%/—/—/—
Uptime (1M/6M/1Y/5Y): 73.0%/0.0%/0.0%/0.0%
Uptime / Downtime: UP 4d 15h 42m ago
Seen (First | Last): 1w 6d 5h ago (2026-01-16 05:00:00) | 1h 17m 10s ago (2026-01-29 09:00:00)
Last Restarted: 4d 15h 43m ago (2026-01-24 18:33:13)
Last Changed Address or Port: 2026-01-16 05:00:00
Hibernating: No
Platform (Short | Long): Linux | Tor 0.4.8.21 on Linux
Version (Running | Recommended | Status): 0.4.8.21 | Yes | recommended

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-01-29 10:15:07).

Consensus Status (need ≥5/9): In Consensus — 9/9 authorities voted.
Flag Eligibility (need ≥5/9 for flag): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 9/9 | Stable: 1/9 | HSDir: 0/9 | Guard: 0/9
Reachability: IPv4: 9/9 | IPv6: 5/0
Consensus Weight (Dir. Auth.): Median: 47.9 Kbit/s | Min: 44.0 Kbit/s | Max: 73.6 Kbit/s [Warning] High deviation
Identified Issues:
- Guard: WFU below threshold: Weighted Fractional Uptime 61.2% is below 98% requirement
  - 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: Time Known 7.1 days is below 8 days requirement (0.9 more days needed)
  - 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.
- 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).
- Not eligible for Stable flag: Uptime or MTBF below network median for most authorities
  - 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: WFU below threshold: WFU 61.2% below 98% required for HSDir
  - Suggestion: HSDir requires ≥98% WFU, Stable flag, and Time Known ≥25 hours (or ~10 days for moria1). Improve uptime consistency.
- 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.

Summary: Your Relay vs Consensus

Green = meets threshold, Red = below threshold, Yellow = partial.

Metric	Dir Auth Measured	Dir Auth Threshold	Status
In Consensus (Dir. Auth.)	9/9 authorities	≥5/9 (majority)	IN CONSENSUS
Running (IPv4 Reachable)	9/9 authorities reached this relay	≥5/9 (majority)	RUNNING
Valid	9/9 (Running + Valid Descriptor)	≥5/9 (majority)	VALID
Consensus Weight (Dir. Auth.)	47.9 Kbit/s (median)	N/A (no threshold, used for path selection)	—
Guard WFU (Dir. Auth., guard-wfu)	72.7%	≥98% (all authorities)	BELOW - cannot get Guard
Guard TK (Dir. Auth., tk)	7.4 days	≥8 days (all authorities)	BELOW - need 0.6 more days
Guard BW (Relay Reported)	47.9 Mbit/s	≥16.0 Mbit/s OR ≥80.0 Mbit/s-312.0 Mbit/s	MEETS - ≥2 MB/s guarantee
Stable Uptime (Relay Reported)	4.7d	≥10.0d - 11.0d (typical)	BELOW - 0/9
Stable MTBF (Dir. Auth., mtbf)	0 days	≥22.2d - 53.8d (typical) [Stricter] moria1: ≥406.4d	BELOW - 1/9
Fast Speed (Relay Reported)	47.9 Mbit/s	≥800.0 Kbit/s (guarantee) OR ≥816.0 Kbit/s (typical) [Stricter] moria1: ≥8.4 Mbit/s	MEETS - ≥100 KB/s guarantee
HSDir WFU (Dir. Auth., wfu)	72.7%	≥98.0% (from all auths)	BELOW - 0/9
HSDir TK (Dir. Auth., tk)	7.4 days	≥1.0d (8/9 auths) [Stricter] moria1: ≥9.9d	BELOW - 0/9
IPv6 Reachable (Dir. Auth.)	5/5 tested	≥3/5 (majority)	REACHABLE

Per-Authority Details

Each cell shows: your measured value | authority threshold. Green = meets, red = below. Flags: green = all authorities agree, yellow = partial.

Authority	Running	Valid	BW Scan (Authority)	v4	v6	Flags	Fast (Relay\|T)	Guard BW (Relay\|Threshold)	Guard WFU (M\|T)	Guard TK (M\|T)	Stable MTBF (M\|T)	Stable Uptime (Relay\|T)	HSDir WFU (M\|T)	HSDir TK (M\|T)	Desc Published	Cons Wt (Authority)
bastet (US)	Yes	Yes	Y	Yes	Yes	Running, Valid, V2Dir, Fast	47.9 Mbit/s \| 816.0 Kbit/s	47.9 Mbit/s \| 232.0 Mbit/s OR 16.0 Mbit/s	61.2% \| 98%	7.1d \| 8d	0.1d \| 50.3d	4.7d \| 11.6d	61.2% \| 98.0%	7.1d \| 1.0d	2026-01-29 06:47:43	44.0 Kbit/s
dannenberg (DE)	Yes	Yes	N	Yes	Yes	Running, Valid, V2Dir, Fast	47.9 Mbit/s \| 816.0 Kbit/s	47.9 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	61.1% \| 98%	7.4d \| 8d	0.1d \| 22.2d	4.7d \| 11.1d	61.1% \| 98.0%	7.4d \| 1.0d	2026-01-29 06:47:43	47.9 Kbit/s
dizum (NL)	Yes	Yes	N	Yes	—	Valid, V2Dir, Fast	47.9 Mbit/s \| 816.0 Kbit/s	47.9 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	74.1% \| 98%	7.5d \| 8d	0.2d \| 34.5d	4.7d \| 11.0d	74.1% \| 98.0%	7.5d \| 1.0d	2026-01-29 06:47:43	47.9 Kbit/s
faravahar (US)	Yes	Yes	N	Yes	Yes	Running, Valid, V2Dir, Fast	47.9 Mbit/s \| 816.0 Kbit/s	47.9 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	69.9% \| 98%	7.4d \| 8d	0.1d \| 47.4d	4.7d \| 10.0d	69.9% \| 98.0%	7.4d \| 1.0d	2026-01-29 06:47:43	47.9 Kbit/s
gabelmoo (DE)	Yes	Yes	Y	Yes	Yes	Running, Valid, V2Dir, Fast	47.9 Mbit/s \| 816.0 Kbit/s	47.9 Mbit/s \| 296.0 Mbit/s OR 16.0 Mbit/s	78.4% \| 98%	7.5d \| 8d	0.2d \| 53.8d	4.7d \| 11.1d	78.4% \| 98.0%	7.5d \| 1.0d	2026-01-29 06:47:43	73.6 Kbit/s
longclaw (US)	Yes	Yes	Y	Yes	—	Running, Valid, V2Dir, Fast	47.9 Mbit/s \| 816.0 Kbit/s	47.9 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	80.0% \| 98%	7.4d \| 8d	0.2d \| 54.6d	4.7d \| 10.6d	80.0% \| 98.0%	7.4d \| 1.0d	2026-01-29 06:47:43	47.9 Kbit/s
maatuska (SE)	Yes	Yes	Y	Yes	—	Valid, V2Dir, Fast	47.9 Mbit/s \| 816.0 Kbit/s	47.9 Mbit/s \| 312.0 Mbit/s OR 16.0 Mbit/s	77.0% \| 98%	7.2d \| 8d	0.2d \| 55.1d	4.7d \| 10.2d	77.0% \| 98.0%	7.2d \| 1.0d	2026-01-29 06:47:43	66.4 Kbit/s
moria1 (US)	Yes	Yes	Y	Yes	—	Valid, V2Dir, Fast, Stable	47.9 Mbit/s \| 8.4 Mbit/s	47.9 Mbit/s \| 240.0 Mbit/s OR 16.0 Mbit/s	71.5% \| 98%	7.5d \| 8d	20478.1d \| 406.4d	4.7d \| 10.7d	71.5% \| 98.0%	7.5d \| 9.9d	2026-01-29 06:47:43	48.8 Kbit/s
tor26 (AT)	Yes	Yes	Y	Yes	Yes	Running, Valid, V2Dir, Fast	47.9 Mbit/s \| 816.0 Kbit/s	47.9 Mbit/s \| 288.0 Mbit/s OR 16.0 Mbit/s	72.7% \| 98%	7.4d \| 8d	0.2d \| 55.7d	4.7d \| 12.0d	72.7% \| 98.0%	7.4d \| 1.0d	2026-01-29 06:47:43	58.4 Kbit/s

— = not tested/available • Format: relay value | authority threshold • WFU = Weighted Fractional Uptime • TK = Time Known

Bandwidth Values Explained:
Relay Reported = Your relay's self-reported bandwidth from its descriptor (observed_bandwidth). Used for flag eligibility (Guard, Fast).
Authority Measured = Bandwidth measured by authority's sbws scanner. Used for consensus weight (path selection probability).
Why different? Authorities verify your reported bandwidth independently. 6 of 9 authorities run bandwidth scanners; 3 use relay-reported values directly.

Stable Uptime (Two Data Sources):
Relay Uptime = From Onionoo API (last_restarted field). This is your relay's self-reported uptime from its 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.