BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
49.217.0.0/16
Announced exactly
- 49.217.0.0/16AS9924Taiwan Fixed Network, Telco and Network Service Provider.RPKI Valid49.217.0.0
- Registry
- APNIC · Taiwan · Dec 7, 2010
- Delegated block
- 49.216.0.0 – 49.219.255.255
Covering routes
- 49.216.0.0/14AS9924Taiwan Fixed Network, Telco and Network Service Provider.RPKI Valid49.216.0.0
More-specific routes
- 49.217.0.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.217.0.0
- 49.217.4.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.217.4.0
- 49.217.8.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.217.8.0
- 49.217.12.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.217.12.0
- 49.217.16.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.217.16.0
- 49.217.20.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.217.20.0
- 49.217.24.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.217.24.0
- 49.217.28.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.217.28.0
- 49.217.32.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.217.32.0
- 49.217.36.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.217.36.0
- 49.217.44.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.217.44.0
- 49.217.48.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.217.48.0
- 49.217.52.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.217.52.0
- 49.217.56.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.217.56.0
- 49.217.60.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.217.60.0
- 49.217.64.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.217.64.0
- 49.217.68.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.217.68.0
- 49.217.72.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.217.72.0
- 49.217.76.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.217.76.0
- 49.217.80.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.217.80.0
- 49.217.84.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.217.84.0
- 49.217.88.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.217.88.0
- 49.217.92.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.217.92.0
- 49.217.96.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.217.96.0
- 49.217.100.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.217.100.0
- 49.217.108.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.217.108.0
- 49.217.112.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.217.112.0
- 49.217.116.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.217.116.0
- 49.217.120.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.217.120.0
- 49.217.124.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.217.124.0
- 49.217.128.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.217.128.0
- 49.217.132.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.217.132.0
- 49.217.136.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.217.136.0
- 49.217.140.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.217.140.0
- 49.217.144.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.217.144.0
- 49.217.148.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.217.148.0
- 49.217.152.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.217.152.0
- 49.217.156.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.217.156.0
- 49.217.160.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.217.160.0
- 49.217.164.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.217.164.0
- 49.217.172.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.217.172.0
- 49.217.176.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.217.176.0
- 49.217.180.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.217.180.0
- 49.217.184.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.217.184.0
- 49.217.188.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.217.188.0
- 49.217.192.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.217.192.0
- 49.217.196.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.217.196.0
- 49.217.200.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.217.200.0
- 49.217.204.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.217.204.0
- 49.217.208.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.217.208.0
- 49.217.212.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.217.212.0
- 49.217.216.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.217.216.0
- 49.217.220.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.217.220.0
- 49.217.224.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.217.224.0
- 49.217.228.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.217.228.0
- 49.217.232.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.217.232.0
- 49.217.236.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.217.236.0
- 49.217.240.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.217.240.0
- 49.217.244.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.217.244.0
- 49.217.248.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.217.248.0
- 49.217.252.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.217.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, 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.