BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
2a01:5a8::/32
Announced exactly
- 2a01:5a8::/32AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8::
- Registry
- RIPE NCC · Bulgaria · Nov 2, 2007
- Delegated block
- 2a01:5a8:: – 2a01:5a8:ffff:ffff:ffff:ffff:ffff:ffff
Covering routes
No less-specific route covers it.
More-specific routes
- 2a01:5a8:1::/48AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:1::
- 2a01:5a8:5::/48AS50013Multicomp Ltd.RPKI Valid2a01:5a8:5::
- 2a01:5a8:8::/48AS211526Darjavna Agencia za Elektronno UpravlenieRPKI Valid2a01:5a8:8::
- 2a01:5a8:1a0::/46AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:1a0::
- 2a01:5a8:1b8::/45AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:1b8::
- 2a01:5a8:2b8::/45AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:2b8::
- 2a01:5a8:300::/47AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:300::
- 2a01:5a8:302::/47AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:302::
- 2a01:5a8:304::/47AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:304::
- 2a01:5a8:306::/47AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:306::
- 2a01:5a8:308::/46AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:308::
- 2a01:5a8:30c::/48AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:30c::
- 2a01:5a8:30d::/48AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:30d::
- 2a01:5a8:30e::/48AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:30e::
- 2a01:5a8:30f::/48AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:30f::
- 2a01:5a8:310::/48AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:310::
- 2a01:5a8:311::/48AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:311::
- 2a01:5a8:312::/48AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:312::
- 2a01:5a8:313::/48AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:313::
- 2a01:5a8:314::/48AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:314::
- 2a01:5a8:315::/48AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:315::
- 2a01:5a8:316::/48AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:316::
- 2a01:5a8:317::/48AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:317::
- 2a01:5a8:318::/48AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:318::
- 2a01:5a8:319::/48AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:319::
- 2a01:5a8:31a::/48AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:31a::
- 2a01:5a8:31b::/48AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:31b::
- 2a01:5a8:31c::/48AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:31c::
- 2a01:5a8:31d::/48AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:31d::
- 2a01:5a8:31e::/48AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:31e::
- 2a01:5a8:31f::/48AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:31f::
- 2a01:5a8:320::/48AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:320::
- 2a01:5a8:321::/48AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:321::
- 2a01:5a8:330::/47AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:330::
- 2a01:5a8:332::/47AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:332::
- 2a01:5a8:334::/46AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:334::
- 2a01:5a8:338::/46AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:338::
- 2a01:5a8:33c::/46AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:33c::
- 2a01:5a8:400::/40AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:400::
- 2a01:5a8:400::/46AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:400::
- 2a01:5a8:404::/46AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:404::
- 2a01:5a8:408::/46AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:408::
- 2a01:5a8:40c::/46AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:40c::
- 2a01:5a8:410::/46AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:410::
- 2a01:5a8:414::/46AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:414::
- 2a01:5a8:418::/46AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:418::
- 2a01:5a8:440::/46AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:440::
- 2a01:5a8:444::/46AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:444::
- 2a01:5a8:448::/46AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:448::
- 2a01:5a8:44c::/46AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:44c::
- 2a01:5a8:450::/46AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:450::
- 2a01:5a8:454::/46AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:454::
- 2a01:5a8:458::/46AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:458::
- 2a01:5a8:45c::/46AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:45c::
- 2a01:5a8:464::/46AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:464::
- 2a01:5a8:46c::/46AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:46c::
- 2a01:5a8:474::/46AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:474::
- 2a01:5a8:4a0::/47AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:4a0::
- 2a01:5a8:4a2::/48AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:4a2::
- 2a01:5a8:4a3::/48AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:4a3::
- 2a01:5a8:4a4::/48AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:4a4::
- 2a01:5a8:4a5::/48AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:4a5::
- 2a01:5a8:4a6::/48AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:4a6::
- 2a01:5a8:4a7::/48AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:4a7::
- 2a01:5a8:4a8::/47AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:4a8::
- 2a01:5a8:4aa::/48AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:4aa::
- 2a01:5a8:4ab::/48AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:4ab::
- 2a01:5a8:4ac::/48AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:4ac::
- 2a01:5a8:4ad::/48AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:4ad::
- 2a01:5a8:4ae::/48AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:4ae::
- 2a01:5a8:4af::/48AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:4af::
- 2a01:5a8:4b2::/48AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:4b2::
- 2a01:5a8:4ba::/48AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:4ba::
- 2a01:5a8:4bb::/48AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:4bb::
- 2a01:5a8:500::/40AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:500::
- 2a01:5a8:500::/46AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:500::
- 2a01:5a8:504::/46AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:504::
- 2a01:5a8:508::/46AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:508::
- 2a01:5a8:50c::/46AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:50c::
- 2a01:5a8:510::/46AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:510::
- 2a01:5a8:514::/46AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:514::
- 2a01:5a8:518::/46AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:518::
- 2a01:5a8:51c::/46AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:51c::
- 2a01:5a8:524::/46AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:524::
- 2a01:5a8:52c::/46AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:52c::
- 2a01:5a8:534::/46AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:534::
- 2a01:5a8:540::/46AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:540::
- 2a01:5a8:548::/46AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:548::
- 2a01:5a8:54c::/46AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:54c::
- 2a01:5a8:550::/46AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:550::
- 2a01:5a8:554::/46AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:554::
- 2a01:5a8:558::/46AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:558::
- 2a01:5a8:560::/46AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:560::
- 2a01:5a8:580::/47AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:580::
- 2a01:5a8:582::/48AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:582::
- 2a01:5a8:583::/48AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:583::
- 2a01:5a8:584::/48AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:584::
- 2a01:5a8:585::/48AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:585::
- 2a01:5a8:586::/48AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:586::
- 2a01:5a8:587::/48AS8866Vivacom Bulgaria EADRPKI Valid2a01:5a8:587::
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, 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.