BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
58.180.0.0/16
Announced exactly
- 58.180.0.0/16AS4670ShinbiroRPKI Not found58.180.0.0
- Registry
- APNIC · South Korea · Jun 15, 2005
- Delegated block
- 58.180.0.0 – 58.180.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 58.180.0.0/17AS4670ShinbiroRPKI Not found58.180.0.0
- 58.180.0.0/24AS4670ShinbiroRPKI Not found58.180.0.0
- 58.180.2.0/24AS4670ShinbiroRPKI Not found58.180.2.0
- 58.180.3.0/24AS4670ShinbiroRPKI Not found58.180.3.0
- 58.180.4.0/24AS4670ShinbiroRPKI Not found58.180.4.0
- 58.180.5.0/24AS4670ShinbiroRPKI Not found58.180.5.0
- 58.180.7.0/24AS9848SEJONG NETWORKSRPKI Not found58.180.7.0
- 58.180.8.0/24AS4670ShinbiroRPKI Not found58.180.8.0
- 58.180.9.0/24AS4670ShinbiroRPKI Not found58.180.9.0
- 58.180.10.0/24AS4670ShinbiroRPKI Not found58.180.10.0
- 58.180.13.0/24AS4670ShinbiroRPKI Not found58.180.13.0
- 58.180.15.0/24AS4670ShinbiroRPKI Not found58.180.15.0
- 58.180.16.0/24AS4670ShinbiroRPKI Not found58.180.16.0
- 58.180.17.0/24AS4670ShinbiroRPKI Not found58.180.17.0
- 58.180.19.0/24AS4670ShinbiroRPKI Not found58.180.19.0
- 58.180.22.0/24AS4664ShinbiroRPKI Not found58.180.22.0
- 58.180.23.0/24AS4670ShinbiroRPKI Not found58.180.23.0
- 58.180.24.0/24AS4670ShinbiroRPKI Not found58.180.24.0
- 58.180.26.0/24AS4670ShinbiroRPKI Not found58.180.26.0
- 58.180.27.0/24AS4670ShinbiroRPKI Not found58.180.27.0
- 58.180.28.0/24AS4670ShinbiroRPKI Not found58.180.28.0
- 58.180.30.0/24AS4670ShinbiroRPKI Not found58.180.30.0
- 58.180.32.0/24AS4670ShinbiroRPKI Not found58.180.32.0
- 58.180.33.0/24AS4670ShinbiroRPKI Not found58.180.33.0
- 58.180.34.0/24AS4670ShinbiroRPKI Not found58.180.34.0
- 58.180.36.0/24AS4670ShinbiroRPKI Not found58.180.36.0
- 58.180.40.0/24AS4670ShinbiroRPKI Not found58.180.40.0
- 58.180.43.0/24AS4670ShinbiroRPKI Not found58.180.43.0
- 58.180.56.0/24AS4670ShinbiroRPKI Not found58.180.56.0
- 58.180.58.0/24AS4670ShinbiroRPKI Not found58.180.58.0
- 58.180.60.0/24AS4670ShinbiroRPKI Not found58.180.60.0
- 58.180.61.0/24AS4664ShinbiroRPKI Not found58.180.61.0
- 58.180.62.0/24AS4664ShinbiroRPKI Not found58.180.62.0
- 58.180.64.0/24AS4670ShinbiroRPKI Not found58.180.64.0
- 58.180.68.0/24AS4670ShinbiroRPKI Not found58.180.68.0
- 58.180.69.0/24AS4670ShinbiroRPKI Not found58.180.69.0
- 58.180.70.0/24AS4670ShinbiroRPKI Not found58.180.70.0
- 58.180.71.0/24AS4670ShinbiroRPKI Not found58.180.71.0
- 58.180.72.0/24AS4670ShinbiroRPKI Not found58.180.72.0
- 58.180.74.0/24AS38676flexnetworksRPKI Not found58.180.74.0
- 58.180.77.0/24AS4670ShinbiroRPKI Not found58.180.77.0
- 58.180.79.0/24AS38676flexnetworksRPKI Not found58.180.79.0
- 58.180.81.0/24AS4670ShinbiroRPKI Not found58.180.81.0
- 58.180.82.0/23AS4670ShinbiroRPKI Not found58.180.82.0
- 58.180.84.0/23AS4670ShinbiroRPKI Not found58.180.84.0
- 58.180.86.0/23AS4670ShinbiroRPKI Not found58.180.86.0
- 58.180.88.0/23AS4670ShinbiroRPKI Not found58.180.88.0
- 58.180.90.0/24AS4670ShinbiroRPKI Not found58.180.90.0
- 58.180.101.0/24AS4670ShinbiroRPKI Not found58.180.101.0
- 58.180.102.0/24AS4670ShinbiroRPKI Not found58.180.102.0
- 58.180.104.0/24AS4670ShinbiroRPKI Not found58.180.104.0
- 58.180.105.0/24AS4670ShinbiroRPKI Not found58.180.105.0
- 58.180.106.0/24AS4670ShinbiroRPKI Not found58.180.106.0
- 58.180.110.0/24AS4670ShinbiroRPKI Not found58.180.110.0
- 58.180.111.0/24AS4670ShinbiroRPKI Not found58.180.111.0
- 58.180.112.0/24AS4670ShinbiroRPKI Not found58.180.112.0
- 58.180.113.0/24AS38676flexnetworksRPKI Not found58.180.113.0
- 58.180.114.0/24AS38676flexnetworksRPKI Not found58.180.114.0
- 58.180.120.0/24AS4670ShinbiroRPKI Not found58.180.120.0
- 58.180.121.0/24AS4670ShinbiroRPKI Not found58.180.121.0
- 58.180.122.0/23AS4670ShinbiroRPKI Not found58.180.122.0
- 58.180.124.0/22AS4670ShinbiroRPKI Not found58.180.124.0
- 58.180.128.0/17AS4670ShinbiroRPKI Not found58.180.128.0
- 58.180.133.0/24AS9848SEJONG NETWORKSRPKI Not found58.180.133.0
- 58.180.136.0/24AS9848SEJONG NETWORKSRPKI Not found58.180.136.0
- 58.180.179.0/24AS4670ShinbiroRPKI Not found58.180.179.0
- 58.180.188.0/24AS9842LOTTE INNOVATE Co.,LtdRPKI Not found58.180.188.0
- 58.180.191.0/24AS9842LOTTE INNOVATE Co.,LtdRPKI Not found58.180.191.0
- 58.180.224.0/22AS4664ShinbiroRPKI Not found58.180.224.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.