BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
207.201.192.0/18
Announced exactly
- 207.201.192.0/18AS3549Level 3 Parent, LLCRPKI Not found207.201.192.0
- Registry
- ARIN · United States · Sep 17, 1996
- Delegated block
- 207.201.192.0 – 207.201.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 207.201.195.0/24AS3356Level 3 Parent, LLCRPKI Not found207.201.195.0
- 207.201.198.0/24AS23436LogistaRPKI Not found207.201.198.0
- 207.201.208.0/24AS46381E-INS, LLCRPKI Not found207.201.208.0
- 207.201.213.0/24AS63264Alternative Choice Wireless, LLCRPKI Not found207.201.213.0
- 207.201.214.0/24AS397151Trans Union, LLCRPKI Not found207.201.214.0
- 207.201.216.0/22AS40805JMF Solutions, IncRPKI Not found207.201.216.0
- 207.201.224.0/24AS26831Cameron Communications, LLCRPKI Not found207.201.224.0
- 207.201.237.0/24AS393447Virtual Stacks LLCRPKI Not found207.201.237.0
- 207.201.249.0/24AS26831Cameron Communications, LLCRPKI Not found207.201.249.0
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 193.166.0.0/15. 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.