BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
61.100.0.0/17
Announced exactly
- 61.100.0.0/17AS9848SEJONG NETWORKSRPKI Not found61.100.0.0
- Registry
- APNIC · South Korea · Mar 21, 2001
- Delegated block
- 61.100.0.0 – 61.100.127.255
Covering routes
No less-specific route covers it.
More-specific routes
- 61.100.0.0/20AS9952Hostway IDCRPKI Not found61.100.0.0
- 61.100.0.0/24AS9952Hostway IDCRPKI Not found61.100.0.0
- 61.100.1.0/24AS9952Hostway IDCRPKI Not found61.100.1.0
- 61.100.2.0/24AS9952Hostway IDCRPKI Not found61.100.2.0
- 61.100.3.0/24AS9952Hostway IDCRPKI Not found61.100.3.0
- 61.100.4.0/24AS9952Hostway IDCRPKI Not found61.100.4.0
- 61.100.5.0/24AS9952Hostway IDCRPKI Not found61.100.5.0
- 61.100.6.0/24AS9952Hostway IDCRPKI Not found61.100.6.0
- 61.100.7.0/24AS9952Hostway IDCRPKI Not found61.100.7.0
- 61.100.8.0/24AS9952Hostway IDCRPKI Not found61.100.8.0
- 61.100.9.0/24AS9952Hostway IDCRPKI Not found61.100.9.0
- 61.100.10.0/24AS9952Hostway IDCRPKI Not found61.100.10.0
- 61.100.11.0/24AS9952Hostway IDCRPKI Not found61.100.11.0
- 61.100.12.0/24AS9952Hostway IDCRPKI Not found61.100.12.0
- 61.100.13.0/24AS9952Hostway IDCRPKI Not found61.100.13.0
- 61.100.14.0/24AS9952Hostway IDCRPKI Not found61.100.14.0
- 61.100.15.0/24AS9952Hostway IDCRPKI Not found61.100.15.0
- 61.100.25.0/24AS38676flexnetworksRPKI Not found61.100.25.0
- 61.100.26.0/24AS38676flexnetworksRPKI Not found61.100.26.0
- 61.100.27.0/24AS38676flexnetworksRPKI Not found61.100.27.0
- 61.100.28.0/24AS38676flexnetworksRPKI Not found61.100.28.0
- 61.100.29.0/24AS38676flexnetworksRPKI Not found61.100.29.0
- 61.100.38.0/24AS214432Zhilian Technology CO., LTD.RPKI Not found61.100.38.0
- 61.100.40.0/21AS131866Digital Edge KoreaRPKI Not found61.100.40.0
- 61.100.40.0/24AS131866Digital Edge KoreaRPKI Not found61.100.40.0
- 61.100.41.0/24AS131866Digital Edge KoreaRPKI Not found61.100.41.0
- 61.100.42.0/24AS131866Digital Edge KoreaRPKI Not found61.100.42.0
- 61.100.43.0/24AS131866Digital Edge KoreaRPKI Not found61.100.43.0
- 61.100.44.0/24AS131866Digital Edge KoreaRPKI Not found61.100.44.0
- 61.100.45.0/24AS131866Digital Edge KoreaRPKI Not found61.100.45.0
- 61.100.46.0/24AS131866Digital Edge KoreaRPKI Not found61.100.46.0
- 61.100.47.0/24AS131866Digital Edge KoreaRPKI Not found61.100.47.0
- 61.100.48.0/21AS131866Digital Edge KoreaRPKI Not found61.100.48.0
- 61.100.48.0/24AS131866Digital Edge KoreaRPKI Not found61.100.48.0
- 61.100.49.0/24AS131866Digital Edge KoreaRPKI Not found61.100.49.0
- 61.100.50.0/24AS131866Digital Edge KoreaRPKI Not found61.100.50.0
- 61.100.51.0/24AS131866Digital Edge KoreaRPKI Not found61.100.51.0
- 61.100.52.0/24AS131866Digital Edge KoreaRPKI Not found61.100.52.0
- 61.100.53.0/24AS131866Digital Edge KoreaRPKI Not found61.100.53.0
- 61.100.54.0/24AS131866Digital Edge KoreaRPKI Not found61.100.54.0
- 61.100.71.0/24AS9947kt cloud Co., LtdRPKI Not found61.100.71.0
- 61.100.72.0/24AS9947kt cloud Co., LtdRPKI Not found61.100.72.0
- 61.100.88.0/24AS152294KIS Information Communication,IncRPKI Not found61.100.88.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.