BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
202.30.128.0/17
Announced exactly
- 202.30.128.0/17AS4670ShinbiroRPKI Not found202.30.128.0
- Registry
- APNIC · South Korea · Feb 29, 1996
- Delegated block
- 202.30.128.0 – 202.30.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 202.30.128.0/18AS4670ShinbiroRPKI Not found202.30.128.0
- 202.30.130.0/24AS4670ShinbiroRPKI Not found202.30.130.0
- 202.30.131.0/24AS4670ShinbiroRPKI Not found202.30.131.0
- 202.30.143.0/24AS4670ShinbiroRPKI Not found202.30.143.0
- 202.30.164.0/24AS4670ShinbiroRPKI Not found202.30.164.0
- 202.30.171.0/24AS9980LOTTE INNOVATE Co.,LtdRPKI Not found202.30.171.0
- 202.30.172.0/24AS9980LOTTE INNOVATE Co.,LtdRPKI Not found202.30.172.0
- 202.30.173.0/24AS9980LOTTE INNOVATE Co.,LtdRPKI Not found202.30.173.0
- 202.30.174.0/24AS9980LOTTE INNOVATE Co.,LtdRPKI Not found202.30.174.0
- 202.30.176.0/24AS9980LOTTE INNOVATE Co.,LtdRPKI Not found202.30.176.0
- 202.30.180.0/24AS9980LOTTE INNOVATE Co.,LtdRPKI Not found202.30.180.0
- 202.30.181.0/24AS9980LOTTE INNOVATE Co.,LtdRPKI Not found202.30.181.0
- 202.30.191.0/24AS9980LOTTE INNOVATE Co.,LtdRPKI Not found202.30.191.0
- 202.30.192.0/18AS4670ShinbiroRPKI Not found202.30.192.0
- 202.30.192.0/19AS4670ShinbiroRPKI Not found202.30.192.0
- 202.30.198.0/24AS4670ShinbiroRPKI Not found202.30.198.0
- 202.30.206.0/24AS9980LOTTE INNOVATE Co.,LtdRPKI Not found202.30.206.0
- 202.30.209.0/24AS9848SEJONG NETWORKSRPKI Not found202.30.209.0
- 202.30.210.0/24AS9848SEJONG NETWORKSRPKI Not found202.30.210.0
- 202.30.212.0/24AS9848SEJONG NETWORKSRPKI Not found202.30.212.0
- 202.30.213.0/24AS9848SEJONG NETWORKSRPKI Not found202.30.213.0
- 202.30.215.0/24AS9980LOTTE INNOVATE Co.,LtdRPKI Not found202.30.215.0
- 202.30.216.0/24AS9980LOTTE INNOVATE Co.,LtdRPKI Not found202.30.216.0
- 202.30.217.0/24AS9848SEJONG NETWORKSRPKI Not found202.30.217.0
- 202.30.219.0/24AS9980LOTTE INNOVATE Co.,LtdRPKI Not found202.30.219.0
- 202.30.220.0/24AS9980LOTTE INNOVATE Co.,LtdRPKI Not found202.30.220.0
- 202.30.221.0/24AS9980LOTTE INNOVATE Co.,LtdRPKI Not found202.30.221.0
- 202.30.223.0/24AS9980LOTTE INNOVATE Co.,LtdRPKI Not found202.30.223.0
- 202.30.224.0/19AS4670ShinbiroRPKI Not found202.30.224.0
- 202.30.225.0/24AS4670ShinbiroRPKI Not found202.30.225.0
- 202.30.226.0/24AS4670ShinbiroRPKI Not found202.30.226.0
- 202.30.230.0/24AS4670ShinbiroRPKI Not found202.30.230.0
- 202.30.232.0/24AS9848SEJONG NETWORKSRPKI Not found202.30.232.0
- 202.30.233.0/24AS9848SEJONG NETWORKSRPKI Not found202.30.233.0
- 202.30.234.0/24AS9848SEJONG NETWORKSRPKI Not found202.30.234.0
- 202.30.235.0/24AS9848SEJONG NETWORKSRPKI Not found202.30.235.0
- 202.30.236.0/24AS9848SEJONG NETWORKSRPKI Not found202.30.236.0
- 202.30.237.0/24AS9848SEJONG NETWORKSRPKI Not found202.30.237.0
- 202.30.238.0/24AS9848SEJONG NETWORKSRPKI Not found202.30.238.0
- 202.30.239.0/24AS9848SEJONG NETWORKSRPKI Not found202.30.239.0
- 202.30.240.0/24AS9848SEJONG NETWORKSRPKI Not found202.30.240.0
- 202.30.241.0/24AS9848SEJONG NETWORKSRPKI Not found202.30.241.0
- 202.30.242.0/24AS9848SEJONG NETWORKSRPKI Not found202.30.242.0
- 202.30.243.0/24AS9848SEJONG NETWORKSRPKI Not found202.30.243.0
- 202.30.249.0/24AS9848SEJONG NETWORKSRPKI Not found202.30.249.0
- 202.30.255.0/24AS9980LOTTE INNOVATE Co.,LtdRPKI Not found202.30.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, 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.