View Relay "forest53"

Fingerprint: 740F146D37F59B66FDF87D92A52DF5FC3CA8A53C | Family: 60 relays | email:theforest[]riseup.net... | AS64457 | Austria | Linux

Consensus
In Consensus (9/9 Directory Auths)
BW Verified
6/7 BW Auths Measured 208 Mbit/s Median
Stability
Overloaded | UP 1d 4h 57m ago | UP 98% (1M)
Reachability
IPv4: 9/9 | v6: 8/8(Directory Auths)
BW Weight
0.01% of Network | 256 Mbit/s Observed By Relay
Version
0.4.9.17 Recommended
Issues Detected:
  • Guard: WFU below threshold : 0/9 authorities meet guard-wfu (≥98%; 5 needed). E30CF7B3, dannenberg, dizum, faravahar, gabelmoo, longclaw, maatuska, moria1 and tor26 measured 76.4%–97.7%.
    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.
  • 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.
  • Write Bandwidth Limit Hit : Write rate-limit counter is 557 (configured rate 150.99 Mbit/s). Read and write counters increment at most once per minute per direction. They are not a count of blocked connections, the duration of throttling, or necessarily the number of events in the last 24 hours.
    Suggestion: Inspect BandwidthRate and BandwidthBurst (the values reported with this hit), any relay-specific caps such as RelayBandwidthRate and RelayBandwidthBurst, the intended bandwidth budget, and actual uplink headroom. A rate-limit report is not evidence of ISP throttling. After checking that evidence and the capacity you meant to offer, review whether those limits should change. MetricsPort: tor_relay_load_global_rate_limit_reached_total{side="read"} and {side="write"}. Increases indicate additional global token-bucket limit events.
Notes:
  • Rate Limit Configuration: Configured limits: Rate=150.99 Mbit/s, Burst=1.1 GB. Counters: Write=557, Read=0. These values are BandwidthRate and BandwidthBurst from the extra-info descriptor. RelayBandwidthRate and RelayBandwidthBurst are additional torrc caps, not the names of these values. Burst is a quantity of bytes.
    Suggestion: Inspect BandwidthRate and BandwidthBurst (the values reported with this hit), any relay-specific caps such as RelayBandwidthRate and RelayBandwidthBurst, the intended bandwidth budget, and actual uplink headroom. A rate-limit report is not evidence of ISP throttling. After checking that evidence and the capacity you meant to offer, review whether those limits should change. MetricsPort: tor_relay_load_global_rate_limit_reached_total{side="read"} and {side="write"}. Increases indicate additional global token-bucket limit events.

