The I2P network is currently experiencing an attack by unknown actor(s). Tens of thousands of malicious routers have been introduced to the network that are not actually routing any traffic. This is causing:
- Extremely low tunnel build success rates
- Overall network congestion
- Degraded performance for legitimate users
The I2P development team is aware of this situation and actively investigating mitigations.
We will post updates to this thread as the situation develops. Thank you for your patience.
Update: 2/4/2026 11AM CST - Fixes are being tested now.
Update: 2/4/2026 7pm EST - Some changes were implemented in a new build to help combat the issue. Right now I only have the binaries for apple silicon.
IRC is semi alive, if you update your IRC config to use irc.echelon.i2p:6667 you should be able to connect.
https://files.i2p.net/I2P-2.10.0-5.dmg
2.10.0-5 i2pupdate.zip
Anything we as users can do to help? Other then already running the router of course.
Apply the fix specified for now.
I will update asap when the docker version becomes available.
Any chance it’s related to the influx of new Lemmy/Piefed users? People want to try out I2P but misconfigure their nodes, causing network problems. I2P is a pretty active community
This looks like a coordinated attack more than anything else apparently.
The fix should remedy the situation by blocking the specific version of i2p that the attackers are using.
Is i2pd affected?
Yes. All implementations affected.
It’s not a fault in the code as such, just a large amount of routers that’s joined the network configured to not route messages.
Ah, that explains why my tunnel creation success rate is suddenly down to 1%. I was wondering what happened while I was away from home