Tor Relays :: vpsonfire

View Relay "vpsonfire"

Family: 1 relay | nobodies@home | AS211619 | Bulgaria | Linux

Health Status

Consensus: In Consensus (9/9 Directory Auths)
Flags: Exit, Running, V2Dir, Valid (4)
BW Verified: 4/6 BW Auths Measured
Stability: Not Overloaded | UP 19h 33m 37s ago

Reachability: IPv4: 9/9 | v6: 7/7 (Directory Auths)
First Seen: 18h 55m 4s ago
BW Weight: 0.00% of Network | 0 Kbit/s Observed By Relay
Version: 0.4.8.21 Recommended

Issues Detected:

Guard: Time Known below threshold : Time Known 0.8 days is below 8 days requirement (7.2 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).
Guard: requires Fast flag : Guard flag requires having the Fast flag first
Suggestion: Get Fast flag by having bandwidth ≥100 KB/s OR in top 7/8ths of network. Most relays get this easily.
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: Time Known below threshold : Time Known 18.6 hours below 25 hours (dir-spec default)
Suggestion: Most authorities use 25 hours for HSDir TK. moria1 uses ~10 days. Keep running stably.
StaleDesc flag assigned : Relay descriptor is older than 18 hours
Suggestion: Your relay is not publishing fresh descriptors. Check: 1) Tor process is running, 2) Network connectivity, 3) Clock is synchronized (NTP). Restart Tor if needed.

Connectivity and Location

Addresses

OR Address: 45.9.156.100:443
[2a0e:bfc7::216:3cff:fef0:ae94]:443
Exit Address: 45.9.156.100

Reachability (Directory Authorities)

IPv4: 9/9
IPv6: 7/7 (2 don't test)

Location

Country: Bulgaria
Interactive Map: View on Interactive Map

Autonomous System

AS Number: AS211619
AS Name: MAXKO d.o.o. (BGP.tools)

Flags and Eligibility

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

Eligibility Flag Vote Details

Flag	Metric	Status	Relay Value	Threshold Required
Guard	WFU	Meets	100.0% (DA)	≥98% (all authorities)
	Time Known	Below (need 7.2 more days)	0.8 days (DA)	≥8 days (all authorities)
	Bandwidth	Below	8 bit/s (R)	≥16.0 Mbit/s OR ≥80.0 Mbit/s-296.0 Mbit/s
Stable	MTBF	Below	1 days (DA)	≥26.6d - 45.4d (varies)
Stable	Uptime	Below	0.8d (R)	≥19.1d - 19.7d (varies)
Fast	Speed	Below	8 bit/s (R)	≥800.0 Kbit/s (guarantee) OR top 7/8
HSDir	WFU	Meets	100.0% (DA)	≥98.0%
HSDir	Time Known	Below	0.8 days (DA)	≥1.0d (most) / 9.9d (max)

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

Last fetch was at Sat, 10 Jan 2026 04:47:26 GMT.

Nickname

vpsonfire

Fingerprint

D8D783F30063AAB9FEA8816F61D654576453AB2E

AROI (?)

none

Contact

nobodies@home

IPv4 Exit Policy Summary

accept: 
  20-21
  43
  53
  80-81
  443
  5222-5223
  6667-7000
  8008
  8082
  8332-8333
  8888
  9418
  18080-18081
  50002
  64738

IPv6 Exit Policy Summary

accept: 
  20-21
  43
  53
  80-81
  443
  5222-5223
  6667-7000
  8008
  8082
  8332-8333
  8888
  9418
  18080-18081
  50002
  64738

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.9.156.100:*
accept *:20-21
accept *:43
accept *:53
accept *:80-81
accept *:443
accept *:5222-5223
accept *:6667-7000
accept *:8008
accept *:8082
accept *:8332-8333
accept *:8888
accept *:9418
accept *:18080-18081
accept *:50002
accept *:64738
reject *:*

Effective Family Member: 1

D8D783F30063AAB9FEA8816F61D654576453AB2E

Alleged Family Members: 0

none

Indirect Family Members: 0

none

Bandwidth Capacity (Observed | Advertised | Rate Limit | Burst Limit): 0.00 Kbit/s | unknown| 8.59 Gbit/s| 8.59 Gbit/s Measured
Network Participation (Consensus Weight | Guard | Middle | Exit): 0.00% | N/A | N/A | 0.00%
OR Address: 45.9.156.100:443, [2a0e:bfc7::216:3cff:fef0:ae94]:443
Exit Address: none
Dir Address: none
Country: Bulgaria
Interactive Map: View on Interactive Map
Autonomous System (AS Number | AS Name): AS211619 | MAXKO d.o.o. (BGP.tools)
Flags: 4: Exit Running V2Dir Valid
Flag Uptime (1M/6M/1Y/5Y): Match Overall Uptime (0.0%/0.0%/0.0%/0.0%)
Uptime (1M/6M/1Y/5Y): 0.0%/0.0%/0.0%/0.0%
Uptime / Downtime: UP 19h 33m 37s ago
Seen (First | Last): 18h 55m 4s ago (2026-01-09 10:00:00) | 1h 55m 4s ago (2026-01-10 03:00:00)
Last Restarted: 19h 41m 12s ago (2026-01-09 09:13:52)
Last Changed Address or Port: 2026-01-09 10: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-10 04:46:16).