Addresses
OR Address
185.224.3.41:443
[2a14:7c0:f100:1::a]:443
Reachability (Directory Authorities)
IPv4
9/9
IPv6
8/8 (1 don't test)
Location
Country
Austria Austria
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS64457
AS Name
Matteo Fruhwald trading as PipeHost e.U. (BGP.tools)
AS Rarity
Legendary (score: 5/5, <0.05% consensus weight, 1 operator)

Current Flags (6): Running, Valid, V2Dir, Fast, Stable, HSDir
Eligible Flags (6): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 9/9 | Stable: 6/9 | HSDir: 5/9 | Guard: 0/9 | Exit: 0/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 Meets (9/9 DA) Tunnelled: Yes (no DirPort) (R) Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Fast Speed Meets (9/9 DA) 184.0 Mbit/s – 488.0 Mbit/s (6 DA measured)
80.0 Mbit/s (3 DA relay-reported)
≥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 (4/9 DA) Median: 8.2d (6/9 DA above threshold)
Min/Max: 1.2d / 16293.6d (9/9 DA, Voting / Total Eligible)
≥2.3d - 8.2d (varies) (≥5/9 DA)
[Stricter] moria1: ≥12669.7d
Uptime Below (0/9 DA) 1.2d (R) ≥5.0d - 5.1d (varies) (≥5/9 DA)
HSDir Prereq: Fast Meets (9/9 DA) 9/9 DA assigned Fast
184.0 Mbit/s – 488.0 Mbit/s (6 DA measured)
80.0 Mbit/s (3 DA relay-reported)
≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Meets (6/9 DA) 6/9 DA assigned Stable ≥2.3d - 8.2d (varies) (≥5/9 DA)
[Stricter] moria1: ≥12669.7d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Uptime Partial (5/9 DA) 1.2d (R) ≥96h as each authority sees it (MinUptimeHidServDirectoryV2) (≥5/9 DA)
[Stricter] moria1: ≥98% WFU and ≥9.7d Time Known
Guard Prereq: Fast Meets (9/9 DA) 9/9 DA assigned Fast
184.0 Mbit/s – 488.0 Mbit/s (6 DA measured)
80.0 Mbit/s (3 DA relay-reported)
≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Meets (6/9 DA) 6/9 DA assigned Stable ≥2.3d - 8.2d (varies) (≥5/9 DA)
[Stricter] moria1: ≥12669.7d
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: 81.1% (0/9 DA above threshold)
Min/Max: 76.4% / 97.7% (9/9 DA, Voting / Total Eligible)
≥98% (≥5/9 DA)
Time Known Partial (8/9 DA) Median: 15.7d (8/9 DA above threshold)
Min/Max: 5.4455d / 15.8d (9/9 DA, Voting / Total Eligible)
≥8 days; E30CF7B3: ≥5 days 10 hours 41 minutes 56 seconds (≥5/9 DA)
Bandwidth Meets (9/9 DA) 184.0 Mbit/s – 488.0 Mbit/s (6 DA measured)
80.0 Mbit/s (3 DA relay-reported)
≥16.8 Mbit/s (AuthDirGuardBWGuarantee) OR top 25% (≥80.0 Mbit/s-248.0 Mbit/s) (≥5/9 DA)
Exit Exit Policy Below (0/9 DA) Port 80: No | Port 443: No (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-20 08:45:05).

Capacity (Relay Reported)
Observed Bandwidth
256.62 Mbit/s
Advertised Bandwidth
150.99 Mbit/s
Rate Limit
150.99 Mbit/s
Burst Limit
8.59 Gbit/s
Total Data
32 TB (1 month)
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-11-20 08:45:05

Measured By
6/7 Bandwidth Authorities
Not measured by: faravahar
Consensus Weight
208.0 Mbit/s (median of 6 measurements)
Measured Min / Max
184.0 Mbit/s / 488.0 Mbit/s
Deviation
304.0 Mbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0141% of network (74th pctl) | Guard: N/A | Middle: 0.0416% (92th pctl) | Exit: N/A
History
Throughput and write/read, last 30 days

Uptime Metrics
Current Status
UP 1d 4h 57m ago
Overall Uptime (1M/6M/1Y/5Y)
98.4%/0.0%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (98.4%/0.0%/0.0%/0.0%)
Hibernating
No
Timestamps
First Seen
2w 4d 8h ago (2026-11-02 01:00:00)
Last Seen
1h 15m 37s ago (2026-11-20 08:00:00)
Last Restarted
1d 4h 57m ago (2026-11-19 04:18:13)
Last Changed Address
2026-11-02 01:00:00
[Warning] OVERLOADED — Rate limits hit W:557 R:0 (limit: 150.99 Mbit/s)

Evaluated 2026-11-20 09:15 UTC. /details snapshot 2026-11-20 08:00:00 UTC (cached 33s ago). /bandwidth snapshot 2026-11-20 02:00:00 UTC (cached 6h ago).

Reported timestamps use hour precision, so the displayed minute is not an exact incident time.

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
Reported
Rate Limit
150.99 Mbit/s
Burst Limit
1.1 GB
Write counter
557
Read counter
0
Reported
2026-11-19 21:00 UTC (12 hours ago)

Read and write counters increment at most once per minute per direction. They are not a count of blocked connections, the duration of throttling, or necessarily the number of events in the last 24 hours. Rate is BandwidthRate and follows this site’s bits/bytes setting. Burst is BandwidthBurst, already a byte quantity. RelayBandwidthRate and RelayBandwidthBurst are extra torrc caps, not the names of these values. A hit stays eligible for 24 hours.

What to check
  • Configured bandwidth limits
    Inspect BandwidthRate and BandwidthBurst (the values reported with this hit), any relay-specific caps such as RelayBandwidthRate and RelayBandwidthBurst, the intended bandwidth budget, and actual uplink headroom. A rate-limit report is not evidence of ISP throttling. After checking that evidence and the capacity you meant to offer, review whether those limits should change.
    MetricsPort: tor_relay_load_global_rate_limit_reached_total{side="read"} and {side="write"} — Increases indicate additional global token-bucket limit events.
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 Identity

Source: AROI Validation API — 2026-11-19 23:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
email:theforest[]riseup.net pgp:BCBAE3E9CB8E2FE23F29DC58061D7CAC428DD60B ciissversion:2
Family Configuration
Family Support
Both — Happy Families (64 / 100%) and MyFamily (0 / 0%) | View Full Family (60)
Happy Families (family-cert)
Effective Members: 64
0153A0723F39CA78F5B60735DEC4A84E0991C5FD
01B1E1F4354A1390E4ABE459BE138CE5026D3CAE
029C0DD3A8DE99F77B07EFE4391418C410102430
0D4E91A90AA181DF386167F72B84C2F7C05B856E
0E33CE0721903F24B5680E1105D19EC4D7D335EB
0EF2A357140FCBDAE2F948CC2228909695B81B35
1D364AA273528C67ACB91D2504607E4A66F7C141
228E44687D0623BC611322397A8AC5FF22153501
26E0FE8CD20DBD1E44BA266C44911BAF93F1AE10
2A4841DDD43CA0F87B0692BB4A56BB90430559BE
2C6310892B606A8821172FEEC5A087AD30D13492
30F924D758C2A89C56382D10AF3E5447FB796C2F
31086DF46AD6060A165819D116502E3D93A615C0
33DC480A5C9DAF1E8B0CC79D771849B9343D6D6B
36B8855417A4DA8BFED2D09E224DA57C05012428
3874F1E6BD03011BCDF7ED9ECCAFB93F8DDFE868
49834AA2038D295FFC4338F0E567F6D382076D1E
4BC912403ED890A2D056D6F82FE11D159BF151C1
531F58F1A9431F9C46A79FE6847568FFEEF637B5
548FA7BBE882FA285895051AC8157A02E1637211
54C85B97B4A5253483AA269B341C4CCF9328C443
58F46CEEA4E3BB6EDA3E37BAD31E1326D61E17D4
6435C5172690160DA25681BEBA1EA5EAC6F2BE70
64DC0A2FEFCE139947157E8286C3A60F7AF22A9D
69798BF64FE8E358D8DE03DF35ED5604EF03C275
6CD14EA6695075CF2170A362574A77A84ACC1B59
6F980F25A2088542E3970BADBD5EDE5471143825
740F146D37F59B66FDF87D92A52DF5FC3CA8A53C (this relay)
7EDCEA659F03D2F9D83CAB1386512F91C44A057B
809ADD3CB3A2A6CCD2529E1327632EDAD7123C4B
80A2AC3C6991F3C93C6F4EE0EAFFDA9DC25977B4
832F03B44C745298961C63673F499422459BAB7B
846A6B34D1705B3370EAA9FD55C11BE59782FFEB
869C8E4EF22EB57ED3FD461A87751BA4D6A3589A
86D925BACCA2153E325E4CBED1D3514EB2CD5ECF
9280034AD4A6C0614793C1D126DFEAB78D15079B
9399852077AEBDF86903BD92E1BED2B9F154FCD5
95BDDCF59B254244CCF6B1DFC9F0E1F7E90F9FE7
967134B2F44E90FE113786068F424D6716E63A7E
968924D9166CB6A5D1F70A62C0752E73DD019D28
9706A2F1F3872BFAC1074338D0AF96DB580B8FDC
99931DC425687983CEE16523CF82800CDFC73114
9E7055D89DCF66B08F949D31F0E1E09F284BFA28
9FECF023896C3445C939FD8903B5BE196F2A9D15
A2CFC74E7E3ABC98516F7B1967C52CF7CF418A4B
AA0A159472934A588AA9ADF709988EF95E0E8FF2
AACB3F67B91F446121837C3DAA27B2CB92B4B4C0
AE02D18B9AA9954D3C77AC0A5E21EFA11B28E39E
AE1E8ABA00292A1ADF5A5F70AC9ADDB2F1FAA4DA
AEF67E736F7880B4D25A48A9866F461A22AB3CCC
B85F15B041A52AB71520BF2CE81BE5B660108AB5
BD28A8CB90C4FDAFBF9C3E5E7CDDE29B5F04696A
BDB0F71C8EB2572080D38F036E3EB33494500E9E
BE376A38E3544BD46702A0813D1C20F1CA0F2774
C79C7E957B045113F6633AB5DA17433F30E49920
C845F4940640111E54B95F940408D875CAEFDB2D
D413EFB945DD329590FD906F409B0570EA3D15A3
E1187B549916C32F4B784C02BC53B0FC8DD939E7
E5EAA232F5DBE71006A2C72F928055325D9731AA
F367D050B44CDBCFC92E7EE9AD10A71F2DE58FA3
F79C822281CB1001E589296C80ABA6EA5DC7E36A
FD44963BCB64D01C91E3AD2F656803F8819F0CBA
FE60EAB170C7D45B57E5C55D6D3E9B7F4DEE314A
FE95DEED6113559858942A303D095C23AAD9D954
MyFamily (legacy declarations)
Effective Members: 0
none
Alleged Members: 5
(they don't list you back)
31DF86181F39B9F7464F33E633996274079CD122 (not in the network)
6B24AB532979E56A956A4F5EE23CC0B4AA17FA81 (not in the network)
998BF851EC7DB8F6ECBB0DB3F5366CD71BFF799C (not in the network)
A8594D49241615BB39B7A8A1B65908392B493D0E (not in the network)
F3D59D6E53CD3B7C114D8BFBB6DECBD99085B1D2 (not in the network)
Indirect Members: 4
(they list you, you don't list them)
49834AA2038D295FFC4338F0E567F6D382076D1E
4BC912403ED890A2D056D6F82FE11D159BF151C1
548FA7BBE882FA285895051AC8157A02E1637211
A2CFC74E7E3ABC98516F7B1967C52CF7CF418A4B

Platform
Linux — Tor 0.4.9.17 on Linux
Version
0.4.9.17 — Recommended
Version Status
Recommended

DNS Health
Not an exit relay — DNS health testing does not apply.
IPv4 Exit Policy Summary
reject: 
  1-65535
IPv6 Exit Policy Summary
None
Full Exit Policy
reject *:*

Last fetch was at Fri, 20 Nov 2026 09:15:37 GMT.

Data from Tor CollecTor (authority votes, fetched 2026-11-20 08:45:05).

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)
E30CF7B3 Yes Yes No — Y Yes Yes Running, Valid, V2Dir, Fast 184.0 Mbit/s (M) | 816.0 Kbit/s 184.0 Mbit/s (M) | 184.0 Mbit/s OR 16.8 Mbit/s 97.7% | 98% 5.4455d | 5d 2.3d | 3.9d 1.2d | 5.1d 2026-11-19 22:18:20 184.0 Mbit/s (M)
dannenberg (DE) Yes Yes No — Y Yes Yes Running, Valid, V2Dir, Fast, Stable, HSDir 488.0 Mbit/s (M) | 816.0 Kbit/s 488.0 Mbit/s (M) | 248.0 Mbit/s OR 16.8 Mbit/s 81.1% | 98% 15.7d | 8d 8.2d | 8.2d 1.2d | 5.1d 2026-11-19 22:18:20 488.0 Mbit/s (M)
dizum (NL) Yes Yes No — N Yes Yes Running, Valid, V2Dir, Fast, Stable, HSDir 80.0 Mbit/s (R) | 816.0 Kbit/s 80.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 79.8% | 98% 15.8d | 8d 8.2d | 6.8d 1.2d | 5.1d 2026-11-19 22:18:20 80.0 Mbit/s (R)
faravahar (US) Yes Yes No — Y Yes Yes Running, Valid, V2Dir, Fast, Stable, HSDir 80.0 Mbit/s (R) | 816.0 Kbit/s 80.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 81.1% | 98% 15.7d | 8d 8.3d | 7.0d 1.2d | 5.1d 2026-11-19 22:18:20 80.0 Mbit/s (R)
gabelmoo (DE) Yes Yes No — Y Yes Yes Running, Valid, V2Dir, Fast 192.0 Mbit/s (M) | 816.0 Kbit/s 192.0 Mbit/s (M) | 240.0 Mbit/s OR 16.8 Mbit/s 80.2% | 98% 15.8d | 8d 4.0d | 8.3d 1.2d | 5.1d 2026-11-19 22:18:20 192.0 Mbit/s (M)
longclaw (US) Yes Yes No — Y Yes N/T Running, Valid, V2Dir, Fast, Stable, HSDir 464.0 Mbit/s (M) | 816.0 Kbit/s 464.0 Mbit/s (M) | 240.0 Mbit/s OR 16.8 Mbit/s 81.1% | 98% 15.7d | 8d 8.3d | 9.1d 1.2d | 5.1d 2026-11-19 22:18:20 464.0 Mbit/s (M)
maatuska (SE) Yes Yes No — N Yes Yes Running, Valid, V2Dir, Fast 80.0 Mbit/s (R) | 816.0 Kbit/s 80.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 76.4% | 98% 14.2d | 8d 1.2d | 2.3d 1.2d | 5.1d 2026-11-19 22:18:20 80.0 Mbit/s (R)
moria1 (US) Yes Yes No — Y Yes Yes Running, Valid, V2Dir, Fast, Stable 208.0 Mbit/s (M) | 8.4 Mbit/s 208.0 Mbit/s (M) | 184.0 Mbit/s OR 16.8 Mbit/s 84.2% | 98% 9.8d | 8d 16293.6d | 12669.7d 1.2d | 5.0d 2026-11-19 22:18:20 208.0 Mbit/s (M)
tor26 (AT) Yes Yes No — Y Yes Yes Running, Valid, V2Dir, Fast, Stable, HSDir 352.0 Mbit/s (M) | 816.0 Kbit/s 352.0 Mbit/s (M) | 240.0 Mbit/s OR 16.8 Mbit/s 80.5% | 98% 15.6d | 8d 8.2d | 8.2d 1.2d | 5.1d 2026-11-19 22:18:20 352.0 Mbit/s (M)

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.