BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
2a03:f003::/32
Announced exactly
- 2a03:f003::/32AS25472Nova Telecommunications & Media Single Member S.ARPKI Valid2a03:f003::
- Registry
- RIPE NCC · Greece · Dec 8, 2010
- Delegated block
- 2a03:f000:: – 2a03:f007:ffff:ffff:ffff:ffff:ffff:ffff
Covering routes
- 2a03:f000::/29AS25472Nova Telecommunications & Media Single Member S.ARPKI Valid2a03:f000::
More-specific routes
- 2a03:f003:1::/48AS25472Nova Telecommunications & Media Single Member S.ARPKI Valid2a03:f003:1::
- 2a03:f003:2::/48AS25472Nova Telecommunications & Media Single Member S.ARPKI Valid2a03:f003:2::
- 2a03:f003:3::/48AS25472Nova Telecommunications & Media Single Member S.ARPKI Valid2a03:f003:3::
- 2a03:f003:4::/48AS25472Nova Telecommunications & Media Single Member S.ARPKI Valid2a03:f003:4::
- 2a03:f003:5::/48AS25472Nova Telecommunications & Media Single Member S.ARPKI Valid2a03:f003:5::
- 2a03:f003:8::/48AS25472Nova Telecommunications & Media Single Member S.ARPKI Valid2a03:f003:8::
- 2a03:f003:100::/40AS25472Nova Telecommunications & Media Single Member S.ARPKI Valid2a03:f003:100::
- 2a03:f003:200::/40AS25472Nova Telecommunications & Media Single Member S.ARPKI Valid2a03:f003:200::
- 2a03:f003:300::/40AS25472Nova Telecommunications & Media Single Member S.ARPKI Valid2a03:f003:300::
- 2a03:f003:400::/40AS25472Nova Telecommunications & Media Single Member S.ARPKI Valid2a03:f003:400::
- 2a03:f003:500::/40AS25472Nova Telecommunications & Media Single Member S.ARPKI Valid2a03:f003:500::
- 2a03:f003:800::/40AS25472Nova Telecommunications & Media Single Member S.ARPKI Valid2a03:f003:800::
- 2a03:f003:1000::/48AS25472Nova Telecommunications & Media Single Member S.ARPKI Valid2a03:f003:1000::
- 2a03:f003:1001::/48AS25472Nova Telecommunications & Media Single Member S.ARPKI Valid2a03:f003:1001::
- 2a03:f003:1100::/40AS25472Nova Telecommunications & Media Single Member S.ARPKI Valid2a03:f003:1100::
- 2a03:f003:1200::/40AS25472Nova Telecommunications & Media Single Member S.ARPKI Valid2a03:f003:1200::
- 2a03:f003:1801::/48AS25472Nova Telecommunications & Media Single Member S.ARPKI Valid2a03:f003:1801::
- 2a03:f003:1940::/42AS25472Nova Telecommunications & Media Single Member S.ARPKI Valid2a03:f003:1940::
- 2a03:f003:1a00::/48AS25472Nova Telecommunications & Media Single Member S.ARPKI Valid2a03:f003:1a00::
- 2a03:f003:1a01::/48AS25472Nova Telecommunications & Media Single Member S.ARPKI Valid2a03:f003:1a01::
- 2a03:f003:1b00::/42AS25472Nova Telecommunications & Media Single Member S.ARPKI Valid2a03:f003:1b00::
- 2a03:f003:1b40::/42AS25472Nova Telecommunications & Media Single Member S.ARPKI Valid2a03:f003:1b40::
- 2a03:f003:1e00::/48AS25472Nova Telecommunications & Media Single Member S.ARPKI Valid2a03:f003:1e00::
- 2a03:f003:1e01::/48AS25472Nova Telecommunications & Media Single Member S.ARPKI Valid2a03:f003:1e01::
- 2a03:f003:1f00::/42AS25472Nova Telecommunications & Media Single Member S.ARPKI Valid2a03:f003:1f00::
- 2a03:f003:1f40::/42AS25472Nova Telecommunications & Media Single Member S.ARPKI Valid2a03:f003:1f40::
- 2a03:f003:2001::/48AS25472Nova Telecommunications & Media Single Member S.ARPKI Valid2a03:f003:2001::
- 2a03:f003:2200::/40AS25472Nova Telecommunications & Media Single Member S.ARPKI Valid2a03:f003:2200::
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 62.103.0.0/16. 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.