Consensus Status (need ≥5/9): In Consensus — 9/9 authorities voted.
Flag Eligibility (need ≥5/9 for flag): Guard: 0/9 | Stable: 0/9 | Fast: 0/9 | HSDir: 0/9 | Running: 9/9 | Valid: 9/9 | V2Dir: 9/9
Reachability: IPv4: 9/9 | IPv6: 7/7 (2 don't test)
Consensus Weight (Dir. Auth.): Median: 0 bit/s | Min: 0 bit/s | Max: 8 bit/s
Identified Issues:
- Guard: Time Known below threshold: Time Known 0.8 days is below 8 days requirement (7.2 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).
- Guard: requires Fast flag: Guard flag requires having the Fast flag first
  - Suggestion: Get Fast flag by having bandwidth ≥100 KB/s OR in top 7/8ths of network. Most relays get this easily.
- 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: Time Known below threshold: Time Known 18.6 hours below 25 hours (dir-spec default)
  - Suggestion: Most authorities use 25 hours for HSDir TK. moria1 uses ~10 days. Keep running stably.
- StaleDesc flag assigned: Relay descriptor is older than 18 hours
  - Suggestion: Your relay is not publishing fresh descriptors. Check: 1) Tor process is running, 2) Network connectivity, 3) Clock is synchronized (NTP). Restart Tor if needed.

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.)	0 bit/s (median)	N/A (no threshold, used for path selection)	—
Guard WFU (Dir. Auth., guard-wfu)	100.0%	≥98% (all authorities)	MEETS
Guard TK (Dir. Auth., tk)	0.8 days	≥8 days (all authorities)	BELOW - need 7.2 more days
Guard BW (Relay Reported)	8 bit/s	≥16.0 Mbit/s OR ≥80.0 Mbit/s-296.0 Mbit/s	BELOW - need ≥2 MB/s
Stable Uptime (Relay Reported)	0.8d	≥19.1d - 19.7d (typical)	BELOW - 0/9
Stable MTBF (Dir. Auth., mtbf)	1 days	≥26.6d - 45.4d (typical) [Stricter] moria1: ≥376.2d	BELOW - 0/9
Fast Speed (Relay Reported)	8 bit/s	≥800.0 Kbit/s (guarantee) OR ≥816.0 Kbit/s (typical) [Stricter] moria1: ≥8.4 Mbit/s	BELOW - need ≥100 KB/s
HSDir WFU (Dir. Auth., wfu)	100.0%	≥98.0% (from all auths)	BELOW - 0/9
HSDir TK (Dir. Auth., tk)	0.8 days	≥1.0d (8/9 auths) [Stricter] moria1: ≥9.9d	BELOW - 0/9
IPv6 Reachable (Dir. Auth.)	7/7 tested	≥4/7 (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	Exit, Running, StaleDesc, V2Dir, Valid	0 bit/s \| 816.0 Kbit/s	0 bit/s \| 224.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	0.8d \| 8d	0.8d \| 47.0d	0.8d \| 19.7d	100.0% \| 98.0%	0.8d \| 1.0d	2026-01-09 09:14:11 [Stale]	8 bit/s
dannenberg (DE)	Yes	Yes	N	Yes	Yes	Exit, Running, StaleDesc, V2Dir, Valid	0 bit/s \| 816.0 Kbit/s	0 bit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	0.8d \| 8d	0.8d \| 35.7d	0.8d \| 20.2d	100.0% \| 98.0%	0.8d \| 1.0d	2026-01-09 09:14:11 [Stale]	—
dizum (NL)	Yes	Yes	N	Yes	—	Exit, Running, StaleDesc, V2Dir, Valid	0 bit/s \| 816.0 Kbit/s	0 bit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	0.8d \| 8d	0.8d \| 26.6d	0.8d \| 20.4d	100.0% \| 98.0%	0.8d \| 1.0d	2026-01-09 09:14:11 [Stale]	—
faravahar (US)	Yes	Yes	N	Yes	Yes	Exit, Running, StaleDesc, V2Dir, Valid	0 bit/s \| 816.0 Kbit/s	0 bit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	0.8d \| 8d	0.8d \| 41.9d	0.8d \| 19.1d	100.0% \| 98.0%	0.8d \| 1.0d	2026-01-09 09:14:11 [Stale]	—
gabelmoo (DE)	Yes	Yes	Y	Yes	Yes	Exit, Running, StaleDesc, V2Dir, Valid	0 bit/s \| 816.0 Kbit/s	0 bit/s \| 288.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	0.8d \| 8d	0.8d \| 45.4d	0.8d \| 19.6d	100.0% \| 98.0%	0.8d \| 1.0d	2026-01-09 09:14:11 [Stale]	8 bit/s
longclaw (US)	Yes	Yes	Y	Yes	—	Exit, Running, StaleDesc, V2Dir, Valid	0 bit/s \| 816.0 Kbit/s	0 bit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	0.8d \| 8d	0.8d \| 48.7d	0.8d \| 19.5d	100.0% \| 98.0%	0.8d \| 1.0d	2026-01-09 09:14:11 [Stale]	—
maatuska (SE)	Yes	Yes	Y	Yes	Yes	Exit, Running, StaleDesc, V2Dir, Valid	0 bit/s \| 816.0 Kbit/s	0 bit/s \| 296.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	0.8d \| 8d	0.8d \| 42.3d	0.8d \| 19.4d	100.0% \| 98.0%	0.8d \| 1.0d	2026-01-09 09:14:11 [Stale]	8 bit/s
moria1 (US)	Yes	Yes	Y	Yes	Yes	Exit, Running, StaleDesc, V2Dir, Valid	0 bit/s \| 8.4 Mbit/s	0 bit/s \| 232.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	0.7d \| 8d	0.8d \| 376.2d	0.8d \| 20.4d	100.0% \| 98.0%	0.7d \| 9.9d	2026-01-09 09:14:11 [Stale]	8 bit/s
tor26 (AT)	Yes	Yes	Y	Yes	Yes	Exit, Running, StaleDesc, V2Dir, Valid	0 bit/s \| 816.0 Kbit/s	0 bit/s \| 272.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	0.8d \| 8d	0.8d \| 51.8d	0.8d \| 19.7d	100.0% \| 98.0%	0.8d \| 1.0d	2026-01-09 09:14:11 [Stale]	—

— = 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.