BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
2804:10a0::/32
Announced exactly
- 2804:10a0::/32AS28173Dinamica Telecomunicacoes LtdaRPKI Valid2804:10a0::
- Registry
- LACNIC · Brazil · Oct 10, 2013
- Delegated block
- 2804:10a0:: – 2804:10a0:ffff:ffff:ffff:ffff:ffff:ffff
Covering routes
No less-specific route covers it.
More-specific routes
- 2804:10a0::/33AS28173Dinamica Telecomunicacoes LtdaRPKI Valid2804:10a0::
- 2804:10a0::/34AS28173Dinamica Telecomunicacoes LtdaRPKI Valid2804:10a0::
- 2804:10a0::/35AS28173Dinamica Telecomunicacoes LtdaRPKI Valid2804:10a0::
- 2804:10a0:2::/48AS28173Dinamica Telecomunicacoes LtdaRPKI Valid2804:10a0:2::
- 2804:10a0:10::/44AS28173Dinamica Telecomunicacoes LtdaRPKI Valid2804:10a0:10::
- 2804:10a0:11::/48AS28173Dinamica Telecomunicacoes LtdaRPKI Valid2804:10a0:11::
- 2804:10a0:40::/44AS28173Dinamica Telecomunicacoes LtdaRPKI Valid2804:10a0:40::
- 2804:10a0:50::/44AS28173Dinamica Telecomunicacoes LtdaRPKI Valid2804:10a0:50::
- 2804:10a0:51::/48AS28173Dinamica Telecomunicacoes LtdaRPKI Valid2804:10a0:51::
- 2804:10a0:52::/48AS28173Dinamica Telecomunicacoes LtdaRPKI Valid2804:10a0:52::
- 2804:10a0:54::/48AS28173Dinamica Telecomunicacoes LtdaRPKI Valid2804:10a0:54::
- 2804:10a0:56::/48AS28173Dinamica Telecomunicacoes LtdaRPKI Valid2804:10a0:56::
- 2804:10a0:57::/48AS28173Dinamica Telecomunicacoes LtdaRPKI Valid2804:10a0:57::
- 2804:10a0:59::/48AS28173Dinamica Telecomunicacoes LtdaRPKI Valid2804:10a0:59::
- 2804:10a0:5d::/48AS28173Dinamica Telecomunicacoes LtdaRPKI Valid2804:10a0:5d::
- 2804:10a0:60::/44AS28173Dinamica Telecomunicacoes LtdaRPKI Valid2804:10a0:60::
- 2804:10a0:70::/48AS28173Dinamica Telecomunicacoes LtdaRPKI Valid2804:10a0:70::
- 2804:10a0:80::/42AS28173Dinamica Telecomunicacoes LtdaRPKI Valid2804:10a0:80::
- 2804:10a0:c8::/48AS28173Dinamica Telecomunicacoes LtdaRPKI Valid2804:10a0:c8::
- 2804:10a0:ca::/48AS28173Dinamica Telecomunicacoes LtdaRPKI Valid2804:10a0:ca::
- 2804:10a0:f1::/48AS28173Dinamica Telecomunicacoes LtdaRPKI Valid2804:10a0:f1::
- 2804:10a0:f3::/48AS28173Dinamica Telecomunicacoes LtdaRPKI Valid2804:10a0:f3::
- 2804:10a0:200::/45AS28173Dinamica Telecomunicacoes LtdaRPKI Valid2804:10a0:200::
- 2804:10a0:218::/46AS28173Dinamica Telecomunicacoes LtdaRPKI Valid2804:10a0:218::
- 2804:10a0:220::/46AS28173Dinamica Telecomunicacoes LtdaRPKI Valid2804:10a0:220::
- 2804:10a0:230::/44AS28173Dinamica Telecomunicacoes LtdaRPKI Valid2804:10a0:230::
- 2804:10a0:245::/48AS28173Dinamica Telecomunicacoes LtdaRPKI Valid2804:10a0:245::
- 2804:10a0:248::/46AS28173Dinamica Telecomunicacoes LtdaRPKI Valid2804:10a0:248::
- 2804:10a0:249::/48AS28173Dinamica Telecomunicacoes LtdaRPKI Valid2804:10a0:249::
- 2804:10a0:260::/44AS28173Dinamica Telecomunicacoes LtdaRPKI Valid2804:10a0:260::
- 2804:10a0:270::/44AS28173Dinamica Telecomunicacoes LtdaRPKI Valid2804:10a0:270::
- 2804:10a0:2000::/35AS28173Dinamica Telecomunicacoes LtdaRPKI Valid2804:10a0:2000::
- 2804:10a0:3000::/44AS28173Dinamica Telecomunicacoes LtdaRPKI Valid2804:10a0:3000::
- 2804:10a0:3010::/44AS28173Dinamica Telecomunicacoes LtdaRPKI Valid2804:10a0:3010::
- 2804:10a0:3020::/44AS28173Dinamica Telecomunicacoes LtdaRPKI Valid2804:10a0:3020::
- 2804:10a0:3030::/44AS28173Dinamica Telecomunicacoes LtdaRPKI Valid2804:10a0:3030::
- 2804:10a0:4000::/34AS28173Dinamica Telecomunicacoes LtdaRPKI Valid2804:10a0:4000::
- 2804:10a0:4000::/35AS28173Dinamica Telecomunicacoes LtdaRPKI Valid2804:10a0:4000::
- 2804:10a0:4000::/44AS28173Dinamica Telecomunicacoes LtdaRPKI Valid2804:10a0:4000::
- 2804:10a0:4010::/44AS28173Dinamica Telecomunicacoes LtdaRPKI Valid2804:10a0:4010::
- 2804:10a0:6000::/35AS28173Dinamica Telecomunicacoes LtdaRPKI Valid2804:10a0:6000::
- 2804:10a0:8000::/33AS28173Dinamica Telecomunicacoes LtdaRPKI Valid2804:10a0:8000::
- 2804:10a0:8000::/34AS28173Dinamica Telecomunicacoes LtdaRPKI Valid2804:10a0:8000::
- 2804:10a0:8000::/35AS28173Dinamica Telecomunicacoes LtdaRPKI Valid2804:10a0:8000::
- 2804:10a0:8060::/44AS28173Dinamica Telecomunicacoes LtdaRPKI Valid2804:10a0:8060::
- 2804:10a0:8070::/44AS28173Dinamica Telecomunicacoes LtdaRPKI Valid2804:10a0:8070::
- 2804:10a0:8090::/44AS28173Dinamica Telecomunicacoes LtdaRPKI Valid2804:10a0:8090::
- 2804:10a0:80c0::/44AS28173Dinamica Telecomunicacoes LtdaRPKI Valid2804:10a0:80c0::
- 2804:10a0:a000::/35AS28173Dinamica Telecomunicacoes LtdaRPKI Valid2804:10a0:a000::
- 2804:10a0:c000::/34AS28173Dinamica Telecomunicacoes LtdaRPKI Valid2804:10a0:c000::
- 2804:10a0:c000::/35AS28173Dinamica Telecomunicacoes LtdaRPKI Valid2804:10a0:c000::
- 2804:10a0:c000::/40AS28173Dinamica Telecomunicacoes LtdaRPKI Valid2804:10a0:c000::
- 2804:10a0:e000::/35AS28173Dinamica Telecomunicacoes LtdaRPKI Valid2804:10a0:e000::
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 158.36.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.