BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
210.86.128.0/18
Announced exactly
- 210.86.128.0/18AS7470TRUE INTERNET Co.,Ltd.RPKI Valid210.86.128.0
- Registry
- APNIC · Thailand · Mar 10, 2003
- Delegated block
- 210.86.128.0 – 210.86.191.255
Covering routes
No less-specific route covers it.
More-specific routes
- 210.86.128.0/21AS7470TRUE INTERNET Co.,Ltd.RPKI Valid210.86.128.0
- 210.86.137.0/24AS24214CSLOXINFORPKI Valid210.86.137.0
- 210.86.139.0/24AS9287True Internet Data Center Company LimitedRPKI Valid210.86.139.0
- 210.86.140.0/22AS7470TRUE INTERNET Co.,Ltd.RPKI Valid210.86.140.0
- 210.86.140.0/24AS7470TRUE INTERNET Co.,Ltd.RPKI Valid210.86.140.0
- 210.86.141.0/24AS7470TRUE INTERNET Co.,Ltd.RPKI Valid210.86.141.0
- 210.86.145.0/24AS7470TRUE INTERNET Co.,Ltd.RPKI Valid210.86.145.0
- 210.86.152.0/24AS134095National ITMX Company LimitedRPKI Valid210.86.152.0
- 210.86.160.0/24AS7470TRUE INTERNET Co.,Ltd.RPKI Valid210.86.160.0
- 210.86.161.0/24AS7470TRUE INTERNET Co.,Ltd.RPKI Valid210.86.161.0
- 210.86.162.0/24AS7470TRUE INTERNET Co.,Ltd.RPKI Valid210.86.162.0
- 210.86.163.0/24AS7470TRUE INTERNET Co.,Ltd.RPKI Valid210.86.163.0
- 210.86.164.0/24AS7470TRUE INTERNET Co.,Ltd.RPKI Valid210.86.164.0
- 210.86.165.0/24AS7470TRUE INTERNET Co.,Ltd.RPKI Valid210.86.165.0
- 210.86.166.0/24AS7470TRUE INTERNET Co.,Ltd.RPKI Valid210.86.166.0
- 210.86.167.0/24AS7470TRUE INTERNET Co.,Ltd.RPKI Valid210.86.167.0
- 210.86.168.0/24AS7470TRUE INTERNET Co.,Ltd.RPKI Valid210.86.168.0
- 210.86.169.0/24AS7470TRUE INTERNET Co.,Ltd.RPKI Valid210.86.169.0
- 210.86.170.0/24AS7470TRUE INTERNET Co.,Ltd.RPKI Valid210.86.170.0
- 210.86.171.0/24AS7470TRUE INTERNET Co.,Ltd.RPKI Valid210.86.171.0
- 210.86.172.0/24AS7470TRUE INTERNET Co.,Ltd.RPKI Valid210.86.172.0
- 210.86.173.0/24AS7470TRUE INTERNET Co.,Ltd.RPKI Valid210.86.173.0
- 210.86.174.0/24AS7470TRUE INTERNET Co.,Ltd.RPKI Valid210.86.174.0
- 210.86.175.0/24AS7470TRUE INTERNET Co.,Ltd.RPKI Valid210.86.175.0
- 210.86.176.0/21AS9287True Internet Data Center Company LimitedRPKI Valid210.86.176.0
- 210.86.176.0/24AS9287True Internet Data Center Company LimitedRPKI Valid210.86.176.0
- 210.86.177.0/24AS9287True Internet Data Center Company LimitedRPKI Valid210.86.177.0
- 210.86.178.0/24AS9287True Internet Data Center Company LimitedRPKI Valid210.86.178.0
- 210.86.179.0/24AS9287True Internet Data Center Company LimitedRPKI Valid210.86.179.0
- 210.86.180.0/24AS9287True Internet Data Center Company LimitedRPKI Valid210.86.180.0
- 210.86.181.0/24AS9287True Internet Data Center Company LimitedRPKI Valid210.86.181.0
- 210.86.182.0/24AS9287True Internet Data Center Company LimitedRPKI Valid210.86.182.0
- 210.86.183.0/24AS9287True Internet Data Center Company LimitedRPKI Valid210.86.183.0
- 210.86.190.0/24AS7470TRUE INTERNET Co.,Ltd.RPKI Valid210.86.190.0
- 210.86.191.0/24AS17556TRUE INTERNET Co.,Ltd.RPKI Valid210.86.191.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.