BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
209.194.0.0/16
Announced exactly
- 209.194.0.0/16AS3549Level 3 Parent, LLCRPKI Not found209.194.0.0
- Registry
- ARIN · United States · Dec 24, 1997
- Delegated block
- 209.194.0.0 – 209.194.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 209.194.0.0/24AS30305Black Knight IP Holding Company, LLCRPKI Not found209.194.0.0
- 209.194.20.0/24AS394773Delek USRPKI Not found209.194.20.0
- 209.194.23.0/24AS26831Cameron Communications, LLCRPKI Not found209.194.23.0
- 209.194.25.0/24AS26831Cameron Communications, LLCRPKI Not found209.194.25.0
- 209.194.26.0/24AS394622EmmixRPKI Not found209.194.26.0
- 209.194.41.0/24AS3356Level 3 Parent, LLCRPKI Not found209.194.41.0
- 209.194.44.0/24AS3356Level 3 Parent, LLCRPKI Not found209.194.44.0
- 209.194.47.0/24AS63264Alternative Choice Wireless, LLCRPKI Not found209.194.47.0
- 209.194.54.0/23AS3356Level 3 Parent, LLCRPKI Not found209.194.54.0
- 209.194.93.0/24AS63299Pathways Health and Community Support LLCRPKI Not found209.194.93.0
- 209.194.116.0/24AS23357UNASSIGNEDRPKI Not found209.194.116.0
- 209.194.191.0/24AS16952Lightspeed DatalinksRPKI Not found209.194.191.0
- 209.194.192.0/24AS16952Lightspeed DatalinksRPKI Not found209.194.192.0
- 209.194.193.0/24AS16952Lightspeed DatalinksRPKI Not found209.194.193.0
- 209.194.194.0/24AS16952Lightspeed DatalinksRPKI Not found209.194.194.0
- 209.194.195.0/24AS16952Lightspeed DatalinksRPKI Not found209.194.195.0
- 209.194.196.0/24AS16952Lightspeed DatalinksRPKI Not found209.194.196.0
- 209.194.197.0/24AS16952Lightspeed DatalinksRPKI Not found209.194.197.0
- 209.194.205.0/24AS39957Perella Weinberg Partners GP LLCRPKI Not found209.194.205.0
- 209.194.208.0/23AS19179City of El PasoRPKI Valid209.194.208.0
- 209.194.251.0/24AS33313Crown Castle Fiber LLCRPKI Not found209.194.251.0
- 209.194.252.0/23AS25649AYERA TECHNOLOGIES, INC.RPKI Not found209.194.252.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.