BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
118.213.0.0/16
Announced exactly
- 118.213.0.0/16AS4134No.31,Jin-rong StreetRPKI Not found118.213.0.0
- Registry
- APNIC · China · Oct 29, 2007
- Delegated block
- 118.213.0.0 – 118.213.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 118.213.0.0/17AS140061Qinghai TelecomRPKI Valid118.213.0.0
- 118.213.0.0/22AS140061Qinghai TelecomRPKI Valid118.213.0.0
- 118.213.4.0/22AS140061Qinghai TelecomRPKI Valid118.213.4.0
- 118.213.8.0/22AS140061Qinghai TelecomRPKI Valid118.213.8.0
- 118.213.12.0/22AS140061Qinghai TelecomRPKI Valid118.213.12.0
- 118.213.16.0/22AS140061Qinghai TelecomRPKI Valid118.213.16.0
- 118.213.20.0/24AS140061Qinghai TelecomRPKI Invalid118.213.20.0
- 118.213.21.0/24AS140061Qinghai TelecomRPKI Invalid118.213.21.0
- 118.213.22.0/24AS140061Qinghai TelecomRPKI Invalid118.213.22.0
- 118.213.23.0/24AS140061Qinghai TelecomRPKI Invalid118.213.23.0
- 118.213.24.0/22AS140061Qinghai TelecomRPKI Valid118.213.24.0
- 118.213.35.0/24AS140061Qinghai TelecomRPKI Valid118.213.35.0
- 118.213.36.0/24AS140061Qinghai TelecomRPKI Valid118.213.36.0
- 118.213.37.0/24AS140061Qinghai TelecomRPKI Valid118.213.37.0
- 118.213.38.0/24AS140061Qinghai TelecomRPKI Valid118.213.38.0
- 118.213.39.0/24AS140061Qinghai TelecomRPKI Valid118.213.39.0
- 118.213.44.0/22AS140061Qinghai TelecomRPKI Valid118.213.44.0
- 118.213.48.0/24AS140061Qinghai TelecomRPKI Valid118.213.48.0
- 118.213.49.0/24AS140061Qinghai TelecomRPKI Valid118.213.49.0
- 118.213.50.0/23AS140061Qinghai TelecomRPKI Valid118.213.50.0
- 118.213.52.0/23AS140061Qinghai TelecomRPKI Valid118.213.52.0
- 118.213.56.0/23AS140061Qinghai TelecomRPKI Valid118.213.56.0
- 118.213.58.0/24AS140061Qinghai TelecomRPKI Valid118.213.58.0
- 118.213.59.0/24AS140061Qinghai TelecomRPKI Valid118.213.59.0
- 118.213.60.0/22AS140061Qinghai TelecomRPKI Valid118.213.60.0
- 118.213.76.0/24AS140061Qinghai TelecomRPKI Valid118.213.76.0
- 118.213.82.0/24AS140061Qinghai TelecomRPKI Valid118.213.82.0
- 118.213.88.0/24AS59223CHINANET Qinghai province IDC networkRPKI Valid118.213.88.0
- 118.213.92.0/24AS59223CHINANET Qinghai province IDC networkRPKI Valid118.213.92.0
- 118.213.93.0/24AS59223CHINANET Qinghai province IDC networkRPKI Invalid118.213.93.0
- 118.213.96.0/23AS140061Qinghai TelecomRPKI Valid118.213.96.0
- 118.213.98.0/23AS140061Qinghai TelecomRPKI Valid118.213.98.0
- 118.213.100.0/22AS140061Qinghai TelecomRPKI Valid118.213.100.0
- 118.213.104.0/23AS140061Qinghai TelecomRPKI Valid118.213.104.0
- 118.213.112.0/22AS140061Qinghai TelecomRPKI Valid118.213.112.0
- 118.213.116.0/24AS140061Qinghai TelecomRPKI Valid118.213.116.0
- 118.213.117.0/24AS140061Qinghai TelecomRPKI Valid118.213.117.0
- 118.213.119.0/24AS140061Qinghai TelecomRPKI Valid118.213.119.0
- 118.213.120.0/22AS140061Qinghai TelecomRPKI Valid118.213.120.0
- 118.213.124.0/22AS140061Qinghai TelecomRPKI Valid118.213.124.0
- 118.213.128.0/17AS140061Qinghai TelecomRPKI Valid118.213.128.0
- 118.213.128.0/24AS140061Qinghai TelecomRPKI Invalid118.213.128.0
- 118.213.129.0/24AS140061Qinghai TelecomRPKI Invalid118.213.129.0
- 118.213.130.0/24AS140061Qinghai TelecomRPKI Invalid118.213.130.0
- 118.213.131.0/24AS140061Qinghai TelecomRPKI Invalid118.213.131.0
- 118.213.132.0/24AS140061Qinghai TelecomRPKI Valid118.213.132.0
- 118.213.134.0/24AS140061Qinghai TelecomRPKI Valid118.213.134.0
- 118.213.135.0/24AS140061Qinghai TelecomRPKI Valid118.213.135.0
- 118.213.136.0/22AS140061Qinghai TelecomRPKI Valid118.213.136.0
- 118.213.136.0/24AS140061Qinghai TelecomRPKI Valid118.213.136.0
- 118.213.141.0/24AS59223CHINANET Qinghai province IDC networkRPKI Valid118.213.141.0
- 118.213.142.0/24AS140061Qinghai TelecomRPKI Valid118.213.142.0
- 118.213.143.0/24AS140061Qinghai TelecomRPKI Valid118.213.143.0
- 118.213.144.0/22AS140061Qinghai TelecomRPKI Valid118.213.144.0
- 118.213.148.0/24AS140061Qinghai TelecomRPKI Valid118.213.148.0
- 118.213.149.0/24AS140061Qinghai TelecomRPKI Valid118.213.149.0
- 118.213.150.0/24AS140061Qinghai TelecomRPKI Valid118.213.150.0
- 118.213.151.0/24AS140061Qinghai TelecomRPKI Valid118.213.151.0
- 118.213.153.0/24AS140061Qinghai TelecomRPKI Valid118.213.153.0
- 118.213.154.0/24AS140061Qinghai TelecomRPKI Valid118.213.154.0
- 118.213.157.0/24AS140061Qinghai TelecomRPKI Valid118.213.157.0
- 118.213.158.0/24AS140061Qinghai TelecomRPKI Valid118.213.158.0
- 118.213.160.0/24AS140061Qinghai TelecomRPKI Valid118.213.160.0
- 118.213.161.0/24AS140061Qinghai TelecomRPKI Valid118.213.161.0
- 118.213.162.0/24AS140061Qinghai TelecomRPKI Valid118.213.162.0
- 118.213.163.0/24AS140061Qinghai TelecomRPKI Valid118.213.163.0
- 118.213.164.0/24AS140061Qinghai TelecomRPKI Valid118.213.164.0
- 118.213.165.0/24AS140061Qinghai TelecomRPKI Valid118.213.165.0
- 118.213.166.0/24AS140061Qinghai TelecomRPKI Valid118.213.166.0
- 118.213.172.0/22AS140061Qinghai TelecomRPKI Valid118.213.172.0
- 118.213.176.0/24AS140061Qinghai TelecomRPKI Valid118.213.176.0
- 118.213.177.0/24AS140061Qinghai TelecomRPKI Valid118.213.177.0
- 118.213.178.0/24AS140061Qinghai TelecomRPKI Valid118.213.178.0
- 118.213.179.0/24AS140061Qinghai TelecomRPKI Valid118.213.179.0
- 118.213.180.0/24AS140061Qinghai TelecomRPKI Valid118.213.180.0
- 118.213.182.0/24AS140061Qinghai TelecomRPKI Valid118.213.182.0
- 118.213.183.0/24AS140061Qinghai TelecomRPKI Valid118.213.183.0
- 118.213.184.0/22AS140061Qinghai TelecomRPKI Valid118.213.184.0
- 118.213.188.0/23AS140061Qinghai TelecomRPKI Valid118.213.188.0
- 118.213.190.0/24AS140061Qinghai TelecomRPKI Valid118.213.190.0
- 118.213.191.0/24AS140061Qinghai TelecomRPKI Valid118.213.191.0
- 118.213.192.0/22AS140061Qinghai TelecomRPKI Valid118.213.192.0
- 118.213.200.0/24AS140061Qinghai TelecomRPKI Valid118.213.200.0
- 118.213.201.0/24AS140061Qinghai TelecomRPKI Valid118.213.201.0
- 118.213.202.0/24AS140061Qinghai TelecomRPKI Valid118.213.202.0
- 118.213.203.0/24AS140061Qinghai TelecomRPKI Valid118.213.203.0
- 118.213.204.0/24AS140061Qinghai TelecomRPKI Valid118.213.204.0
- 118.213.205.0/24AS140061Qinghai TelecomRPKI Valid118.213.205.0
- 118.213.207.0/24AS140061Qinghai TelecomRPKI Valid118.213.207.0
- 118.213.212.0/22AS140061Qinghai TelecomRPKI Valid118.213.212.0
- 118.213.220.0/24AS59223CHINANET Qinghai province IDC networkRPKI Valid118.213.220.0
- 118.213.222.0/24AS140061Qinghai TelecomRPKI Valid118.213.222.0
- 118.213.223.0/24AS140061Qinghai TelecomRPKI Valid118.213.223.0
- 118.213.224.0/24AS140061Qinghai TelecomRPKI Valid118.213.224.0
- 118.213.225.0/24AS140061Qinghai TelecomRPKI Valid118.213.225.0
- 118.213.227.0/24AS140061Qinghai TelecomRPKI Valid118.213.227.0
- 118.213.228.0/22AS140061Qinghai TelecomRPKI Valid118.213.228.0
- 118.213.236.0/24AS140061Qinghai TelecomRPKI Valid118.213.236.0
- 118.213.238.0/24AS140061Qinghai TelecomRPKI Valid118.213.238.0
- 118.213.239.0/24AS140061Qinghai TelecomRPKI Valid118.213.239.0
Showing the first 100.
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 144.122.0.0/16 (Middle East Technical University, AS1967). 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.