BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
2604:fa00::/32
Announced exactly
- 2604:fa00::/32AS32278Getwireless.netRPKI Not found2604:fa00::
- Registry
- ARIN · United States · Dec 6, 2010
- Delegated block
- 2604:fa00:: – 2604:fa00:ffff:ffff:ffff:ffff:ffff:ffff
Covering routes
No less-specific route covers it.
More-specific routes
- 2604:fa00:102::/48AS32278Getwireless.netRPKI Not found2604:fa00:102::
- 2604:fa00:104::/48AS32278Getwireless.netRPKI Not found2604:fa00:104::
- 2604:fa00:105::/48AS32278Getwireless.netRPKI Not found2604:fa00:105::
- 2604:fa00:107::/48AS32278Getwireless.netRPKI Not found2604:fa00:107::
- 2604:fa00:108::/48AS32278Getwireless.netRPKI Not found2604:fa00:108::
- 2604:fa00:109::/48AS32278Getwireless.netRPKI Not found2604:fa00:109::
- 2604:fa00:10c::/48AS32278Getwireless.netRPKI Not found2604:fa00:10c::
- 2604:fa00:10d::/48AS32278Getwireless.netRPKI Not found2604:fa00:10d::
- 2604:fa00:10e::/48AS32278Getwireless.netRPKI Not found2604:fa00:10e::
- 2604:fa00:111::/48AS32278Getwireless.netRPKI Not found2604:fa00:111::
- 2604:fa00:116::/48AS32278Getwireless.netRPKI Not found2604:fa00:116::
- 2604:fa00:11a::/48AS32278Getwireless.netRPKI Not found2604:fa00:11a::
- 2604:fa00:11d::/48AS32278Getwireless.netRPKI Not found2604:fa00:11d::
- 2604:fa00:120::/48AS32278Getwireless.netRPKI Not found2604:fa00:120::
- 2604:fa00:121::/48AS32278Getwireless.netRPKI Not found2604:fa00:121::
- 2604:fa00:123::/48AS32278Getwireless.netRPKI Not found2604:fa00:123::
- 2604:fa00:124::/48AS32278Getwireless.netRPKI Not found2604:fa00:124::
- 2604:fa00:125::/48AS32278Getwireless.netRPKI Not found2604:fa00:125::
- 2604:fa00:127::/48AS32278Getwireless.netRPKI Not found2604:fa00:127::
- 2604:fa00:fffe::/48AS32278Getwireless.netRPKI Not found2604:fa00:fffe::
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.