BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
2a10:9300::/29
Announced exactly
- 2a10:9300::/29AS200736MEDIANET INVEST AERPKI Valid2a10:9300::
- Registry
- RIPE NCC · Greece · Nov 11, 2020
- Delegated block
- 2a10:9300:: – 2a10:9307:ffff:ffff:ffff:ffff:ffff:ffff
Covering routes
No less-specific route covers it.
More-specific routes
- 2a10:9300:100::/42AS200736MEDIANET INVEST AERPKI Valid2a10:9300:100::
- 2a10:9300:140::/42AS200736MEDIANET INVEST AERPKI Valid2a10:9300:140::
- 2a10:9300:180::/42AS200736MEDIANET INVEST AERPKI Valid2a10:9300:180::
- 2a10:9300:200::/42AS200736MEDIANET INVEST AERPKI Valid2a10:9300:200::
- 2a10:9300:240::/42AS200736MEDIANET INVEST AERPKI Valid2a10:9300:240::
- 2a10:9300:400::/42AS200736MEDIANET INVEST AERPKI Valid2a10:9300:400::
- 2a10:9300:440::/42AS200736MEDIANET INVEST AERPKI Valid2a10:9300:440::
- 2a10:9300:500::/42AS200736MEDIANET INVEST AERPKI Valid2a10:9300:500::
- 2a10:9300:600::/42AS200736MEDIANET INVEST AERPKI Valid2a10:9300:600::
- 2a10:9300:700::/42AS200736MEDIANET INVEST AERPKI Valid2a10:9300:700::
- 2a10:9300:900::/42AS200736MEDIANET INVEST AERPKI Valid2a10:9300:900::
- 2a10:9300:b00::/42AS200736MEDIANET INVEST AERPKI Valid2a10:9300:b00::
- 2a10:9300:c00::/42AS200736MEDIANET INVEST AERPKI Valid2a10:9300:c00::
- 2a10:9301:40::/42AS200736MEDIANET INVEST AERPKI Valid2a10:9301:40::
- 2a10:9301:100::/42AS200736MEDIANET INVEST AERPKI Valid2a10:9301:100::
- 2a10:9301:140::/42AS200736MEDIANET INVEST AERPKI Valid2a10:9301:140::
- 2a10:9301:180::/42AS200736MEDIANET INVEST AERPKI Valid2a10:9301:180::
- 2a10:9301:300::/42AS200736MEDIANET INVEST AERPKI Valid2a10:9301:300::
- 2a10:9301:340::/42AS200736MEDIANET INVEST AERPKI Valid2a10:9301:340::
- 2a10:9301:380::/42AS200736MEDIANET INVEST AERPKI Valid2a10:9301:380::
- 2a10:9301:700::/42AS200736MEDIANET INVEST AERPKI Valid2a10:9301:700::
- 2a10:9301:740::/42AS200736MEDIANET INVEST AERPKI Valid2a10:9301:740::
- 2a10:9301:980::/42AS200736MEDIANET INVEST AERPKI Valid2a10:9301:980::
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.