View Relay "F3Netze"

Fingerprint: 6BCB964AB74E23F8986BDA905697D3A6BE08AF28 | Operator: f3netze.de v2 (24 relays) ✓ Validated ⚠ this relay: Misconfigured| Family: 8 relays | F3 Netze <abuse@f3netze.de>... | AS205100 | Germany | Linux

Consensus
In Consensus (has Running flag)
Flags
Exit, Running, V2Dir, Valid (4)
BW Verified
Not Measured
Stability
Incomplete | UP 1h 42m 41s ago
BW Weight
0 Kbit/s Observed By Relay
Version
0.4.9.17 Recommended
Overload status incomplete. No bandwidth record available for this relay Overload details

Addresses
OR Address
tor-exit-1.zbau.f3netze.de
185.220.100.252:9100
[2a0b:f4c0:16c:4::1]:9100
Reachability (Directory Authorities)
Status
Reachability data unavailable
Location
Country
Germany Germany
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS205100
AS Name
F3 Netze e.V. (BGP.tools)
AS Rarity
Epic (score: 3/5, 1.29% consensus weight, 1 operator)

Capacity (Relay Reported)
Observed Bandwidth
0.00 Kbit/s
Advertised Bandwidth
Unknown
Rate Limit
8.59 Gbit/s
Burst Limit
8.59 Gbit/s
Total Data
N/A
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-11-20 13:15:05

Measured By
Not Yet Measured
Network Participation: Consensus Weight: N/A | Guard: N/A | Middle: N/A | Exit: N/A

Uptime Metrics
Current Status
UP 1h 42m 41s ago
Overall Uptime (1M/6M/1Y/5Y)
0.0%/0.0%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
N/A
Hibernating
No
Timestamps
First Seen
1h 15m 19s ago (2026-11-20 13:00:00)
Last Seen
1h 15m 19s ago (2026-11-20 13:00:00)
Last Restarted
1h 42m 41s ago (2026-11-20 12:32:38)
Last Changed Address
2026-11-20 13:00:00
Overload status: Incomplete — not every signal could be evaluated. (No bandwidth record available for this relay)

Evaluated 2026-11-20 14:15 UTC. /details snapshot 2026-11-20 13:00:00 UTC (cached 18s ago). /bandwidth snapshot 2026-11-20 02:00:00 UTC (cached 11h ago).

General Overload (from /details)
Status
No general overload report in available data
File Descriptor Exhaustion (from /bandwidth)
Status
No bandwidth record available for this relay
Rate Limits (from /bandwidth)
Status
No bandwidth record available for this relay
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

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

DNS Health
Status
Not Tested
IPv4 Exit Policy Summary
reject: 
  22
  25
IPv6 Exit Policy Summary
reject: 
  22
  25
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 185.220.100.252:*
reject *:25
reject *:22
accept *:*

Last fetch was at Fri, 20 Nov 2026 14:15:19 GMT.