View Relay "teap0t"

Fingerprint: F97CC0ED99EF53EB88FB2FB828CD04E4F7E270C4 | Family: 1 relay | teap0t admin <admin AT teap0t d0t com> | AS9009 | Romania | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, Valid, Fast, Exit (4)
DNS Health
Healthy (11.3s, 8th percentile) (via exitdnshealth.1aeo.com)
BW Verified
6/6 BW Auths Measured 80 Kbit/s Median
Stability
Not Overloaded | UP 2d 12h 44m ago | UP 97% (1M)
Reachability
IPv4: 9/9 | v6: 8/8 (Directory Auths)
First Seen
3y 1mo 1w ago
BW Weight
0.01% of Network | 115 Mbit/s Observed By Relay
Version
0.4.8.18 Not Recommended
Issues Detected:
  • 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: WFU below threshold : Weighted Fractional Uptime 97.7% 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.
  • 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: 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.
  • HSDir: requires V2Dir (tunnelled-dir-server) : HSDir requires the relay to support tunnelled directory requests (V2Dir flag). This relay is missing V2Dir — the descriptor likely does not include tunnelled-dir-server, usually because DirCache 0 is set in torrc.
    Suggestion: Remove DirCache 0 from torrc (DirCache is enabled by default in Tor ≥0.3.3). Restart Tor and verify the descriptor includes tunnelled-dir-server. You can check with: grep tunnelled-dir-server /var/lib/tor/cached-descriptors
  • HSDir: WFU below threshold : WFU 97.7% 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.
  • Tor version not recommended : Running Tor version 0.4.8.18 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
