BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
216.206.0.0/15
Announced exactly
- 216.206.0.0/15AS209CenturyLink Communications, LLCRPKI Not found216.206.0.0
- Registry
- ARIN · United States · Mar 10, 1999
- Delegated block
- 216.206.0.0 – 216.207.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 216.206.18.0/23AS17385Orbitel Communications, LLCRPKI Not found216.206.18.0
- 216.206.86.0/24AS25739Adtran, Inc.RPKI Not found216.206.86.0
- 216.206.109.0/24AS19031CU*Answers, Inc.RPKI Not found216.206.109.0
- 216.206.110.0/24AS14990Avnet Inc.RPKI Valid216.206.110.0
- 216.206.127.0/24AS541141010Data, Inc.RPKI Not found216.206.127.0
- 216.206.128.0/22AS13781Hopkinsville Electric SystemRPKI Valid216.206.128.0
- 216.206.216.0/22AS26133Frankfort Plant BoardRPKI Not found216.206.216.0
- 216.206.231.0/24AS10753Level 3 Parent, LLCRPKI Not found216.206.231.0
- 216.207.17.0/24AS29759Oxford IndustriesRPKI Not found216.207.17.0
- 216.207.42.0/24AS26579Wal-Mart Stores, Inc.RPKI Not found216.207.42.0
- 216.207.56.0/24AS46849TEXAS LONE STAR NETWORK, LLCRPKI Not found216.207.56.0
- 216.207.72.0/24AS209CenturyLink Communications, LLCRPKI Not found216.207.72.0
- 216.207.90.0/24AS17078Allen & Company LLCRPKI Not found216.207.90.0
- 216.207.192.0/24AS26524BUDCORPKI Not found216.207.192.0
- 216.207.206.0/23AS17143Winn TelecomRPKI Not found216.207.206.0
- 216.207.211.0/24AS17385Orbitel Communications, LLCRPKI Not found216.207.211.0
- 216.207.212.0/23AS17385Orbitel Communications, LLCRPKI Not found216.207.212.0
- 216.207.214.0/23AS17385Orbitel Communications, LLCRPKI Not found216.207.214.0
- 216.207.220.0/24AS12250EDWARD HEALTH SERVICE CORPRPKI Not found216.207.220.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.