August 2019 - tor-commits - lists.torproject.org

[community/staging] Fix broken links and typos in community resources child pages
by pili＠torproject.org 02 Aug '19

02 Aug '19

commit 5ba855fc8971c8cf4a2d14b71089fd2048b52119 Author: gus <gus(a)torproject.org> Date: Fri Jul 5 15:28:22 2019 -0400 Fix broken links and typos in community resources child pages --- content/relay-operations/community-resources/contents.lr | 10 +++++----- .../community-resources/tor-abuse-templates/contents.lr | 2 +- .../community-resources/tor-relay-universities/contents.lr | 5 +++-- 3 files changed, 9 insertions(+), 8 deletions(-) diff --git a/content/relay-operations/community-resources/contents.lr b/content/relay-operations/community-resources/contents.lr index 935d20d..e6be9c0 100644 --- a/content/relay-operations/community-resources/contents.lr +++ b/content/relay-operations/community-resources/contents.lr @@ -28,7 +28,7 @@ Also see the [Tor Exit Guidelines](tor-exit-guidelines). Operators can put together their own abuse complaint template responses from one of many templates that Tor has created: [Tor Abuse Templates](tor-abuse-templates). -It is important to respond to abuse complaints in a timely manner (usually within 24 hours). If the hoster gets annoyed by the amount of abuse you can reduce the amount of ports allowed in your exit policy. Please document your experience with new hosters on the following wiki page: [GoodBadISPs](/good-bad-isps) +It is important to respond to abuse complaints in a timely manner (usually within 24 hours). If the hoster gets annoyed by the amount of abuse you can reduce the amount of ports allowed in your exit policy. Please document your experience with new hosters on the following wiki page: [GoodBadISPs](good-bad-isps) Other docs we like: @@ -49,11 +49,11 @@ The next steps are figuring out hardware, transit, and server hosting. Depending ## At your university -Many computer science departments, university libraries, and individual students and faculty run relays from university networks. These universities include the Massachusetts Institute of Technology (MIT CSAIL), Boston University, the University of Waterloo, the University of Washington, Northeastern University, Karlstad University, Universitaet Stuttgart, and Friedrich-Alexander University Erlangen-Nuremberg. To learn more about how to get support for a relay on your university's network, check out EFF's resources: [Tor no campus](https://www.eff.org/torchallenge/tor-on-campus.html). +Many computer science departments, university libraries, and individual students and faculty run relays from university networks. These universities include the Massachusetts Institute of Technology (MIT CSAIL), Boston University, the University of Waterloo, the University of Washington, Northeastern University, Karlstad University, Universitaet Stuttgart, and Friedrich-Alexander University Erlangen-Nuremberg. To learn more about how to get support for a relay on your university's network, check out EFF's resources: [Tor on campus](https://www.eff.org/torchallenge/tor-on-campus.html). ## At your company or organization -If you work at a Tor-friendly company or organization, that's another ideal place to run a relay. Some companies running relays include Brass Horn Communications, Quintex Alliance Consulting, and OmuraVPN. Some organizations running Tor relays include Digital Courage, Access Now, Derechos Digitales, and Lebanon Libraries in New Hampshire. +If you work at a Tor-friendly company or organization, that's another ideal place to run a relay. Some companies running relays include Brass Horn Communications, Quintex Alliance Consulting, and OmuraVPN. Some organizations running Tor relays include Digital Courage, [Access Now](https://www.accessnow.org/), [Derechos Digitales](https://tor.derechosdigitales.org), [Enjambre Digital](https://tor.enjambre.net/) and Lebanon Libraries in New Hampshire. # More resources @@ -61,7 +61,7 @@ Congratulations, you're officially a Tor relay operator! What now? * You can check out traffic and other statistics for your relay at our [Relay Search](https://metrics.torproject.org/rs.html) (your relay will appear on "Relay Search" about 3 hours after you started it). -* There is also more info about running a relay at the [Tor FAQ](https://www.torproject.org/docs/faq.html.en#HowDoIDecide). +* There is also more info about running a relay at the [Tor FAQ](https://2019.www.torproject.org/docs/faq.html.en#HowDoIDecide). -* And, most importantly, make sure to email tshirt(a)torproject.org and [claim your swag](https://www.torproject.org/getinvolved/tshirt.html). It's our way of saying thanks for defending privacy and free speech online. +* And, most importantly, make sure to email tshirt(a)torproject.org and [claim your swag](https://2019.www.torproject.org/getinvolved/tshirt.html). It's our way of saying thanks for defending privacy and free speech online. diff --git a/content/relay-operations/community-resources/tor-abuse-templates/contents.lr b/content/relay-operations/community-resources/tor-abuse-templates/contents.lr index b24cf79..f9952e6 100644 --- a/content/relay-operations/community-resources/tor-abuse-templates/contents.lr +++ b/content/relay-operations/community-resources/tor-abuse-templates/contents.lr @@ -14,7 +14,7 @@ Below are a collection of letters you can use to respond to your ISP about their The general format of these templates is to inform the complaintant about Tor, to help them to find a solution to their particular issue that works in general for the Internet at large (open wifi, open proxies, botnets, etc), and barring all else, how to block Tor. The philosophy of the Tor Project is that abuse should be handled proactively by the site administrators, rather than wasting effort and resources on seeking vengeance and chasing ghosts. -The difference between the proactive approach and the reactive approach to abuse is the difference between decentralized fault-tolerant Internet freedom, and fragile, corruptible totalitarian control. To further preach to the choir, the identity-based Internet "driver's licenses" of South Korea and China have done nothing to curtail cybercrime and Internet abuse. In fact, all [http://boingboing.net/2011/08/12/south-korea-to-abandon-real-name-internet-… objective evidence] seems to indicate that it has only created new markets for organized crime to preside over. This is the core idea that these abuse complaint templates attempt to instil in the recipient. Feel free to improve them if you feel they fall short of this goal. +The difference between the proactive approach and the reactive approach to abuse is the difference between decentralized fault-tolerant Internet freedom, and fragile, corruptible totalitarian control. To further preach to the choir, the identity-based Internet "driver's licenses" of South Korea and China have done nothing to curtail cybercrime and Internet abuse. In fact, all [objective evidence](http://boingboing.net/2011/08/12/south-korea-to-abandon-real-name… seems to indicate that it has only created new markets for organized crime to preside over. This is the core idea that these abuse complaint templates attempt to instil in the recipient. Feel free to improve them if you feel they fall short of this goal. All templates should include the Common Boilerplate below, and append some additional paragraphs depending on the specific Scenario. diff --git a/content/relay-operations/community-resources/tor-relay-universities/contents.lr b/content/relay-operations/community-resources/tor-relay-universities/contents.lr index 0fb65a2..14040b8 100644 --- a/content/relay-operations/community-resources/tor-relay-universities/contents.lr +++ b/content/relay-operations/community-resources/tor-relay-universities/contents.lr @@ -30,13 +30,14 @@ In some cases, you should talk to the network security people before you talk to If the authorities contact your university for logs, be pleasant and helpful. Tor's default log level doesn't provide much that's useful, so if they want copies of your logs, that's fine. Be helpful and take the opportunity to explain to them about Tor and why it's useful to the world. (If they contact you directly for logs, you should send them to your university's lawyers -- acting on it yourself is [almost always a poor idea](https://2019.www.torproject.org/eff/tor-legal-faq.html#RequestForLogs). -If there are too many complaints coming in, there are several approaches you can take to reduce them. First, you should follow the tips in the [Tor relay documentation](https://community.torproject.org/relay), such +If there are too many complaints coming in, there are several approaches you can take to reduce them. First, you should follow the tips in the [Tor relay documentation](https://community.torproject.org/relay-operations), such as picking a descriptive hostname or getting your own IP address. If that doesn't work, you can scale back the advertised speed of your relay, by using the Max``Advertised``Bandwidth to attract less traffic from the Tor network. Lastly, you can scale back your exit policy. Some people have found that their university only tolerates their Tor relay if they're involved in a research project around anonymity. So if you're interested, you might want to get that started early in the process -- see our [Research Portal](https://research.torproject.org/). This approach has the added benefit that you can draw in other faculty and students in the process. The downside is that your Tor relay's existence is more fragile, since the terms of its demise are already negotiated. Note that in many cases you don't even need to be researching the exit node itself -- doing research on the Tor network requires that there be a Tor network, after all, and keeping it going is a community effort. +Subscribe to [Tor Relays Universities](https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-rel… mailing list (and other education institutions too). --- -cta: Subscribe to Tor at universities, colleges, and other education institutions: https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays-universiti… +cta: --- html: two-columns-page.html ---

1 0

[community/staging] Add how to get your Tor swags in community resources
by pili＠torproject.org 02 Aug '19

02 Aug '19

