BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
2804:18:800::/37
Announced exactly
- 2804:18:800::/37AS26599TELEFONICA BRASIL S.ARPKI Not found2804:18:800::
- Registry
- LACNIC · Brazil · Apr 9, 2009
- Delegated block
- 2804:18:: – 2804:18:ffff:ffff:ffff:ffff:ffff:ffff
Covering routes
No less-specific route covers it.
More-specific routes
- 2804:18:800::/44AS26599TELEFONICA BRASIL S.ARPKI Not found2804:18:800::
- 2804:18:800::/45AS26599TELEFONICA BRASIL S.ARPKI Not found2804:18:800::
- 2804:18:820::/45AS10429TELEFONICA BRASIL S.ARPKI Not found2804:18:820::
- 2804:18:828::/45AS10429TELEFONICA BRASIL S.ARPKI Not found2804:18:828::
- 2804:18:830::/45AS26599TELEFONICA BRASIL S.ARPKI Not found2804:18:830::
- 2804:18:838::/45AS26599TELEFONICA BRASIL S.ARPKI Not found2804:18:838::
- 2804:18:840::/45AS10429TELEFONICA BRASIL S.ARPKI Not found2804:18:840::
- 2804:18:848::/45AS10429TELEFONICA BRASIL S.ARPKI Not found2804:18:848::
- 2804:18:860::/45AS10429TELEFONICA BRASIL S.ARPKI Not found2804:18:860::
- 2804:18:868::/45AS10429TELEFONICA BRASIL S.ARPKI Not found2804:18:868::
- 2804:18:880::/45AS26599TELEFONICA BRASIL S.ARPKI Not found2804:18:880::
- 2804:18:888::/45AS26599TELEFONICA BRASIL S.ARPKI Not found2804:18:888::
- 2804:18:890::/45AS26599TELEFONICA BRASIL S.ARPKI Not found2804:18:890::
- 2804:18:898::/45AS26599TELEFONICA BRASIL S.ARPKI Not found2804:18:898::
- 2804:18:8a0::/45AS26599TELEFONICA BRASIL S.ARPKI Not found2804:18:8a0::
- 2804:18:8a8::/45AS26599TELEFONICA BRASIL S.ARPKI Not found2804:18:8a8::
- 2804:18:8b0::/45AS26599TELEFONICA BRASIL S.ARPKI Not found2804:18:8b0::
- 2804:18:8b8::/45AS26599TELEFONICA BRASIL S.ARPKI Not found2804:18:8b8::
- 2804:18:8c0::/45AS26599TELEFONICA BRASIL S.ARPKI Not found2804:18:8c0::
- 2804:18:8c8::/45AS26599TELEFONICA BRASIL S.ARPKI Not found2804:18:8c8::
- 2804:18:8d0::/45AS26599TELEFONICA BRASIL S.ARPKI Not found2804:18:8d0::
- 2804:18:8d8::/45AS26599TELEFONICA BRASIL S.ARPKI Not found2804:18:8d8::
- 2804:18:8f0::/45AS10429TELEFONICA BRASIL S.ARPKI Not found2804:18:8f0::
- 2804:18:8f8::/45AS10429TELEFONICA BRASIL S.ARPKI Not found2804:18:8f8::
- 2804:18:900::/45AS26599TELEFONICA BRASIL S.ARPKI Not found2804:18:900::
- 2804:18:908::/45AS26599TELEFONICA BRASIL S.ARPKI Not found2804:18:908::
- 2804:18:920::/45AS26599TELEFONICA BRASIL S.ARPKI Not found2804:18:920::
- 2804:18:928::/45AS26599TELEFONICA BRASIL S.ARPKI Not found2804:18:928::
- 2804:18:930::/45AS26599TELEFONICA BRASIL S.ARPKI Not found2804:18:930::
- 2804:18:938::/45AS26599TELEFONICA BRASIL S.ARPKI Not found2804:18:938::
- 2804:18:940::/45AS10429TELEFONICA BRASIL S.ARPKI Not found2804:18:940::
- 2804:18:948::/45AS10429TELEFONICA BRASIL S.ARPKI Not found2804:18:948::
- 2804:18:960::/45AS10429TELEFONICA BRASIL S.ARPKI Not found2804:18:960::
- 2804:18:968::/45AS10429TELEFONICA BRASIL S.ARPKI Not found2804:18:968::
- 2804:18:990::/44AS26599TELEFONICA BRASIL S.ARPKI Not found2804:18:990::
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 193.166.0.0/15. 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.