BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
219.128.0.0/13
Announced exactly
- 219.128.0.0/13AS4134No.31,Jin-rong StreetRPKI Valid219.128.0.0
- Registry
- APNIC · China · Mar 21, 2002
- Delegated block
- 219.128.0.0 – 219.143.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 219.128.80.0/24AS136198CHINANET Guangdong province Yuexi MAN networkRPKI Valid219.128.80.0
- 219.128.92.0/22AS140319CHINATELECOM Guangdong province Qingyuan 5G networkRPKI Valid219.128.92.0
- 219.128.97.0/24AS140311CHINATELECOM Guangdong province Jiangmen 5G networkRPKI Valid219.128.97.0
- 219.128.100.0/23AS140319CHINATELECOM Guangdong province Qingyuan 5G networkRPKI Valid219.128.100.0
- 219.128.143.0/24AS140308CHINATELECOM Guangdong province Zhuhai 5G networkRPKI Valid219.128.143.0
- 219.128.168.0/22AS140308CHINATELECOM Guangdong province Zhuhai 5G networkRPKI Valid219.128.168.0
- 219.128.168.0/23AS140308CHINATELECOM Guangdong province Zhuhai 5G networkRPKI Valid219.128.168.0
- 219.128.172.0/23AS140308CHINATELECOM Guangdong province Zhuhai 5G networkRPKI Valid219.128.172.0
- 219.128.176.0/22AS135089China TelecomRPKI Valid219.128.176.0
- 219.128.180.0/24AS135089China TelecomRPKI Valid219.128.180.0
- 219.128.188.0/24AS140308CHINATELECOM Guangdong province Zhuhai 5G networkRPKI Valid219.128.188.0
- 219.128.193.0/24AS135089China TelecomRPKI Valid219.128.193.0
- 219.128.195.0/24AS135089China TelecomRPKI Valid219.128.195.0
- 219.128.204.0/22AS140308CHINATELECOM Guangdong province Zhuhai 5G networkRPKI Valid219.128.204.0
- 219.128.210.0/24AS134763CHINANET Guangdong province networkRPKI Valid219.128.210.0
- 219.128.212.0/24AS135089China TelecomRPKI Valid219.128.212.0
- 219.128.213.0/24AS134763CHINANET Guangdong province networkRPKI Valid219.128.213.0
- 219.129.80.0/21AS140318CHINATELECOM Guangdong province Heyuan 5G networkRPKI Invalid219.129.80.0
- 219.129.88.0/22AS140318CHINATELECOM Guangdong province Heyuan 5G networkRPKI Invalid219.129.88.0
- 219.129.92.0/22AS140318CHINATELECOM Guangdong province Heyuan 5G networkRPKI Invalid219.129.92.0
- 219.129.96.0/20AS140318CHINATELECOM Guangdong province Heyuan 5G networkRPKI Invalid219.129.96.0
- 219.129.112.0/20AS140318CHINATELECOM Guangdong province Heyuan 5G networkRPKI Invalid219.129.112.0
- 219.129.128.0/19AS140319CHINATELECOM Guangdong province Qingyuan 5G networkRPKI Valid219.129.128.0
- 219.129.152.0/21AS140319CHINATELECOM Guangdong province Qingyuan 5G networkRPKI Valid219.129.152.0
- 219.129.160.0/20AS140320CHINATELECOM Guangdong province Shanwei 5G networkRPKI Valid219.129.160.0
- 219.129.240.0/20AS140318CHINATELECOM Guangdong province Heyuan 5G networkRPKI Invalid219.129.240.0
- 219.130.128.0/19AS136199CHINANET Guangdong province Yuedong MAN networkRPKI Valid219.130.128.0
- 219.130.135.0/24AS136199CHINANET Guangdong province Yuedong MAN networkRPKI Invalid219.130.135.0
- 219.130.136.0/22AS136199CHINANET Guangdong province Yuedong MAN networkRPKI Invalid219.130.136.0
- 219.130.140.0/24AS136199CHINANET Guangdong province Yuedong MAN networkRPKI Invalid219.130.140.0
- 219.130.160.0/20AS136199CHINANET Guangdong province Yuedong MAN networkRPKI Valid219.130.160.0
- 219.130.174.0/24AS136199CHINANET Guangdong province Yuedong MAN networkRPKI Invalid219.130.174.0
- 219.130.175.0/24AS136199CHINANET Guangdong province Yuedong MAN networkRPKI Invalid219.130.175.0
- 219.131.112.0/22AS140308CHINATELECOM Guangdong province Zhuhai 5G networkRPKI Valid219.131.112.0
- 219.131.120.0/22AS140308CHINATELECOM Guangdong province Zhuhai 5G networkRPKI Valid219.131.120.0
- 219.131.156.0/22AS140311CHINATELECOM Guangdong province Jiangmen 5G networkRPKI Valid219.131.156.0
- 219.132.112.0/20AS140309CHINATELECOM Guangdong province Zhongshan 5G networkRPKI Valid219.132.112.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.