BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
61.84.0.0/15
Announced exactly
- 61.84.0.0/15AS4766Korea TelecomRPKI Not found61.84.0.0
- Registry
- APNIC · South Korea · May 11, 2001
- Delegated block
- 61.84.0.0 – 61.85.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 61.84.13.0/24AS10184Korean Federation of Community Credit CooperativesRPKI Not found61.84.13.0
- 61.84.95.0/24AS10185Hana Bank Co.RPKI Not found61.84.95.0
- 61.84.112.128/25AS23569SEOJEONG COLLEGERPKI Not found61.84.112.128
- 61.84.121.0/24AS4766Korea TelecomRPKI Not found61.84.121.0
- 61.84.218.0/23AS18164Mokpo UniversityRPKI Not found61.84.218.0
- 61.84.218.0/24AS18164Mokpo UniversityRPKI Not found61.84.218.0
- 61.84.220.0/23AS18164Mokpo UniversityRPKI Not found61.84.220.0
- 61.85.24.0/23AS4766Korea TelecomRPKI Not found61.85.24.0
- 61.85.26.0/24AS4766Korea TelecomRPKI Not found61.85.26.0
- 61.85.27.0/25AS4766Korea TelecomRPKI Not found61.85.27.0
- 61.85.70.0/24AS9960IM BankRPKI Not found61.85.70.0
- 61.85.84.0/24AS10058NACUFOKRPKI Not found61.85.84.0
- 61.85.91.0/24AS10058NACUFOKRPKI Not found61.85.91.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.