BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
58.102.0.0/15
Announced exactly
- 58.102.0.0/15AS9644SK TelecomRPKI Not found58.102.0.0
- Registry
- APNIC · South Korea · May 17, 2005
- Delegated block
- 58.102.0.0 – 58.103.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 58.102.100.0/24AS45393SFSRPKI Not found58.102.100.0
- 58.102.101.0/24AS45393SFSRPKI Not found58.102.101.0
- 58.102.102.0/24AS45393SFSRPKI Not found58.102.102.0
- 58.102.103.0/24AS45393SFSRPKI Not found58.102.103.0
- 58.102.128.0/24AS23580DAILY SPORTSWORLDRPKI Not found58.102.128.0
- 58.102.129.0/24AS23580DAILY SPORTSWORLDRPKI Not found58.102.129.0
- 58.102.135.0/24AS9864Korea Securities DepositoryRPKI Not found58.102.135.0
- 58.102.199.0/24AS38120LG HelloVision Corp.RPKI Not found58.102.199.0
- 58.102.200.0/23AS38120LG HelloVision Corp.RPKI Not found58.102.200.0
- 58.103.2.0/23AS46009YABESKRPKI Not found58.103.2.0
- 58.103.2.0/24AS46009YABESKRPKI Not found58.103.2.0
- 58.103.3.0/24AS46009YABESKRPKI Not found58.103.3.0
- 58.103.4.0/22AS46009YABESKRPKI Not found58.103.4.0
- 58.103.4.0/23AS46009YABESKRPKI Not found58.103.4.0
- 58.103.4.0/24AS46009YABESKRPKI Not found58.103.4.0
- 58.103.5.0/24AS46009YABESKRPKI Not found58.103.5.0
- 58.103.6.0/24AS46009YABESKRPKI Not found58.103.6.0
- 58.103.7.0/24AS46009YABESKRPKI Not found58.103.7.0
- 58.103.8.0/22AS46009YABESKRPKI Not found58.103.8.0
- 58.103.8.0/23AS46009YABESKRPKI Not found58.103.8.0
- 58.103.8.0/24AS46009YABESKRPKI Not found58.103.8.0
- 58.103.9.0/24AS46009YABESKRPKI Not found58.103.9.0
- 58.103.10.0/24AS46009YABESKRPKI Not found58.103.10.0
- 58.103.11.0/24AS46009YABESKRPKI Not found58.103.11.0
- 58.103.160.0/21AS9708Pukyong National UniversityRPKI Not found58.103.160.0
- 58.103.168.0/23AS9708Pukyong National UniversityRPKI Not found58.103.168.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.