BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
49.229.64.0/19
Announced exactly
- 49.229.64.0/19AS45458SBN-ISP/AWN-ISP and SBN-NIX/AWN-NIXRPKI Valid49.229.64.0
- Registry
- APNIC · Thailand · Nov 25, 2010
- Delegated block
- 49.228.0.0 – 49.231.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 49.229.64.0/24AS45458SBN-ISP/AWN-ISP and SBN-NIX/AWN-NIXRPKI Valid49.229.64.0
- 49.229.66.0/24AS45458SBN-ISP/AWN-ISP and SBN-NIX/AWN-NIXRPKI Valid49.229.66.0
- 49.229.67.0/24AS45458SBN-ISP/AWN-ISP and SBN-NIX/AWN-NIXRPKI Valid49.229.67.0
- 49.229.68.0/24AS45430SBN-IIG/AWN-IIG transit providerRPKI Valid49.229.68.0
- 49.229.69.0/24AS45458SBN-ISP/AWN-ISP and SBN-NIX/AWN-NIXRPKI Valid49.229.69.0
- 49.229.70.0/24AS45458SBN-ISP/AWN-ISP and SBN-NIX/AWN-NIXRPKI Valid49.229.70.0
- 49.229.71.0/24AS45458SBN-ISP/AWN-ISP and SBN-NIX/AWN-NIXRPKI Valid49.229.71.0
- 49.229.72.0/24AS45458SBN-ISP/AWN-ISP and SBN-NIX/AWN-NIXRPKI Valid49.229.72.0
- 49.229.73.0/24AS45458SBN-ISP/AWN-ISP and SBN-NIX/AWN-NIXRPKI Valid49.229.73.0
- 49.229.74.0/24AS45458SBN-ISP/AWN-ISP and SBN-NIX/AWN-NIXRPKI Valid49.229.74.0
- 49.229.76.0/24AS45458SBN-ISP/AWN-ISP and SBN-NIX/AWN-NIXRPKI Valid49.229.76.0
- 49.229.77.0/24AS45458SBN-ISP/AWN-ISP and SBN-NIX/AWN-NIXRPKI Valid49.229.77.0
- 49.229.78.0/24AS45458SBN-ISP/AWN-ISP and SBN-NIX/AWN-NIXRPKI Valid49.229.78.0
- 49.229.79.0/24AS45458SBN-ISP/AWN-ISP and SBN-NIX/AWN-NIXRPKI Valid49.229.79.0
- 49.229.80.0/24AS45458SBN-ISP/AWN-ISP and SBN-NIX/AWN-NIXRPKI Valid49.229.80.0
- 49.229.81.0/24AS45458SBN-ISP/AWN-ISP and SBN-NIX/AWN-NIXRPKI Valid49.229.81.0
- 49.229.82.0/24AS45458SBN-ISP/AWN-ISP and SBN-NIX/AWN-NIXRPKI Valid49.229.82.0
- 49.229.83.0/24AS45458SBN-ISP/AWN-ISP and SBN-NIX/AWN-NIXRPKI Valid49.229.83.0
- 49.229.84.0/24AS45458SBN-ISP/AWN-ISP and SBN-NIX/AWN-NIXRPKI Valid49.229.84.0
- 49.229.85.0/24AS45458SBN-ISP/AWN-ISP and SBN-NIX/AWN-NIXRPKI Valid49.229.85.0
- 49.229.86.0/24AS45458SBN-ISP/AWN-ISP and SBN-NIX/AWN-NIXRPKI Valid49.229.86.0
- 49.229.87.0/24AS45458SBN-ISP/AWN-ISP and SBN-NIX/AWN-NIXRPKI Valid49.229.87.0
- 49.229.88.0/23AS134240Super Broadband Network Company LimitedRPKI Valid49.229.88.0
- 49.229.90.0/23AS134240Super Broadband Network Company LimitedRPKI Valid49.229.90.0
- 49.229.92.0/24AS136897Enjoyvc Cloud Group Limited.RPKI Valid49.229.92.0
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 158.36.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.