BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
119.128.0.0/12
Announced exactly
- 119.128.0.0/12AS4134No.31,Jin-rong StreetRPKI Not found119.128.0.0
- Registry
- APNIC · China · Feb 7, 2008
- Delegated block
- 119.128.0.0 – 119.143.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 119.133.0.0/16AS136199CHINANET Guangdong province Yuedong MAN networkRPKI Valid119.133.0.0
- 119.133.234.0/23AS136199CHINANET Guangdong province Yuedong MAN networkRPKI Invalid119.133.234.0
- 119.134.128.0/20AS140320CHINATELECOM Guangdong province Shanwei 5G networkRPKI Valid119.134.128.0
- 119.134.144.0/20AS140320CHINATELECOM Guangdong province Shanwei 5G networkRPKI Valid119.134.144.0
- 119.134.160.0/20AS140320CHINATELECOM Guangdong province Shanwei 5G networkRPKI Valid119.134.160.0
- 119.134.176.0/20AS140320CHINATELECOM Guangdong province Shanwei 5G networkRPKI Valid119.134.176.0
- 119.134.192.0/20AS140320CHINATELECOM Guangdong province Shanwei 5G networkRPKI Valid119.134.192.0
- 119.134.208.0/22AS140320CHINATELECOM Guangdong province Shanwei 5G networkRPKI Valid119.134.208.0
- 119.134.212.0/22AS140320CHINATELECOM Guangdong province Shanwei 5G networkRPKI Valid119.134.212.0
- 119.134.216.0/21AS140320CHINATELECOM Guangdong province Shanwei 5G networkRPKI Valid119.134.216.0
- 119.134.224.0/20AS140320CHINATELECOM Guangdong province Shanwei 5G networkRPKI Valid119.134.224.0
- 119.134.240.0/22AS140320CHINATELECOM Guangdong province Shanwei 5G networkRPKI Valid119.134.240.0
- 119.135.164.0/22AS135089China TelecomRPKI Valid119.135.164.0
- 119.135.168.0/23AS135089China TelecomRPKI Valid119.135.168.0
- 119.138.0.0/21AS140318CHINATELECOM Guangdong province Heyuan 5G networkRPKI Not found119.138.0.0
- 119.138.8.0/21AS140318CHINATELECOM Guangdong province Heyuan 5G networkRPKI Not found119.138.8.0
- 119.138.32.0/19AS140318CHINATELECOM Guangdong province Heyuan 5G networkRPKI Not found119.138.32.0
- 119.138.48.0/21AS140318CHINATELECOM Guangdong province Heyuan 5G networkRPKI Not found119.138.48.0
- 119.138.64.0/20AS140318CHINATELECOM Guangdong province Heyuan 5G networkRPKI Not found119.138.64.0
- 119.138.84.0/22AS140318CHINATELECOM Guangdong province Heyuan 5G networkRPKI Not found119.138.84.0
- 119.138.104.0/21AS140318CHINATELECOM Guangdong province Heyuan 5G networkRPKI Not found119.138.104.0
- 119.138.136.0/21AS140318CHINATELECOM Guangdong province Heyuan 5G networkRPKI Not found119.138.136.0
- 119.138.144.0/20AS140318CHINATELECOM Guangdong province Heyuan 5G networkRPKI Not found119.138.144.0
- 119.140.32.0/19AS140309CHINATELECOM Guangdong province Zhongshan 5G networkRPKI Not found119.140.32.0
- 119.140.144.0/20AS136199CHINANET Guangdong province Yuedong MAN networkRPKI Valid119.140.144.0
- 119.140.160.0/21AS140319CHINATELECOM Guangdong province Qingyuan 5G networkRPKI Valid119.140.160.0
- 119.140.168.0/21AS140319CHINATELECOM Guangdong province Qingyuan 5G networkRPKI Valid119.140.168.0
- 119.140.176.0/20AS140309CHINATELECOM Guangdong province Zhongshan 5G networkRPKI Not found119.140.176.0
- 119.140.244.0/22AS140318CHINATELECOM Guangdong province Heyuan 5G networkRPKI Not found119.140.244.0
- 119.140.248.0/21AS140318CHINATELECOM Guangdong province Heyuan 5G networkRPKI Not found119.140.248.0
- 119.142.176.0/20AS140311CHINATELECOM Guangdong province Jiangmen 5G networkRPKI Valid119.142.176.0
- 119.142.192.0/18AS140311CHINATELECOM Guangdong province Jiangmen 5G networkRPKI Valid119.142.192.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.