BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
79.111.0.0/16
Announced exactly
- 79.111.0.0/16AS12714PJSC MegaFonRPKI Valid79.111.0.0
- Registry
- RIPE NCC · Russia · Feb 15, 2008
- Delegated block
- 79.111.0.0 – 79.111.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 79.111.8.0/22AS12714PJSC MegaFonRPKI Valid79.111.8.0
- 79.111.32.0/20AS12714PJSC MegaFonRPKI Valid79.111.32.0
- 79.111.64.0/21AS12714PJSC MegaFonRPKI Valid79.111.64.0
- 79.111.88.0/21AS12714PJSC MegaFonRPKI Valid79.111.88.0
- 79.111.112.0/24AS12714PJSC MegaFonRPKI Valid79.111.112.0
- 79.111.120.0/24AS31163PJSC MegaFonRPKI Valid79.111.120.0
- 79.111.121.0/24AS12714PJSC MegaFonRPKI Valid79.111.121.0
- 79.111.122.0/24AS31163PJSC MegaFonRPKI Valid79.111.122.0
- 79.111.124.0/22AS12714PJSC MegaFonRPKI Valid79.111.124.0
- 79.111.128.0/20AS12714PJSC MegaFonRPKI Valid79.111.128.0
- 79.111.144.0/21AS12714PJSC MegaFonRPKI Valid79.111.144.0
- 79.111.152.0/22AS12714PJSC MegaFonRPKI Valid79.111.152.0
- 79.111.156.0/23AS12714PJSC MegaFonRPKI Valid79.111.156.0
- 79.111.160.0/19AS12714PJSC MegaFonRPKI Valid79.111.160.0
- 79.111.208.0/21AS12714PJSC MegaFonRPKI Valid79.111.208.0
- 79.111.224.0/21AS12714PJSC MegaFonRPKI Valid79.111.224.0
- 79.111.244.0/23AS12714PJSC MegaFonRPKI Valid79.111.244.0
- 79.111.248.0/21AS12714PJSC MegaFonRPKI Valid79.111.248.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.