BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
14.208.0.0/12
Announced exactly
- 14.208.0.0/12AS4134No.31,Jin-rong StreetRPKI Valid14.208.0.0
- Registry
- APNIC · China · Sep 6, 2010
- Delegated block
- 14.208.0.0 – 14.223.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 14.215.44.0/22AS135089China TelecomRPKI Valid14.215.44.0
- 14.215.44.0/24AS58466CHINANET Guangdong province networkRPKI Valid14.215.44.0
- 14.215.45.0/24AS58466CHINANET Guangdong province networkRPKI Valid14.215.45.0
- 14.215.46.0/24AS58466CHINANET Guangdong province networkRPKI Valid14.215.46.0
- 14.215.47.0/24AS58466CHINANET Guangdong province networkRPKI Valid14.215.47.0
- 14.215.48.0/22AS135089China TelecomRPKI Valid14.215.48.0
- 14.215.48.0/24AS58466CHINANET Guangdong province networkRPKI Valid14.215.48.0
- 14.215.49.0/24AS58466CHINANET Guangdong province networkRPKI Valid14.215.49.0
- 14.215.50.0/24AS58466CHINANET Guangdong province networkRPKI Valid14.215.50.0
- 14.215.51.0/24AS58466CHINANET Guangdong province networkRPKI Valid14.215.51.0
- 14.215.162.0/23AS135089China TelecomRPKI Valid14.215.162.0
- 14.215.163.0/24AS135089China TelecomRPKI Valid14.215.163.0
- 14.215.164.0/24AS135089China TelecomRPKI Valid14.215.164.0
- 14.215.173.0/24AS135089China TelecomRPKI Valid14.215.173.0
- 14.215.174.0/24AS135089China TelecomRPKI Valid14.215.174.0
- 14.215.208.0/22AS140308CHINATELECOM Guangdong province Zhuhai 5G networkRPKI Valid14.215.208.0
- 14.215.224.0/22AS140319CHINATELECOM Guangdong province Qingyuan 5G networkRPKI Valid14.215.224.0
- 14.215.230.0/24AS140309CHINATELECOM Guangdong province Zhongshan 5G networkRPKI Invalid14.215.230.0
- 14.215.231.0/24AS140309CHINATELECOM Guangdong province Zhongshan 5G networkRPKI Invalid14.215.231.0
- 14.217.0.0/17AS136199CHINANET Guangdong province Yuedong MAN networkRPKI Valid14.217.0.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.