BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
159.77.0.0/16
Announced exactly
- 159.77.0.0/16AS721United States Department of Defense (DoD)RPKI Not found159.77.0.0
- Registry
- ARIN · United States · Mar 19, 1992
- Delegated block
- 159.77.0.0 – 159.77.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 159.77.9.0/24AS27065United States Department of Defense (DoD)RPKI Not found159.77.9.0
- 159.77.10.0/24AS27065United States Department of Defense (DoD)RPKI Not found159.77.10.0
- 159.77.13.0/24AS27065United States Department of Defense (DoD)RPKI Not found159.77.13.0
- 159.77.33.0/24AS27066United States Department of Defense (DoD)RPKI Not found159.77.33.0
- 159.77.34.0/24AS27066United States Department of Defense (DoD)RPKI Not found159.77.34.0
- 159.77.35.0/24AS27066United States Department of Defense (DoD)RPKI Not found159.77.35.0
- 159.77.44.0/24AS27066United States Department of Defense (DoD)RPKI Not found159.77.44.0
- 159.77.46.0/24AS27066United States Department of Defense (DoD)RPKI Not found159.77.46.0
- 159.77.47.0/24AS27066United States Department of Defense (DoD)RPKI Not found159.77.47.0
- 159.77.49.0/24AS27064United States Department of Defense (DoD)RPKI Not found159.77.49.0
- 159.77.57.0/24AS27064United States Department of Defense (DoD)RPKI Not found159.77.57.0
- 159.77.58.0/24AS27064United States Department of Defense (DoD)RPKI Not found159.77.58.0
- 159.77.59.0/24AS27064United States Department of Defense (DoD)RPKI Not found159.77.59.0
- 159.77.60.0/24AS27064United States Department of Defense (DoD)RPKI Not found159.77.60.0
- 159.77.79.0/24AS27066United States Department of Defense (DoD)RPKI Not found159.77.79.0
- 159.77.80.0/24AS27066United States Department of Defense (DoD)RPKI Not found159.77.80.0
- 159.77.81.0/24AS27066United States Department of Defense (DoD)RPKI Not found159.77.81.0
- 159.77.84.0/24AS27066United States Department of Defense (DoD)RPKI Not found159.77.84.0
- 159.77.85.0/24AS27066United States Department of Defense (DoD)RPKI Not found159.77.85.0
- 159.77.89.0/24AS27064United States Department of Defense (DoD)RPKI Not found159.77.89.0
- 159.77.90.0/24AS27064United States Department of Defense (DoD)RPKI Not found159.77.90.0
- 159.77.92.0/24AS27064United States Department of Defense (DoD)RPKI Not found159.77.92.0
- 159.77.93.0/24AS27064United States Department of Defense (DoD)RPKI Not found159.77.93.0
- 159.77.106.0/24AS27066United States Department of Defense (DoD)RPKI Not found159.77.106.0
- 159.77.107.0/24AS27066United States Department of Defense (DoD)RPKI Not found159.77.107.0
- 159.77.138.0/24AS27065United States Department of Defense (DoD)RPKI Not found159.77.138.0
- 159.77.148.0/23AS27065United States Department of Defense (DoD)RPKI Not found159.77.148.0
- 159.77.192.0/24AS367United States Department of Defense (DoD)RPKI Not found159.77.192.0
- 159.77.202.0/24AS27065United States Department of Defense (DoD)RPKI Not found159.77.202.0
- 159.77.203.0/24AS27065United States Department of Defense (DoD)RPKI Not found159.77.203.0
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 2.48.0.0/14. This tool looks a prefix up in our daily copy of the global routing table and shows three things:
- Exact announcements: which AS originates exactly this prefix. More than one origin (a MOAS) is normal for anycast services and some multihomed networks, and suspicious otherwise.
- Covering routes: less-specific announcements that contain it. Traffic follows the most specific route, so a covering route matters if the more-specific one disappears.
- More-specifics: announcements inside it, which may belong to other networks (customers, or a hijack).
Each announced route is also checked against the RPKI: whether a ROA authorises its origin AS.
The table is the view from APNIC’s route collector. Most of the global table is the same from everywhere, but a route that is filtered before it reaches that collector will not appear.
Frequently asked questions
Why is my /24 not listed but a /16 is?
Your addresses are announced as part of the larger block, and no one announces the /24 separately. That is the normal case for most customers of a provider.
What is a more-specific hijack?
Someone announces a longer prefix inside your space. Because routers prefer the most specific route, traffic goes to them. RPKI with a strict max length makes such announcements invalid.
Can I enter a single address?
Yes. The tool then shows the most specific announced route that contains it.