I2P Router VPS for Floodfill Nodes and Eepsites

Floodfill nodes store and serve I2P network database entries and are critical to peer discovery. Running a high uptime floodfill on a VPS strengthens the network for every user. We deploy I2P with the official Java router or with i2pd, the C++ implementation that performs better on small VPS. Floodfill participation is enabled in the configuration and the VPS is sized to handle the additional memory and connection load.

We tune kernel parameters for the elevated connection counts that floodfill nodes attract. File descriptor limits and conntrack tables are sized to avoid the most common failure modes that affect long lived floodfill nodes on default configurations.

Eepsites are I2P hidden services with their own .i2p addresses. Operators commonly host eepsites on the same VPS that runs their router, exposing only the I2P tunnel and not any clearnet listener. We provide hardened Nginx and Apache templates for eepsite hosting with no server banner, no version disclosure, and aggressive default Content-Security-Policy headers.

Long lived eepsites benefit from stable destinations and we never reset the I2P data directory between maintenance operations unless the customer requests it. The .i2p address can survive years of operation on the same VPS, accumulating reputation in the network.

I2P is anonymous by design but the operator behind a long lived router is only anonymous if the hosting layer is. AnubizHost provides anonymous signup, crypto only billing, and no KYC. The I2P router identity is independent of the AnubizHost account and rotates on operator command. Linking the two requires breaching both the hosting records and the I2P network database, which neither side retains in a useful form.

Crypto only billing through Bitcoin and Monero keeps the financial trail outside the reach of traditional surveillance pipelines. Romania and Iceland remain the recommended jurisdictions for I2P operators with active threat models.