BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
210.216.0.0/16
Announced exactly
- 210.216.0.0/16AS3786LG DACOM CorporationRPKI Not found210.216.0.0
- Registry
- APNIC · South Korea · Mar 23, 1999
- Delegated block
- 210.216.0.0 – 210.216.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 210.216.16.0/24AS17834WOORICARDRPKI Not found210.216.16.0
- 210.216.21.0/24AS9319HCN CHUNGBUK CABLE TV SYSTEMSRPKI Not found210.216.21.0
- 210.216.22.0/24AS131871HYUNDAICARD CO.RPKI Not found210.216.22.0
- 210.216.56.0/24AS7562HCN DongjakRPKI Not found210.216.56.0
- 210.216.72.128/25AS23591LS ITCRPKI Not found210.216.72.128
- 210.216.80.0/22AS18164Mokpo UniversityRPKI Not found210.216.80.0
- 210.216.84.0/23AS18164Mokpo UniversityRPKI Not found210.216.84.0
- 210.216.95.0/24AS38686Tmoney co., ltdRPKI Not found210.216.95.0
- 210.216.99.0/24AS9319HCN CHUNGBUK CABLE TV SYSTEMSRPKI Not found210.216.99.0
- 210.216.119.0/24AS9319HCN CHUNGBUK CABLE TV SYSTEMSRPKI Not found210.216.119.0
- 210.216.129.0/24AS9319HCN CHUNGBUK CABLE TV SYSTEMSRPKI Not found210.216.129.0
- 210.216.147.0/24AS9319HCN CHUNGBUK CABLE TV SYSTEMSRPKI Not found210.216.147.0
- 210.216.151.0/24AS9319HCN CHUNGBUK CABLE TV SYSTEMSRPKI Not found210.216.151.0
- 210.216.152.0/23AS9319HCN CHUNGBUK CABLE TV SYSTEMSRPKI Not found210.216.152.0
- 210.216.157.0/24AS17852HANWHALIFERPKI Not found210.216.157.0
- 210.216.158.0/24AS17852HANWHALIFERPKI Not found210.216.158.0
- 210.216.159.0/24AS17852HANWHALIFERPKI Not found210.216.159.0
- 210.216.160.0/24AS17852HANWHALIFERPKI Not found210.216.160.0
- 210.216.161.0/24AS17852HANWHALIFERPKI Not found210.216.161.0
- 210.216.162.0/24AS17852HANWHALIFERPKI Not found210.216.162.0
- 210.216.170.0/24AS17852HANWHALIFERPKI Not found210.216.170.0
- 210.216.173.0/24AS138195MOACK.Co.LTDRPKI Not found210.216.173.0
- 210.216.226.0/24AS4668LG CNSRPKI Not found210.216.226.0
- 210.216.227.0/24AS4668LG CNSRPKI Not found210.216.227.0
- 210.216.228.0/24AS38661abcleRPKI Not found210.216.228.0
- 210.216.244.0/24AS9319HCN CHUNGBUK CABLE TV SYSTEMSRPKI Not found210.216.244.0
- 210.216.247.0/24AS9319HCN CHUNGBUK CABLE TV SYSTEMSRPKI Not found210.216.247.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.