Level3 has a very specific/finicky RPSL based router configuration tool. So specific in fact if you have your route objects in RADB and include customer objects from ALTDB the ALTDB objects will be filtered. If you are having this problem – here’s the secret, Level3 needs to add additional sources to their search path, enable recurseok and warnonly. Example below:
import policy:-le=32 RADB::AS-PHYBER -searchpath=RADB;ALTDB -recurseok -warnonly
Using IRR with Level3
September 2, 2009
Facing this decision now? We’ll tell you where you stand.
No pitch. Just answers. We're paid the same whichever vendor you choose.
More on



