BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
83.149.0.0/18
Announced exactly
- 83.149.0.0/18AS31133PJSC MegaFonRPKI Valid83.149.0.0
- Registry
- RIPE NCC · Russia · Mar 9, 2004
- Delegated block
- 83.149.0.0 – 83.149.63.255
Covering routes
No less-specific route covers it.
More-specific routes
- 83.149.0.0/21AS31213PJSC MegaFonRPKI Valid83.149.0.0
- 83.149.13.0/24AS13075PJSC MegaFonRPKI Valid83.149.13.0
- 83.149.14.0/24AS13075PJSC MegaFonRPKI Valid83.149.14.0
- 83.149.16.0/22AS31133PJSC MegaFonRPKI Valid83.149.16.0
- 83.149.16.0/24AS31133PJSC MegaFonRPKI Valid83.149.16.0
- 83.149.17.0/24AS31133PJSC MegaFonRPKI Valid83.149.17.0
- 83.149.18.0/24AS31133PJSC MegaFonRPKI Valid83.149.18.0
- 83.149.20.0/22AS31133PJSC MegaFonRPKI Valid83.149.20.0
- 83.149.20.0/24AS31133PJSC MegaFonRPKI Valid83.149.20.0
- 83.149.21.0/24AS31133PJSC MegaFonRPKI Valid83.149.21.0
- 83.149.22.0/23AS31133PJSC MegaFonRPKI Valid83.149.22.0
- 83.149.24.0/24AS31163PJSC MegaFonRPKI Valid83.149.24.0
- 83.149.25.0/24AS31163PJSC MegaFonRPKI Valid83.149.25.0
- 83.149.26.0/24AS31133PJSC MegaFonRPKI Valid83.149.26.0
- 83.149.28.0/24AS31163PJSC MegaFonRPKI Valid83.149.28.0
- 83.149.29.0/24AS31163PJSC MegaFonRPKI Valid83.149.29.0
- 83.149.30.0/24AS31163PJSC MegaFonRPKI Valid83.149.30.0
- 83.149.31.0/24AS31163PJSC MegaFonRPKI Valid83.149.31.0
- 83.149.32.0/22AS31224PJSC MegaFonRPKI Valid83.149.32.0
- 83.149.34.0/24AS31224PJSC MegaFonRPKI Valid83.149.34.0
- 83.149.36.0/22AS31224PJSC MegaFonRPKI Valid83.149.36.0
- 83.149.37.0/24AS31224PJSC MegaFonRPKI Valid83.149.37.0
- 83.149.39.0/24AS31224PJSC MegaFonRPKI Valid83.149.39.0
- 83.149.40.0/24AS31208PJSC MegaFonRPKI Valid83.149.40.0
- 83.149.41.0/24AS31133PJSC MegaFonRPKI Valid83.149.41.0
- 83.149.42.0/23AS31208PJSC MegaFonRPKI Valid83.149.42.0
- 83.149.44.0/23AS31133PJSC MegaFonRPKI Valid83.149.44.0
- 83.149.46.0/23AS31133PJSC MegaFonRPKI Valid83.149.46.0
- 83.149.48.0/23AS31133PJSC MegaFonRPKI Valid83.149.48.0
- 83.149.48.0/24AS31205PJSC MegaFonRPKI Valid83.149.48.0
- 83.149.49.0/24AS31205PJSC MegaFonRPKI Valid83.149.49.0
- 83.149.50.0/24AS31205PJSC MegaFonRPKI Valid83.149.50.0
- 83.149.51.0/24AS31205PJSC MegaFonRPKI Valid83.149.51.0
- 83.149.52.0/22AS31195PJSC MegaFonRPKI Valid83.149.52.0
- 83.149.53.0/24AS31133PJSC MegaFonRPKI Valid83.149.53.0
- 83.149.54.0/24AS31133PJSC MegaFonRPKI Valid83.149.54.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.