BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
117.52.0.0/16
Announced exactly
- 117.52.0.0/16AS3786LG DACOM CorporationRPKI Not found117.52.0.0
- Registry
- APNIC · South Korea · Jan 10, 2011
- Delegated block
- 117.52.0.0 – 117.52.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 117.52.3.0/24AS131093viva republicaRPKI Not found117.52.3.0
- 117.52.5.0/24AS45974NHNCLOUDRPKI Not found117.52.5.0
- 117.52.6.0/24AS57976Blizzard Entertainment, IncRPKI Not found117.52.6.0
- 117.52.20.0/24AS45974NHNCLOUDRPKI Not found117.52.20.0
- 117.52.23.0/24AS131093viva republicaRPKI Not found117.52.23.0
- 117.52.26.0/23AS57976Blizzard Entertainment, IncRPKI Not found117.52.26.0
- 117.52.33.0/24AS57976Blizzard Entertainment, IncRPKI Not found117.52.33.0
- 117.52.34.0/23AS57976Blizzard Entertainment, IncRPKI Not found117.52.34.0
- 117.52.36.0/23AS57976Blizzard Entertainment, IncRPKI Not found117.52.36.0
- 117.52.114.0/24AS4791JoongAng IlboRPKI Not found117.52.114.0
- 117.52.115.0/24AS4791JoongAng IlboRPKI Not found117.52.115.0
- 117.52.116.0/24AS4791JoongAng IlboRPKI Not found117.52.116.0
- 117.52.118.0/24AS4791JoongAng IlboRPKI Not found117.52.118.0
- 117.52.122.0/24AS45974NHNCLOUDRPKI Not found117.52.122.0
- 117.52.123.0/24AS45974NHNCLOUDRPKI Not found117.52.123.0
- 117.52.126.0/24AS131093viva republicaRPKI Not found117.52.126.0
- 117.52.128.0/20AS23576NAVER Cloud Corp.RPKI Not found117.52.128.0
- 117.52.128.0/21AS23576NAVER Cloud Corp.RPKI Not found117.52.128.0
- 117.52.136.0/21AS23576NAVER Cloud Corp.RPKI Not found117.52.136.0
- 117.52.154.0/24AS45974NHNCLOUDRPKI Not found117.52.154.0
- 117.52.155.0/24AS45974NHNCLOUDRPKI Not found117.52.155.0
- 117.52.165.0/24AS10155KOSMERPKI Not found117.52.165.0
- 117.52.222.0/24AS152211Toss Securities Co., Ltd.RPKI Not found117.52.222.0
- 117.52.255.0/24AS3786LG DACOM CorporationRPKI Not found117.52.255.0
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 158.36.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.