BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
218.38.0.0/15
Announced exactly
- 218.38.0.0/15AS9318SK Broadband Co LtdRPKI Not found218.38.0.0
- Registry
- APNIC · South Korea · Jul 22, 2002
- Delegated block
- 218.38.0.0 – 218.39.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 218.38.32.0/24AS131848YUHANRPKI Not found218.38.32.0
- 218.38.73.0/24AS10069Seoul MetroRPKI Not found218.38.73.0
- 218.38.82.0/24AS38388Korea Copyright Protection AgencyRPKI Not found218.38.82.0
- 218.38.104.0/23AS9318SK Broadband Co LtdRPKI Not found218.38.104.0
- 218.38.130.0/24AS9574Teachers PensionRPKI Not found218.38.130.0
- 218.38.144.0/24AS4766Korea TelecomRPKI Not found218.38.144.0
- 218.38.144.0/25AS4766Korea TelecomRPKI Not found218.38.144.0
- 218.38.144.128/25AS4766Korea TelecomRPKI Not found218.38.144.128
- 218.38.234.0/24AS38404Gyeonggi Provincial Bucheon Office of EducationRPKI Not found218.38.234.0
- 218.38.235.0/24AS38404Gyeonggi Provincial Bucheon Office of EducationRPKI Not found218.38.235.0
- 218.38.240.0/22AS17845Gyeonggi TechnoparkRPKI Not found218.38.240.0
- 218.38.240.0/24AS17845Gyeonggi TechnoparkRPKI Not found218.38.240.0
- 218.38.241.0/24AS17845Gyeonggi TechnoparkRPKI Not found218.38.241.0
- 218.38.242.0/24AS17845Gyeonggi TechnoparkRPKI Not found218.38.242.0
- 218.38.244.0/24AS38391Gyeonggi provincial gimpo office of educationRPKI Not found218.38.244.0
- 218.38.245.0/24AS38391Gyeonggi provincial gimpo office of educationRPKI Not found218.38.245.0
- 218.39.140.0/23AS9318SK Broadband Co LtdRPKI Not found218.39.140.0
- 218.39.141.0/24AS54201We Link Networks LLCRPKI Not found218.39.141.0
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 2.48.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.