BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
152.65.224.0/19
Announced exactly
- 152.65.224.0/19AS15169Google LLCRPKI Valid152.65.224.0
- Registry
- APNIC · Australia · Aug 19, 1991
- Delegated block
- 152.65.192.0 – 152.65.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 152.65.224.0/24AS15169Google LLCRPKI Valid152.65.224.0
- 152.65.225.0/24AS15169Google LLCRPKI Valid152.65.225.0
- 152.65.226.0/24AS19527Google LLCRPKI Valid152.65.226.0
- 152.65.227.0/24AS15169Google LLCRPKI Valid152.65.227.0
- 152.65.228.0/24AS19527Google LLCRPKI Valid152.65.228.0
- 152.65.229.0/24AS15169Google LLCRPKI Valid152.65.229.0
- 152.65.230.0/24AS19527Google LLCRPKI Valid152.65.230.0
- 152.65.231.0/24AS15169Google LLCRPKI Valid152.65.231.0
- 152.65.232.0/24AS15169Google LLCRPKI Valid152.65.232.0
- 152.65.233.0/24AS43515YOUTUBE YOUTUBERPKI Valid152.65.233.0
- 152.65.234.0/24AS19527Google LLCRPKI Valid152.65.234.0
- 152.65.235.0/24AS15169Google LLCRPKI Valid152.65.235.0
- 152.65.236.0/24AS15169Google LLCRPKI Valid152.65.236.0
- 152.65.237.0/24AS15169Google LLCRPKI Valid152.65.237.0
- 152.65.238.0/24AS15169Google LLCRPKI Valid152.65.238.0
- 152.65.239.0/24AS15169Google LLCRPKI Valid152.65.239.0
- 152.65.240.0/24AS43515YOUTUBE YOUTUBERPKI Valid152.65.240.0
- 152.65.241.0/24AS43515YOUTUBE YOUTUBERPKI Valid152.65.241.0
- 152.65.242.0/24AS15169Google LLCRPKI Valid152.65.242.0
- 152.65.243.0/24AS15169Google LLCRPKI Valid152.65.243.0
- 152.65.244.0/24AS19527Google LLCRPKI Valid152.65.244.0
- 152.65.245.0/24AS15169Google LLCRPKI Valid152.65.245.0
- 152.65.246.0/24AS15169Google LLCRPKI Valid152.65.246.0
- 152.65.247.0/24AS15169Google LLCRPKI Valid152.65.247.0
- 152.65.248.0/24AS19527Google LLCRPKI Valid152.65.248.0
- 152.65.249.0/24AS15169Google LLCRPKI Valid152.65.249.0
- 152.65.250.0/24AS15169Google LLCRPKI Valid152.65.250.0
- 152.65.251.0/24AS15169Google LLCRPKI Valid152.65.251.0
- 152.65.254.0/24AS43515YOUTUBE YOUTUBERPKI Valid152.65.254.0
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.