BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
188.75.192.0/18
Announced exactly
- 188.75.192.0/18AS8359MTS PJSCRPKI Not found188.75.192.0
- Registry
- RIPE NCC · Russia · Aug 25, 2009
- Delegated block
- 188.75.192.0 – 188.75.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 188.75.192.0/20AS48212MTS PJSCRPKI Valid188.75.192.0
- 188.75.192.0/23AS48212MTS PJSCRPKI Valid188.75.192.0
- 188.75.194.0/23AS48212MTS PJSCRPKI Valid188.75.194.0
- 188.75.205.0/24AS48212MTS PJSCRPKI Valid188.75.205.0
- 188.75.207.0/24AS48212MTS PJSCRPKI Valid188.75.207.0
- 188.75.208.0/23AS21365MTS PJSCRPKI Not found188.75.208.0
- 188.75.212.0/24AS42087MTS PJSCRPKI Not found188.75.212.0
- 188.75.213.0/24AS8359MTS PJSCRPKI Not found188.75.213.0
- 188.75.214.0/23AS30922MTS PJSCRPKI Not found188.75.214.0
- 188.75.216.0/23AS39811MTS PJSCRPKI Not found188.75.216.0
- 188.75.218.0/23AS39811MTS PJSCRPKI Not found188.75.218.0
- 188.75.220.0/22AS48212MTS PJSCRPKI Valid188.75.220.0
- 188.75.225.0/24AS8359MTS PJSCRPKI Not found188.75.225.0
- 188.75.228.0/23AS8359MTS PJSCRPKI Not found188.75.228.0
- 188.75.230.0/24AS8359MTS PJSCRPKI Not found188.75.230.0
- 188.75.231.0/24AS49154MTS PJSCRPKI Not found188.75.231.0
- 188.75.242.0/23AS8359MTS PJSCRPKI Not found188.75.242.0
- 188.75.252.0/22AS48212MTS PJSCRPKI Valid188.75.252.0
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 193.166.0.0/15. 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.