BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
168.215.0.0/16
Announced exactly
- 168.215.0.0/16AS3549Level 3 Parent, LLCRPKI Not found168.215.0.0
- Registry
- ARIN · United States · Jul 18, 1994
- Delegated block
- 168.215.0.0 – 168.215.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 168.215.0.0/19AS10753Level 3 Parent, LLCRPKI Not found168.215.0.0
- 168.215.0.0/24AS10753Level 3 Parent, LLCRPKI Not found168.215.0.0
- 168.215.1.0/24AS10753Level 3 Parent, LLCRPKI Not found168.215.1.0
- 168.215.47.0/24AS10753Level 3 Parent, LLCRPKI Not found168.215.47.0
- 168.215.63.0/24AS3356Level 3 Parent, LLCRPKI Not found168.215.63.0
- 168.215.65.0/24AS3356Level 3 Parent, LLCRPKI Not found168.215.65.0
- 168.215.66.0/24AS3356Level 3 Parent, LLCRPKI Not found168.215.66.0
- 168.215.67.0/24AS27608Rippe & Kingston, LLCRPKI Not found168.215.67.0
- 168.215.82.0/24AS35997UFS LLCRPKI Not found168.215.82.0
- 168.215.85.0/24AS26729Midwest Internet, Inc.RPKI Not found168.215.85.0
- 168.215.94.0/24AS3356Level 3 Parent, LLCRPKI Not found168.215.94.0
- 168.215.97.0/24AS3356Level 3 Parent, LLCRPKI Not found168.215.97.0
- 168.215.98.0/24AS22984Lightspeed CommunicationsRPKI Not found168.215.98.0
- 168.215.103.0/24AS22984Lightspeed CommunicationsRPKI Not found168.215.103.0
- 168.215.115.0/24AS3356Level 3 Parent, LLCRPKI Not found168.215.115.0
- 168.215.123.0/24AS3356Level 3 Parent, LLCRPKI Not found168.215.123.0
- 168.215.128.0/24AS3356Level 3 Parent, LLCRPKI Not found168.215.128.0
- 168.215.155.0/24AS35863Telco 214, Inc.RPKI Not found168.215.155.0
- 168.215.168.0/24AS54266ABC Financial Services, Inc.RPKI Not found168.215.168.0
- 168.215.180.0/22AS53780APPRIVER LLCRPKI Not found168.215.180.0
- 168.215.194.0/23AS26729Midwest Internet, Inc.RPKI Not found168.215.194.0
- 168.215.198.0/24AS14060Brookdale Senior Living IncRPKI Not found168.215.198.0
- 168.215.204.0/24AS3356Level 3 Parent, LLCRPKI Not found168.215.204.0
- 168.215.212.0/24AS12210UNASSIGNEDRPKI Not found168.215.212.0
- 168.215.213.0/24AS19881Valley Telecommunications CompanyRPKI Not found168.215.213.0
- 168.215.224.0/20AS3549Level 3 Parent, LLCRPKI Not found168.215.224.0
- 168.215.226.0/24AS32532Kuakini Medical CenterRPKI Not found168.215.226.0
- 168.215.247.0/24AS22702RingSquaredRPKI Not found168.215.247.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.