BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
2a14:6781::/32
Announced exactly
- 2a14:6781::/32AS51202NUXOA GmbHRPKI Valid2a14:6781::
- Registry
- RIPE NCC · Germany · Jan 9, 2024
- Delegated block
- 2a14:6780:: – 2a14:6787:ffff:ffff:ffff:ffff:ffff:ffff
Covering routes
No less-specific route covers it.
More-specific routes
- 2a14:6781::/48AS215828Tizian Maxime Weigt trading as "TMW Global Networks"RPKI Valid2a14:6781::
- 2a14:6781:201::/48AS51202NUXOA GmbHRPKI Valid2a14:6781:201::
- 2a14:6781:300::/48AS51202NUXOA GmbHRPKI Valid2a14:6781:300::
- 2a14:6781:301::/48AS51202NUXOA GmbHRPKI Valid2a14:6781:301::
- 2a14:6781:302::/48AS51202NUXOA GmbHRPKI Valid2a14:6781:302::
- 2a14:6781:303::/48AS51202NUXOA GmbHRPKI Valid2a14:6781:303::
- 2a14:6781:304::/48AS51202NUXOA GmbHRPKI Valid2a14:6781:304::
- 2a14:6781:305::/48AS51202NUXOA GmbHRPKI Valid2a14:6781:305::
- 2a14:6781:333::/48AS51202NUXOA GmbHRPKI Valid2a14:6781:333::
- 2a14:6781:1400::/38AS215375Luca NowakRPKI Valid2a14:6781:1400::
- 2a14:6781:1400::/46AS215375Luca NowakRPKI Valid2a14:6781:1400::
- 2a14:6781:1800::/38AS207695Mario Kurz trading as LUME SolutionsRPKI Valid2a14:6781:1800::
- 2a14:6781:1c00::/38AS203442Steffen BarthelRPKI Valid2a14:6781:1c00::
- 2a14:6781:2000::/38AS203029Alec PutzmannRPKI Valid2a14:6781:2000::
- 2a14:6781:2400::/38AS200842Palior UG (haftungsbeschraenkt)RPKI Valid2a14:6781:2400::
- 2a14:6781:f000::/36AS215828Tizian Maxime Weigt trading as "TMW Global Networks"RPKI Valid2a14:6781:f000::
- 2a14:6781:ff01::/48AS59449Mitja HerbajRPKI Valid2a14:6781:ff01::
- 2a14:6781:ff02::/48AS59449Mitja HerbajRPKI Valid2a14:6781:ff02::
- 2a14:6781:ff04::/48AS59449Mitja HerbajRPKI Valid2a14:6781:ff04::
- 2a14:6781:ff05::/48AS59449Mitja HerbajRPKI Valid2a14:6781:ff05::
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.