BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
49.214.0.0/15
Announced exactly
- 49.214.0.0/15AS9924Taiwan Fixed Network, Telco and Network Service Provider.RPKI Valid49.214.0.0
- Registry
- APNIC · Taiwan · Dec 7, 2010
- Delegated block
- 49.214.0.0 – 49.215.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 49.214.0.0/16AS9924Taiwan Fixed Network, Telco and Network Service Provider.RPKI Valid49.214.0.0
- 49.214.0.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.214.0.0
- 49.214.4.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.214.4.0
- 49.214.8.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.214.8.0
- 49.214.12.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.214.12.0
- 49.214.16.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.214.16.0
- 49.214.20.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.214.20.0
- 49.214.254.0/24AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.214.254.0
- 49.214.255.0/24AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.214.255.0
- 49.215.0.0/16AS9924Taiwan Fixed Network, Telco and Network Service Provider.RPKI Valid49.215.0.0
- 49.215.0.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.215.0.0
- 49.215.4.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.215.4.0
- 49.215.8.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.215.8.0
- 49.215.12.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.215.12.0
- 49.215.16.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.215.16.0
- 49.215.20.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.215.20.0
- 49.215.24.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.215.24.0
- 49.215.28.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.215.28.0
- 49.215.32.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.215.32.0
- 49.215.36.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.215.36.0
- 49.215.40.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.215.40.0
- 49.215.44.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.215.44.0
- 49.215.48.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.215.48.0
- 49.215.52.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.215.52.0
- 49.215.56.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.215.56.0
- 49.215.60.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.215.60.0
- 49.215.64.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.215.64.0
- 49.215.68.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.215.68.0
- 49.215.72.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.215.72.0
- 49.215.76.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.215.76.0
- 49.215.80.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.215.80.0
- 49.215.84.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.215.84.0
- 49.215.88.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.215.88.0
- 49.215.92.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.215.92.0
- 49.215.96.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.215.96.0
- 49.215.100.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.215.100.0
- 49.215.104.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.215.104.0
- 49.215.108.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.215.108.0
- 49.215.112.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.215.112.0
- 49.215.116.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.215.116.0
- 49.215.120.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.215.120.0
- 49.215.124.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.215.124.0
- 49.215.128.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.215.128.0
- 49.215.132.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.215.132.0
- 49.215.136.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.215.136.0
- 49.215.140.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.215.140.0
- 49.215.144.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.215.144.0
- 49.215.148.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.215.148.0
- 49.215.152.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.215.152.0
- 49.215.156.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.215.156.0
- 49.215.160.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.215.160.0
- 49.215.164.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.215.164.0
- 49.215.168.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.215.168.0
- 49.215.172.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.215.172.0
- 49.215.176.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.215.176.0
- 49.215.180.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.215.180.0
- 49.215.184.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.215.184.0
- 49.215.188.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.215.188.0
- 49.215.192.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.215.192.0
- 49.215.196.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.215.196.0
- 49.215.200.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.215.200.0
- 49.215.204.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.215.204.0
- 49.215.208.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.215.208.0
- 49.215.212.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.215.212.0
- 49.215.216.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.215.216.0
- 49.215.220.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.215.220.0
- 49.215.224.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.215.224.0
- 49.215.228.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.215.228.0
- 49.215.232.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.215.232.0
- 49.215.236.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.215.236.0
- 49.215.240.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.215.240.0
- 49.215.244.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.215.244.0
- 49.215.248.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.215.248.0
- 49.215.252.0/24AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.215.252.0
- 49.215.253.0/24AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.215.253.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.