BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
2a00:4800::/29
Announced exactly
- 2a00:4800::/29AS8717A1 Bulgaria EADRPKI Valid2a00:4800::
- Registry
- RIPE NCC · Bulgaria · Dec 8, 2010
- Delegated block
- 2a00:4800:: – 2a00:4807:ffff:ffff:ffff:ffff:ffff:ffff
Covering routes
No less-specific route covers it.
More-specific routes
- 2a00:4800:a0::/44AS13124A1 Bulgaria EADRPKI Valid2a00:4800:a0::
- 2a00:4800:e0::/44AS13124A1 Bulgaria EADRPKI Valid2a00:4800:e0::
- 2a00:4800:1a0::/44AS13124A1 Bulgaria EADRPKI Valid2a00:4800:1a0::
- 2a00:4802:220::/44AS13124A1 Bulgaria EADRPKI Valid2a00:4802:220::
- 2a00:4802:260::/44AS13124A1 Bulgaria EADRPKI Valid2a00:4802:260::
- 2a00:4802:280::/44AS13124A1 Bulgaria EADRPKI Valid2a00:4802:280::
- 2a00:4802:2a0::/44AS13124A1 Bulgaria EADRPKI Valid2a00:4802:2a0::
- 2a00:4802:2c0::/44AS13124A1 Bulgaria EADRPKI Valid2a00:4802:2c0::
- 2a00:4802:2e0::/44AS13124A1 Bulgaria EADRPKI Valid2a00:4802:2e0::
- 2a00:4802:300::/44AS13124A1 Bulgaria EADRPKI Valid2a00:4802:300::
- 2a00:4802:320::/44AS13124A1 Bulgaria EADRPKI Valid2a00:4802:320::
- 2a00:4802:350::/44AS13124A1 Bulgaria EADRPKI Valid2a00:4802:350::
- 2a00:4802:360::/44AS13124A1 Bulgaria EADRPKI Valid2a00:4802:360::
- 2a00:4802:380::/44AS13124A1 Bulgaria EADRPKI Valid2a00:4802:380::
- 2a00:4802:3a0::/44AS13124A1 Bulgaria EADRPKI Valid2a00:4802:3a0::
- 2a00:4802:a00::/40AS13124A1 Bulgaria EADRPKI Valid2a00:4802:a00::
- 2a00:4802:a00::/44AS13124A1 Bulgaria EADRPKI Valid2a00:4802:a00::
- 2a00:4802:a20::/44AS13124A1 Bulgaria EADRPKI Valid2a00:4802:a20::
- 2a00:4802:a40::/44AS13124A1 Bulgaria EADRPKI Valid2a00:4802:a40::
- 2a00:4802:a60::/44AS13124A1 Bulgaria EADRPKI Valid2a00:4802:a60::
- 2a00:4802:a80::/44AS13124A1 Bulgaria EADRPKI Valid2a00:4802:a80::
- 2a00:4802:aa0::/44AS13124A1 Bulgaria EADRPKI Valid2a00:4802:aa0::
- 2a00:4802:d00::/44AS13124A1 Bulgaria EADRPKI Valid2a00:4802:d00::
- 2a00:4802:e00::/40AS13124A1 Bulgaria EADRPKI Valid2a00:4802:e00::
- 2a00:4802:e00::/44AS13124A1 Bulgaria EADRPKI Valid2a00:4802:e00::
- 2a00:4802:e10::/44AS13124A1 Bulgaria EADRPKI Valid2a00:4802:e10::
- 2a00:4802:e20::/44AS13124A1 Bulgaria EADRPKI Valid2a00:4802:e20::
- 2a00:4802:e30::/44AS13124A1 Bulgaria EADRPKI Valid2a00:4802:e30::
- 2a00:4802:1000::/44AS13124A1 Bulgaria EADRPKI Valid2a00:4802:1000::
- 2a00:4802:1800::/44AS13124A1 Bulgaria EADRPKI Valid2a00:4802:1800::
- 2a00:4802:1a00::/40AS13124A1 Bulgaria EADRPKI Valid2a00:4802:1a00::
- 2a00:4802:1c00::/44AS13124A1 Bulgaria EADRPKI Valid2a00:4802:1c00::
- 2a00:4802:1e00::/44AS13124A1 Bulgaria EADRPKI Valid2a00:4802:1e00::
- 2a00:4802:1e10::/44AS13124A1 Bulgaria EADRPKI Valid2a00:4802:1e10::
- 2a00:4802:1e20::/44AS13124A1 Bulgaria EADRPKI Valid2a00:4802:1e20::
- 2a00:4802:1e30::/44AS13124A1 Bulgaria EADRPKI Valid2a00:4802:1e30::
- 2a00:4802:1e40::/44AS13124A1 Bulgaria EADRPKI Valid2a00:4802:1e40::
- 2a00:4802:1e50::/44AS13124A1 Bulgaria EADRPKI Valid2a00:4802:1e50::
- 2a00:4802:2200::/44AS13124A1 Bulgaria EADRPKI Valid2a00:4802:2200::
- 2a00:4802:2600::/44AS13124A1 Bulgaria EADRPKI Valid2a00:4802:2600::
- 2a00:4802:2610::/44AS13124A1 Bulgaria EADRPKI Valid2a00:4802:2610::
- 2a00:4802:2800::/44AS13124A1 Bulgaria EADRPKI Valid2a00:4802:2800::
- 2a00:4802:2a00::/44AS13124A1 Bulgaria EADRPKI Valid2a00:4802:2a00::
- 2a00:4802:2c00::/44AS13124A1 Bulgaria EADRPKI Valid2a00:4802:2c00::
- 2a00:4802:2c10::/44AS13124A1 Bulgaria EADRPKI Valid2a00:4802:2c10::
- 2a00:4802:2c20::/44AS13124A1 Bulgaria EADRPKI Valid2a00:4802:2c20::
- 2a00:4802:2c30::/44AS13124A1 Bulgaria EADRPKI Valid2a00:4802:2c30::
- 2a00:4802:2e00::/44AS13124A1 Bulgaria EADRPKI Valid2a00:4802:2e00::
- 2a00:4802:2e10::/44AS13124A1 Bulgaria EADRPKI Valid2a00:4802:2e10::
- 2a00:4802:2e20::/44AS13124A1 Bulgaria EADRPKI Valid2a00:4802:2e20::
- 2a00:4802:2e30::/44AS13124A1 Bulgaria EADRPKI Valid2a00:4802:2e30::
- 2a00:4802:2e40::/44AS13124A1 Bulgaria EADRPKI Valid2a00:4802:2e40::
- 2a00:4802:3000::/44AS13124A1 Bulgaria EADRPKI Valid2a00:4802:3000::
- 2a00:4802:3010::/44AS13124A1 Bulgaria EADRPKI Valid2a00:4802:3010::
- 2a00:4802:3020::/44AS13124A1 Bulgaria EADRPKI Valid2a00:4802:3020::
- 2a00:4802:3200::/44AS13124A1 Bulgaria EADRPKI Valid2a00:4802:3200::
- 2a00:4802:3400::/44AS13124A1 Bulgaria EADRPKI Valid2a00:4802:3400::
- 2a00:4802:3800::/44AS13124A1 Bulgaria EADRPKI Valid2a00:4802:3800::
- 2a00:4802:3c00::/44AS13124A1 Bulgaria EADRPKI Valid2a00:4802:3c00::
- 2a00:4802:3e00::/44AS13124A1 Bulgaria EADRPKI Valid2a00:4802:3e00::
- 2a00:4802:3e10::/44AS13124A1 Bulgaria EADRPKI Valid2a00:4802:3e10::
- 2a00:4802:3e20::/44AS13124A1 Bulgaria EADRPKI Valid2a00:4802:3e20::
- 2a00:4802:4a00::/44AS13124A1 Bulgaria EADRPKI Valid2a00:4802:4a00::
- 2a00:4802:4a10::/44AS13124A1 Bulgaria EADRPKI Valid2a00:4802:4a10::
- 2a00:4802:4e00::/44AS13124A1 Bulgaria EADRPKI Valid2a00:4802:4e00::
- 2a00:4802:4e20::/44AS13124A1 Bulgaria EADRPKI Valid2a00:4802:4e20::
- 2a00:4802:5000::/44AS13124A1 Bulgaria EADRPKI Valid2a00:4802:5000::
- 2a00:4802:5200::/44AS13124A1 Bulgaria EADRPKI Valid2a00:4802:5200::
- 2a00:4804:800::/37AS29580A1 Bulgaria EADRPKI Valid2a00:4804:800::
- 2a00:4804:4800::/37AS29580A1 Bulgaria EADRPKI Valid2a00:4804:4800::
- 2a00:4804:8800::/37AS29580A1 Bulgaria EADRPKI Valid2a00:4804:8800::
- 2a00:4804:9000::/37AS29580A1 Bulgaria EADRPKI Valid2a00:4804:9000::
- 2a00:4804:9800::/37AS29580A1 Bulgaria EADRPKI Valid2a00:4804:9800::
- 2a00:4804:a000::/37AS29580A1 Bulgaria EADRPKI Valid2a00:4804:a000::
- 2a00:4804:a800::/37AS29580A1 Bulgaria EADRPKI Valid2a00:4804:a800::
- 2a00:4804:b000::/37AS29580A1 Bulgaria EADRPKI Valid2a00:4804:b000::
- 2a00:4804:b800::/37AS29580A1 Bulgaria EADRPKI Valid2a00:4804:b800::
- 2a00:4804:d000::/37AS29580A1 Bulgaria EADRPKI Valid2a00:4804:d000::
- 2a00:4804:d800::/37AS29580A1 Bulgaria EADRPKI Valid2a00:4804:d800::
- 2a00:4804:e000::/37AS29580A1 Bulgaria EADRPKI Valid2a00:4804:e000::
- 2a00:4804:e800::/37AS29580A1 Bulgaria EADRPKI Valid2a00:4804:e800::
- 2a00:4804:f000::/37AS29580A1 Bulgaria EADRPKI Valid2a00:4804:f000::
- 2a00:4804:f800::/37AS29580A1 Bulgaria EADRPKI Valid2a00:4804:f800::
- 2a00:4805:1000::/37AS29580A1 Bulgaria EADRPKI Valid2a00:4805:1000::
- 2a00:4805:1800::/37AS29580A1 Bulgaria EADRPKI Valid2a00:4805:1800::
- 2a00:4805:8000::/37AS29580A1 Bulgaria EADRPKI Valid2a00:4805:8000::
- 2a00:4805:8800::/37AS29580A1 Bulgaria EADRPKI Valid2a00:4805:8800::
- 2a00:4805:9000::/37AS29580A1 Bulgaria EADRPKI Valid2a00:4805:9000::
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.