BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
143.212.0.0/15
Announced exactly
- 143.212.0.0/15AS721United States Department of Defense (DoD)RPKI Not found143.212.0.0
- Registry
- ARIN · United States · Jun 30, 1990
- Delegated block
- 143.212.0.0 – 143.212.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 143.212.0.0/16AS1602Headquarters, USAISCRPKI Not found143.212.0.0
- 143.212.11.0/24AS1602Headquarters, USAISCRPKI Not found143.212.11.0
- 143.212.12.0/24AS1602Headquarters, USAISCRPKI Not found143.212.12.0
- 143.212.17.0/24AS1602Headquarters, USAISCRPKI Not found143.212.17.0
- 143.212.18.0/24AS1602Headquarters, USAISCRPKI Not found143.212.18.0
- 143.212.22.0/24AS1602Headquarters, USAISCRPKI Not found143.212.22.0
- 143.212.23.0/24AS1602Headquarters, USAISCRPKI Not found143.212.23.0
- 143.212.33.0/24AS1602Headquarters, USAISCRPKI Not found143.212.33.0
- 143.212.34.0/24AS1602Headquarters, USAISCRPKI Not found143.212.34.0
- 143.212.35.0/24AS1602Headquarters, USAISCRPKI Not found143.212.35.0
- 143.212.36.0/24AS1602Headquarters, USAISCRPKI Not found143.212.36.0
- 143.212.37.0/24AS1602Headquarters, USAISCRPKI Not found143.212.37.0
- 143.212.38.0/24AS1602Headquarters, USAISCRPKI Not found143.212.38.0
- 143.212.52.0/24AS1602Headquarters, USAISCRPKI Not found143.212.52.0
- 143.212.54.0/24AS1602Headquarters, USAISCRPKI Not found143.212.54.0
- 143.212.104.0/24AS1602Headquarters, USAISCRPKI Not found143.212.104.0
- 143.212.106.0/24AS1602Headquarters, USAISCRPKI Not found143.212.106.0
- 143.212.108.0/24AS1602Headquarters, USAISCRPKI Not found143.212.108.0
- 143.212.111.0/24AS1602Headquarters, USAISCRPKI Not found143.212.111.0
- 143.212.112.0/24AS1602Headquarters, USAISCRPKI Not found143.212.112.0
- 143.212.118.0/24AS1602Headquarters, USAISCRPKI Not found143.212.118.0
- 143.212.245.0/24AS1602Headquarters, USAISCRPKI Not found143.212.245.0
- 143.212.249.0/24AS1602Headquarters, USAISCRPKI Not found143.212.249.0
- 143.213.0.0/16AS1602Headquarters, USAISCRPKI Not found143.213.0.0
- 143.213.11.0/24AS1602Headquarters, USAISCRPKI Not found143.213.11.0
- 143.213.12.0/24AS1602Headquarters, USAISCRPKI Not found143.213.12.0
- 143.213.17.0/24AS1602Headquarters, USAISCRPKI Not found143.213.17.0
- 143.213.18.0/24AS1602Headquarters, USAISCRPKI Not found143.213.18.0
- 143.213.19.0/24AS1602Headquarters, USAISCRPKI Not found143.213.19.0
- 143.213.20.0/24AS1602Headquarters, USAISCRPKI Not found143.213.20.0
- 143.213.22.0/24AS1602Headquarters, USAISCRPKI Not found143.213.22.0
- 143.213.23.0/24AS1602Headquarters, USAISCRPKI Not found143.213.23.0
- 143.213.25.0/24AS1602Headquarters, USAISCRPKI Not found143.213.25.0
- 143.213.34.0/24AS1602Headquarters, USAISCRPKI Not found143.213.34.0
- 143.213.36.0/23AS1602Headquarters, USAISCRPKI Not found143.213.36.0
- 143.213.40.0/23AS1602Headquarters, USAISCRPKI Not found143.213.40.0
- 143.213.42.0/24AS1602Headquarters, USAISCRPKI Not found143.213.42.0
- 143.213.44.0/24AS1602Headquarters, USAISCRPKI Not found143.213.44.0
- 143.213.46.0/23AS1602Headquarters, USAISCRPKI Not found143.213.46.0
- 143.213.48.0/24AS1602Headquarters, USAISCRPKI Not found143.213.48.0
- 143.213.52.0/24AS1602Headquarters, USAISCRPKI Not found143.213.52.0
- 143.213.54.0/23AS1602Headquarters, USAISCRPKI Not found143.213.54.0
- 143.213.57.0/24AS1602Headquarters, USAISCRPKI Not found143.213.57.0
- 143.213.58.0/24AS1602Headquarters, USAISCRPKI Not found143.213.58.0
- 143.213.60.0/24AS1602Headquarters, USAISCRPKI Not found143.213.60.0
- 143.213.64.0/24AS1602Headquarters, USAISCRPKI Not found143.213.64.0
- 143.213.65.0/24AS1602Headquarters, USAISCRPKI Not found143.213.65.0
- 143.213.67.0/24AS1602Headquarters, USAISCRPKI Not found143.213.67.0
- 143.213.69.0/24AS1602Headquarters, USAISCRPKI Not found143.213.69.0
- 143.213.80.0/24AS1602Headquarters, USAISCRPKI Not found143.213.80.0
- 143.213.81.0/24AS1602Headquarters, USAISCRPKI Not found143.213.81.0
- 143.213.82.0/24AS1602Headquarters, USAISCRPKI Not found143.213.82.0
- 143.213.98.0/23AS1602Headquarters, USAISCRPKI Not found143.213.98.0
- 143.213.104.0/24AS1602Headquarters, USAISCRPKI Not found143.213.104.0
- 143.213.106.0/24AS1602Headquarters, USAISCRPKI Not found143.213.106.0
- 143.213.107.0/24AS1602Headquarters, USAISCRPKI Not found143.213.107.0
- 143.213.111.0/24AS1602Headquarters, USAISCRPKI Not found143.213.111.0
- 143.213.112.0/24AS1602Headquarters, USAISCRPKI Not found143.213.112.0
- 143.213.114.0/24AS1602Headquarters, USAISCRPKI Not found143.213.114.0
- 143.213.115.0/24AS1602Headquarters, USAISCRPKI Not found143.213.115.0
- 143.213.125.0/24AS1602Headquarters, USAISCRPKI Not found143.213.125.0
- 143.213.158.0/24AS1602Headquarters, USAISCRPKI Not found143.213.158.0
- 143.213.160.0/24AS1602Headquarters, USAISCRPKI Not found143.213.160.0
- 143.213.180.0/24AS1602Headquarters, USAISCRPKI Not found143.213.180.0
- 143.213.181.0/24AS1602Headquarters, USAISCRPKI Not found143.213.181.0
- 143.213.182.0/24AS1602Headquarters, USAISCRPKI Not found143.213.182.0
- 143.213.183.0/24AS1602Headquarters, USAISCRPKI Not found143.213.183.0
- 143.213.185.0/24AS1602Headquarters, USAISCRPKI Not found143.213.185.0
- 143.213.190.0/24AS1602Headquarters, USAISCRPKI Not found143.213.190.0
- 143.213.195.0/24AS1602Headquarters, USAISCRPKI Not found143.213.195.0
- 143.213.206.0/23AS1602Headquarters, USAISCRPKI Not found143.213.206.0
- 143.213.216.0/23AS1602Headquarters, USAISCRPKI Not found143.213.216.0
- 143.213.218.0/24AS1602Headquarters, USAISCRPKI Not found143.213.218.0
- 143.213.221.0/24AS1602Headquarters, USAISCRPKI Not found143.213.221.0
- 143.213.222.0/24AS1602Headquarters, USAISCRPKI Not found143.213.222.0
- 143.213.245.0/24AS1602Headquarters, USAISCRPKI Not found143.213.245.0
- 143.213.250.0/24AS1602Headquarters, USAISCRPKI Not found143.213.250.0
- 143.213.252.0/24AS1602Headquarters, USAISCRPKI Not found143.213.252.0
- 143.213.253.0/24AS1602Headquarters, USAISCRPKI Not found143.213.253.0
- 143.213.254.0/24AS1602Headquarters, USAISCRPKI Not found143.213.254.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.