BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
111.94.0.0/15
Announced exactly
- 111.94.0.0/15AS23700Linknet-Fastnet ASNRPKI Not found111.94.0.0
- Registry
- APNIC · Indonesia · Jun 24, 2009
- Delegated block
- 111.94.0.0 – 111.95.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 111.94.0.0/16AS23700Linknet-Fastnet ASNRPKI Not found111.94.0.0
- 111.94.0.0/19AS23700Linknet-Fastnet ASNRPKI Not found111.94.0.0
- 111.94.32.0/19AS23700Linknet-Fastnet ASNRPKI Not found111.94.32.0
- 111.94.64.0/19AS23700Linknet-Fastnet ASNRPKI Not found111.94.64.0
- 111.94.96.0/19AS23700Linknet-Fastnet ASNRPKI Not found111.94.96.0
- 111.94.128.0/19AS23700Linknet-Fastnet ASNRPKI Not found111.94.128.0
- 111.94.160.0/19AS23700Linknet-Fastnet ASNRPKI Not found111.94.160.0
- 111.94.192.0/19AS23700Linknet-Fastnet ASNRPKI Not found111.94.192.0
- 111.94.224.0/19AS23700Linknet-Fastnet ASNRPKI Not found111.94.224.0
- 111.94.252.0/22AS23700Linknet-Fastnet ASNRPKI Not found111.94.252.0
- 111.95.0.0/16AS23700Linknet-Fastnet ASNRPKI Not found111.95.0.0
- 111.95.0.0/19AS23700Linknet-Fastnet ASNRPKI Not found111.95.0.0
- 111.95.32.0/19AS23700Linknet-Fastnet ASNRPKI Not found111.95.32.0
- 111.95.64.0/19AS23700Linknet-Fastnet ASNRPKI Not found111.95.64.0
- 111.95.96.0/19AS23700Linknet-Fastnet ASNRPKI Not found111.95.96.0
- 111.95.128.0/19AS23700Linknet-Fastnet ASNRPKI Not found111.95.128.0
- 111.95.160.0/19AS23700Linknet-Fastnet ASNRPKI Not found111.95.160.0
- 111.95.192.0/19AS23700Linknet-Fastnet ASNRPKI Not found111.95.192.0
- 111.95.224.0/19AS23700Linknet-Fastnet ASNRPKI Not found111.95.224.0
- 111.95.244.0/23AS7632Linknet-Exchange ASNRPKI Not found111.95.244.0
- 111.95.244.0/24AS7632Linknet-Exchange ASNRPKI Not found111.95.244.0
- 111.95.245.0/24AS7632Linknet-Exchange ASNRPKI Not found111.95.245.0
- 111.95.246.0/23AS7632Linknet-Exchange ASNRPKI Not found111.95.246.0
- 111.95.247.0/24AS7632Linknet-Exchange ASNRPKI Not found111.95.247.0
- 111.95.248.0/23AS55673Linknet-IDX ASNRPKI Not found111.95.248.0
- 111.95.248.0/24AS55673Linknet-IDX ASNRPKI Not found111.95.248.0
- 111.95.249.0/24AS55673Linknet-IDX ASNRPKI Not found111.95.249.0
- 111.95.252.0/22AS23700Linknet-Fastnet ASNRPKI Not found111.95.252.0
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 2.48.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.