BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
2804:2bb8::/32
Announced exactly
- 2804:2bb8::/32AS265171SITELBRA LTDARPKI Not found2804:2bb8::
- Registry
- LACNIC · Brazil · Dec 1, 2015
- Delegated block
- 2804:2bb8:: – 2804:2bb8:ffff:ffff:ffff:ffff:ffff:ffff
Covering routes
No less-specific route covers it.
More-specific routes
- 2804:2bb8:100::/40AS265171SITELBRA LTDARPKI Not found2804:2bb8:100::
- 2804:2bb8:300::/40AS265171SITELBRA LTDARPKI Not found2804:2bb8:300::
- 2804:2bb8:500::/40AS265171SITELBRA LTDARPKI Not found2804:2bb8:500::
- 2804:2bb8:600::/40AS265171SITELBRA LTDARPKI Not found2804:2bb8:600::
- 2804:2bb8:800::/40AS265171SITELBRA LTDARPKI Not found2804:2bb8:800::
- 2804:2bb8:900::/40AS265171SITELBRA LTDARPKI Not found2804:2bb8:900::
- 2804:2bb8:a00::/40AS265171SITELBRA LTDARPKI Not found2804:2bb8:a00::
- 2804:2bb8:b00::/40AS265171SITELBRA LTDARPKI Not found2804:2bb8:b00::
- 2804:2bb8:c00::/40AS265171SITELBRA LTDARPKI Not found2804:2bb8:c00::
- 2804:2bb8:e00::/40AS265171SITELBRA LTDARPKI Not found2804:2bb8:e00::
- 2804:2bb8:f00::/40AS265171SITELBRA LTDARPKI Not found2804:2bb8:f00::
- 2804:2bb8:1200::/40AS265171SITELBRA LTDARPKI Not found2804:2bb8:1200::
- 2804:2bb8:1300::/40AS265171SITELBRA LTDARPKI Not found2804:2bb8:1300::
- 2804:2bb8:1400::/40AS265171SITELBRA LTDARPKI Not found2804:2bb8:1400::
- 2804:2bb8:1500::/40AS265171SITELBRA LTDARPKI Not found2804:2bb8:1500::
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.