BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
64.235.224.0/19
Announced exactly
- 64.235.224.0/19AS3257GTT Communications Inc.RPKI Not found64.235.224.0
- Registry
- ARIN · United States · Sep 20, 2002
- Delegated block
- 64.235.224.0 – 64.235.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 64.235.224.0/23AS5580GTT Communications Netherlands B.V.RPKI Not found64.235.224.0
- 64.235.225.0/24AS5580GTT Communications Netherlands B.V.RPKI Not found64.235.225.0
- 64.235.227.0/24AS5580GTT Communications Netherlands B.V.RPKI Not found64.235.227.0
- 64.235.228.0/24AS5580GTT Communications Netherlands B.V.RPKI Not found64.235.228.0
- 64.235.229.0/24AS33494IHNetworks, LLCRPKI Not found64.235.229.0
- 64.235.230.0/24AS5580GTT Communications Netherlands B.V.RPKI Not found64.235.230.0
- 64.235.231.0/24AS33494IHNetworks, LLCRPKI Not found64.235.231.0
- 64.235.232.0/24AS5580GTT Communications Netherlands B.V.RPKI Not found64.235.232.0
- 64.235.234.0/23AS5580GTT Communications Netherlands B.V.RPKI Not found64.235.234.0
- 64.235.236.0/24AS5580GTT Communications Netherlands B.V.RPKI Not found64.235.236.0
- 64.235.238.0/23AS5580GTT Communications Netherlands B.V.RPKI Not found64.235.238.0
- 64.235.240.0/23AS5580GTT Communications Netherlands B.V.RPKI Not found64.235.240.0
- 64.235.242.0/24AS33494IHNetworks, LLCRPKI Not found64.235.242.0
- 64.235.243.0/24AS33494IHNetworks, LLCRPKI Not found64.235.243.0
- 64.235.244.0/23AS5580GTT Communications Netherlands B.V.RPKI Not found64.235.244.0
- 64.235.244.0/24AS5580GTT Communications Netherlands B.V.RPKI Not found64.235.244.0
- 64.235.245.0/24AS5580GTT Communications Netherlands B.V.RPKI Not found64.235.245.0
- 64.235.246.0/24AS5580GTT Communications Netherlands B.V.RPKI Not found64.235.246.0
- 64.235.247.0/24AS33494IHNetworks, LLCRPKI Not found64.235.247.0
- 64.235.248.0/24AS5580GTT Communications Netherlands B.V.RPKI Not found64.235.248.0
- 64.235.249.0/24AS5580GTT Communications Netherlands B.V.RPKI Not found64.235.249.0
- 64.235.250.0/23AS5580GTT Communications Netherlands B.V.RPKI Not found64.235.250.0
- 64.235.251.0/24AS63168T. Rowe Price Associates, INC.RPKI Not found64.235.251.0
- 64.235.252.0/22AS5580GTT Communications Netherlands B.V.RPKI Not found64.235.252.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.