BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
209.12.0.0/16
Announced exactly
- 209.12.0.0/16AS3549Level 3 Parent, LLCRPKI Not found209.12.0.0
- Registry
- ARIN · United States · Dec 23, 1996
- Delegated block
- 209.12.0.0 – 209.12.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 209.12.4.0/24AS40139Jackson Technical LLCRPKI Not found209.12.4.0
- 209.12.23.0/24AS40139Jackson Technical LLCRPKI Not found209.12.23.0
- 209.12.25.0/24AS26831Cameron Communications, LLCRPKI Not found209.12.25.0
- 209.12.26.0/24AS26831Cameron Communications, LLCRPKI Not found209.12.26.0
- 209.12.34.0/24AS26831Cameron Communications, LLCRPKI Not found209.12.34.0
- 209.12.35.0/24AS26831Cameron Communications, LLCRPKI Not found209.12.35.0
- 209.12.49.0/24AS33489Comcast Cable Communications, LLCRPKI Not found209.12.49.0
- 209.12.52.0/24AS32166Troutman Pepper Locke LLPRPKI Not found209.12.52.0
- 209.12.56.0/24AS23357UNASSIGNEDRPKI Not found209.12.56.0
- 209.12.60.0/24AS13649Flexential Colorado Corp.RPKI Not found209.12.60.0
- 209.12.64.0/24AS399876Inland Empire Health PlanRPKI Not found209.12.64.0
- 209.12.71.0/24AS395918Sandestin Investments LLCRPKI Not found209.12.71.0
- 209.12.79.0/24AS3356Level 3 Parent, LLCRPKI Not found209.12.79.0
- 209.12.95.0/24AS3356Level 3 Parent, LLCRPKI Not found209.12.95.0
- 209.12.96.0/24AS3356Level 3 Parent, LLCRPKI Not found209.12.96.0
- 209.12.97.0/24AS3356Level 3 Parent, LLCRPKI Not found209.12.97.0
- 209.12.105.0/24AS3356Level 3 Parent, LLCRPKI Not found209.12.105.0
- 209.12.110.0/24AS26831Cameron Communications, LLCRPKI Not found209.12.110.0
- 209.12.118.0/24AS33623Hayneville Telephone CompanyRPKI Not found209.12.118.0
- 209.12.122.0/24AS26831Cameron Communications, LLCRPKI Not found209.12.122.0
- 209.12.128.0/24AS26831Cameron Communications, LLCRPKI Not found209.12.128.0
- 209.12.133.0/24AS46413Fulair, LLCRPKI Not found209.12.133.0
- 209.12.153.0/24AS33623Hayneville Telephone CompanyRPKI Not found209.12.153.0
- 209.12.154.0/24AS3356Level 3 Parent, LLCRPKI Not found209.12.154.0
- 209.12.155.0/24AS3356Level 3 Parent, LLCRPKI Not found209.12.155.0
- 209.12.156.0/24AS3356Level 3 Parent, LLCRPKI Not found209.12.156.0
- 209.12.161.0/24AS26831Cameron Communications, LLCRPKI Not found209.12.161.0
- 209.12.164.0/24AS33606TekLinks, Inc.RPKI Not found209.12.164.0
- 209.12.165.0/24AS33606TekLinks, Inc.RPKI Not found209.12.165.0
- 209.12.170.0/24AS3356Level 3 Parent, LLCRPKI Not found209.12.170.0
- 209.12.172.0/23AS3356Level 3 Parent, LLCRPKI Not found209.12.172.0
- 209.12.188.0/23AS3356Level 3 Parent, LLCRPKI Not found209.12.188.0
- 209.12.196.0/23AS3356Level 3 Parent, LLCRPKI Not found209.12.196.0
- 209.12.200.0/24AS33623Hayneville Telephone CompanyRPKI Not found209.12.200.0
- 209.12.214.0/24AS3356Level 3 Parent, LLCRPKI Not found209.12.214.0
- 209.12.229.0/24AS25679Tulsa Datacenter, LLCRPKI Not found209.12.229.0
- 209.12.231.0/24AS26831Cameron Communications, LLCRPKI Not found209.12.231.0
- 209.12.232.0/24AS26831Cameron Communications, LLCRPKI Not found209.12.232.0
- 209.12.233.0/24AS26831Cameron Communications, LLCRPKI Not found209.12.233.0
- 209.12.237.0/24AS395372First Command Financial Services, Inc.RPKI Not found209.12.237.0
- 209.12.244.0/24AS40139Jackson Technical LLCRPKI Not found209.12.244.0
- 209.12.255.0/24AS40139Jackson Technical LLCRPKI Not found209.12.255.0
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 49.224.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.