BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
2001:18b8::/32
Announced exactly
- 2001:18b8::/32AS29789Reflected Networks, Inc.RPKI Valid2001:18b8::
- Registry
- ARIN · United States · Dec 1, 2003
- Delegated block
- 2001:18b8:: – 2001:18b8:ffff:ffff:ffff:ffff:ffff:ffff
Covering routes
No less-specific route covers it.
More-specific routes
- 2001:18b8:2::/48AS29789Reflected Networks, Inc.RPKI Valid2001:18b8:2::
- 2001:18b8:3::/48AS29789Reflected Networks, Inc.RPKI Valid2001:18b8:3::
- 2001:18b8:5::/48AS30361Swiftwill, Inc.RPKI Valid2001:18b8:5::
- 2001:18b8:6::/48AS29789Reflected Networks, Inc.RPKI Valid2001:18b8:6::
- 2001:18b8:7::/48AS29789Reflected Networks, Inc.RPKI Valid2001:18b8:7::
- 2001:18b8:8::/48AS29789Reflected Networks, Inc.RPKI Valid2001:18b8:8::
- 2001:18b8:9::/48AS29789Reflected Networks, Inc.RPKI Valid2001:18b8:9::
- 2001:18b8:39::/48AS29789Reflected Networks, Inc.RPKI Valid2001:18b8:39::
- 2001:18b8:42::/48AS29789Reflected Networks, Inc.RPKI Valid2001:18b8:42::
- 2001:18b8:45::/48AS29789Reflected Networks, Inc.RPKI Valid2001:18b8:45::
- 2001:18b8:49::/48AS29789Reflected Networks, Inc.RPKI Valid2001:18b8:49::
- 2001:18b8:50::/48AS29789Reflected Networks, Inc.RPKI Valid2001:18b8:50::
- 2001:18b8:51::/48AS29789Reflected Networks, Inc.RPKI Valid2001:18b8:51::
- 2001:18b8:52::/48AS29789Reflected Networks, Inc.RPKI Valid2001:18b8:52::
- 2001:18b8:53::/48AS29789Reflected Networks, Inc.RPKI Valid2001:18b8:53::
- 2001:18b8:112::/48AS30361Swiftwill, Inc.RPKI Valid2001:18b8:112::
- 2001:18b8:115::/48AS29789Reflected Networks, Inc.RPKI Valid2001:18b8:115::
- 2001:18b8:118::/48AS29789Reflected Networks, Inc.RPKI Valid2001:18b8:118::
- 2001:18b8:123::/48AS29789Reflected Networks, Inc.RPKI Valid2001:18b8:123::
- 2001:18b8:133::/48AS29789Reflected Networks, Inc.RPKI Valid2001:18b8:133::
- 2001:18b8:134::/48AS29789Reflected Networks, Inc.RPKI Valid2001:18b8:134::
- 2001:18b8:a114::/48AS29789Reflected Networks, Inc.RPKI Valid2001:18b8:a114::
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.