BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
210.99.0.0/16
Announced exactly
- 210.99.0.0/16AS4766Korea TelecomRPKI Not found210.99.0.0
- Registry
- APNIC · South Korea · Mar 10, 1998
- Delegated block
- 210.99.0.0 – 210.99.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 210.99.7.0/24AS10185Hana Bank Co.RPKI Not found210.99.7.0
- 210.99.10.0/24AS45400Korea TelecomRPKI Not found210.99.10.0
- 210.99.16.0/22AS4766Korea TelecomRPKI Not found210.99.16.0
- 210.99.24.0/24AS17841NATIONAL INFORMATION RESOURCES SERVICERPKI Not found210.99.24.0
- 210.99.25.0/24AS17841NATIONAL INFORMATION RESOURCES SERVICERPKI Not found210.99.25.0
- 210.99.43.0/24AS4766Korea TelecomRPKI Not found210.99.43.0
- 210.99.44.0/24AS4766Korea TelecomRPKI Not found210.99.44.0
- 210.99.48.0/24AS17841NATIONAL INFORMATION RESOURCES SERVICERPKI Not found210.99.48.0
- 210.99.49.0/24AS17841NATIONAL INFORMATION RESOURCES SERVICERPKI Not found210.99.49.0
- 210.99.50.0/24AS17841NATIONAL INFORMATION RESOURCES SERVICERPKI Not found210.99.50.0
- 210.99.51.0/24AS17841NATIONAL INFORMATION RESOURCES SERVICERPKI Not found210.99.51.0
- 210.99.52.0/24AS17841NATIONAL INFORMATION RESOURCES SERVICERPKI Not found210.99.52.0
- 210.99.53.0/24AS17841NATIONAL INFORMATION RESOURCES SERVICERPKI Not found210.99.53.0
- 210.99.54.0/24AS17841NATIONAL INFORMATION RESOURCES SERVICERPKI Not found210.99.54.0
- 210.99.55.0/24AS17841NATIONAL INFORMATION RESOURCES SERVICERPKI Not found210.99.55.0
- 210.99.62.0/24AS17841NATIONAL INFORMATION RESOURCES SERVICERPKI Not found210.99.62.0
- 210.99.75.0/24AS4766Korea TelecomRPKI Not found210.99.75.0
- 210.99.81.0/24AS17600KOREA RESOURCES RECOVERY AND REUTILIZATION CORPORATIONRPKI Not found210.99.81.0
- 210.99.84.0/25AS45400Korea TelecomRPKI Not found210.99.84.0
- 210.99.86.0/24AS4766Korea TelecomRPKI Not found210.99.86.0
- 210.99.87.0/24AS4766Korea TelecomRPKI Not found210.99.87.0
- 210.99.89.0/25AS4766Korea TelecomRPKI Not found210.99.89.0
- 210.99.89.128/25AS4766Korea TelecomRPKI Not found210.99.89.128
- 210.99.98.0/24AS4766Korea TelecomRPKI Not found210.99.98.0
- 210.99.98.0/25AS4766Korea TelecomRPKI Not found210.99.98.0
- 210.99.98.128/25AS4766Korea TelecomRPKI Not found210.99.98.128
- 210.99.154.0/25AS45400Korea TelecomRPKI Not found210.99.154.0
- 210.99.158.0/24AS45400Korea TelecomRPKI Not found210.99.158.0
- 210.99.159.0/24AS45400Korea TelecomRPKI Not found210.99.159.0
- 210.99.168.0/24AS45400Korea TelecomRPKI Not found210.99.168.0
- 210.99.169.0/24AS4766Korea TelecomRPKI Not found210.99.169.0
- 210.99.170.0/24AS9647Seoul Metropolitan GovernmentRPKI Not found210.99.170.0
- 210.99.172.0/24AS4766Korea TelecomRPKI Not found210.99.172.0
- 210.99.177.0/24AS4766Korea TelecomRPKI Not found210.99.177.0
- 210.99.187.0/24AS9647Seoul Metropolitan GovernmentRPKI Not found210.99.187.0
- 210.99.189.0/24AS9647Seoul Metropolitan GovernmentRPKI Not found210.99.189.0
- 210.99.209.0/24AS4766Korea TelecomRPKI Not found210.99.209.0
- 210.99.214.0/24AS4766Korea TelecomRPKI Not found210.99.214.0
- 210.99.222.0/24AS4766Korea TelecomRPKI Not found210.99.222.0
- 210.99.229.0/24AS38707TosspaymentsRPKI Not found210.99.229.0
- 210.99.240.0/24AS131093viva republicaRPKI Not found210.99.240.0
- 210.99.248.0/24AS17841NATIONAL INFORMATION RESOURCES SERVICERPKI Not found210.99.248.0
- 210.99.252.0/24AS38707TosspaymentsRPKI Not found210.99.252.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.