BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
203.251.192.0/18
Announced exactly
- 203.251.192.0/18AS4670ShinbiroRPKI Not found203.251.192.0
- Registry
- APNIC · South Korea · Sep 29, 1996
- Delegated block
- 203.251.192.0 – 203.251.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 203.251.192.0/19AS4670ShinbiroRPKI Not found203.251.192.0
- 203.251.192.0/24AS9980LOTTE INNOVATE Co.,LtdRPKI Not found203.251.192.0
- 203.251.193.0/24AS9980LOTTE INNOVATE Co.,LtdRPKI Not found203.251.193.0
- 203.251.194.0/24AS9980LOTTE INNOVATE Co.,LtdRPKI Not found203.251.194.0
- 203.251.195.0/24AS9980LOTTE INNOVATE Co.,LtdRPKI Not found203.251.195.0
- 203.251.196.0/24AS9980LOTTE INNOVATE Co.,LtdRPKI Not found203.251.196.0
- 203.251.197.0/24AS9980LOTTE INNOVATE Co.,LtdRPKI Not found203.251.197.0
- 203.251.201.0/24AS4670ShinbiroRPKI Not found203.251.201.0
- 203.251.202.0/24AS4670ShinbiroRPKI Not found203.251.202.0
- 203.251.203.0/24AS9980LOTTE INNOVATE Co.,LtdRPKI Not found203.251.203.0
- 203.251.205.0/24AS4670ShinbiroRPKI Not found203.251.205.0
- 203.251.207.0/24AS7562HCN DongjakRPKI Not found203.251.207.0
- 203.251.210.0/24AS9980LOTTE INNOVATE Co.,LtdRPKI Not found203.251.210.0
- 203.251.216.0/23AS4664ShinbiroRPKI Not found203.251.216.0
- 203.251.224.0/19AS4670ShinbiroRPKI Not found203.251.224.0
- 203.251.224.0/24AS4670ShinbiroRPKI Not found203.251.224.0
- 203.251.225.0/24AS4670ShinbiroRPKI Not found203.251.225.0
- 203.251.232.0/22AS4670ShinbiroRPKI Not found203.251.232.0
- 203.251.233.0/24AS20940Akamai International B.V.RPKI Not found203.251.233.0
- 203.251.234.0/24AS20940Akamai International B.V.RPKI Not found203.251.234.0
- 203.251.237.0/24AS7562HCN DongjakRPKI Not found203.251.237.0
- 203.251.238.0/24AS7562HCN DongjakRPKI Not found203.251.238.0
- 203.251.239.0/24AS7562HCN DongjakRPKI Not found203.251.239.0
- 203.251.240.0/24AS7562HCN DongjakRPKI Not found203.251.240.0
- 203.251.241.0/24AS7562HCN DongjakRPKI Not found203.251.241.0
- 203.251.242.0/24AS7562HCN DongjakRPKI Not found203.251.242.0
- 203.251.243.0/24AS7562HCN DongjakRPKI Not found203.251.243.0
- 203.251.244.0/24AS4670ShinbiroRPKI Not found203.251.244.0
- 203.251.245.0/24AS4670ShinbiroRPKI Not found203.251.245.0
- 203.251.246.0/24AS9848SEJONG NETWORKSRPKI Not found203.251.246.0
- 203.251.249.0/24AS9848SEJONG NETWORKSRPKI Not found203.251.249.0
- 203.251.250.0/24AS9848SEJONG NETWORKSRPKI Not found203.251.250.0
- 203.251.251.0/24AS9980LOTTE INNOVATE Co.,LtdRPKI Not found203.251.251.0
- 203.251.252.0/24AS9848SEJONG NETWORKSRPKI Not found203.251.252.0
- 203.251.253.0/24AS9848SEJONG NETWORKSRPKI Not found203.251.253.0
- 203.251.254.0/24AS9980LOTTE INNOVATE Co.,LtdRPKI Not found203.251.254.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.