BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
209.136.0.0/16
Announced exactly
- 209.136.0.0/16AS3549Level 3 Parent, LLCRPKI Not found209.136.0.0
- Registry
- ARIN · United States · Aug 22, 1997
- Delegated block
- 209.136.0.0 – 209.136.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 209.136.2.0/24AS64288Masonite CorporationRPKI Not found209.136.2.0
- 209.136.4.0/24AS23357UNASSIGNEDRPKI Not found209.136.4.0
- 209.136.8.0/24AS3356Level 3 Parent, LLCRPKI Not found209.136.8.0
- 209.136.9.0/24AS33623Hayneville Telephone CompanyRPKI Not found209.136.9.0
- 209.136.11.0/24AS63480ProSource Technology SolutionsRPKI Not found209.136.11.0
- 209.136.13.0/24AS21985Masco Contractor ServicesRPKI Not found209.136.13.0
- 209.136.14.0/24AS33623Hayneville Telephone CompanyRPKI Not found209.136.14.0
- 209.136.15.0/24AS398847GTE FinancialRPKI Not found209.136.15.0
- 209.136.26.0/24AS10445Huntleigh TelcomRPKI Not found209.136.26.0
- 209.136.27.0/24AS10445Huntleigh TelcomRPKI Not found209.136.27.0
- 209.136.28.0/22AS10445Huntleigh TelcomRPKI Not found209.136.28.0
- 209.136.28.0/24AS10445Huntleigh TelcomRPKI Not found209.136.28.0
- 209.136.29.0/24AS10445Huntleigh TelcomRPKI Not found209.136.29.0
- 209.136.30.0/24AS10445Huntleigh TelcomRPKI Not found209.136.30.0
- 209.136.31.0/24AS10445Huntleigh TelcomRPKI Not found209.136.31.0
- 209.136.32.0/22AS10445Huntleigh TelcomRPKI Not found209.136.32.0
- 209.136.32.0/24AS10445Huntleigh TelcomRPKI Not found209.136.32.0
- 209.136.33.0/24AS10445Huntleigh TelcomRPKI Not found209.136.33.0
- 209.136.34.0/24AS10445Huntleigh TelcomRPKI Not found209.136.34.0
- 209.136.35.0/24AS10445Huntleigh TelcomRPKI Not found209.136.35.0
- 209.136.36.0/24AS10445Huntleigh TelcomRPKI Not found209.136.36.0
- 209.136.37.0/24AS17378TierPoint, LLCRPKI Not found209.136.37.0
- 209.136.38.0/24AS23357UNASSIGNEDRPKI Not found209.136.38.0
- 209.136.66.0/23AS33302Data102RPKI Not found209.136.66.0
- 209.136.70.0/24AS26831Cameron Communications, LLCRPKI Not found209.136.70.0
- 209.136.71.0/24AS26831Cameron Communications, LLCRPKI Not found209.136.71.0
- 209.136.72.0/23AS32877Skyway NetworksRPKI Not found209.136.72.0
- 209.136.82.0/24AS26831Cameron Communications, LLCRPKI Not found209.136.82.0
- 209.136.83.0/24AS26831Cameron Communications, LLCRPKI Not found209.136.83.0
- 209.136.99.0/24AS26831Cameron Communications, LLCRPKI Not found209.136.99.0
- 209.136.103.0/24AS26831Cameron Communications, LLCRPKI Not found209.136.103.0
- 209.136.113.0/24AS3356Level 3 Parent, LLCRPKI Not found209.136.113.0
- 209.136.114.0/23AS3356Level 3 Parent, LLCRPKI Not found209.136.114.0
- 209.136.122.0/24AS26831Cameron Communications, LLCRPKI Not found209.136.122.0
- 209.136.123.0/24AS26831Cameron Communications, LLCRPKI Not found209.136.123.0
- 209.136.139.0/24AS30320Kia America, Inc.RPKI Not found209.136.139.0
- 209.136.140.0/24AS26831Cameron Communications, LLCRPKI Not found209.136.140.0
- 209.136.153.0/24AS33623Hayneville Telephone CompanyRPKI Not found209.136.153.0
- 209.136.158.0/24AS25679Tulsa Datacenter, LLCRPKI Not found209.136.158.0
- 209.136.168.0/24AS33623Hayneville Telephone CompanyRPKI Not found209.136.168.0
- 209.136.169.0/24AS33623Hayneville Telephone CompanyRPKI Not found209.136.169.0
- 209.136.192.0/24AS11402Charlotte Colocation Center, LLcRPKI Not found209.136.192.0
- 209.136.193.0/24AS11402Charlotte Colocation Center, LLcRPKI Not found209.136.193.0
- 209.136.194.0/24AS11402Charlotte Colocation Center, LLcRPKI Not found209.136.194.0
- 209.136.195.0/24AS11402Charlotte Colocation Center, LLcRPKI Not found209.136.195.0
- 209.136.196.0/24AS11402Charlotte Colocation Center, LLcRPKI Not found209.136.196.0
- 209.136.197.0/24AS11402Charlotte Colocation Center, LLcRPKI Not found209.136.197.0
- 209.136.198.0/24AS11402Charlotte Colocation Center, LLcRPKI Not found209.136.198.0
- 209.136.199.0/24AS11402Charlotte Colocation Center, LLcRPKI Not found209.136.199.0
- 209.136.200.0/24AS11402Charlotte Colocation Center, LLcRPKI Not found209.136.200.0
- 209.136.201.0/24AS11402Charlotte Colocation Center, LLcRPKI Not found209.136.201.0
- 209.136.202.0/24AS11402Charlotte Colocation Center, LLcRPKI Not found209.136.202.0
- 209.136.203.0/24AS11402Charlotte Colocation Center, LLcRPKI Not found209.136.203.0
- 209.136.204.0/24AS11402Charlotte Colocation Center, LLcRPKI Not found209.136.204.0
- 209.136.205.0/24AS11402Charlotte Colocation Center, LLcRPKI Not found209.136.205.0
- 209.136.206.0/24AS11402Charlotte Colocation Center, LLcRPKI Not found209.136.206.0
- 209.136.207.0/24AS11402Charlotte Colocation Center, LLcRPKI Not found209.136.207.0
- 209.136.212.0/24AS3356Level 3 Parent, LLCRPKI Not found209.136.212.0
- 209.136.244.0/24AS393671Warren Averett, LLCRPKI Not found209.136.244.0
- 209.136.246.0/24AS399454Global Linking SolutionsRPKI Not found209.136.246.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.