Only proven relays are included in the graph and table. A proven relay claims to be part of a domain and can be verified to be part of it via the “well-known” URL or DNS records.
| Nickname | Mbit/s | Exit | IPv4 | IPv6 | First Seen | Tor Version | AS Name |
|---|---|---|---|---|---|---|---|
| toralf2 | 419 | N | 65.21.94.13 | 2a01:4f9:3b:468e::13 | 2018-10-06 | 0.4.8.0-alpha-dev | Hetzner Online GmbH |
| toralf | 406 | N | 65.21.94.13 | 2a01:4f9:3b:468e::13 | 2018-10-06 | 0.4.8.0-alpha-dev | Hetzner Online GmbH |
Bridges
| Nickname | Advertised Bandwidth (Mbit/s) | Tor Version |
|---|---|---|
| toralf4borstel | 129 | 0.4.7.13 |
| toralf4casimir | 104 | 0.4.7.13 |
| toralf4hoppel | 92 | 0.4.7.13 |
| toralf4seidenpelz | 83 | 0.4.7.13 |
| toralf4nickeneck | 77 | 0.4.7.13 |
| toralf4pittiplatsch | 76 | 0.4.7.13 |
| toralf4uhu | 69 | 0.4.7.13 |
| toralf4moppi | 62 | 0.4.7.13 |
| toralf4mauz | 53 | 0.4.7.13 |
| toralf4schwarzrock | 51 | 0.4.7.13 |
| toralf4igel | 45 | 0.4.7.13 |
| toralf4tim | 41 | 0.4.7.13 |
| toralf4struppi | 41 | 0.4.7.13 |
| toralf4buddelflink | 40 | 0.4.7.13 |
| toralf4drehrumbum | 40 | 0.4.7.13 |
| toralf4fuchs | 34 | 0.4.7.13 |
| toralf4rotpelz | 29 | 0.4.7.13 |
| toralf4gertrud | 27 | 0.4.7.13 |
| toralf4elster | 26 | 0.4.7.13 |
| toralf4schnatterinc | 26 | 0.4.7.13 |
| toralf4mischka | 23 | 0.4.7.13 |