BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
49.216.0.0/16
Announced exactly
- 49.216.0.0/16AS9924Taiwan Fixed Network, Telco and Network Service Provider.RPKI Valid49.216.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.216.0.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.216.0.0
- 49.216.4.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.216.4.0
- 49.216.8.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.216.8.0
- 49.216.12.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.216.12.0
- 49.216.16.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.216.16.0
- 49.216.20.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.216.20.0
- 49.216.24.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.216.24.0
- 49.216.28.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.216.28.0
- 49.216.32.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.216.32.0
- 49.216.36.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.216.36.0
- 49.216.40.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.216.40.0
- 49.216.44.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.216.44.0
- 49.216.48.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.216.48.0
- 49.216.52.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.216.52.0
- 49.216.56.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.216.56.0
- 49.216.60.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.216.60.0
- 49.216.64.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.216.64.0
- 49.216.68.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.216.68.0
- 49.216.72.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.216.72.0
- 49.216.76.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.216.76.0
- 49.216.80.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.216.80.0
- 49.216.84.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.216.84.0
- 49.216.88.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.216.88.0
- 49.216.92.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.216.92.0
- 49.216.96.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.216.96.0
- 49.216.100.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.216.100.0
- 49.216.104.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.216.104.0
- 49.216.108.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.216.108.0
- 49.216.112.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.216.112.0
- 49.216.116.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.216.116.0
- 49.216.120.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.216.120.0
- 49.216.124.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.216.124.0
- 49.216.128.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.216.128.0
- 49.216.132.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.216.132.0
- 49.216.136.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.216.136.0
- 49.216.140.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.216.140.0
- 49.216.144.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.216.144.0
- 49.216.148.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.216.148.0
- 49.216.152.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.216.152.0
- 49.216.156.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.216.156.0
- 49.216.160.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.216.160.0
- 49.216.164.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.216.164.0
- 49.216.168.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.216.168.0
- 49.216.172.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.216.172.0
- 49.216.176.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.216.176.0
- 49.216.180.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.216.180.0
- 49.216.184.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.216.184.0
- 49.216.188.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.216.188.0
- 49.216.192.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.216.192.0
- 49.216.196.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.216.196.0
- 49.216.200.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.216.200.0
- 49.216.204.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.216.204.0
- 49.216.208.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.216.208.0
- 49.216.212.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.216.212.0
- 49.216.216.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.216.216.0
- 49.216.220.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.216.220.0
- 49.216.224.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.216.224.0
- 49.216.228.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.216.228.0
- 49.216.232.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.216.232.0
- 49.216.236.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.216.236.0
- 49.216.240.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.216.240.0
- 49.216.244.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.216.244.0
- 49.216.248.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.216.248.0
- 49.216.252.0/22AS24158Taiwan Mobile Co., Ltd.RPKI Valid49.216.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.