BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
66.97.224.0/19
Announced exactly
- 66.97.224.0/19AS26794Dakota Carrier NetworkRPKI Not found66.97.224.0
- Registry
- ARIN · United States · Jan 23, 2003
- Delegated block
- 66.97.224.0 – 66.97.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 66.97.226.0/24AS18780Reservation Telephone Coop.RPKI Not found66.97.226.0
- 66.97.227.0/24AS18780Reservation Telephone Coop.RPKI Not found66.97.227.0
- 66.97.228.0/24AS18780Reservation Telephone Coop.RPKI Not found66.97.228.0
- 66.97.229.0/24AS18780Reservation Telephone Coop.RPKI Not found66.97.229.0
- 66.97.233.0/24AS18780Reservation Telephone Coop.RPKI Not found66.97.233.0
- 66.97.235.0/24AS18780Reservation Telephone Coop.RPKI Not found66.97.235.0
- 66.97.236.0/24AS18780Reservation Telephone Coop.RPKI Not found66.97.236.0
- 66.97.237.0/24AS394321National Information Solutions Cooperative, IncRPKI Valid66.97.237.0
- 66.97.239.0/24AS394321National Information Solutions Cooperative, IncRPKI Not found66.97.239.0
- 66.97.240.0/24AS26794Dakota Carrier NetworkRPKI Not found66.97.240.0
- 66.97.241.0/24AS18780Reservation Telephone Coop.RPKI Not found66.97.241.0
- 66.97.242.0/24AS18780Reservation Telephone Coop.RPKI Not found66.97.242.0
- 66.97.246.0/24AS18780Reservation Telephone Coop.RPKI Not found66.97.246.0
- 66.97.247.0/24AS18780Reservation Telephone Coop.RPKI Not found66.97.247.0
- 66.97.248.0/24AS18780Reservation Telephone Coop.RPKI Not found66.97.248.0
- 66.97.251.0/24AS18780Reservation Telephone Coop.RPKI Not found66.97.251.0
- 66.97.253.0/24AS11138BEK Communications CooperativeRPKI Not found66.97.253.0
- 66.97.255.0/24AS11138BEK Communications CooperativeRPKI Not found66.97.255.0
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 158.36.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.