exit.teap0t.com
83.97.20.77:9001
[2a04:9dc0:31::c0cc:4d]:9001
Exit Address
83.97.20.77
Reachability (Directory Authorities)
IPv4
9/9
IPv6
8/8 (1 don't test)
Location
Country
Romania Romania
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS9009
AS Name
M247 Europe SRL (BGP.tools)
AS Rarity
Rare (score: 2/5, 0.16% consensus weight, 19 operators)

Flags and Eligibility

Current Flags (4): Running, Valid, Fast, Exit
Eligible Flags (5): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 9/9 | Stable: 1/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 (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 Below (0/9 DA) No DirPort, no tunnelled-dir-server (R) Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Fast Speed Meets (9/9 DA) 115.4 Mbit/s (R) ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Stable MTBF Below (1/9 DA) Median: 4.4d (1/9 DA above threshold)
Min/Max: 4.1d / 13229.1d (9/9 DA, Voting / Total Eligible)		 ≥17.9d - 58.6d (varies) (≥5/9 DA)
Uptime Below (0/9 DA) 2.5d (R) ≥3.3d - 3.4d (varies) (≥5/9 DA)
HSDir Prereq: Fast Meets (9/9 DA) 9/9 DA assigned Fast ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Below (1/9 DA) 1/9 DA assigned Stable ≥17.9d - 58.6d (varies) (≥5/9 DA)
Prereq: V2Dir Below (0/9 DA) 0/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Below (0/9 DA) Median: 96.9% (0/9 DA above threshold)
Min/Max: 96.1% / 97.7% (9/9 DA, Voting / Total Eligible)		 ≥98.0% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 12.6d (9/9 DA above threshold)
Min/Max: 9.9d / 12.7d (9/9 DA, Voting / Total Eligible)		 ≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.9d
Guard Prereq: Fast Meets (9/9 DA) 9/9 DA assigned Fast ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Below (1/9 DA) 1/9 DA assigned Stable ≥17.9d - 58.6d (varies) (≥5/9 DA)
Prereq: V2Dir Below (0/9 DA) 0/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Below (0/9 DA) Median: 96.9% (0/9 DA above threshold)
Min/Max: 96.1% / 97.7% (9/9 DA, Voting / Total Eligible)		 ≥98% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 12.6d (9/9 DA above threshold)
Min/Max: 9.9d / 12.7d (9/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Meets (9/9 DA) 115.4 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-296.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-03-29 09:45:08).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
115.38 Mbit/s
Advertised Bandwidth
115.38 Mbit/s
Rate Limit
8.59 Gbit/s
Burst Limit
8.59 Gbit/s
Total Data
194 TB (5 years)
1mo: 5.0 TB | 6mo: 26 TB | 1y: 59 TB | 5y: 194 TB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-03-29 09:45:08

Measured By
6/6 Bandwidth Authorities
Median Measurement
80.0 Kbit/s
Min / Max
53.6 Kbit/s / 160.0 Kbit/s
Deviation
106.4 Kbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0057% of network (50th pctl) | Guard: N/A | Middle: N/A | Exit: 0.0171% (33th pctl)

Uptime and Stability

Uptime Metrics
Current Status
UP 2d 12h 44m ago
Overall Uptime (1M/6M/1Y/5Y)
97.2%/97.0%/96.8%/97.2%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (97.2%/97.0%/96.8%/97.2%)
Hibernating
No
Timestamps
First Seen
3y 1mo 1w ago (2023-02-21 00:00:00)
Last Seen
2h 46m 39s ago (2026-03-29 08:00:00)
Last Restarted
2d 12h 44m ago (2026-03-26 22:02:17)
Last Changed Address
2024-01-29 19:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-03-29 02:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
teap0t admin <admin AT teap0t d0t com>
Family Configuration
Family Support
None — No family membership configured
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Member: 1 
F97CC0ED99EF53EB88FB2FB828CD04E4F7E270C4 (this relay)
Alleged Members: 0
none
Indirect Members: 0
none

Software and Version

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

Exit Health & Policy

DNS Health
Status
Healthy (avg. 11.3s, 8th percentile)
Query Domain
4819139a20cd4a4197cc83d1ccb35968.f97cc0ed.tor.exit.validator.1aeo.com
DNS Result
Resolved to 64.65.4.1
Cross-Validation
4/4 instances succeeded
First Hop
bauruine (NO) 977FE9A7634A592C0A704F226E5B70DCF71A9197
Exit Address Used
83.97.20.77
Per-Instance Results
Cross Validation Attempt 1: Success, 7.8s (cv1_w4)
Cross Validation Attempt 2: Success, 12.9s (cv2_w4)
Cross Validation Attempt 3: Success, 9.6s (cv3_w4)
Cross Validation Attempt 4: Success, 15.0s (cv4_w4)
Tested: 2026-03-24 19:20:01 UTC
Source: exitdnshealth.1aeo.com
IPv4 Exit Policy Summary
accept: 
  53
  80
  443
IPv6 Exit Policy Summary
None
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 83.97.20.77:*
accept *:53
accept *:80
accept *:443
reject *:*

Last fetch was at Sun, 29 Mar 2026 10:46:38 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-03-29 09:45: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 (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 Yes — Y Yes Yes Running, Valid, Fast, Exit 115.4 Mbit/s | 816.0 Kbit/s 115.4 Mbit/s | 200.0 Mbit/s OR 16.0 Mbit/s 97.7% | 98% 12.6d | 8d 4.4d | 63.4d 2.5d | 3.3d 97.7% | 98.0% 12.6d | 1.0d 2026-03-29 04:01:55 53.6 Kbit/s
dannenberg (DE) Yes Yes Yes — N Yes Yes Running, Valid, Fast, Exit 115.4 Mbit/s | 816.0 Kbit/s 115.4 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 97.0% | 98% 12.6d | 8d 4.4d | 17.9d 2.5d | 3.3d 97.0% | 98.0% 12.6d | 1.0d 2026-03-29 04:01:55 80.0 Kbit/s
dizum (NL) Yes Yes Yes — N Yes Yes Running, Valid, Fast, Exit 115.4 Mbit/s | 816.0 Kbit/s 115.4 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 96.7% | 98% 11.8d | 8d 4.1d | 42.9d 2.5d | 3.4d 96.7% | 98.0% 11.8d | 1.0d 2026-03-29 04:01:55 80.0 Kbit/s
faravahar (US) Yes Yes Yes — N Yes Yes Running, Valid, Fast, Exit 115.4 Mbit/s | 816.0 Kbit/s 115.4 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 97.1% | 98% 12.6d | 8d 4.4d | 56.4d 2.5d | 3.4d 97.1% | 98.0% 12.6d | 1.0d 2026-03-29 04:01:55 80.0 Kbit/s
gabelmoo (DE) Yes Yes Yes — Y Yes Yes Running, Valid, Fast, Exit 115.4 Mbit/s | 816.0 Kbit/s 115.4 Mbit/s | 280.0 Mbit/s OR 16.0 Mbit/s 96.8% | 98% 12.6d | 8d 4.4d | 62.1d 2.5d | 3.4d 96.8% | 98.0% 12.6d | 1.0d 2026-03-29 04:01:55 160.0 Kbit/s
longclaw (US) Yes Yes Yes — Y Yes — Running, Valid, Fast, Exit 115.4 Mbit/s | 816.0 Kbit/s 115.4 Mbit/s | 232.0 Mbit/s OR 16.0 Mbit/s 96.9% | 98% 12.4d | 8d 4.3d | 62.6d 2.5d | 3.3d 96.9% | 98.0% 12.4d | 1.0d 2026-03-29 04:01:55 78.4 Kbit/s
maatuska (SE) Yes Yes Yes — Y Yes Yes Running, Valid, Fast, Exit 115.4 Mbit/s | 816.0 Kbit/s 115.4 Mbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 96.9% | 98% 12.7d | 8d 4.4d | 50.7d 2.5d | 3.3d 96.9% | 98.0% 12.7d | 1.0d 2026-03-29 04:01:55 96.0 Kbit/s
moria1 (US) Yes Yes Yes — Y Yes Yes Running, Valid, Fast, Stable, Exit 115.4 Mbit/s | 8.4 Mbit/s 115.4 Mbit/s | 216.0 Mbit/s OR 16.0 Mbit/s 96.1% | 98% 9.9d | 8d 13229.1d | 291.4d 2.5d | 4.1d 96.1% | 98.0% 9.95d | 9.90d 2026-03-29 04:01:55 80.0 Kbit/s
tor26 (AT) Yes Yes Yes — Y Yes Yes Running, Valid, Fast, Exit 115.4 Mbit/s | 816.0 Kbit/s 115.4 Mbit/s | 264.0 Mbit/s OR 16.0 Mbit/s 97.0% | 98% 12.6d | 8d 4.4d | 58.6d 2.5d | 3.9d 97.0% | 98.0% 12.6d | 1.0d 2026-03-29 04:01:55 136.0 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). 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.