View Relay "PandaHideout"

Fingerprint: 260F8C20B290C38247E442EA0D81348ACA4ED8F9 | Family: 1 relay | me@lilithya.su | AS213605 | China | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, Valid, V2Dir, Exit (4)
DNS Health
Not Tested (via exitdnshealth.1aeo.com)
BW Verified
0/7 BW Auths Measured 160 Kbit/s Median
Stability
Not Overloaded | DOWN 5h 45m 11s ago
Reachability
IPv4: 9/9 | v6: 6/8(Directory Auths)
First Seen
1d 3h 45m ago
BW Weight
0.00% of Network | 8 Mbit/s Observed By Relay
Version
0.4.9.11 Not Recommended
Issues Detected:
  • Not getting the Fast flag : Only 0/9 authorities vote Fast (5 needed). dizum, faravahar, longclaw and maatuska used the relay-reported 496.0 Kbit/s, below the Fast threshold (816.0 Kbit/s). bastet, dannenberg, 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/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 – 280.0 Mbit/s). dizum, faravahar, longclaw and maatuska used the relay-reported 496.0 Kbit/s. bastet, 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: WFU below threshold : 0/9 authorities meet guard-wfu (≥98%; dizum: ≥97.63200000000001%; 5 needed). bastet and moria1 measured 0% (no uptime history for this relay). dannenberg, dizum, faravahar, gabelmoo, longclaw, maatuska and tor26 measured 0.0%–92.8%.
    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.
  • 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.
  • 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.
  • Tor version not recommended : Running Tor version 0.4.9.11 which is not on the recommended list.
    Suggestion: Update to the latest stable Tor version. Outdated versions may have security vulnerabilities and could eventually be rejected by the network. See torproject.org/download for latest releases.

Connectivity and Location

