BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
119.144.0.0/14
Announced exactly
- 119.144.0.0/14AS4134No.31,Jin-rong StreetRPKI Not found119.144.0.0
- Registry
- APNIC · China · Feb 7, 2008
- Delegated block
- 119.144.0.0 – 119.147.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 119.145.184.0/21AS140319CHINATELECOM Guangdong province Qingyuan 5G networkRPKI Valid119.145.184.0
- 119.145.192.0/21AS140319CHINATELECOM Guangdong province Qingyuan 5G networkRPKI Valid119.145.192.0
- 119.145.200.0/22AS140319CHINATELECOM Guangdong province Qingyuan 5G networkRPKI Valid119.145.200.0
- 119.145.204.0/22AS140319CHINATELECOM Guangdong province Qingyuan 5G networkRPKI Valid119.145.204.0
- 119.146.0.0/21AS140318CHINATELECOM Guangdong province Heyuan 5G networkRPKI Not found119.146.0.0
- 119.146.8.0/22AS140318CHINATELECOM Guangdong province Heyuan 5G networkRPKI Not found119.146.8.0
- 119.146.24.0/23AS140309CHINATELECOM Guangdong province Zhongshan 5G networkRPKI Not found119.146.24.0
- 119.146.28.0/22AS140320CHINATELECOM Guangdong province Shanwei 5G networkRPKI Valid119.146.28.0
- 119.146.32.0/23AS140309CHINATELECOM Guangdong province Zhongshan 5G networkRPKI Not found119.146.32.0
- 119.146.34.0/23AS140318CHINATELECOM Guangdong province Heyuan 5G networkRPKI Not found119.146.34.0
- 119.146.36.0/22AS140318CHINATELECOM Guangdong province Heyuan 5G networkRPKI Not found119.146.36.0
- 119.146.40.0/23AS140318CHINATELECOM Guangdong province Heyuan 5G networkRPKI Not found119.146.40.0
- 119.146.42.0/23AS140319CHINATELECOM Guangdong province Qingyuan 5G networkRPKI Valid119.146.42.0
- 119.146.44.0/22AS140319CHINATELECOM Guangdong province Qingyuan 5G networkRPKI Valid119.146.44.0
- 119.146.48.0/22AS140319CHINATELECOM Guangdong province Qingyuan 5G networkRPKI Valid119.146.48.0
- 119.146.100.0/23AS136199CHINANET Guangdong province Yuedong MAN networkRPKI Valid119.146.100.0
- 119.146.172.0/22AS136199CHINANET Guangdong province Yuedong MAN networkRPKI Valid119.146.172.0
- 119.146.208.0/21AS140320CHINATELECOM Guangdong province Shanwei 5G networkRPKI Valid119.146.208.0
- 119.146.224.0/20AS140320CHINATELECOM Guangdong province Shanwei 5G networkRPKI Valid119.146.224.0
- 119.147.96.0/21AS134763CHINANET Guangdong province networkRPKI Valid119.147.96.0
- 119.147.104.0/21AS134763CHINANET Guangdong province networkRPKI Valid119.147.104.0
- 119.147.112.0/21AS134763CHINANET Guangdong province networkRPKI Valid119.147.112.0
- 119.147.120.0/21AS134763CHINANET Guangdong province networkRPKI Valid119.147.120.0
- 119.147.128.0/21AS134763CHINANET Guangdong province networkRPKI Valid119.147.128.0
- 119.147.144.0/20AS134763CHINANET Guangdong province networkRPKI Valid119.147.144.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.