BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
2a02:ee80::/32
Announced exactly
- 2a02:ee80::/32AS3573Accenture LLPRPKI Not found2a02:ee80::
- Registry
- RIPE NCC · Netherlands · Dec 4, 2012
- Delegated block
- 2a02:ee80:: – 2a02:ee87:ffff:ffff:ffff:ffff:ffff:ffff
Covering routes
No less-specific route covers it.
More-specific routes
- 2a02:ee80:102::/47AS21433Accenture UK LimitedRPKI Not found2a02:ee80:102::
- 2a02:ee80:200::/40AS3573Accenture LLPRPKI Not found2a02:ee80:200::
- 2a02:ee80:2030::/44AS3573Accenture LLPRPKI Not found2a02:ee80:2030::
- 2a02:ee80:4014::/47AS3573Accenture LLPRPKI Not found2a02:ee80:4014::
- 2a02:ee80:4014::/48AS3573Accenture LLPRPKI Not found2a02:ee80:4014::
- 2a02:ee80:4016::/47AS3573Accenture LLPRPKI Valid2a02:ee80:4016::
- 2a02:ee80:4026::/47AS3573Accenture LLPRPKI Valid2a02:ee80:4026::
- 2a02:ee80:4026::/48AS3573Accenture LLPRPKI Valid2a02:ee80:4026::
- 2a02:ee80:4028::/47AS3573Accenture LLPRPKI Not found2a02:ee80:4028::
- 2a02:ee80:402a::/47AS3573Accenture LLPRPKI Valid2a02:ee80:402a::
- 2a02:ee80:402a::/48AS3573Accenture LLPRPKI Valid2a02:ee80:402a::
- 2a02:ee80:402c::/47AS3573Accenture LLPRPKI Valid2a02:ee80:402c::
- 2a02:ee80:402c::/48AS3573Accenture LLPRPKI Valid2a02:ee80:402c::
- 2a02:ee80:4040::/47AS3573Accenture LLPRPKI Valid2a02:ee80:4040::
- 2a02:ee80:4046::/47AS3573Accenture LLPRPKI Not found2a02:ee80:4046::
- 2a02:ee80:404a::/47AS3573Accenture LLPRPKI Valid2a02:ee80:404a::
- 2a02:ee80:404a::/48AS3573Accenture LLPRPKI Valid2a02:ee80:404a::
- 2a02:ee80:404b::/48AS3573Accenture LLPRPKI Valid2a02:ee80:404b::
- 2a02:ee80:4068::/48AS3573Accenture LLPRPKI Not found2a02:ee80:4068::
- 2a02:ee80:4072::/47AS3573Accenture LLPRPKI Valid2a02:ee80:4072::
- 2a02:ee80:4076::/47AS3573Accenture LLPRPKI Valid2a02:ee80:4076::
- 2a02:ee80:4076::/48AS3573Accenture LLPRPKI Valid2a02:ee80:4076::
- 2a02:ee80:4077::/48AS3573Accenture LLPRPKI Valid2a02:ee80:4077::
- 2a02:ee80:407c::/47AS3573Accenture LLPRPKI Not found2a02:ee80:407c::
- 2a02:ee80:407c::/48AS3573Accenture LLPRPKI Valid2a02:ee80:407c::
- 2a02:ee80:407e::/47AS3573Accenture LLPRPKI Valid2a02:ee80:407e::
- 2a02:ee80:407e::/48AS3573Accenture LLPRPKI Valid2a02:ee80:407e::
- 2a02:ee80:4092::/47AS3573Accenture LLPRPKI Valid2a02:ee80:4092::
- 2a02:ee80:40ae::/47AS3573Accenture LLPRPKI Valid2a02:ee80:40ae::
- 2a02:ee80:40b0::/47AS3573Accenture LLPRPKI Not found2a02:ee80:40b0::
- 2a02:ee80:40b2::/47AS21433Accenture UK LimitedRPKI Not found2a02:ee80:40b2::
- 2a02:ee80:40c0::/47AS21433Accenture UK LimitedRPKI Not found2a02:ee80:40c0::
- 2a02:ee80:40db::/48AS21433Accenture UK LimitedRPKI Not found2a02:ee80:40db::
- 2a02:ee80:410a::/47AS3573Accenture LLPRPKI Not found2a02:ee80:410a::
- 2a02:ee80:410a::/48AS3573Accenture LLPRPKI Valid2a02:ee80:410a::
- 2a02:ee80:4118::/47AS3573Accenture LLPRPKI Valid2a02:ee80:4118::
- 2a02:ee80:4118::/48AS3573Accenture LLPRPKI Valid2a02:ee80:4118::
- 2a02:ee80:411c::/47AS3573Accenture LLPRPKI Valid2a02:ee80:411c::
- 2a02:ee80:411c::/48AS3573Accenture LLPRPKI Valid2a02:ee80:411c::
- 2a02:ee80:4122::/47AS3573Accenture LLPRPKI Valid2a02:ee80:4122::
- 2a02:ee80:4122::/48AS3573Accenture LLPRPKI Valid2a02:ee80:4122::
- 2a02:ee80:412a::/47AS3573Accenture LLPRPKI Valid2a02:ee80:412a::
- 2a02:ee80:412c::/48AS3573Accenture LLPRPKI Not found2a02:ee80:412c::
- 2a02:ee80:412e::/47AS3573Accenture LLPRPKI Not found2a02:ee80:412e::
- 2a02:ee80:4134::/47AS3573Accenture LLPRPKI Valid2a02:ee80:4134::
- 2a02:ee80:413e::/47AS3573Accenture LLPRPKI Valid2a02:ee80:413e::
- 2a02:ee80:413e::/48AS3573Accenture LLPRPKI Valid2a02:ee80:413e::
- 2a02:ee80:4170::/47AS3573Accenture LLPRPKI Valid2a02:ee80:4170::
- 2a02:ee80:4170::/48AS3573Accenture LLPRPKI Valid2a02:ee80:4170::
- 2a02:ee80:4174::/47AS3573Accenture LLPRPKI Valid2a02:ee80:4174::
- 2a02:ee80:4174::/48AS3352TELEFONICA DE ESPANA S.A.U.RPKI Valid2a02:ee80:4174::
- 2a02:ee80:417c::/47AS3573Accenture LLPRPKI Valid2a02:ee80:417c::
- 2a02:ee80:417c::/48AS3573Accenture LLPRPKI Valid2a02:ee80:417c::
- 2a02:ee80:4180::/48AS3573Accenture LLPRPKI Valid2a02:ee80:4180::
- 2a02:ee80:4181::/48AS3573Accenture LLPRPKI Valid2a02:ee80:4181::
- 2a02:ee80:418c::/47AS3573Accenture LLPRPKI Valid2a02:ee80:418c::
- 2a02:ee80:4196::/48AS3573Accenture LLPRPKI Not found2a02:ee80:4196::
- 2a02:ee80:4197::/48AS3573Accenture LLPRPKI Valid2a02:ee80:4197::
- 2a02:ee80:419a::/47AS21433Accenture UK LimitedRPKI Not found2a02:ee80:419a::
- 2a02:ee80:419a::/48AS21433Accenture UK LimitedRPKI Not found2a02:ee80:419a::
- 2a02:ee80:419b::/48AS21433Accenture UK LimitedRPKI Not found2a02:ee80:419b::
- 2a02:ee80:41a0::/47AS3573Accenture LLPRPKI Valid2a02:ee80:41a0::
- 2a02:ee80:41a0::/48AS3573Accenture LLPRPKI Valid2a02:ee80:41a0::
- 2a02:ee80:41a8::/47AS3573Accenture LLPRPKI Valid2a02:ee80:41a8::
- 2a02:ee80:41aa::/47AS3573Accenture LLPRPKI Valid2a02:ee80:41aa::
- 2a02:ee80:41aa::/48AS3573Accenture LLPRPKI Valid2a02:ee80:41aa::
- 2a02:ee80:41ac::/47AS3573Accenture LLPRPKI Valid2a02:ee80:41ac::
- 2a02:ee80:41b0::/48AS3573Accenture LLPRPKI Not found2a02:ee80:41b0::
- 2a02:ee80:41b1::/48AS3573Accenture LLPRPKI Not found2a02:ee80:41b1::
- 2a02:ee80:41c2::/47AS21433Accenture UK LimitedRPKI Not found2a02:ee80:41c2::
- 2a02:ee80:41c2::/48AS21433Accenture UK LimitedRPKI Not found2a02:ee80:41c2::
- 2a02:ee80:41d0::/47AS3573Accenture LLPRPKI Valid2a02:ee80:41d0::
- 2a02:ee80:41d0::/48AS3573Accenture LLPRPKI Valid2a02:ee80:41d0::
- 2a02:ee80:41d1::/48AS3573Accenture LLPRPKI Valid2a02:ee80:41d1::
- 2a02:ee80:41d6::/47AS3573Accenture LLPRPKI Valid2a02:ee80:41d6::
- 2a02:ee80:41d6::/48AS3573Accenture LLPRPKI Valid2a02:ee80:41d6::
- 2a02:ee80:41e2::/47AS3573Accenture LLPRPKI Valid2a02:ee80:41e2::
- 2a02:ee80:41e4::/47AS3573Accenture LLPRPKI Valid2a02:ee80:41e4::
- 2a02:ee80:41e4::/48AS3573Accenture LLPRPKI Valid2a02:ee80:41e4::
- 2a02:ee80:41ec::/47AS21433Accenture UK LimitedRPKI Not found2a02:ee80:41ec::
- 2a02:ee80:41ee::/48AS3573Accenture LLPRPKI Not found2a02:ee80:41ee::
- 2a02:ee80:41ef::/48AS3573Accenture LLPRPKI Not found2a02:ee80:41ef::
- 2a02:ee80:41f2::/47AS3573Accenture LLPRPKI Valid2a02:ee80:41f2::
- 2a02:ee80:41fa::/47AS3573Accenture LLPRPKI Not found2a02:ee80:41fa::
- 2a02:ee80:4208::/48AS21433Accenture UK LimitedRPKI Not found2a02:ee80:4208::
- 2a02:ee80:4209::/48AS21433Accenture UK LimitedRPKI Not found2a02:ee80:4209::
- 2a02:ee80:420c::/47AS3573Accenture LLPRPKI Valid2a02:ee80:420c::
- 2a02:ee80:420c::/48AS3573Accenture LLPRPKI Valid2a02:ee80:420c::
- 2a02:ee80:4218::/47AS3573Accenture LLPRPKI Not found2a02:ee80:4218::
- 2a02:ee80:4218::/48AS3573Accenture LLPRPKI Valid2a02:ee80:4218::
- 2a02:ee80:4228::/47AS3573Accenture LLPRPKI Not found2a02:ee80:4228::
- 2a02:ee80:422c::/47AS3573Accenture LLPRPKI Not found2a02:ee80:422c::
- 2a02:ee80:422c::/48AS3573Accenture LLPRPKI Valid2a02:ee80:422c::
- 2a02:ee80:4236::/47AS21433Accenture UK LimitedRPKI Not found2a02:ee80:4236::
- 2a02:ee80:4236::/48AS21433Accenture UK LimitedRPKI Not found2a02:ee80:4236::
- 2a02:ee80:4240::/47AS3573Accenture LLPRPKI Valid2a02:ee80:4240::
- 2a02:ee80:4240::/48AS3573Accenture LLPRPKI Valid2a02:ee80:4240::
- 2a02:ee80:4241::/48AS3573Accenture LLPRPKI Valid2a02:ee80:4241::
- 2a02:ee80:4244::/47AS3573Accenture LLPRPKI Valid2a02:ee80:4244::
- 2a02:ee80:4248::/47AS21433Accenture UK LimitedRPKI Valid2a02:ee80:4248::
Showing the first 100.
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 2.48.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.