To Report a Bug

We have migrated our ticket system to I2P's Gitlab (clearnet) (in-I2P)

View open tickets on Gitlab: (clearnet) (in-I2P)

To file a new ticket, you'll need to log in or create an account on Gitlab first. Please allow up to 24 hours for your account to be approved. Unfortunately, approval is necessary to limit spam.

Please enter as much information as you can when filing a new bug, including version information and relevant logs from in your router console.

All links below are for Trac ticket queries. Please visit the Gitlab links above to see current tickets or to enter a new ticket. Open Trac tickets have been migrated to Gitlab.

The Standard Trac Tickets Page

Custom Query

Special Tickets


Each keyword links to all of the open tickets mentioning that keyword. If you find existing tickets that are missing keywords, please feel free to add them.

  • new-user (0): issues that affect users who are new to I2P
  • websec (0): interaction between I2P's security model and the routerconsole
  • iputil (0): having to do with automatically detecting the router's own IP address
  • privacy (12): could lead to the unintended disclosure of information
  • anonymity (5): relevant to the direct anonymity properties of I2P (should usually also be tagged with 'privacy')
  • security (6): security issues not necessarily tagged with a more specific keyword (confidentiality, integrity, etc.)
  • reliability (9): could lead to unpredictable failure of functionality
  • anti-censorship (5): could help with resistance to censorship or denial of service
  • scalability (4): scaling to large and/or geographically dispersed routers, or to high traffic volumes or numbers of clients
  • peer-selection (5): related to the choice of tunnel peers according to topographical, geographical, bandwidth, etc. constraints
  • forward-compatibility (1): relevant to forward compatibility of network protocols with future I2P versions
  • transparency (2): features that help the user see and understand the inner workings, such as visualization, statistics, explorability
  • unicode (0): related to Unicode
  • i18n (0): related to internationalization (usually also to Unicode)
  • usability (27): concerned with ease of use (interface or mental models)
  • error (9): concerned with error reporting to end-users
  • install (9): installation problems (not always with the installer)
  • docs (15): fixing this issue involves updating documentation
  • test (5): additional or better test coverage needed
  • performance (22): an opportunity to improve some aspect of performance (speed, latency, bandwidth, space usage, etc.)
  • memory (1): an opportunity to improve memory usage (should usually also be tagged with 'performance')
  • extensibility (2): extensibility and customization mechanisms
  • race (0): related to race conditions between different threads
  • hang (7): could cause an operation to hang, either indefinitely or for long periods
  • firewall (4): firewall and NAT traversal issues
  • standards (3): compliance to standards (HTTP, HTML etc.)
  • heisenbug (3): bugs that are not easily reproducible so far
  • cleanup (6): code clean-up / refactoring
  • time (6): having to do with time and clocks
  • defaults (1): having to do with the default settings for configuration parameters
  • no keywords (319): open tickets with no keywords

Platform keywords



Android apps

Development infrastructure

  • mtn (1): Monotone revision control system
  • trac (1): Trac bug tracker and wiki
  • coverage (0): test coverage analyzer
  • jenkins (0): automated builds by Jenkins
  • irc (1): IRC bots for #i2p-dev channel
  • build (7): related to the build scripts
  • release (3): related to the release process
  • metrics (2): Metrics collection

Tickets by Component

The Standard Trac Tickets Page

Last modified 4 months ago Last modified on May 16, 2021 1:07:27 PM