BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
210.97.128.0/19
Announced exactly
- 210.97.128.0/19AS4766Korea TelecomRPKI Not found210.97.128.0
- Registry
- APNIC · South Korea · May 21, 1998
- Delegated block
- 210.97.128.0 – 210.97.159.255
Covering routes
No less-specific route covers it.
More-specific routes
- 210.97.132.0/24AS9318SK Broadband Co LtdRPKI Not found210.97.132.0
- 210.97.136.0/24AS9271Wonkwang UniversityRPKI Not found210.97.136.0
- 210.97.137.0/24AS9271Wonkwang UniversityRPKI Not found210.97.137.0
- 210.97.138.0/24AS9271Wonkwang UniversityRPKI Not found210.97.138.0
- 210.97.139.0/24AS9271Wonkwang UniversityRPKI Not found210.97.139.0
- 210.97.140.0/24AS4766Korea TelecomRPKI Not found210.97.140.0
- 210.97.141.0/24AS3786LG DACOM CorporationRPKI Not found210.97.141.0
- 210.97.142.0/24AS4766Korea TelecomRPKI Not found210.97.142.0
- 210.97.143.0/24AS4766Korea TelecomRPKI Not found210.97.143.0
- 210.97.144.0/22AS3786LG DACOM CorporationRPKI Not found210.97.144.0
- 210.97.144.0/24AS4766Korea TelecomRPKI Not found210.97.144.0
- 210.97.145.0/24AS4766Korea TelecomRPKI Not found210.97.145.0
- 210.97.146.0/24AS4766Korea TelecomRPKI Not found210.97.146.0
- 210.97.147.0/24AS4766Korea TelecomRPKI Not found210.97.147.0
- 210.97.148.0/23AS3786LG DACOM CorporationRPKI Not found210.97.148.0
- 210.97.148.0/24AS4766Korea TelecomRPKI Not found210.97.148.0
- 210.97.149.0/24AS4766Korea TelecomRPKI Not found210.97.149.0
- 210.97.150.0/24AS4766Korea TelecomRPKI Not found210.97.150.0
- 210.97.151.0/24AS4766Korea TelecomRPKI Not found210.97.151.0
- 210.97.155.0/24AS18343Daegu Technical CollegeRPKI Not found210.97.155.0
- 210.97.156.0/22AS18343Daegu Technical CollegeRPKI Not found210.97.156.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.