Improve performance & scalability whilst reducing Bogon related costs and resource drain
Bogon filtering should be undertaken only if the impacts are well-understood. These are not simple filters, and can have adverse impacts if improperly applied. In particular, please consult RFC6598 regarding 100.64.0.0/10. It’s important that you know your network, and that any planned filters are rigorously tested before adoption. These filters may be more applicable to some devices, such as gear that functions as a border router, than other devices.
​
Be sure to check out the main Bogon Reference for more information on the project and terminology used, and why it is important to keep your bogon filters up-to-date.
​
We provide several HTTP-based resources for tracking bogon allocations:
HTML Formatted
​
This is the list of bogons in dotted decimal and reversed-netmask Cisco ACL formats, both aggregated and unaggregated.
​
​
This is the list of bogons in bit notation and Juniper prefix-list formats, both aggregated and unaggregated.
Plain Text
Suitable for scripted wget and parse activities. Please do not fetch more often than the listed update interval, for the lists that are updated only as IANA allocations change, please do not fetch more than once per day.
​
The Text Bogon List, Unaggregated
​
This is the list of bit notation bogons, unaggregated, in text format.
Updated as IANA allocations and special prefix reservations are made.
​
The Text Bogon List, Aggregated
​
This is the list of bit notation bogons, aggregated, in text format.
Updated as IANA allocations and special prefix reservations are made.
​
​
The traditional bogon prefixes, plus prefixes that have been allocated to RIRs but not yet assigned by those RIRs to ISPs, end-users, etc.
​
-
Updated every four hours.
​
IPv6 “fullbogons”, all IPv6 prefixes that have not been allocated to RIRs and that have not been assigned by RIRs to ISPs, end-users, etc.
​
-
Updated every four hours.