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 |
|---|---|---|---|---|---|---|---|
| TorRelay2b | 167 | N | 89.58.5.0 | 2a03:4000:5e:c47::1 | 2022-11-29 | 0.4.7.13 | netcup GmbH |
| TorRelay1b | 167 | N | 89.58.54.129 | 2a03:4000:69:e40::1 | 2022-01-06 | 0.4.7.13 | netcup GmbH |
| TorRelay1c | 167 | N | 89.58.54.129 | 2a03:4000:69:e40::1 | 2023-03-11 | 0.4.7.13 | netcup GmbH |
| TorRelay2c | 167 | N | 89.58.5.0 | 2a03:4000:5e:c47::1 | 2023-03-11 | 0.4.7.13 | netcup GmbH |
| TorRelay1a | 167 | N | 89.58.54.129 | 2a03:4000:69:e40::1 | 2022-01-06 | 0.4.7.13 | netcup GmbH |
| TorRelay2a | 167 | N | 89.58.5.0 | 2a03:4000:5e:c47::1 | 2022-11-29 | 0.4.7.13 | netcup GmbH |
Bridges
| Nickname | Advertised Bandwidth (Mbit/s) | Tor Version |
|---|---|---|
| Obfs4Bridge | 131 | 0.4.7.13 |
| Obfs4Bridge | 89 | 0.4.7.13 |
| Obfs4Bridge | 52 | 0.4.7.13 |
| Obfs4Bridge | 46 | 0.4.7.13 |
| Obfs4Bridge | 35 | 0.4.7.13 |