BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
149.88.160.0/19
Announced exactly
- 149.88.160.0/19AS197537WISDOM-CLOUDRPKI Not found149.88.160.0
- Registry
- ARIN · United States · Jan 28, 1992
- Delegated block
- 149.88.0.0 – 149.88.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 149.88.160.0/24AS9304HUTCHISON-AS-AP HGC Global Communications LimitedRPKI Not found149.88.160.0
- 149.88.161.0/24AS9304HUTCHISON-AS-AP HGC Global Communications LimitedRPKI Not found149.88.161.0
- 149.88.162.0/24AS9304HUTCHISON-AS-AP HGC Global Communications LimitedRPKI Not found149.88.162.0
- 149.88.163.0/24AS9304HUTCHISON-AS-AP HGC Global Communications LimitedRPKI Not found149.88.163.0
- 149.88.164.0/24AS174Cogent Communications, LLCRPKI Not found149.88.164.0
- 149.88.165.0/24AS55201SkyQuantum Internet ServiceRPKI Not found149.88.165.0
- 149.88.166.0/24AS174Cogent Communications, LLCRPKI Not found149.88.166.0
- 149.88.167.0/24AS174Cogent Communications, LLCRPKI Not found149.88.167.0
- 149.88.168.0/24AS174Cogent Communications, LLCRPKI Not found149.88.168.0
- 149.88.169.0/24AS55201SkyQuantum Internet ServiceRPKI Not found149.88.169.0
- 149.88.170.0/23AS197537WISDOM-CLOUDRPKI Not found149.88.170.0
- 149.88.172.0/24AS197537WISDOM-CLOUDRPKI Not found149.88.172.0
- 149.88.173.0/24AS202736WISDOMRPKI Not found149.88.173.0
- 149.88.174.0/24AS197537WISDOM-CLOUDRPKI Not found149.88.174.0
- 149.88.175.0/24AS23532IOVZ NETWORKS INCRPKI Not found149.88.175.0
- 149.88.176.0/24AS216138SKYQUANTUM-TELECOMRPKI Not found149.88.176.0
- 149.88.177.0/24AS197537WISDOM-CLOUDRPKI Not found149.88.177.0
- 149.88.178.0/24AS197537WISDOM-CLOUDRPKI Not found149.88.178.0
- 149.88.179.0/24AS9304HUTCHISON-AS-AP HGC Global Communications LimitedRPKI Not found149.88.179.0
- 149.88.180.0/24AS197537WISDOM-CLOUDRPKI Not found149.88.180.0
- 149.88.181.0/24AS197537WISDOM-CLOUDRPKI Not found149.88.181.0
- 149.88.182.0/23AS197537WISDOM-CLOUDRPKI Not found149.88.182.0
- 149.88.184.0/24AS202736WISDOMRPKI Not found149.88.184.0
- 149.88.185.0/24AS202736WISDOMRPKI Not found149.88.185.0
- 149.88.186.0/24AS202736WISDOMRPKI Not found149.88.186.0
- 149.88.187.0/24AS202736WISDOMRPKI Not found149.88.187.0
- 149.88.189.0/24AS197537WISDOM-CLOUDRPKI Not found149.88.189.0
- 149.88.190.0/23AS197537WISDOM-CLOUDRPKI Not found149.88.190.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.