March 2 2018: There are some problems with the automated software used to prevent abuse of the Web site (mainly to prevent mass downloads from hurting site performance for everyone else).
"http://www. w3. org/TR/REC-html40/loose. dtd">
<html lang="en" dir="ltr">
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>Request Blocked - www. gutenberg. org
</TITLE>
<meta charset="UTF-8" />
<link rel="shortcut icon" href="/favicon. ico" />
</HEAD>
<body>
<font color="red">
<h1 align="center">Your IP Address is Blocked from www. gutenberg. org</h1>
</font>
<p>We apologize for this inconvenience. Your IP address has been automatically blocked from the address you tried to visit at www. gutenberg. org or a partner site. </p>
<p>March 2 2018: There are some problems with the automated software used to prevent abuse of the Web site (mainly to prevent mass downloads from hurting site performance for everyone else). Unfortunately the systems staff will not be available until Monday, to apply fixes. Meanwhile, it appears that downloads of epub and mobi (Kindle) formatted eBooks is triggering blocks. The HTML ("Read this book online") links seem to work better. Apologies for this problem. We hope it will be fixed early in the week of March 5. </p>
<h2>Diagnostic information:</h2>
<code> <p>Your IP address: 73. 246. 62. 242</p>
<p>Referrer URL (if available): (none)</p>
<p>Time (GMT): Saturday, 03-Mar-2018 06:23:43 GMT</p>
</code>
<h2>Why did this block occur? </h2>
<p>Project Gutenberg's <a href="https://www. gutenberg. org/wiki/Gutenberg:Terms_of_Use">Terms of Use</a> prohibit mass downloads or automated harvesting of the collection. The site relies on donated servers and bandwidth, so has automated mechanisms in place to detect when too many downloads are occurring from a single location (IP address). This helps to keep the site as available as possible for visitors. Some reasons why IP addresses are blocked include:</p>
<ul>
<li>Your program is trying to "harvest" the contents. Instead, see the <a href="https://www. gutenberg. org/wiki/Gutenberg:Mirroring_How-To">Mirroring How-To</a>, and the <a href="https://www. gutenberg. org/wiki/Gutenberg:Information_About_Robot_Access_to_our_Pages">Robot ReadMe</a>, once your block has expired. </li>
<li>You have a shared IP address, and someone else has triggered the block. This has happened with Amazon Kindle, where Amazon funnels Kindles through their cloud servers. Instead, download to your computer, and transfer to your reader device. See the <a href="https://www. gutenberg. org/wiki/Gutenberg:MobileReader_Devices_How-To">Mobile reader devices how-to</a>, once your block has expired. It also happens sometimes with TOR, with classrooms/schools, and other situations where the same IP address is being shared. </li>
</ul>
<h2>How can I get unblocked? </h2>
<p>Blocks automatically expire. </p>
<h2>I have other questions or need to report an error</h2>
<p>Please email the diagnostic information to <pre>help2018 @ pglaf. org</pre> (removing the spaces around the @) and we will try to help. Adjustment of the blocking software in late February and early March 2018 has resulted in some "false positives" -- that is, blocks that should not have occurred. If that happened to you, please let us know so we can keep adjusting the software. Apologies if this happened, because human users who are making use of the eBooks or other site features should almost never be blocked. </p>
<hr />
<p><i>Most recently updated: March 2, 2018.
March 2 2018: There are some problems with the
automated
software used to prevent abuse of the Web site (mainly to prevent mass downloads from hurting site performance for everyone else).
Unfortunately the systems staff will not be available until Monday, to apply fixes.
Meanwhile, it appears that downloads of epub and mobi (Kindle) formatted eBooks is triggering blocks.
The HTML ("Read this book online") links seem to work better.
Apologies for this problem.
We hope it will be fixed early in the week of March 5.
</p>
<h2>Diagnostic information:</h2>
<code> <p>Your IP address: 73.
246.
62.
242</p>
<p>Referrer URL (if available): (none)</p>
<p>Time (GMT): Saturday, 03-Mar-2018 06:23:43 GMT</p>
</code>
<h2>Why did this block occur?
</h2>
<p>Project Gutenberg's <a href="https://www.
gutenberg.
org/wiki/Gutenberg:Terms_of_Use">Terms of Use</a> prohibit mass downloads or automated harvesting of the collection.
The site relies on donated servers and bandwidth, so has automated mechanisms in place to detect when too many downloads are occurring from a single location (IP address).
This helps to keep the site as available as possible for visitors.
Some reasons why IP addresses are blocked include:</p>
<ul>
<li>Your program is trying to "harvest" the contents.
Instead, see the <a href="https://www.
gutenberg.
org/wiki/Gutenberg:Mirroring_How-To">Mirroring How-To</a>, and the <a href="https://www.
gutenberg.
org/wiki/Gutenberg:Information_About_Robot_Access_to_our_Pages">Robot ReadMe</a>, once your block has expired.
</li>
<li>You have a shared IP address, and someone else has triggered the block.
This has happened with Amazon Kindle, where Amazon funnels Kindles through their cloud servers.
Instead, download to your computer, and transfer to your reader device.
See the <a href="https://www.
gutenberg.
org/wiki/Gutenberg:MobileReader_Devices_How-To">Mobile reader devices how-to</a>, once your block has expired.
It also happens sometimes with TOR, with classrooms/schools, and other situations where the same IP address is being shared.
</li>
</ul>
<h2>How can I get unblocked?
</h2>
<p>Blocks automatically expire.
</p>
<h2>I have other questions or need to report an error</h2>
<p>Please email the diagnostic information to <pre>help2018 @ pglaf.
org</pre> (removing the spaces around the @) and we will try to help.
Adjustment of the blocking software in late February and early March 2018 has resulted in some "false positives" -- that is, blocks that should not have occurred.
If that happened to you, please let us know so we can keep adjusting the software.
Apologies if this happened, because human users who are making use of the eBooks or other site features should almost never be blocked.
</p>
<hr />
<p><i>Most recently updated: March 2, 2018.
