BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
157.238.0.0/16
Announced exactly
- 157.238.0.0/16AS2914NTT America, Inc.RPKI Valid157.238.0.0
- Registry
- ARIN · United States · Feb 4, 1992
- Delegated block
- 157.238.0.0 – 157.238.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 157.238.0.0/18AS6079RCNRPKI Valid157.238.0.0
- 157.238.80.0/20AS18731Cityside FiberRPKI Valid157.238.80.0
- 157.238.96.0/19AS203020HostRoyale Technologies Pvt LtdRPKI Valid157.238.96.0
- 157.238.136.0/21AS19693Centrilogic, Inc.RPKI Valid157.238.136.0
- 157.238.172.0/24AS148996GLOBAL COMMUNICATION NETWORK LIMITEDRPKI Valid157.238.172.0
- 157.238.174.0/24AS148996GLOBAL COMMUNICATION NETWORK LIMITEDRPKI Valid157.238.174.0
- 157.238.175.0/24AS214432Zhilian Technology CO., LTD.RPKI Valid157.238.175.0
- 157.238.180.0/22AS3491PCCW Global (HK) Ltd.RPKI Valid157.238.180.0
- 157.238.211.0/24AS393536NTT DATA AMERICAS, INCRPKI Valid157.238.211.0
- 157.238.240.0/24AS148996GLOBAL COMMUNICATION NETWORK LIMITEDRPKI Valid157.238.240.0
- 157.238.241.0/24AS148996GLOBAL COMMUNICATION NETWORK LIMITEDRPKI Valid157.238.241.0
- 157.238.242.0/24AS148996GLOBAL COMMUNICATION NETWORK LIMITEDRPKI Valid157.238.242.0
- 157.238.243.0/24AS148996GLOBAL COMMUNICATION NETWORK LIMITEDRPKI Valid157.238.243.0
- 157.238.244.0/24AS214432Zhilian Technology CO., LTD.RPKI Valid157.238.244.0
- 157.238.245.0/24AS214432Zhilian Technology CO., LTD.RPKI Valid157.238.245.0
- 157.238.246.0/24AS148996GLOBAL COMMUNICATION NETWORK LIMITEDRPKI Valid157.238.246.0
- 157.238.247.0/24AS148996GLOBAL COMMUNICATION NETWORK LIMITEDRPKI Valid157.238.247.0
- 157.238.250.0/24AS152179GLOBAL COMMUNICATION NETWORK LIMITEDRPKI Valid157.238.250.0
- 157.238.251.0/24AS152179GLOBAL COMMUNICATION NETWORK LIMITEDRPKI Valid157.238.251.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.