Addresses
OR Address
49.213.62.84:9001
[2a14:67c1:b142:1:be24:11ff:fe9b:c096]:9001
Reachability (Directory Authorities)
IPv4
9/9
IPv6
6/8 (1 don't test)
Location
Country
China China
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS213605
AS Name
Liu HaoRan (BGP.tools)
AS Rarity
Legendary (score: 5/5, <0.05% consensus weight, 1 operator)

Flags and Eligibility

Current Flags (4): Running, Valid, V2Dir, Exit
Eligible Flags (4): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 0/9 | Stable: 0/9 | HSDir: 0/9 | Guard: 0/9 | Exit: 9/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 (6/8 DA) 6/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 (0/9 DA) 496.0 Kbit/s (4 DA relay-reported)
0 bit/s (5 DA unmeasured, counted as 0)		 ≥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 (0/9 DA above threshold)
Min/Max: 0.0d / 3.2d (9/9 DA, Voting / Total Eligible)		 ≥2.3d - 9.1d (varies) (≥5/9 DA)
[Stricter] moria1: ≥8041.9d
Uptime Meets (9/9 DA) 17.6d (R) ≥4.3d - 4.8d (varies) (≥5/9 DA)
HSDir Prereq: Fast Below (0/9 DA) 0/9 DA assigned Fast
496.0 Kbit/s (4 DA relay-reported)
0 bit/s (5 DA unmeasured, counted as 0)		 ≥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 ≥2.3d - 9.1d (varies) (≥5/9 DA)
[Stricter] moria1: ≥8041.9d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Uptime Below (2/9 DA) 17.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 (0/9 DA) 0/9 DA assigned Fast
496.0 Kbit/s (4 DA relay-reported)
0 bit/s (5 DA unmeasured, counted as 0)		 ≥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 ≥2.3d - 9.1d (varies) (≥5/9 DA)
[Stricter] moria1: ≥8041.9d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Below (0/9 DA) Median: 0.0% (0/9 DA above threshold)
Min/Max: 0.0% / 92.8% (9/9 DA, Voting / Total Eligible)		 ≥98%; dizum: ≥97.63200000000001% (≥5/9 DA)
Time Known Partial (7/9 DA) Median: 12.9d (7/9 DA above threshold)
Min/Max: 0.0d / 95.3d (9/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Below (0/9 DA) 496.0 Kbit/s (4 DA relay-reported)
0 bit/s (5 DA unmeasured, counted as 0)		 ≥16.8 Mbit/s (AuthDirGuardBWGuarantee) OR top 25% (≥80.0 Mbit/s-280.0 Mbit/s) (≥5/9 DA)
Exit Exit Policy Meets (9/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-11-03 19:15:08).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
8.06 Mbit/s
Advertised Bandwidth
8.06 Mbit/s
Rate Limit
167.77 Mbit/s
Burst Limit
251.66 Mbit/s
Total Data
2.5 GB (6 months)
1mo: 1.5 GB | 6mo: 2.5 GB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-11-03 19:15:08

Measured By
0/7 Bandwidth Authorities
Not measured by: bastet, dannenberg, faravahar, gabelmoo, longclaw, moria1, tor26
Consensus Weight
160.0 Kbit/s (Unmeasured)
Measured Min / Max
N/A / N/A
Network Participation: Consensus Weight: 0.0000% of network (4th pctl) | Guard: N/A | Middle: N/A | Exit: N/A
History
Throughput and write/read, last 6 months Throughput and write/read, last 30 days
1M 6M

Uptime and Stability

Uptime Metrics
Current Status
DOWN 5h 45m 11s 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 3h 45m ago (2026-11-02 16:00:00)
Last Seen
5h 45m 11s ago (2026-11-03 14:00:00)
Last Restarted
2w 3d 14h ago (2026-10-17 05:29:48)
Last Changed Address
2026-11-02 16:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Evaluated 2026-11-03 19:45 UTC. /details snapshot 2026-11-03 18:00:00 UTC (cached 11s ago). /bandwidth snapshot 2026-11-03 18:00:00 UTC (cached 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
Uptime, last 30 days

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-11-03 11:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
me@lilithya.su
Family Configuration
Family Support
None — No family membership configured
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Member: 1 
260F8C20B290C38247E442EA0D81348ACA4ED8F9 (this relay)
Alleged Members: 0
none
Indirect Members: 0
none

Software and Version

Platform
Linux — Tor 0.4.9.11 on Linux
Version
0.4.9.11 — Not Recommended
Version Status
Obsolete — Update urgently. See torproject.org/download

Exit Health & Policy

DNS Health
Status
Not Tested
Source: exitdnshealth.1aeo.com
IPv4 Exit Policy Summary
accept: 
  20-23
  43
  53
  79-81
  88
  110
  143
  194
  220
  389
  443
  464-465
  531
  543-544
  554
  563
  587
  636
  706
  749
  873
  902-904
  981
  989-995
  1194
  1220
  1293
  1500
  1533
  1677
  1723
  1755
  1863
  2082-2083
  2086-2087
  2095-2096
  2102-2104
  3128
  3389
  3690
  4321
  4643
  5050
  5190
  5222-5223
  5228
  5900
  6660-6669
  6679
  6697
  8000
  8008
  8074
  8080
  8087-8088
  8332-8333
  8443
  8888
  9418
  9999-10000
  11371
  19294
  19638
  50002
  64738
IPv6 Exit Policy Summary
accept: 
  20-23
  43
  53
  79-81
  88
  110
  143
  194
  220
  389
  443
  464-465
  531
  543-544
  554
  563
  587
  636
  706
  749
  873
  902-904
  981
  989-995
  1194
  1220
  1293
  1500
  1533
  1677
  1723
  1755
  1863
  2082-2083
  2086-2087
  2095-2096
  2102-2104
  3128
  3389
  3690
  4321
  4643
  5050
  5190
  5222-5223
  5228
  5900
  6660-6669
  6679
  6697
  8000
  8008
  8074
  8080
  8087-8088
  8332-8333
  8443
  8888
  9418
  9999-10000
  11371
  19294
  19638
  50002
  64738
Full 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 49.213.62.84:*
accept *:20-23
accept *:43
accept *:53
accept *:79-81
accept *:88
accept *:110
accept *:143
accept *:194
accept *:220
accept *:389
accept *:443
accept *:464
accept *:465
accept *:531
accept *:543-544
accept *:554
accept *:563
accept *:587
accept *:636
accept *:706
accept *:749
accept *:873
accept *:902-904
accept *:981
accept *:989-995
accept *:1194
accept *:1220
accept *:1293
accept *:1500
accept *:1533
accept *:1677
accept *:1723
accept *:1755
accept *:1863
accept *:2082-2083
accept *:2086-2087
accept *:2095-2096
accept *:2102-2104
accept *:3128
accept *:3389
accept *:3690
accept *:4321
accept *:4643
accept *:5050
accept *:5190
accept *:5222-5223
accept *:5228
accept *:5900
accept *:6660-6669
accept *:6679
accept *:6697
accept *:8000
accept *:8008
accept *:8074
accept *:8080
accept *:8087-8088
accept *:8332-8333
accept *:8443
accept *:8888
accept *:9418
accept *:9999
accept *:10000
accept *:11371
accept *:19294
accept *:19638
accept *:50002
accept *:64738
reject *:*

Last fetch was at Tue, 03 Nov 2026 19:45:10 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-11-03 19:15:08).

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 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 Yes — Y Yes Yes Valid, V2Dir, Exit 0 bit/s (U) | 816.0 Kbit/s 0 bit/s (U) | 184.0 Mbit/s OR 16.8 Mbit/s 0.0% | 98% 0.0d | 8d 0.0d | 7.5d 17.6d | 4.3d 2026-11-02 11:09:39 496.0 Kbit/s (R)
dannenberg (DE) Yes Yes Yes — Y Yes Yes Valid, V2Dir, Exit 0 bit/s (U) | 816.0 Kbit/s 0 bit/s (U) | 280.0 Mbit/s OR 16.8 Mbit/s 0.0% | 98% 79.5d | 8d 0.0d | 9.1d 17.6d | 4.9d 2026-11-03 09:09:41 496.0 Kbit/s (R)
dizum (NL) Yes Yes Yes — N Yes Yes Running, Valid, V2Dir, Exit 496.0 Kbit/s (R) | 816.0 Kbit/s 496.0 Kbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 91.7% | 98% 12.9d | 8d 1.2d | 6.4d 17.6d | 4.8d 2026-11-03 09:09:41 496.0 Kbit/s (R)
faravahar (US) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Exit 496.0 Kbit/s (R) | 816.0 Kbit/s 496.0 Kbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 92.8% | 98% 12.6d | 8d 1.3d | 6.3d 17.6d | 4.8d 2026-11-03 09:09:41 496.0 Kbit/s (R)
gabelmoo (DE) Yes Yes Yes — Y Yes Yes Valid, V2Dir, Exit 0 bit/s (U) | 816.0 Kbit/s 0 bit/s (U) | 256.0 Mbit/s OR 16.8 Mbit/s 0.0% | 98% 95.3d | 8d 3.2d | 10.5d 17.6d | 4.9d 2026-11-03 09:09:41 496.0 Kbit/s (R)
longclaw (US) Yes Yes Yes — Y Yes N/T Valid, V2Dir, Exit 496.0 Kbit/s (R) | 816.0 Kbit/s 496.0 Kbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 0.0% | 98% 55.0d | 8d 0.1d | 10.5d 17.6d | 4.8d 2026-11-03 09:09:41 496.0 Kbit/s (R)
maatuska (SE) Yes Yes Yes — N Yes No Valid, V2Dir, Exit 496.0 Kbit/s (R) | 816.0 Kbit/s 496.0 Kbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 92.3% | 98% 12.9d | 8d 1.2d | 2.3d 17.6d | 4.8d 2026-11-03 09:09:41 496.0 Kbit/s (R)
moria1 (US) Yes Yes Yes — Y Yes Yes Valid, V2Dir, Exit 0 bit/s (U) | 8.4 Mbit/s 0 bit/s (U) | 192.0 Mbit/s OR 16.8 Mbit/s 0.0% | 98% 0.0d | 8d 0.0d | 8041.9d 17.6d | 4.9d 2026-11-03 09:09:41 496.0 Kbit/s (R)
tor26 (AT) Yes Yes Yes — Y Yes No Valid, V2Dir, Exit 0 bit/s (U) | 816.0 Kbit/s 0 bit/s (U) | 264.0 Mbit/s OR 16.8 Mbit/s 92.6% | 98% 12.7d | 8d 1.5d | 10.3d 17.6d | 4.9d 2026-11-03 09:09:41 496.0 Kbit/s (R)

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 (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.