commit e0e57946065e6104cfc8e826f3d63151c78bc559 Author: gus <gus(a)torproject.org> Date: Fri Jul 5 18:29:22 2019 -0400 Add how to get your Tor swags in community resources --- .../community-resources/swags/contents.lr | 25 ++++++++++++++++++++++ 1 file changed, 25 insertions(+) diff --git a/content/relay-operations/community-resources/swags/contents.lr b/content/relay-operations/community-resources/swags/contents.lr new file mode 100644 index 0000000..f8b7c20 --- /dev/null +++ b/content/relay-operations/community-resources/swags/contents.lr @@ -0,0 +1,25 @@ +_model: page +--- +title: Swags +--- +body: + +You can get one of these fine Tor T-shirts for contributing to the Tor project. There are two primary ways of contributing: + +* Operate a fast Tor relay that's been running for the past two months: you are eligible if you allow exits to port 80 and you average 250 KBytes/s traffic, or if you're not an exit but you average 500 KBytes/s traffic. + +* Help out in other ways. Maintain a translation. Run Tor trainings. Write a good support program and get a lot of people to use it. Do research on Tor and anonymity, solve some of our bugs, or establish yourself as a Tor advocate. + +If you're operating a fast relay or you've done something else cool, email us at tshirt(a)torproject.org with the details. (We want to make sure our shirts help outreach happen all around the world, so please understand if we can't send you 5 shirts for your 5 excellent relays.) + +There are a variety of colors, shapes, and sizes available in the great roots design that Leiah Jansen made for us, as well as some older designs. +--- +html: two-columns-page.html +--- +key: 5 +--- +section: Community Resources +--- +section_id: community-resources +--- +subtitle: If you're operating a fast relay or you've done something else cool, you're eligible to receive our swags

1 0

[community/staging] Move how to use ansible relayor from technical-setup main page to good practices page
by pili＠torproject.org 02 Aug '19

02 Aug '19

commit e45978fc08d83d0c0d444240932857eb510a16c9 Author: gus <gus(a)torproject.org> Date: Fri Jul 5 18:28:18 2019 -0400 Move how to use ansible relayor from technical-setup main page to good practices page --- .../relay-operations/technical-setup/contents.lr | 10 +---- .../contents.lr | 52 ++++++++++++---------- 2 files changed, 29 insertions(+), 33 deletions(-) diff --git a/content/relay-operations/technical-setup/contents.lr b/content/relay-operations/technical-setup/contents.lr index 07925c7..886bacc 100644 --- a/content/relay-operations/technical-setup/contents.lr +++ b/content/relay-operations/technical-setup/contents.lr @@ -38,14 +38,6 @@ If you are looking to run a relay with minimal effort we recommend you stick to The installation commands are shown in code blocks and must be executed with root privileges. -## Configuration Management - -If you plan to run more than a single relay, or you want to run a high capacity relay (multiple Tor instances per server) or want to use strong security features like [Offline Master Keys](https://trac.torproject.org/projects/tor/wiki/doc/TorRelaySecurity/Of… without performing additional steps manually, you may want to use a configuration management for better maintainability. - -There are multiple configuration management solutions for Unix based operating systems (Ansible, Puppet, Salt, ...). - -The following Ansible Role has specifically been build for Tor relay operators and supports multiple operating systems: [Ansible Relayor](http://github.com/nusenu/ansible-relayor). - -Click below in which type of relay do you want to host. +Click below in which type of relay do you want to host and don't forget to read [Relay post-install and good practices](relays-post-install-and-good-practices). --- _slug: {{setup}} diff --git a/content/relay-operations/technical-setup/relays-post-install-and-good-practices/contents.lr b/content/relay-operations/technical-setup/relays-post-install-and-good-practices/contents.lr index 8373219..5236fbe 100644 --- a/content/relay-operations/technical-setup/relays-post-install-and-good-practices/contents.lr +++ b/content/relay-operations/technical-setup/relays-post-install-and-good-practices/contents.lr @@ -28,8 +28,31 @@ You can search for your relay using your nickname or IP address. It takes some time for relay traffic to ramp up, this is especially true for guard relays but to a lesser extend also for exit relays. To understand this process, read about the [lifecycle of a new relay](https://blog.torproject.org/lifecycle-new-relay). +# 4. Configuration Management -#4. Optional: Limiting bandwidth usage (and traffic) +If you plan to run more than a single relay, or you want to run a high capacity relay (multiple Tor instances per server) or want to use strong security features like [Offline Master Keys](https://trac.torproject.org/projects/tor/wiki/doc/TorRelaySecurity/Of… without performing additional steps manually, you may want to use a configuration management for better maintainability. + +There are multiple configuration management solutions for Unix based operating systems (Ansible, Puppet, Salt, ...). + +The following Ansible Role has specifically been build for Tor relay operators and supports multiple operating systems: [Ansible Relayor](http://github.com/nusenu/ansible-relayor). + +# 5. Important: if you run more than one Tor instance + +To avoid putting Tor clients at risk when operating multiple relays you must set a proper [MyFamily](https://2019.www.torproject.org/docs/tor-manual.html.en#MyFamily) value and have a valid [ContactInfo](https://2019.www.torproject.org/docs/tor-manual.html.en#Contac… in your torrc configuration. +The MyFamily setting is simply telling Tor clients what Tor relays are controlled by a single entity/operator/organization, so they are not used in multiple positions in a single circuit. + +If you run two relays and they have fingerprints AAAAAAAAAA and BBBBBBBB, you would add the following configuration to set MyFamily: + +``` +MyFamily AAAAAAAAAA,BBBBBBBB +``` + +to both relays. To find your relays fingerprint you can look into the log files when tor starts up or find the file named "fingerprint" in your tor DataDirectory. + +Instead of doing so manually for big operators we recommend to automate the MyFamily setting via a configuration management solution. +Manually managing MyFamily for big relay groups is error prone and can put Tor clients at risk. + +# 6. Optional: Limiting bandwidth usage (and traffic) Tor will not limit its bandwidth usage by default, but supports multiple ways to restrict the used bandwidth and the amount of traffic. This can be handy if you want to ensure that your Tor relay does not exceed a certain amount of bandwidth or total traffic per day/week/month. @@ -44,9 +67,9 @@ The following torrc configuration options can be used to restrict bandwidth and Having a fast relay for some time of the month is preferred over a slow relay for the entire month. -Also see the bandwidth entry in the FAQ: https://www.torproject.org/docs/faq.html.en#BandwidthShaping +Also see the bandwidth entry in the [FAQ](https://www.torproject.org/docs/faq.html.en#BandwidthShaping). -# 5. Check IPv6 availability +# 7. Check IPv6 availability We encourage everyone to enable IPv6 on their relays. This is especially valuable on exit and guard relays. @@ -84,24 +107,7 @@ IPv6Exit 1 Note: Tor requires IPv4 connectivity, you can not run a Tor relay on IPv6-only. -# 6. Important: if you run more than one Tor instance - -To avoid putting Tor clients at risk when operating multiple relays you must set a proper [MyFamily](https://2019.www.torproject.org/docs/tor-manual.html.en#MyFamily) value and have a valid [ContactInfo](https://2019.www.torproject.org/docs/tor-manual.html.en#Contac… in your torrc configuration. -The MyFamily setting is simply telling Tor clients what Tor relays are controlled by a single entity/operator/organization, so they are not used in multiple positions in a single circuit. - -If you run two relays and they have fingerprints AAAAAAAAAA and BBBBBBBB, you would add the following configuration to set MyFamily: - -``` -MyFamily AAAAAAAAAA,BBBBBBBB -``` - -to both relays. To find your relays fingerprint you can look into the log files when tor starts up or find the file named "fingerprint" in your tor DataDirectory. - -Instead of doing so manually for big operators we recommend to automate the MyFamily setting via a configuration management solution. -Manually managing MyFamily for big relaygroups is error prone and can put Tor clients at risk. - - -# 7. Maintaining a relay +# 8. Maintaining a relay ## Backup Tor Identity Keys @@ -116,9 +122,7 @@ Default locations of the keys folder: ## Subscribe to the tor-announce mailing list -This is a very low traffic mailing list and you will get information about new stable tor releases and important security update information. - -* https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-announce +This is a very low traffic mailing list and you will get information about new stable tor releases and important security update information: [tor-announce](https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-ann…. ## Setting up outage notifications

1 0

[community/staging] GoodBadISPs - Austria, Bulgaria, Germany, UK, France, Finland, Hungary, Iceland, Italy, Moldova
by pili＠torproject.org 02 Aug '19

02 Aug '19

commit 843b24e9870413e4d74d00ecea02811493514ae1 Author: gus <gus(a)torproject.org> Date: Sat Jul 6 11:13:33 2019 -0400 GoodBadISPs - Austria, Bulgaria, Germany, UK, France, Finland, Hungary, Iceland, Italy, Moldova --- .../community-resources/good-bad-isps/contents.lr | 118 ++++++++++++++++++++- 1 file changed, 117 insertions(+), 1 deletion(-) diff --git a/content/relay-operations/community-resources/good-bad-isps/contents.lr b/content/relay-operations/community-resources/good-bad-isps/contents.lr index 7384bc1..9e2576e 100644 --- a/content/relay-operations/community-resources/good-bad-isps/contents.lr +++ b/content/relay-operations/community-resources/good-bad-isps/contents.lr @@ -16,7 +16,8 @@ For network diversity and stronger anonymity, you should avoid providers and cou # Good Experiences -## US + +### US | **Company/ISP** | **ASN** | **Bridges** | **Relay** | **Exit** | **Comments** | **Last Updated** | |-------------------------|-------------|-----------------|--------------|-------------|---------------------|------------------------| @@ -66,6 +67,121 @@ For network diversity and stronger anonymity, you should avoid providers and cou +### Austria + +| **Company/ISP** | **ASN** | **Bridges** | **Relay** | **Exit** | **Comments** | **Last Updated** | +|-------------------------|-------------|-----------------|--------------|-------------|---------------------|------------------------| +| [UPC Austria GmbH](https://www.upc.at/) | - | - | Yes | Yes | (ISP) does not care what their customers do at all (unless you have a business connection) | 12/2011 | +| [Silver Server GmbH](http://sil.at/) | - | -| Yes | Yes | Forwards abuse. Hosts already some big exit/entry nodes which seem to have no problems. Very expensive traffic. | 12/2011 | +| [Tele2 Austria GmbH](https://tele2.at/) | - | - | Yes | Yes | Forwards abuse at business connections, good quality traffic, does not like "proxys" on private lines. Cheap synchronous (SDSL) connections. | 12/2011 | +| [A1(former Telekom Austria)](http://a1.net) | - | - | Yes | No | Does not like Abuse (in any form) at all. Seems to give out customer data at alleged abuse. Not recommended but cheap. | 12/2011 | +| [xpirio GmbH](http://xpirio.at) | - | - | Yes | ? | In general rather relaxed at all services, but better get in touch with their (very understanding) support when you expect abuse. | 12/2011 | + + + +### Bulgaria + +| **Company/ISP** | **ASN** | **Bridges** | **Relay** | **Exit** | **Comments** | **Last Updated** | +|-------------------------|-------------|-----------------|--------------|-------------|---------------------|------------------------| +| [VPS.BG](https://www.vpsbg.eu/en/) | - | Yes | Yes | Yes | They don't collect any personal info and you can pay in bitcoin. | 01/11/2016 | + + + +### Germany + +| **Company/ISP** | **ASN** | **Bridges** | **Relay** | **Exit** | **Comments** | **Last Updated** | +|-------------------------|-------------|-----------------|--------------|-------------|---------------------|------------------------| +| [Weesly](http://weesly.de) | - | Yes | Yes | Yes | Note that you should let them know about your intention when ordering a server or in advance. | 06/2013 | +| [EUServ](http://euserv.de) | - | - | Yes | No | They have a bad support, but if you know how to maintain your server, this ISP is a good choice. | - | +| [IPX-Server](https://www.ipx-server.de/) | - | Yes | Yes | - | - | - | +| [Keyweb](https://www.keyweb.de/) | - | - | Yes | Yes | - | - | +| [Afterburst](http://afterburst.com) | - | - | Yes | No | - | - | +| [myLoc Managed IT](https://myloc.de) | AS31010, AS24961 | Yes | Yes | No | - | 2018-10-25 | +| [linevast](https://www.linevast.de/) | - | Yes | Yes | Yes | Only allowed on dedicated servers | 13/11/2015 | +| [Server4You](https://www.server4you.de/)| - | Yes | Yes | No | Part of [Intergenia AG](http://www.intergenia.de/)), I've asked Server4You support and they state servers with complaints about Tor will be canceled immediately (see the quote in the "Bad Experience" section) | - | +| [Hetzner](http://hetzner.de/) | - | - | Yes | No | Offers good dedicated root servers for a good price. | +| [Contabo](https://contabo.de) | - | Yes | Yes | Yes | Has no restriction for relays or exit nodes. However, possible abuse complaints will be forwarded to the owner and need to be addressed. | 2018/06 | +| [Strato](https://strato.de) | - | - | Yes | No | Exit-Nodes are prohibited by their general terms and conditions | - | +| [PraHost](https://www.prahost.com/) | - | - | Yes | Yes | Stated in November 2014 that they allow exit nodes if abuse complaints are handled. Suspends the server if no "valid" action (read: blocking) is taken within 24 hours of an abuse ticket. Their ticket system does not reliably handle email replies, use the web interface instead. | 2017-10-31 | +| [DomainFactory](https://www.df.eu/de/cloud-hosting/cloud-server/) | - | - | Yes | No | - | - | +| [NetCologne](https://www.netcologne.de/) | - | - | Yes | Yes | - | - | + + + +### United Kingdom + +| **Company/ISP** | **ASN** | **Bridges** | **Relay** | **Exit** | **Comments** | **Last Updated** | +|-------------------------|-------------|-----------------|--------------|-------------|---------------------|------------------------| +| [Gigatux](https://www.gigatux.com) | - | Yes | Yes | Yes | They actually run their own relay named Gigatux. They also offer servers in the US, Germany, and Israel. | - | +| [Clustered.net](http://www.clustered.net) | - | Yes | Yes | Yes | - | - | +| [Bitfolk](http://bitfolk.com/) | - | Yes | Yes | Yes | They are very knowledgable and understand Tor and its uses. They are hot on spam and abuse so advise changing the default exit (good idea in the UK anyhow). Any DMCA notices received were simply forwarded on without agro | - | +| [RapidSwitch](http://rapidswitch.com/) | - | Yes | Yes | ? | - | 07/2014 | + + + +### France + +| **Company/ISP** | **ASN** | **Bridges** | **Relay** | **Exit** | **Comments** | **Last Updated** | +|-------------------------|-------------|-----------------|--------------|-------------|---------------------|------------------------| +| [Online.net](http://www.online.net/) | AS12876 | Yes | Yes | Yes | The account holder is responsible for all the traffic going through theirs servers.| 01/28/2019 | +| [Gandi VPS](https://www.gandi.net/) | - | Yes | Yes | Yes| Gandi send some abuse complaints to Exit relays, but they do not stop the server, and when you tell them your server is a Tor Exit relay, they say it is OK. They ask Exit relays to use the standard Reduced Exit Policy | - | +| [OVH Kimsufi](http://www.kimsufi.com/) | - | Yes | Yes | No | Changed their TOS in July 2013 and allow Tor as long as they don't notice illegal activities. Exit nodes would eventually be shut down, but relays are allowed. Octave Klaba, CEO of OVH said himself that the TOS have been changed to make them clearer about the use of Tor. Many relays are currently running on Kimsufi servers | - | +| [Digicube](http://www.digicube.fr/) | - | Yes | Yes | Yes | - | - | +| [Pulse Servers](http://www.pulseservers.com/) | - | Yes | Yes | Yes | VPS uses OVH AS. You can build ANY kind tor relays. | 05/01/2016 | + + + +### Finland + +| **Company/ISP** | **ASN** | **Bridges** | **Relay** | **Exit** | **Comments** | **Last Updated** | +|-------------------------|-------------|-----------------|--------------|-------------|---------------------|------------------------| +| [Creanova](http://creanova.org) | AS51765 | Yes | Yes | No | - | 12/19/2018 | +| [TeliaSonera Finland](https://www.sonera.fi/) | AS1759 | Yes | Yes | No | - | 03/26/2016 | + + + +### Hungary + +| **Company/ISP** | **ASN** | **Bridges** | **Relay** | **Exit** | **Comments** | **Last Updated** | +|-------------------------|-------------|-----------------|--------------|-------------|---------------------|------------------------| +| [ServerAstra](https://serverastra.com/) | AS56322 | Yes | Yes | Yes | They only say you should answer abuse requests in 24h. ISP has re-confirmed by e-mail that exit nodes are acceptable, with "strict" exit node policies. | 2014-10-15 | + + +### Iceland + +| **Company/ISP** | **ASN** | **Bridges** | **Relay** | **Exit** | **Comments** | **Last Updated** | +|-------------------------|-------------|-----------------|--------------|-------------|---------------------|------------------------| +| [1984Hosting](https://1984hosting.com/) | - | Yes | Yes | Yes | - | - | +| [FlokiNET]https://flokinet.is/) | (AS200651) | Yes | Yes | Yes | Sponsor enn.lu and saveyourprivacy exit nodes | - | +| [orangewebsite](https://www.orangewebsite.com/vps.php) | - | Yes | Yes | Yes? | - | - | + + +### Italy + +| **Company/ISP** | **ASN** | **Bridges** | **Relay** | **Exit** | **Comments** | **Last Updated** | +|-------------------------|-------------|-----------------|--------------|-------------|---------------------|------------------------| +| [Fastweb](https://fastweb.it/) | - | Yes | Yes | Yes | - | - | +| [Prometeus](https://www.prometeus.net/sito/) | - | Yes | Yes | No | - | - | +| [ArubaCloud /Aruba](https://cloud.it/) | - | Yes | Yes | Yes | TOS generically indicate that the operator is responsible for all the activities on the machine. [Read more](https://balist.es/blog/2016/04/18/running-a-tor-exit-node-on-aruba-arubacloud-a-detailed-account/) | - | +| [SelfServer by Enter](https://selfserver.it/) | - | Yes | Yes | Yes | Uncomfortable due to old CentOS 6.10, NATed IPv4-only networking, ports other than the well-known are filtered. Abuse complaints need to go through their support service | 11/2018 | + + + + +### Moldova + +| **Company/ISP** | **ASN** | **Bridges** | **Relay** | **Exit** | **Comments** | **Last Updated** | +|-------------------------|-------------|-----------------|--------------|-------------|---------------------|------------------------| +| [MivoCloud](https://www.mivocloud.com/) | - | Yes | Yes | No | - | 09/13/16 | +| [Trabia](https://www.trabia.com/) | - | Yes | Yes | Yes | - | 08/13/17 | +| [AlexHost](https://alexhost.md/) | - | Yes | Yes | Yes | - | 07/21/2014 | + + + +### Netherlands + +| **Company/ISP** | **ASN** | **Bridges** | **Relay** | **Exit** | **Comments** | **Last Updated** | +|-------------------------|-------------|-----------------|--------------|-------------|---------------------|------------------------| --- html: two-columns-page.html

1 0

[community/staging] GoodBadISPs - add good isps from all countries.
by pili＠torproject.org 02 Aug '19

02 Aug '19

commit fd45bf3c3801655fab68d5e82a2d84a1e7d76770 Author: gus <gus(a)torproject.org> Date: Sun Jul 7 11:00:33 2019 -0400 GoodBadISPs - add good isps from all countries. --- .../community-resources/good-bad-isps/contents.lr | 142 ++++++++++++++++++++- 1 file changed, 141 insertions(+), 1 deletion(-) diff --git a/content/relay-operations/community-resources/good-bad-isps/contents.lr b/content/relay-operations/community-resources/good-bad-isps/contents.lr index 9e2576e..c9e52e1 100644 --- a/content/relay-operations/community-resources/good-bad-isps/contents.lr +++ b/content/relay-operations/community-resources/good-bad-isps/contents.lr @@ -12,6 +12,13 @@ Since non-exits do not attract complaints, it should be fine to run them without For network diversity and stronger anonymity, you should avoid providers and countries that already attract a lot of Tor capacity. [Metrics](https://metrics.torproject.org/) is a great tool that allows you to group probabilities by country and AS (autonomous systems), so you can more easily identify networks you want to avoid. + **Try to avoid** the following hosters: + +* OVH SAS (AS16276) +* Online S.a.s. (AS12876) +* Hetzner Online GmbH (AS24940) +* DigitalOcean, LLC (AS14061) + **Note**: This page is currently being revamped. If you would like to help out please see [#31063](https://trac.torproject.org/projects/tor/ticket/31063). # Good Experiences @@ -152,7 +159,7 @@ For network diversity and stronger anonymity, you should avoid providers and cou | **Company/ISP** | **ASN** | **Bridges** | **Relay** | **Exit** | **Comments** | **Last Updated** | |-------------------------|-------------|-----------------|--------------|-------------|---------------------|------------------------| | [1984Hosting](https://1984hosting.com/) | - | Yes | Yes | Yes | - | - | -| [FlokiNET]https://flokinet.is/) | (AS200651) | Yes | Yes | Yes | Sponsor enn.lu and saveyourprivacy exit nodes | - | +| [FlokiNET](https://flokinet.is/) | (AS200651) | Yes | Yes | Yes | Sponsor enn.lu and saveyourprivacy exit nodes | - | | [orangewebsite](https://www.orangewebsite.com/vps.php) | - | Yes | Yes | Yes? | - | - | @@ -182,6 +189,139 @@ For network diversity and stronger anonymity, you should avoid providers and cou | **Company/ISP** | **ASN** | **Bridges** | **Relay** | **Exit** | **Comments** | **Last Updated** | |-------------------------|-------------|-----------------|--------------|-------------|---------------------|------------------------| +| [XS4ALL](https://www.xs4all.nl/en/) | AS3265 | Yes | Yes | Yes | Abuse can result in temporary blocks, therefore they recommend to use an dedicated IP address for exit nodes | 06/16/15 | +| [verelox](https://verelox.com/) | AS12876 | Yes | Yes | Yes | - | 5/16 | +| [HostHatch](https://hosthatch.com/) | AS42708 | Yes | Yes | No | - | 05/01/16 | +| Ziggo | AS9143 | Yes | Yes | Yes | - | 05/24/2016 | +| [LiteServer](https://www.liteserver.nl/) | AS60404 | Yes | Yes | Yes | Can pay with Bitcoin. While their AUP doesn\'t allow tor exit nodes, see here[here](https://www.liteserver.nl/en/acceptable-usage-policy/). They make an exception if your exit-node has a reduced exit policy. And you must leave a note to them that you are running a exit-node. "We allow tor exit nodes as long you run a limited exit policy (block SMTP) to avoid abuse. | 12/26/2018 | +| [i3D](https://www.i3d.net/) | - | Yes | Yes | Yes | Allows also exits, if abuse is handled properly | 08/13/2017 | +| [KoDDoS](https://koddos.net) | AS206264 | Yes | Yes | Yes | Bitcoin accepted. | 10/12/2017 | +| [Worldstream](https://www.worldstream.nl) | AS49981 | Yes | Yes | No | - | 02/06/2019 | +| [LeaseWeb](https://www.leaseweb.com/) | - | Yes | Yes | Yes | - | - | +| [Novogara](http://www.novogara.com) | - | Yes | Yes | Yes | Explicitly allows Tor exit nodes and forwards abuse/DCMA, but their network isn't the most stable. You need to email them for a custom offer. They also accept Bitcoin/UKash/CashU | - | +| [Netrouting`](http://netrouting.nl/) | - | Yes | Yes | No | ISP has confirmed by e-mail that exit nodes are NOT acceptable. | 2014-10-15 | +| [DirectVPS](http://directvps.nl/) | - | Yes | Yes | ? | - | - | +| [Versio](http://versio.nl/) | - | Yes | Yes | No | - | 2013 | +| [CyberBunker](http://www.cyberbunker.com/) | - | Yes | Yes | Yes | Customers can remain anonymous. | - | +| [SnelServer](https://www.snelserver.com/) | - | Yes | Yes | Yes | Abuse complaints must be responded to within 24 hours or the system automatically suspends your account until you do. | 2014 | +| [ChmuraNet](https://www.chmuranet.com/) | - | Yes | Yes | Yes | Allows anonymous users to run tor exits. Abuse issues will be forwarded. Make sure to tell them that you're running an exit | 09/2014 | + + + +### Romania + +| **Company/ISP** | **ASN** | **Bridges** | **Relay** | **Exit** | **Comments** | **Last Updated** | +|-------------------------|-------------|-----------------|--------------|-------------|---------------------|------------------------| +| [m247.ro](https://www.m247.ro/) | - | Yes | Yes | Yes | - | 12/14/15 | +| [Voxility](http://www.voxility.com/) | - | Yes | Yes | ? | Read more [2015 tor-talk thread](https://lists.torproject.org/pipermail/tor-relays/2015-April/006867… | 04/2015 | +| [JavaPipe](https://javapipe.com/) | - | Yes | Yes | ? | - | 04/2016 | +| [MilesWeb](https://www.milesweb.com/) | - | Yes | Yes | No | Plans in Romania and also have data centers in USA and UK with 24x7 free support. | 03/2017 | + + + +### Sweden + +| **Company/ISP** | **ASN** | **Bridges** | **Relay** | **Exit** | **Comments** | **Last Updated** | +|-------------------------|-------------|-----------------|--------------|-------------|---------------------|------------------------| +| [Dataclub](https://www.dataclub.biz) | - | Yes | Yes | Yes | Your Exit should use Reduced Exit Policy | 2016/06/30 | +| [HostHatch](https://hosthatch.com) | AS42708 | Yes | Yes | No | - | 2016/05 | +| TeliaSonera | - | Yes | Yes | ? | TeliaSonera is also big in Sweden and deliver where other ISPs can't. | - | +| [PRQ](http://prq.se/?p=dedicated&intl=1) | - | Yes | Yes | Yes | - | - | +| [Portlane](http://www.portlane.com/) | - | Yes | Yes | Yes | Previously provided connectivity for ThePirateBay, OpenBitTorrent tracker et al. Handles abuse according to "Swedish praxis". | - | +| [Yourserver](https://www.yourserver.se/) | - | Yes | Yes | ? | Support team will allow relay/exit but TOR Traffic is throttled to 5Mbps speed. If your Exit relay receive too much complaints, they will ask to you to stop or otherwise they will suspend. | 2015/03/06 | + + +### Switzerland + + +| **Company/ISP** | **ASN** | **Bridges** | **Relay** | **Exit** | **Comments** | **Last Updated** | +|-------------------------|-------------|-----------------|--------------|-------------|---------------------|------------------------| +| [Solar Communications Gmbh](https://solarcom.ch/) | AS197988 | Yes | Yes | No | "We allow to place Tor routers, but don't allow to place Tor exit nodes." This applies to all their partners, who actually sell Solar's services to the public, namely: [Server & cloud](https://server-cloud.com), [CoinsHost](https://coinshost.com), [Incloudibly](https://incloudibly.net), [Cloudcom](https://cloudc.me), [AtomDrive](https://atomdrive.net). Cryptocurrencies are accepted. | 12/04/2015 | +| [fsit](http://www.fsit.ch/) | - | Yes | Yes | Yes | - | 11/2015 | + + +### Latvia + +| **Company/ISP** | **ASN** | **Bridges** | **Relay** | **Exit** | **Comments** | **Last Updated** | +|-------------------------|-------------|-----------------|--------------|-------------|---------------------|------------------------| +| [Yourserver](https://www.yourserver.se/) | - | Yes | Yes | ? | Support team will allow relay/exit but TOR Traffic is throttled to 5Mbps speed. If your Exit relay receive too much complaints, they will ask to you to stop or otherwise they will suspend. | 2015/03/06 | + + +### Canada + +| **Company/ISP** | **ASN** | **Bridges** | **Relay** | **Exit** | **Comments** | **Last Updated** | +|-------------------------|-------------|-----------------|--------------|-------------|---------------------|------------------------| +| [TekSavvy](http://www.teksavvy.ca) | - | Yes | Yes | ? | has a server-friendly Internet Use Policy (e.g., running a Tor relay) and has taken a stand in favor of net neutrality | 2008/12 | +| [CloudatCost.ca](http://www.cloudatcost.com/) | - | Yes | Yes | ? | operated by Fibernetics, has liberal abuse handling policies [AUP](http://www.cloudatcost.com/terms.php), however Tor is not explicitly allowed. | 2015/02 | +| [oneprovider](http://oneprovider.com/) | - | Yes | Yes | Yes | They are reselling dedicated servers in many locations around the world. Abuse handling differs depending on the provider from which they resell. | 2016/06 | + + + +### Slovenia + +| **Company/ISP** | **ASN** | **Bridges** | **Relay** | **Exit** | **Comments** | **Last Updated** | +|-------------------------|-------------|-----------------|--------------|-------------|---------------------|------------------------| +| [Tus Hosting](http://www.tushosting.si/) | - | Yes | Yes | Yes | They just simply forward DMCA notices to us to handle (or ignore) them | - | + + + +### Ukraine +| **Company/ISP** | **ASN** | **Bridges** | **Relay** | **Exit** | **Comments** | **Last Updated** | +|-------------------------|-------------|-----------------|--------------|-------------|---------------------|------------------------| +| [UrDN](http://urdn.com.ua) | - | Yes | Yes | Yes | free speech hoster, allows anything but spam/scam. Abuse always forwarded. | 10/08/2015 | +| [Colocall](http://www.colocall.net/) | - | Yes | Yes | Yes | - | - | + + +### Lithuania + +| **Company/ISP** | **ASN** | **Bridges** | **Relay** | **Exit** | **Comments** | **Last Updated** | +|-------------------------|-------------|-----------------|--------------|-------------|---------------------|------------------------| +| [Baltic Servers](http://www.balticservers.com) | - | Yes | Yes | Yes | All abuse mails they got yielded support tickets | - | + + +### New Zealand and Australia + +| **Company/ISP** | **ASN** | **Bridges** | **Relay** | **Exit** | **Comments** | **Last Updated** | +|-------------------------|-------------|-----------------|--------------|-------------|---------------------|------------------------| +| [HostHatch](https://hosthatch.com/) | AS36351 | Yes | Yes | No | Their VPS location is: Sydney, AU - Equinix IBX SY3 Data Center.Their ISP is:SoftLayer network, which includes primary transit from Telstra and peering with Equinix, Pipe-IX, NSW-IX and Megaport. | - | +| [Rimu hosting](http://rimuhosting.com) | - | Yes | Yes | Yes | Have servers in N.Z.; Sydney; London; and Dallas. Locations may vary, but quite happy with the specific Oz/NZ query. | - | + + + +### Hong Kong +| **Company/ISP** | **ASN** | **Bridges** | **Relay** | **Exit** | **Comments** | **Last Updated** | +|-------------------------|-------------|-----------------|--------------|-------------|---------------------|------------------------| +| [hosthatch](https://hosthatch.com/) | AS36351 | Yes | Yes | No | Their Hong Kong VPS type is OpenVZ,and ISP is SoftLayer. VPS locate in Pacnet's data centers, Hong Kong. | - | 05/01/16 | + + +### Czech Republic + +| **Company/ISP** | **ASN** | **Bridges** | **Relay** | **Exit** | **Comments** | **Last Updated** | +|-------------------------|-------------|-----------------|--------------|-------------|---------------------|------------------------| +| [T-Systems`](http://www.t-systems.cz/) | - | Yes | Yes | ? | - | + + +### Poland + +| **Company/ISP** | **ASN** | **Bridges** | **Relay** | **Exit** | **Comments** | **Last Updated** | +|-------------------------|-------------|-----------------|--------------|-------------|---------------------|------------------------| +| [Hitme.net.pl](http://hitme.net.pl/) | - | Yes | Yes | Yes | - | 12/06/2017 | +| [Hostowisko.pl](http://www.hostowisko.pl/) | - | Yes | Yes | ? | - | 27/08/2013 | +| [Exone](http://www.exone.pl/) | - | Yes | Yes | ? | - | 28/08/2013 | +| [e24cloud](http://www.e24cloud.com/en) | - | Yes | Yes | ? | - | 01/10/2013 | +| [hostinger.pl](http://www.hostinger.pl) | - | Yes | Yes | Yes | 02/10/2013 | +| [statnet.pl](http://www.statnet.pl/) | - | No | No | No | Used to allow Tor-relays, but now is blocking Tor activity | 12/06/2017 | +| [IQ PL](http://www.iq.pl/) | - | Yes | Yes | Yes | They allow running exit node on collocated dedicated server | - | +| [Slask DataCenter](https://sldc.eu/) | - | Yes | Yes | Yes | - | 21/02/2018 | + + +### Mexico + +| **Company/ISP** | **ASN** | **Bridges** | **Relay** | **Exit** | **Comments** | **Last Updated** | +|-------------------------|-------------|-----------------|--------------|-------------|---------------------|------------------------| +| Axtel | - | Yes | Yes | ? | Currently some Guard / Middle nodes are running in Axtel network | 2019 | + + --- html: two-columns-page.html

1 0

[community/staging] Fix link to other guides
by pili＠torproject.org 02 Aug '19

02 Aug '19

commit ab90ee0b38b4741568903632a2adc1b73d4252ea Author: gus <gus(a)torproject.org> Date: Sun Jul 7 16:53:47 2019 -0400 Fix link to other guides --- .../tor-exit-guidelines/contents.lr | 34 +++++++++++----------- 1 file changed, 17 insertions(+), 17 deletions(-) diff --git a/content/relay-operations/community-resources/tor-exit-guidelines/contents.lr b/content/relay-operations/community-resources/tor-exit-guidelines/contents.lr index 37e98d1..a7f098e 100644 --- a/content/relay-operations/community-resources/tor-exit-guidelines/contents.lr +++ b/content/relay-operations/community-resources/tor-exit-guidelines/contents.lr @@ -12,13 +12,13 @@ NOTE: This FAQ is for informational purposes only and does not constitute legal ### Tor at Universities: Find allies. -Find some professors (or deans!) who like the idea of supporting and/or researching anonymity on the Internet. If possible, use an extra IP range whose abuse contact doesn't go through the main university abuse team. Ideally, use addresses that are not trusted by the IP-based authentication many library-related services use -- if the university's entire IP address space is "trusted" to access these library resources, the university is forced to maintain an iron grip on all its addresses. Also read [How do I make my University / ISP / etc happy with my exit node?](FIXME) +Find some professors (or deans!) who like the idea of supporting and/or researching anonymity on the Internet. If possible, use an extra IP range whose abuse contact doesn't go through the main university abuse team. Ideally, use addresses that are not trusted by the IP-based authentication many library-related services use -- if the university's entire IP address space is "trusted" to access these library resources, the university is forced to maintain an iron grip on all its addresses. Also read [How do I make my University / ISP / etc happy with my exit node?](tor-relay-universities) ### Find Tor-friendly ISPs. A good ISP is one that offers cheap bandwidth and is not being used by other members of the Tor community. Before you continue, you may ask the Tor community if your choice is a good one. We very much need diversity, and it does not help if we pool too many exits at one friendly ISP. -In any case, add the ISP to the [GoodBadISPs](FIXME) wiki page. +In any case, add the ISP to the [GoodBadISPs](good-bad-isps) page. To find an ISP, go through forums and sites where ISPs posts their latest deals, and contact them about Tor hosting. Once you identified your ISP, you can follow the two-step advice of TorServers.net. @@ -31,28 +31,28 @@ The two-step process usually helps in elevating your request to higher levels of ## Legal -* Make sure you know the relevant legal paragraphs for common-carrier like communication services in your country (and the country of your hosting provider!). +### Make sure you know the relevant legal paragraphs for common-carrier like communication services in your country (and the country of your hosting provider!). At least most western countries should have regulations that exclude communication service providers from liability. Please add your country's regulations to this list. * USA: [DMCA 512](https://www.law.cornell.edu/uscode/text/17/512); see [EFF's Legal FAQ for Tor Operators](https://2019.www.torproject.org/eff/tor-legal-faq) (a very good and relevant read for other countries as well) - * Germany: [TMG 8](http://www.gesetze-im-internet.de/tmg/__8.html) and [15](http://www.gesetze-im-internet.de/tmg/__15.html). - * Netherlands: [Artikel 6:196c BW](http://wetten.overheid.nl/BWBR0005289/Boek6/Titel3/Afdeling4A/Artikel196c/) - * Austria: [ECG 13](http://www.ris.bka.gv.at/Dokument.wxe?Abfrage=Bundesnormen&Dokumentnummer=NOR40025809) +* Germany: [TMG 8](http://www.gesetze-im-internet.de/tmg/__8.html) and [15](http://www.gesetze-im-internet.de/tmg/__15.html). +* Netherlands: [Artikel 6:196c BW](http://wetten.overheid.nl/BWBR0005289/Boek6/Titel3/Afdeling4A/Artikel196c/) +* Austria: [ECG 13](http://www.ris.bka.gv.at/Dokument.wxe?Abfrage=Bundesnormen&Dokumentnummer=NOR40025809) * France: FIXME - * Sweden: [16-19 2002:562](https://lagen.nu/2002:562#P16S1) +* Sweden: [16-19 2002:562](https://lagen.nu/2002:562#P16S1) If you country is missing here and you know a lawyer who can provide a legal opinion, please get in contact with Tor Project. -* If you're part of an organization that will be running the exit relay (ISP, university etc), consider teaching your legal people about Tor. +### If you're part of an organization that will be running the exit relay (ISP, university etc), consider teaching your legal people about Tor. It's way better for them to hear about Tor from you, in a relaxed environment, than to hear about it from a stranger over the phone. Make them aware of [EFF's Legal FAQ for Tor Operators](https://2019.www.torproject.org/eff/tor-legal-faq). EFF has also offered to talk to other lawyers to explain the legal aspects of Tor; contact us at support(a)torservers.net and we'll make the connections for you. -* If you're not part of an organization, think about starting one! +### If you're not part of an organization, think about starting one! Depending on the chosen form, setting up a legal body might help with liability, and in general it helps to appear bigger than you are (and less likely to get raided). The guys from Torservers.net in Germany found a lawyer who would agree to "host" them inside his office. They are now are a non-profit association ("eingetragener Verein, gemeinnutzig") registered inside a lawyer's office. The setup process was easy and cheap. Similar setups probably exist for your country. Another benefit of an association-like structure is that it might still work even when you leave, if you manage to find successors. -* Consider preemptively teaching your local law enforcement about Tor. +### Consider preemptively teaching your local law enforcement about Tor. "Cybercrime" people actually love it when you offer to [teach them about Tor and the Internet](https://blog.torproject.org/blog/talking-german-police-stuttgart) -- they're typically overwhelmed by their jobs and don't have enough background to know where to start. Contacting them gives you a chance to teach them why Tor is useful to the world (and why it's [not particularly helpful to criminals](https://2019.www.torproject.org/docs/faq-abuse#WhatAboutCriminal…. Also, if they do get a report about your relay, they'll think of you as a helpful expert rather than a potential criminal. @@ -62,13 +62,13 @@ Depending on the chosen form, setting up a legal body might help with liability, If you receive an abuse complaint, don't freak out! Here is some advice for you: -* Answer to abuse complaints in a professional manner within a reasonable time span. +### Answer to abuse complaints in a professional manner within a reasonable time span. TorServers.net is a fairly large Tor exit operator and we receive only a very small number of complaints, especially compared to the amount of traffic we push. Roughly 80% are automated reports, and the rest is usually satisfied with [our default reply](https://www.torservers.net/wiki/abuse/templates). We have not needed the input of a lawyer in many years of operation following the advice on this page. -In addition to the [templates at Torservers.net](https://www.torservers.net/wiki/abuse/templates), you can find many more templates for various scenarios on the [Tor Abuse Templates](FIXME) . It is exceptionally rare to encounter a scenario where none of these templates apply. +In addition to the [templates at Torservers.net](https://www.torservers.net/wiki/abuse/templates), you can find many more templates for various scenarios on the [Tor Abuse Templates](tor-abuse-templates) . It is exceptionally rare to encounter a scenario where none of these templates apply. -* If you receive a threatening letter from a lawyer about abusive use or a DMCA complaint, also don't freak out. +### If you receive a threatening letter from a lawyer about abusive use or a DMCA complaint, also don't freak out. We are not aware of any case that made it near a court, and we will do everything in our power to support you if it does. You can look up if an IP address was listed as an exit relay at a given time at [ExoneraTor](https://exonerator.torproject.org/). Point to that page in your reply to the complaint. If you feel it might be helpful, we can write you a signed letter confirming this information: Contact us at tor-assistants(a)torproject.org if you need one. @@ -76,15 +76,15 @@ In your reply, state clearly that you are not liable for forwarded content passi ## Things you can do preemptively -* Make the WHOIS info point as close to you as possible. +### Make the WHOIS info point as close to you as possible. One of the biggest reasons exit relays disappear is because the people answering the abuse address get nervous and ask you to stop. If you can get your own IP block, great. Even if not, many providers will still reassign subblocks to you if you ask. ARIN uses [SWIP](https://www.arin.net/resources/request/reassignments.html), and RIPE uses something similar. You can also add comments to your range, hinting at your usage as anonymization service ([Example](https://apps.db.ripe.net/search/query.html?searchtext=ZWIEBELFREUN…) If you have questions about the process, please write an email to support(a)torservers.net and we will try to explain the process to you. -* Register a phone number and a fax number as abuse contact. +### Register a phone number and a fax number as abuse contact. At least law enforcement in Germany regularly uses the fax and phone numbers present in IP records. Torservers.net uses a free German fax-to-email service, call-manager.de, and a VoIP number from Sipgate.de. -* Consider using the Reduced Exit Policy. +### Consider using the Reduced Exit Policy. The [Reduced Exit Policy](FIXME) is an alternative to the default exit policy. It allows many Internet services while still blocking the majority of TCP ports. This drastically reduces the odds that a Bittorrent user will select your node and thus reduces or even eliminates the number of [DMCA complaints](https://2019.www.torproject.org/eff/tor-dmca-response) you will receive. @@ -94,7 +94,7 @@ If you have your own experience of abuse handling, just share it on our public m Please read all the technical details before getting started. If you have any questions or need help, please contact us at [tor-relays](https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relay…. -* [TorRelayGuide](https://community.torproject.org/relay) +* [TorRelayGuide](https://community.torproject.org/relay-operations) * Set up an informative website on the exit IP(s) on port 80.

1 0

[community/staging] Merge branch 'relays' into 'master'
by pili＠torproject.org 02 Aug '19

02 Aug '19

commit 6b6168afce194e4ff7f003e042671f9fca588890 Merge: b9ecab7 ab90ee0 Author: gus <gus(a)riseup.net> Date: Mon Jul 8 13:24:36 2019 -0700 Merge branch 'relays' into 'master' Relay-operations: Include Good ISPs, Swag page and fix broken links See merge request gus/communitytpo!2 .../community-resources/contents.lr | 12 +- .../community-resources/good-bad-isps/contents.lr | 324 +++++++++++++++++++-- .../community-resources/swags/contents.lr | 25 ++ .../tor-abuse-templates/contents.lr | 4 +- .../tor-exit-guidelines/contents.lr | 34 +-- .../tor-relay-universities/contents.lr | 5 +- .../technical-setup/centosrhel/contents.lr | 58 ---- .../relay-operations/technical-setup/contents.lr | 10 +- .../technical-setup/debianubuntu/contents.lr | 44 --- .../technical-setup/fedora/contents.lr | 37 --- .../technical-setup/freebsd/contents.lr | 75 ----- .../contents.lr | 52 ++-- 12 files changed, 389 insertions(+), 291 deletions(-)

1 0

[community/staging] Merge remote-tracking branch 'gus/master'
by pili＠torproject.org 02 Aug '19

02 Aug '19

commit d48c8c055e13b3edc3f08273191db34aeb4e48e6 Merge: 3d74e69 6b6168a Author: hiro <hiro(a)torproject.org> Date: Tue Jul 23 14:04:09 2019 +0200 Merge remote-tracking branch 'gus/master'

1 0

[community/staging] Update .gitignore
by pili＠torproject.org 02 Aug '19

02 Aug '19

commit 3d74e69935afda5b1a934a72cd4d76862ad0b633 Author: hiro <hiro(a)torproject.org> Date: Sat Jul 13 13:01:12 2019 +0200 Update .gitignore --- .gitignore | 2 ++ 1 file changed, 2 insertions(+) diff --git a/.gitignore b/.gitignore index c9ef7f1..41a4e3a 100644 --- a/.gitignore +++ b/.gitignore @@ -8,6 +8,8 @@ public *.po contents+*.lr +.cache + *.egg-info *.pyc __pycache__

1 0

[community/staging] correct tables. alphabetic order
by pili＠torproject.org 02 Aug '19

02 Aug '19

commit 1f3016e17a5368e7f45702e54dce969d09d19f64 Author: emma peel <emma.peel(a)riseup.net> Date: Wed Jul 24 14:21:21 2019 +0200 correct tables. alphabetic order --- .../community-resources/good-bad-isps/contents.lr | 257 ++++++++++----------- 1 file changed, 122 insertions(+), 135 deletions(-) diff --git a/content/relay-operations/community-resources/good-bad-isps/contents.lr b/content/relay-operations/community-resources/good-bad-isps/contents.lr index 0dd47f8..0220596 100644 --- a/content/relay-operations/community-resources/good-bad-isps/contents.lr +++ b/content/relay-operations/community-resources/good-bad-isps/contents.lr @@ -24,56 +24,6 @@ For network diversity and stronger anonymity, you should avoid providers and cou # Good Experiences -### US - -| **Company/ISP** | **ASN** | **Bridges** | **Relay** | **Exit** | **Comments** | **Last Updated** | -|-------------------------|-------------|-----------------|--------------|-------------|---------------------|------------------------| -| [2HOST](https://2host.com/) | - | Yes | Yes | Yes(?) | Vague AUP/Abuse handling | 10/15/14 | -| [Amazon Web Services (AWS)](https://aws.amazon.com) | - | Yes | Yes | No | - | - | -| [AmeriNOC](https://www.amerinoc.com/) | - | Yes | Yes | Yes | - | - | -| [Arvixe](https://www.arvixe.com/vps_virtual_private_servers_hosting/) | - | Yes | Yes | Yes | - | 06/19/13 | -| [Axigy](http://www.axigy.com) | - | Yes | Yes | Yes | - | - | -| [Blacklotus](http://www.blacklotus.net) | - | Yes | Yes | Yes | Liberal abuse handling policies | - | -| [BuyVM.net](https://buyvm.net) | AS53667 | Yes | Yes | Yes | New Tor rules [here](https://buyvm.net/acceptable-use-policy/#3). All relays are fine if you follow the steps. | - | -| [Catalyst Host](https://catalysthost.com/) | - | ? | No | No | "If you are interested in hosting either, you can ask us about a dedicated server." | 10/01/14 | -| [ChunkHost](http://chunkhost.com) | - | Yes | Yes | ? | Questionable DMCA handling | 01/01/12 | -| [Cyberonic](http://www.cyberonic.com) | - | Yes | Yes | ? | - | - | -| [Datawagon](https://datawagon.net) | AS27176 | Yes | Yes | Yes | Customers are forwarded abuse complaints to handle themselves | 03/06/19 | -| [DreamHost](https://www.dreamhost.com/) | - | Yes | Yes | ? | - | 11/29/17 | -| [Ethr.net](http://ethr.net/) | - | Yes | Yes | Yes | - | - | -| [Evolucix](http://www.evolucix.com) | - | Yes | Yes | No(?) | - | - | -| [Future Hosting](http://www.futurehosting.com/) | - | Yes | Yes | No | - | 09/01/14 | -| [HostGator](http://www.hostgator.com/) | - | No | No | No | - | - | -| [HostHatch](https://hosthatch.com) | AS46562 | Yes | Yes | No | Their vps isp are mixed include: QuadraNet, nLayer, AboveNet, Inteliquent, Atrato Networks and open peering with the entire Any2LA and Atlanta TIE networks. | 05/01/16 | -| [HostUS](http://hostus.us/) | AS25926 | Yes | Yes | No | - | 10/16/14 | -| [IPXcore](https://ipxcore.com/) | - | Yes | Yes | No | - | -| [Luna Node](https://www.lunanode.com/index.php) | - | Yes | Yes | No | - | 05/01/14 | -| [OVH](https://www.ovh.com/us/index.xml ) | AS16276 | Yes | Yes | ? | - | 12/31/14 | -| [Oplink.net](https://www.oplink.net) | - | Yes | Yes | No | - | 09/03/15 | -| [Psychz.net](https://www.psychz.net/) | - | Yes | Yes | Yes | Very Exit friendly. Standard Tor response will resolve abuse issues. | 10/07/15 | -| [PulseServers](https://www.pulseservers.com) | AS16276 | Yes | Yes | Yes | Exit-friendly. | 05/01/16 | -| [RamNode](http://ramnode.com/) | AS3842 | Yes | Yes | No | - | 11/03/14 | -| [Server Complete](https://servercomplete.com/) | - | ? | ? | No | - | 11/03/14 | -| [Softlayer](http://www.softlayer.com) | - | Yes | Yes | ? | - | - | -| [Slicehost/Rackspace](http://www.slicehost.com/) | - | Yes | Yes | No | Host, not an ISP | - | -| [Sh3lls](http://www.sh3lls.net/dedicated.htm) | - | Yes | Yes | No | - | - | -| [SolarVPS](https://solarvps.com) | - | Yes | Yes | Yes | - | - | -| [SeedVPS](https://www.seedvps.com) | - | Yes | Yes | No | - | - | -| [Tailored VPS](http://tailoredvps.com/) | - | Yes | Yes | Yes(?) | - | - | -| [VPS6.NET](https://vps6.net/) | - | Yes | Yes | No | - | - | -| [VPSWebServer.com](http://www.vpswebserver.com) | - | Yes || No | ? | - | - | -| [Inerail](http://inerail.net/) | - | Yes | Yes | Yes | Tor only allowed on dedicated/colocation | - | -| [CondoInternet ISP](http://www.condointernet.net/) | - | Yes | Yes | Yes | - | - | -| [DigitalOcean](http://digitalocean.com/) | - | Yes | Yes | No | - | - | -| [PhoenixNap / Secured Servers](http://www.phoenixnap.com/) | - | Yes | Yes | No | - | 08/01/14 | -| [Vultr](http://vultr.com) | AS20473 | Yes | Yes | No | When asked directly they will claim they do support Tor exits but will pull the rug out from under you later on. This has happened to at least two exit operators. | - | -| [ChicagoVPS](http://chicagovps.net/) | - | Yes | Yes | No | Tor bridge/relay is allowed on the whole VPS range. Any VPS running Exit nodes will be suspended without prior notice. | 15/01/15 | -| [Xmission](https://www.xmission.com/) | - | Yes | Yes | Yes | - | 01/28/15 | -| [blackpulsehosting](https://www.blackpulsehosting.com) | - | Yes | Yes | No | - | 10/25/15 | -| [MonkeyBrains](https://monkeybrains.net) | AS32329 | Yes | Yes | Yes | Only offers colocation, no cheap VPS option. | 1/14/19 | - - - ### Austria | **Company/ISP** | **ASN** | **Bridges** | **Relay** | **Exit** | **Comments** | **Last Updated** | @@ -93,37 +43,20 @@ For network diversity and stronger anonymity, you should avoid providers and cou | [VPS.BG](https://www.vpsbg.eu/en/) | - | Yes | Yes | Yes | They don't collect any personal info and you can pay in bitcoin. | 01/11/2016 | - -### Germany +### Canada | **Company/ISP** | **ASN** | **Bridges** | **Relay** | **Exit** | **Comments** | **Last Updated** | |-------------------------|-------------|-----------------|--------------|-------------|---------------------|------------------------| -| [Weesly](http://weesly.de) | - | Yes | Yes | Yes | Note that you should let them know about your intention when ordering a server or in advance. | 06/2013 | -| [EUServ](http://euserv.de) | - | - | Yes | No | They have a bad support, but if you know how to maintain your server, this ISP is a good choice. | - | -| [IPX-Server](https://www.ipx-server.de/) | - | Yes | Yes | - | - | - | -| [Keyweb](https://www.keyweb.de/) | - | - | Yes | Yes | - | - | -| [Afterburst](http://afterburst.com) | - | - | Yes | No | - | - | -| [myLoc Managed IT](https://myloc.de) | AS31010, AS24961 | Yes | Yes | No | - | 2018-10-25 | -| [linevast](https://www.linevast.de/) | - | Yes | Yes | Yes | Only allowed on dedicated servers | 13/11/2015 | -| [Server4You](https://www.server4you.de/)| - | Yes | Yes | No | Part of [Intergenia AG](http://www.intergenia.de/)), I've asked Server4You support and they state servers with complaints about Tor will be canceled immediately (see the quote in the "Bad Experience" section) | - | -| [Hetzner](http://hetzner.de/) | - | - | Yes | No | Offers good dedicated root servers for a good price. | -| [Contabo](https://contabo.de) | - | Yes | Yes | Yes | Has no restriction for relays or exit nodes. However, possible abuse complaints will be forwarded to the owner and need to be addressed. | 2018/06 | -| [Strato](https://strato.de) | - | - | Yes | No | Exit-Nodes are prohibited by their general terms and conditions | - | -| [PraHost](https://www.prahost.com/) | - | - | Yes | Yes | Stated in November 2014 that they allow exit nodes if abuse complaints are handled. Suspends the server if no "valid" action (read: blocking) is taken within 24 hours of an abuse ticket. Their ticket system does not reliably handle email replies, use the web interface instead. | 2017-10-31 | -| [DomainFactory](https://www.df.eu/de/cloud-hosting/cloud-server/) | - | - | Yes | No | - | - | -| [NetCologne](https://www.netcologne.de/) | - | - | Yes | Yes | - | - | - +| [TekSavvy](http://www.teksavvy.ca) | - | Yes | Yes | ? | has a server-friendly Internet Use Policy (e.g., running a Tor relay) and has taken a stand in favor of net neutrality | 2008/12 | +| [CloudatCost.ca](http://www.cloudatcost.com/) | - | Yes | Yes | ? | operated by Fibernetics, has liberal abuse handling policies [AUP](http://www.cloudatcost.com/terms.php), however Tor is not explicitly allowed. | 2015/02 | +| [oneprovider](http://oneprovider.com/) | - | Yes | Yes | Yes | They are reselling dedicated servers in many locations around the world. Abuse handling differs depending on the provider from which they resell. | 2016/06 | -### United Kingdom +### Czech Republic | **Company/ISP** | **ASN** | **Bridges** | **Relay** | **Exit** | **Comments** | **Last Updated** | |-------------------------|-------------|-----------------|--------------|-------------|---------------------|------------------------| -| [Gigatux](https://www.gigatux.com) | - | Yes | Yes | Yes | They actually run their own relay named Gigatux. They also offer servers in the US, Germany, and Israel. | - | -| [Clustered.net](http://www.clustered.net) | - | Yes | Yes | Yes | - | - | -| [Bitfolk](http://bitfolk.com/) | - | Yes | Yes | Yes | They are very knowledgable and understand Tor and its uses. They are hot on spam and abuse so advise changing the default exit (good idea in the UK anyhow). Any DMCA notices received were simply forwarded on without agro | - | -| [RapidSwitch](http://rapidswitch.com/) | - | Yes | Yes | ? | - | 07/2014 | - +| [T-Systems`](http://www.t-systems.cz/) | - | Yes | Yes | ? | - | - | ### France @@ -146,6 +79,31 @@ For network diversity and stronger anonymity, you should avoid providers and cou | [TeliaSonera Finland](https://www.sonera.fi/) | AS1759 | Yes | Yes | No | - | 03/26/2016 | +### Germany + +| **Company/ISP** | **ASN** | **Bridges** | **Relay** | **Exit** | **Comments** | **Last Updated** | +|-------------------------|-------------|-----------------|--------------|-------------|---------------------|------------------------| +| [Weesly](http://weesly.de) | - | Yes | Yes | Yes | Note that you should let them know about your intention when ordering a server or in advance. | 06/2013 | +| [EUServ](http://euserv.de) | - | - | Yes | No | They have a bad support, but if you know how to maintain your server, this ISP is a good choice. | - | +| [IPX-Server](https://www.ipx-server.de/) | - | Yes | Yes | - | - | - | +| [Keyweb](https://www.keyweb.de/) | - | - | Yes | Yes | - | - | +| [Afterburst](http://afterburst.com) | - | - | Yes | No | - | - | +| [myLoc Managed IT](https://myloc.de) | AS31010, AS24961 | Yes | Yes | No | - | 2018-10-25 | +| [linevast](https://www.linevast.de/) | - | Yes | Yes | Yes | Only allowed on dedicated servers | 13/11/2015 | +| [Server4You](https://www.server4you.de/)| - | Yes | Yes | No | Part of [Intergenia AG](http://www.intergenia.de/)), I've asked Server4You support and they state servers with complaints about Tor will be canceled immediately (see the quote in the "Bad Experience" section) | - | +| [Hetzner](http://hetzner.de/) | - | - | Yes | No | Offers good dedicated root servers for a good price. | - | +| [Contabo](https://contabo.de) | - | Yes | Yes | Yes | Has no restriction for relays or exit nodes. However, possible abuse complaints will be forwarded to the owner and need to be addressed. | 2018/06 | +| [Strato](https://strato.de) | - | - | Yes | No | Exit-Nodes are prohibited by their general terms and conditions | - | +| [PraHost](https://www.prahost.com/) | - | - | Yes | Yes | Stated in November 2014 that they allow exit nodes if abuse complaints are handled. Suspends the server if no "valid" action (read: blocking) is taken within 24 hours of an abuse ticket. Their ticket system does not reliably handle email replies, use the web interface instead. | 2017-10-31 | +| [DomainFactory](https://www.df.eu/de/cloud-hosting/cloud-server/) | - | - | Yes | No | - | - | +| [NetCologne](https://www.netcologne.de/) | - | - | Yes | Yes | - | - | + + +### Hong Kong +| **Company/ISP** | **ASN** | **Bridges** | **Relay** | **Exit** | **Comments** | **Last Updated** | +|-------------------------|-------------|-----------------|--------------|-------------|---------------------|------------------------| +| [hosthatch](https://hosthatch.com/) | AS36351 | Yes | Yes | No | Their Hong Kong VPS type is OpenVZ,and ISP is SoftLayer. VPS locate in Pacnet's data centers, Hong Kong. | - | 05/01/16 | + ### Hungary @@ -173,6 +131,25 @@ For network diversity and stronger anonymity, you should avoid providers and cou | [SelfServer by Enter](https://selfserver.it/) | - | Yes | Yes | Yes | Uncomfortable due to old CentOS 6.10, NATed IPv4-only networking, ports other than the well-known are filtered. Abuse complaints need to go through their support service | 11/2018 | +### Latvia + +| **Company/ISP** | **ASN** | **Bridges** | **Relay** | **Exit** | **Comments** | **Last Updated** | +|-------------------------|-------------|-----------------|--------------|-------------|---------------------|------------------------| +| [Yourserver](https://www.yourserver.se/) | - | Yes | Yes | ? | Support team will allow relay/exit but TOR Traffic is throttled to 5Mbps speed. If your Exit relay receive too much complaints, they will ask to you to stop or otherwise they will suspend. | 2015/03/06 | + + +### Lithuania + +| **Company/ISP** | **ASN** | **Bridges** | **Relay** | **Exit** | **Comments** | **Last Updated** | +|-------------------------|-------------|-----------------|--------------|-------------|---------------------|------------------------| +| [Baltic Servers](http://www.balticservers.com) | - | Yes | Yes | Yes | All abuse mails they got yielded support tickets | - | + + +### Mexico + +| **Company/ISP** | **ASN** | **Bridges** | **Relay** | **Exit** | **Comments** | **Last Updated** | +|-------------------------|-------------|-----------------|--------------|-------------|---------------------|------------------------| +| Axtel | - | Yes | Yes | ? | Currently some Guard / Middle nodes are running in Axtel network | 2019 | ### Moldova @@ -184,7 +161,6 @@ For network diversity and stronger anonymity, you should avoid providers and cou | [AlexHost](https://alexhost.md/) | - | Yes | Yes | Yes | - | 07/21/2014 | - ### Netherlands | **Company/ISP** | **ASN** | **Bridges** | **Relay** | **Exit** | **Comments** | **Last Updated** | @@ -193,7 +169,7 @@ For network diversity and stronger anonymity, you should avoid providers and cou | [verelox](https://verelox.com/) | AS12876 | Yes | Yes | Yes | - | 5/16 | | [HostHatch](https://hosthatch.com/) | AS42708 | Yes | Yes | No | - | 05/01/16 | | Ziggo | AS9143 | Yes | Yes | Yes | - | 05/24/2016 | -| [LiteServer](https://www.liteserver.nl/) | AS60404 | Yes | Yes | Yes | Can pay with Bitcoin. While their AUP doesn\'t allow tor exit nodes, see here[here](https://www.liteserver.nl/en/acceptable-usage-policy/). They make an exception if your exit-node has a reduced exit policy. And you must leave a note to them that you are running a exit-node. "We allow tor exit nodes as long you run a limited exit policy (block SMTP) to avoid abuse. | 12/26/2018 | +| [LiteServer](https://www.liteserver.nl/) | AS60404 | Yes | Yes | Yes | Can pay with Bitcoin. While their AUP doesn't allow tor exit nodes (see [here](https://www.liteserver.nl/en/acceptable-usage-policy/)), they make an exception if your exit-node has a reduced exit policy. And you must leave a note to them that you are running a exit-node. "We allow tor exit nodes as long you run a limited exit policy (block SMTP) to avoid abuse. | 12/26/2018 | | [i3D](https://www.i3d.net/) | - | Yes | Yes | Yes | Allows also exits, if abuse is handled properly | 08/13/2017 | | [KoDDoS](https://koddos.net) | AS206264 | Yes | Yes | Yes | Bitcoin accepted. | 10/12/2017 | | [Worldstream](https://www.worldstream.nl) | AS49981 | Yes | Yes | No | - | 02/06/2019 | @@ -207,6 +183,27 @@ For network diversity and stronger anonymity, you should avoid providers and cou | [ChmuraNet](https://www.chmuranet.com/) | - | Yes | Yes | Yes | Allows anonymous users to run tor exits. Abuse issues will be forwarded. Make sure to tell them that you're running an exit | 09/2014 | +### New Zealand and Australia + +| **Company/ISP** | **ASN** | **Bridges** | **Relay** | **Exit** | **Comments** | **Last Updated** | +|-------------------------|-------------|-----------------|--------------|-------------|---------------------|------------------------| +| [HostHatch](https://hosthatch.com/) | AS36351 | Yes | Yes | No | Their VPS location is: Sydney, AU - Equinix IBX SY3 Data Center.Their ISP is:SoftLayer network, which includes primary transit from Telstra and peering with Equinix, Pipe-IX, NSW-IX and Megaport. | - | +| [Rimu hosting](http://rimuhosting.com) | - | Yes | Yes | Yes | Have servers in N.Z.; Sydney; London; and Dallas. Locations may vary, but quite happy with the specific Oz/NZ query. | - | + + +### Poland + +| **Company/ISP** | **ASN** | **Bridges** | **Relay** | **Exit** | **Comments** | **Last Updated** | +|-------------------------|-------------|-----------------|--------------|-------------|---------------------|------------------------| +| [Hitme.net.pl](http://hitme.net.pl/) | - | Yes | Yes | Yes | - | 12/06/2017 | +| [Hostowisko.pl](http://www.hostowisko.pl/) | - | Yes | Yes | ? | - | 27/08/2013 | +| [Exone](http://www.exone.pl/) | - | Yes | Yes | ? | - | 28/08/2013 | +| [e24cloud](http://www.e24cloud.com/en) | - | Yes | Yes | ? | - | 01/10/2013 | +| [hostinger.pl](http://www.hostinger.pl) | - | Yes | Yes | Yes | | 02/10/2013 | +| [statnet.pl](http://www.statnet.pl/) | - | No | No | No | Used to allow Tor-relays, but now is blocking Tor activity | 12/06/2017 | +| [IQ PL](http://www.iq.pl/) | - | Yes | Yes | Yes | They allow running exit node on collocated dedicated server | - | +| [Slask DataCenter](https://sldc.eu/) | - | Yes | Yes | Yes | - | 21/02/2018 | + ### Romania @@ -218,7 +215,6 @@ For network diversity and stronger anonymity, you should avoid providers and cou | [MilesWeb](https://www.milesweb.com/) | - | Yes | Yes | No | Plans in Romania and also have data centers in USA and UK with 24x7 free support. | 03/2017 | - ### Sweden | **Company/ISP** | **ASN** | **Bridges** | **Relay** | **Exit** | **Comments** | **Last Updated** | @@ -233,30 +229,12 @@ For network diversity and stronger anonymity, you should avoid providers and cou ### Switzerland - | **Company/ISP** | **ASN** | **Bridges** | **Relay** | **Exit** | **Comments** | **Last Updated** | |-------------------------|-------------|-----------------|--------------|-------------|---------------------|------------------------| | [Solar Communications Gmbh](https://solarcom.ch/) | AS197988 | Yes | Yes | No | "We allow to place Tor routers, but don't allow to place Tor exit nodes." This applies to all their partners, who actually sell Solar's services to the public, namely: [Server & cloud](https://server-cloud.com), [CoinsHost](https://coinshost.com), [Incloudibly](https://incloudibly.net), [Cloudcom](https://cloudc.me), [AtomDrive](https://atomdrive.net). Cryptocurrencies are accepted. | 12/04/2015 | | [fsit](http://www.fsit.ch/) | - | Yes | Yes | Yes | - | 11/2015 | -### Latvia - -| **Company/ISP** | **ASN** | **Bridges** | **Relay** | **Exit** | **Comments** | **Last Updated** | -|-------------------------|-------------|-----------------|--------------|-------------|---------------------|------------------------| -| [Yourserver](https://www.yourserver.se/) | - | Yes | Yes | ? | Support team will allow relay/exit but TOR Traffic is throttled to 5Mbps speed. If your Exit relay receive too much complaints, they will ask to you to stop or otherwise they will suspend. | 2015/03/06 | - - -### Canada - -| **Company/ISP** | **ASN** | **Bridges** | **Relay** | **Exit** | **Comments** | **Last Updated** | -|-------------------------|-------------|-----------------|--------------|-------------|---------------------|------------------------| -| [TekSavvy](http://www.teksavvy.ca) | - | Yes | Yes | ? | has a server-friendly Internet Use Policy (e.g., running a Tor relay) and has taken a stand in favor of net neutrality | 2008/12 | -| [CloudatCost.ca](http://www.cloudatcost.com/) | - | Yes | Yes | ? | operated by Fibernetics, has liberal abuse handling policies [AUP](http://www.cloudatcost.com/terms.php), however Tor is not explicitly allowed. | 2015/02 | -| [oneprovider](http://oneprovider.com/) | - | Yes | Yes | Yes | They are reselling dedicated servers in many locations around the world. Abuse handling differs depending on the provider from which they resell. | 2016/06 | - - - ### Slovenia | **Company/ISP** | **ASN** | **Bridges** | **Relay** | **Exit** | **Comments** | **Last Updated** | @@ -264,62 +242,71 @@ For network diversity and stronger anonymity, you should avoid providers and cou | [Tus Hosting](http://www.tushosting.si/) | - | Yes | Yes | Yes | They just simply forward DMCA notices to us to handle (or ignore) them | - | - ### Ukraine + | **Company/ISP** | **ASN** | **Bridges** | **Relay** | **Exit** | **Comments** | **Last Updated** | |-------------------------|-------------|-----------------|--------------|-------------|---------------------|------------------------| | [UrDN](http://urdn.com.ua) | - | Yes | Yes | Yes | free speech hoster, allows anything but spam/scam. Abuse always forwarded. | 10/08/2015 | | [Colocall](http://www.colocall.net/) | - | Yes | Yes | Yes | - | - | -### Lithuania - -| **Company/ISP** | **ASN** | **Bridges** | **Relay** | **Exit** | **Comments** | **Last Updated** | -|-------------------------|-------------|-----------------|--------------|-------------|---------------------|------------------------| -| [Baltic Servers](http://www.balticservers.com) | - | Yes | Yes | Yes | All abuse mails they got yielded support tickets | - | - - -### New Zealand and Australia - -| **Company/ISP** | **ASN** | **Bridges** | **Relay** | **Exit** | **Comments** | **Last Updated** | -|-------------------------|-------------|-----------------|--------------|-------------|---------------------|------------------------| -| [HostHatch](https://hosthatch.com/) | AS36351 | Yes | Yes | No | Their VPS location is: Sydney, AU - Equinix IBX SY3 Data Center.Their ISP is:SoftLayer network, which includes primary transit from Telstra and peering with Equinix, Pipe-IX, NSW-IX and Megaport. | - | -| [Rimu hosting](http://rimuhosting.com) | - | Yes | Yes | Yes | Have servers in N.Z.; Sydney; London; and Dallas. Locations may vary, but quite happy with the specific Oz/NZ query. | - | - - - -### Hong Kong -| **Company/ISP** | **ASN** | **Bridges** | **Relay** | **Exit** | **Comments** | **Last Updated** | -|-------------------------|-------------|-----------------|--------------|-------------|---------------------|------------------------| -| [hosthatch](https://hosthatch.com/) | AS36351 | Yes | Yes | No | Their Hong Kong VPS type is OpenVZ,and ISP is SoftLayer. VPS locate in Pacnet's data centers, Hong Kong. | - | 05/01/16 | - - -### Czech Republic +### United Kingdom | **Company/ISP** | **ASN** | **Bridges** | **Relay** | **Exit** | **Comments** | **Last Updated** | |-------------------------|-------------|-----------------|--------------|-------------|---------------------|------------------------| -| [T-Systems`](http://www.t-systems.cz/) | - | Yes | Yes | ? | - | - +| [Gigatux](https://www.gigatux.com) | - | Yes | Yes | Yes | They actually run their own relay named Gigatux. They also offer servers in the US, Germany, and Israel. | - | +| [Clustered.net](http://www.clustered.net) | - | Yes | Yes | Yes | - | - | +| [Bitfolk](http://bitfolk.com/) | - | Yes | Yes | Yes | They are very knowledgable and understand Tor and its uses. They are hot on spam and abuse so advise changing the default exit (good idea in the UK anyhow). Any DMCA notices received were simply forwarded on without agro | - | +| [RapidSwitch](http://rapidswitch.com/) | - | Yes | Yes | ? | - | 07/2014 | -### Poland +### US | **Company/ISP** | **ASN** | **Bridges** | **Relay** | **Exit** | **Comments** | **Last Updated** | |-------------------------|-------------|-----------------|--------------|-------------|---------------------|------------------------| -| [Hitme.net.pl](http://hitme.net.pl/) | - | Yes | Yes | Yes | - | 12/06/2017 | -| [Hostowisko.pl](http://www.hostowisko.pl/) | - | Yes | Yes | ? | - | 27/08/2013 | -| [Exone](http://www.exone.pl/) | - | Yes | Yes | ? | - | 28/08/2013 | -| [e24cloud](http://www.e24cloud.com/en) | - | Yes | Yes | ? | - | 01/10/2013 | -| [hostinger.pl](http://www.hostinger.pl) | - | Yes | Yes | Yes | 02/10/2013 | -| [statnet.pl](http://www.statnet.pl/) | - | No | No | No | Used to allow Tor-relays, but now is blocking Tor activity | 12/06/2017 | -| [IQ PL](http://www.iq.pl/) | - | Yes | Yes | Yes | They allow running exit node on collocated dedicated server | - | -| [Slask DataCenter](https://sldc.eu/) | - | Yes | Yes | Yes | - | 21/02/2018 | - - -### Mexico +| [2HOST](https://2host.com/) | - | Yes | Yes | Yes(?) | Vague AUP/Abuse handling | 10/15/14 | +| [Amazon Web Services (AWS)](https://aws.amazon.com) | - | Yes | Yes | No | - | - | +| [AmeriNOC](https://www.amerinoc.com/) | - | Yes | Yes | Yes | - | - | +| [Arvixe](https://www.arvixe.com/vps_virtual_private_servers_hosting/) | - | Yes | Yes | Yes | - | 06/19/13 | +| [Axigy](http://www.axigy.com) | - | Yes | Yes | Yes | - | - | +| [Blacklotus](http://www.blacklotus.net) | - | Yes | Yes | Yes | Liberal abuse handling policies | - | +| [BuyVM.net](https://buyvm.net) | AS53667 | Yes | Yes | Yes | New Tor rules [here](https://buyvm.net/acceptable-use-policy/#3). All relays are fine if you follow the steps. | - | +| [Catalyst Host](https://catalysthost.com/) | - | ? | No | No | "If you are interested in hosting either, you can ask us about a dedicated server." | 10/01/14 | +| [ChunkHost](http://chunkhost.com) | - | Yes | Yes | ? | Questionable DMCA handling | 01/01/12 | +| [Cyberonic](http://www.cyberonic.com) | - | Yes | Yes | ? | - | - | +| [Datawagon](https://datawagon.net) | AS27176 | Yes | Yes | Yes | Customers are forwarded abuse complaints to handle themselves | 03/06/19 | +| [DreamHost](https://www.dreamhost.com/) | - | Yes | Yes | ? | - | 11/29/17 | +| [Ethr.net](http://ethr.net/) | - | Yes | Yes | Yes | - | - | +| [Evolucix](http://www.evolucix.com) | - | Yes | Yes | No(?) | - | - | +| [Future Hosting](http://www.futurehosting.com/) | - | Yes | Yes | No | - | 09/01/14 | +| [HostGator](http://www.hostgator.com/) | - | No | No | No | - | - | +| [HostHatch](https://hosthatch.com) | AS46562 | Yes | Yes | No | Their vps isp are mixed include: QuadraNet, nLayer, AboveNet, Inteliquent, Atrato Networks and open peering with the entire Any2LA and Atlanta TIE networks. | 05/01/16 | +| [HostUS](http://hostus.us/) | AS25926 | Yes | Yes | No | - | 10/16/14 | +| [IPXcore](https://ipxcore.com/) | - | Yes | Yes | No | - | - | +| [Luna Node](https://www.lunanode.com/index.php) | - | Yes | Yes | No | - | 05/01/14 | +| [OVH](https://www.ovh.com/us/index.xml ) | AS16276 | Yes | Yes | ? | - | 12/31/14 | +| [Oplink.net](https://www.oplink.net) | - | Yes | Yes | No | - | 09/03/15 | +| [Psychz.net](https://www.psychz.net/) | - | Yes | Yes | Yes | Very Exit friendly. Standard Tor response will resolve abuse issues. | 10/07/15 | +| [PulseServers](https://www.pulseservers.com) | AS16276 | Yes | Yes | Yes | Exit-friendly. | 05/01/16 | +| [RamNode](http://ramnode.com/) | AS3842 | Yes | Yes | No | - | 11/03/14 | +| [Server Complete](https://servercomplete.com/) | - | ? | ? | No | - | 11/03/14 | +| [Softlayer](http://www.softlayer.com) | - | Yes | Yes | ? | - | - | +| [Slicehost/Rackspace](http://www.slicehost.com/) | - | Yes | Yes | No | Host, not an ISP | - | +| [Sh3lls](http://www.sh3lls.net/dedicated.htm) | - | Yes | Yes | No | - | - | +| [SolarVPS](https://solarvps.com) | - | Yes | Yes | Yes | - | - | +| [SeedVPS](https://www.seedvps.com) | - | Yes | Yes | No | - | - | +| [Tailored VPS](http://tailoredvps.com/) | - | Yes | Yes | Yes(?) | - | - | +| [VPS6.NET](https://vps6.net/) | - | Yes | Yes | No | - | - | +| [VPSWebServer.com](http://www.vpswebserver.com) | - | Yes || No | ? | - | - | +| [Inerail](http://inerail.net/) | - | Yes | Yes | Yes | Tor only allowed on dedicated/colocation | - | +| [CondoInternet ISP](http://www.condointernet.net/) | - | Yes | Yes | Yes | - | - | +| [DigitalOcean](http://digitalocean.com/) | - | Yes | Yes | No | - | - | +| [PhoenixNap / Secured Servers](http://www.phoenixnap.com/) | - | Yes | Yes | No | - | 08/01/14 | +| [Vultr](http://vultr.com) | AS20473 | Yes | Yes | No | When asked directly they will claim they do support Tor exits but will pull the rug out from under you later on. This has happened to at least two exit operators. | - | +| [ChicagoVPS](http://chicagovps.net/) | - | Yes | Yes | No | Tor bridge/relay is allowed on the whole VPS range. Any VPS running Exit nodes will be suspended without prior notice. | 15/01/15 | +| [Xmission](https://www.xmission.com/) | - | Yes | Yes | Yes | - | 01/28/15 | +| [blackpulsehosting](https://www.blackpulsehosting.com) | - | Yes | Yes | No | - | 10/25/15 | +| [MonkeyBrains](https://monkeybrains.net) | AS32329 | Yes | Yes | Yes | Only offers colocation, no cheap VPS option. | 1/14/19 | -| **Company/ISP** | **ASN** | **Bridges** | **Relay** | **Exit** | **Comments** | **Last Updated** | -|-------------------------|-------------|-----------------|--------------|-------------|---------------------|------------------------| -| Axtel | - | Yes | Yes | ? | Currently some Guard / Middle nodes are running in Axtel network | 2019 |

1 0