NetBox RIR Manager
Manage Regional Internet Registry (RIR) resources directly from within NetBox.
Features
- Sync RIR resources -- import organizations, contacts (POCs), networks, and ASNs from your RIR into NetBox
- Auto-link to IPAM -- synced networks are linked to existing NetBox Aggregates, Prefixes, and ASNs
- Write operations -- reassign, reallocate, remove, and delete networks directly through the plugin
- Ticket tracking -- monitor RIR tickets and their status
- Per-user API keys -- encrypted at rest
- Scheduled sync -- daily background jobs keep RIR data current
- Pluggable backend architecture -- ARIN supported today; PRs welcome for RIPE, APNIC, LACNIC, AFRINIC
- Full REST API -- every resource and action exposed under
/api/plugins/rir-manager/ - Sync logging -- full audit trail of every sync operation
Compatibility
| Plugin version | NetBox version | Python |
|---|---|---|
| 0.3.x | 4.5 | 3.12-3.14 |
Installation
pip
pip install netbox-rir-manager
From source
pip install git+https://github.com/jsenecal/netbox-rir-manager.git
Configuration
In your NetBox configuration.py:
PLUGINS = [
"netbox_rir_manager",
]
PLUGINS_CONFIG = {
"netbox_rir_manager": {
"top_level_menu": True,
"sync_interval_hours": 24,
"auto_link_networks": True,
"enabled_backends": ["ARIN"],
"encryption_key": "", # defaults to NetBox SECRET_KEY
"api_retry_count": 3,
"api_retry_backoff": 2,
},
}
Then run migrations:
cd /opt/netbox/netbox
python manage.py migrate
Warning: the
encryption_key(or NetBox'sSECRET_KEYwhen empty) is used to encrypt stored API keys. Changing or losing it makes previously encrypted keys unrecoverable.
See Configuration -> Settings for the full reference.
Documentation
Full documentation: jsenecal.github.io/netbox-rir-manager
Contributing
PRs welcome -- especially for additional RIR backends (RIPE, APNIC, LACNIC, AFRINIC). The plugin uses a pluggable backend architecture; see netbox_rir_manager/backends/base.py for the abstract RIRBackend class.
Use conventional-commits PR titles (feat:, fix:, chore:, docs:, ...) -- release-drafter assembles release notes from them. Run make setup after cloning to install dev dependencies and the pre-commit hooks (including the AI-attribution-rejecting commit-msg hook).
License
Metadata
Release files for netbox-rir-manager 0.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| netbox_rir_manager-0.4.0.tar.gz | 66.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| netbox_rir_manager-0.4.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 147.8 kB
Release files / netbox_rir_manager-0.4.0.tar.gz
| Download URL | netbox_rir_manager-0.4.0.tar.gz |
|---|---|
| Size | 66.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6b877c6bc66d3185635d60cbffa1532dee30f7682ec8d8e1c2dc6286ad38e857
|
|
BLAKE2b-256 checksum How to use checksums |
a7e08131d52249f105ba5f35aa282036313335d6b44e4c65793bb13877616409
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 18, 2026.
Transparency logRelease files / netbox_rir_manager-0.4.0-py3-none-any.whl
| Download URL | netbox_rir_manager-0.4.0-py3-none-any.whl |
|---|---|
| Size | 81.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c3cc3e9cfe422e091aaaefc229d9543b63072d42f2e79b5b63c9ec6301853a4f
|
|
BLAKE2b-256 checksum How to use checksums |
5969466f871d02a48df93c3652a3f5195ab3dc36ffdae858868169b428485f97
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 18, 2026.
Transparency log