BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
2a02:c6c0::/29
Announced exactly
- 2a02:c6c0::/29AS58061Scalaxy B.V.RPKI Not found2a02:c6c0::
- Registry
- RIPE NCC · United Kingdom · Sep 25, 2012
- Delegated block
- 2a02:c6c0:: – 2a02:c6c7:ffff:ffff:ffff:ffff:ffff:ffff
Covering routes
No less-specific route covers it.
More-specific routes
- 2a02:c6c0::/32AS12722RECONN LLCRPKI Valid2a02:c6c0::
- 2a02:c6c1::/48AS44050Petersburg Internet Network ltd.RPKI Valid2a02:c6c1::
- 2a02:c6c1:1::/48AS10929eStruxture Data Centers Inc.RPKI Valid2a02:c6c1:1::
- 2a02:c6c1:2::/48AS58061Scalaxy B.V.RPKI Valid2a02:c6c1:2::
- 2a02:c6c1:3::/48AS58061Scalaxy B.V.RPKI Valid2a02:c6c1:3::
- 2a02:c6c1:4::/48AS9009M247 Europe SRLRPKI Valid2a02:c6c1:4::
- 2a02:c6c1:5::/48AS9009M247 Europe SRLRPKI Valid2a02:c6c1:5::
- 2a02:c6c1:6::/48AS9009M247 Europe SRLRPKI Valid2a02:c6c1:6::
- 2a02:c6c1:7::/48AS9009M247 Europe SRLRPKI Valid2a02:c6c1:7::
- 2a02:c6c1:8::/48AS9009M247 Europe SRLRPKI Valid2a02:c6c1:8::
- 2a02:c6c1:9::/48AS9009M247 Europe SRLRPKI Valid2a02:c6c1:9::
- 2a02:c6c1:a::/48AS9009M247 Europe SRLRPKI Valid2a02:c6c1:a::
- 2a02:c6c1:b::/48AS9009M247 Europe SRLRPKI Valid2a02:c6c1:b::
- 2a02:c6c1:e::/48AS58061Scalaxy B.V.RPKI Valid2a02:c6c1:e::
- 2a02:c6c1:f::/48AS29802HIVELOCITY, Inc.RPKI Valid2a02:c6c1:f::
- 2a02:c6c1:10::/48AS58061Scalaxy B.V.RPKI Valid2a02:c6c1:10::
- 2a02:c6c1:11::/48AS9009M247 Europe SRLRPKI Not found2a02:c6c1:11::
- 2a02:c6c1:141::/48AS58061Scalaxy B.V.RPKI Valid2a02:c6c1:141::
- 2a02:c6c1:142::/48AS58061Scalaxy B.V.RPKI Valid2a02:c6c1:142::
- 2a02:c6c1:143::/48AS9009M247 Europe SRLRPKI Valid2a02:c6c1:143::
- 2a02:c6c1:151::/48AS58061Scalaxy B.V.RPKI Valid2a02:c6c1:151::
- 2a02:c6c1:152::/48AS58061Scalaxy B.V.RPKI Valid2a02:c6c1:152::
- 2a02:c6c1:153::/48AS58061Scalaxy B.V.RPKI Valid2a02:c6c1:153::
- 2a02:c6c1:154::/48AS58061Scalaxy B.V.RPKI Valid2a02:c6c1:154::
- 2a02:c6c1:155::/48AS58061Scalaxy B.V.RPKI Valid2a02:c6c1:155::
- 2a02:c6c1:156::/48AS58061Scalaxy B.V.RPKI Valid2a02:c6c1:156::
- 2a02:c6c1:160::/43AS58061Scalaxy B.V.RPKI Not found2a02:c6c1:160::
- 2a02:c6c3::/32AS58061Scalaxy B.V.RPKI Valid2a02:c6c3::
- 2a02:c6c7::/32AS58061Scalaxy B.V.RPKI Valid2a02:c6c7::
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 85.240.0.0/13. 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.