BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
2620:11a:a000::/40
Announced exactly
- 2620:11a:a000::/40AS43515Google Ireland LimitedRPKI Valid2620:11a:a000::
- Registry
- ARIN · United States · Jul 3, 2014
- Delegated block
- 2620:11a:a000:: – 2620:11a:a0ff:ffff:ffff:ffff:ffff:ffff
Covering routes
No less-specific route covers it.
More-specific routes
- 2620:11a:a017::/48AS36040Google LLCRPKI Valid2620:11a:a017::
- 2620:11a:a01c::/48AS36040Google LLCRPKI Valid2620:11a:a01c::
- 2620:11a:a024::/48AS36040Google LLCRPKI Valid2620:11a:a024::
- 2620:11a:a025::/48AS36040Google LLCRPKI Valid2620:11a:a025::
- 2620:11a:a036::/48AS36040Google LLCRPKI Valid2620:11a:a036::
- 2620:11a:a037::/48AS36040Google LLCRPKI Valid2620:11a:a037::
- 2620:11a:a038::/48AS36040Google LLCRPKI Valid2620:11a:a038::
- 2620:11a:a039::/48AS36040Google LLCRPKI Valid2620:11a:a039::
- 2620:11a:a03a::/48AS36040Google LLCRPKI Valid2620:11a:a03a::
- 2620:11a:a03b::/48AS36040Google LLCRPKI Valid2620:11a:a03b::
- 2620:11a:a03c::/48AS36040Google LLCRPKI Valid2620:11a:a03c::
- 2620:11a:a03d::/48AS36040Google LLCRPKI Valid2620:11a:a03d::
- 2620:11a:a03e::/48AS36040Google LLCRPKI Valid2620:11a:a03e::
- 2620:11a:a040::/48AS36040Google LLCRPKI Valid2620:11a:a040::
- 2620:11a:a041::/48AS36040Google LLCRPKI Valid2620:11a:a041::
- 2620:11a:a042::/48AS36040Google LLCRPKI Valid2620:11a:a042::
- 2620:11a:a043::/48AS36040Google LLCRPKI Valid2620:11a:a043::
- 2620:11a:a044::/48AS36040Google LLCRPKI Valid2620:11a:a044::
- 2620:11a:a045::/48AS36040Google LLCRPKI Valid2620:11a:a045::
- 2620:11a:a046::/48AS36040Google LLCRPKI Valid2620:11a:a046::
- 2620:11a:a047::/48AS36040Google LLCRPKI Valid2620:11a:a047::
- 2620:11a:a048::/48AS36040Google LLCRPKI Valid2620:11a:a048::
- 2620:11a:a049::/48AS36040Google LLCRPKI Valid2620:11a:a049::
- 2620:11a:a04a::/48AS36040Google LLCRPKI Valid2620:11a:a04a::
- 2620:11a:a04b::/48AS36040Google LLCRPKI Valid2620:11a:a04b::
- 2620:11a:a04c::/48AS36040Google LLCRPKI Valid2620:11a:a04c::
- 2620:11a:a04d::/48AS36040Google LLCRPKI Valid2620:11a:a04d::
- 2620:11a:a04e::/48AS36040Google LLCRPKI Valid2620:11a:a04e::
- 2620:11a:a04f::/48AS36040Google LLCRPKI Valid2620:11a:a04f::
- 2620:11a:a050::/48AS36040Google LLCRPKI Valid2620:11a:a050::
- 2620:11a:a051::/48AS36040Google LLCRPKI Valid2620:11a:a051::
- 2620:11a:a055::/48AS36040Google LLCRPKI Valid2620:11a:a055::
- 2620:11a:a056::/48AS36040Google LLCRPKI Valid2620:11a:a056::
- 2620:11a:a059::/48AS36040Google LLCRPKI Valid2620:11a:a059::
- 2620:11a:a05a::/48AS36040Google LLCRPKI Valid2620:11a:a05a::
- 2620:11a:a05b::/48AS36040Google LLCRPKI Valid2620:11a:a05b::
- 2620:11a:a05c::/48AS36040Google LLCRPKI Valid2620:11a:a05c::
- 2620:11a:a05d::/48AS36040Google LLCRPKI Valid2620:11a:a05d::
- 2620:11a:a05f::/48AS36040Google LLCRPKI Valid2620:11a:a05f::
- 2620:11a:a060::/48AS36040Google LLCRPKI Valid2620:11a:a060::
- 2620:11a:a061::/48AS36040Google LLCRPKI Valid2620:11a:a061::
- 2620:11a:a062::/48AS36040Google LLCRPKI Valid2620:11a:a062::
- 2620:11a:a063::/48AS36040Google LLCRPKI Valid2620:11a:a063::
- 2620:11a:a064::/48AS36040Google LLCRPKI Valid2620:11a:a064::
- 2620:11a:a065::/48AS36040Google LLCRPKI Valid2620:11a:a065::
- 2620:11a:a066::/48AS36040Google LLCRPKI Valid2620:11a:a066::
- 2620:11a:a067::/48AS36040Google LLCRPKI Valid2620:11a:a067::
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.