BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
83.169.192.0/18
Announced exactly
- 83.169.192.0/18AS31133PJSC MegaFonRPKI Valid83.169.192.0
- Registry
- RIPE NCC · Russia · Apr 20, 2004
- Delegated block
- 83.169.192.0 – 83.169.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 83.169.192.0/24AS31133PJSC MegaFonRPKI Valid83.169.192.0
- 83.169.193.0/24AS31133PJSC MegaFonRPKI Valid83.169.193.0
- 83.169.194.0/24AS31133PJSC MegaFonRPKI Valid83.169.194.0
- 83.169.195.0/24AS31133PJSC MegaFonRPKI Valid83.169.195.0
- 83.169.196.0/24AS31133PJSC MegaFonRPKI Valid83.169.196.0
- 83.169.197.0/24AS31133PJSC MegaFonRPKI Valid83.169.197.0
- 83.169.198.0/24AS31133PJSC MegaFonRPKI Valid83.169.198.0
- 83.169.199.0/24AS31133PJSC MegaFonRPKI Valid83.169.199.0
- 83.169.200.0/24AS31133PJSC MegaFonRPKI Valid83.169.200.0
- 83.169.201.0/24AS31133PJSC MegaFonRPKI Valid83.169.201.0
- 83.169.202.0/24AS31133PJSC MegaFonRPKI Valid83.169.202.0
- 83.169.203.0/24AS31133PJSC MegaFonRPKI Valid83.169.203.0
- 83.169.205.0/24AS31133PJSC MegaFonRPKI Valid83.169.205.0
- 83.169.206.0/24AS31133PJSC MegaFonRPKI Valid83.169.206.0
- 83.169.207.0/24AS31133PJSC MegaFonRPKI Valid83.169.207.0
- 83.169.208.0/24AS31208PJSC MegaFonRPKI Valid83.169.208.0
- 83.169.209.0/24AS31133PJSC MegaFonRPKI Valid83.169.209.0
- 83.169.210.0/24AS31133PJSC MegaFonRPKI Valid83.169.210.0
- 83.169.211.0/24AS31208PJSC MegaFonRPKI Valid83.169.211.0
- 83.169.212.0/24AS31208PJSC MegaFonRPKI Valid83.169.212.0
- 83.169.213.0/24AS31208PJSC MegaFonRPKI Valid83.169.213.0
- 83.169.214.0/24AS31208PJSC MegaFonRPKI Valid83.169.214.0
- 83.169.215.0/24AS31133PJSC MegaFonRPKI Valid83.169.215.0
- 83.169.216.0/24AS31224PJSC MegaFonRPKI Valid83.169.216.0
- 83.169.217.0/24AS29648PJSC MegaFonRPKI Valid83.169.217.0
- 83.169.218.0/24AS29648PJSC MegaFonRPKI Valid83.169.218.0
- 83.169.219.0/24AS29648PJSC MegaFonRPKI Valid83.169.219.0
- 83.169.220.0/24AS29648PJSC MegaFonRPKI Valid83.169.220.0
- 83.169.221.0/24AS29648PJSC MegaFonRPKI Valid83.169.221.0
- 83.169.222.0/24AS29648PJSC MegaFonRPKI Valid83.169.222.0
- 83.169.223.0/24AS29648PJSC MegaFonRPKI Valid83.169.223.0
- 83.169.224.0/23AS31195PJSC MegaFonRPKI Valid83.169.224.0
- 83.169.226.0/24AS31195PJSC MegaFonRPKI Valid83.169.226.0
- 83.169.227.0/24AS31195PJSC MegaFonRPKI Valid83.169.227.0
- 83.169.228.0/23AS31195PJSC MegaFonRPKI Valid83.169.228.0
- 83.169.230.0/24AS31195PJSC MegaFonRPKI Valid83.169.230.0
- 83.169.231.0/24AS31133PJSC MegaFonRPKI Valid83.169.231.0
- 83.169.232.0/24AS31163PJSC MegaFonRPKI Valid83.169.232.0
- 83.169.233.0/24AS31163PJSC MegaFonRPKI Valid83.169.233.0
- 83.169.234.0/24AS31163PJSC MegaFonRPKI Valid83.169.234.0
- 83.169.235.0/24AS31163PJSC MegaFonRPKI Valid83.169.235.0
- 83.169.236.0/24AS31163PJSC MegaFonRPKI Valid83.169.236.0
- 83.169.237.0/24AS31163PJSC MegaFonRPKI Valid83.169.237.0
- 83.169.238.0/24AS31163PJSC MegaFonRPKI Valid83.169.238.0
- 83.169.239.0/24AS31163PJSC MegaFonRPKI Valid83.169.239.0
- 83.169.240.0/24AS31163PJSC MegaFonRPKI Valid83.169.240.0
- 83.169.241.0/24AS31163PJSC MegaFonRPKI Valid83.169.241.0
- 83.169.242.0/24AS31163PJSC MegaFonRPKI Valid83.169.242.0
- 83.169.243.0/24AS31163PJSC MegaFonRPKI Valid83.169.243.0
- 83.169.244.0/24AS31163PJSC MegaFonRPKI Valid83.169.244.0
- 83.169.245.0/24AS31163PJSC MegaFonRPKI Valid83.169.245.0
- 83.169.246.0/24AS31163PJSC MegaFonRPKI Valid83.169.246.0
- 83.169.247.0/24AS31163PJSC MegaFonRPKI Valid83.169.247.0
- 83.169.248.0/22AS31205PJSC MegaFonRPKI Valid83.169.248.0
- 83.169.252.0/22AS31205PJSC MegaFonRPKI Valid83.169.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, 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.