BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
8.224.0.0/14
Announced exactly
- 8.224.0.0/14AS3356Level 3 Parent, LLCRPKI Not found8.224.0.0
- Registry
- ARIN · United States · Dec 1, 1992
- Delegated block
- 8.224.0.0 – 8.227.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 8.224.5.0/24AS14785BCBSVTRPKI Not found8.224.5.0
- 8.224.10.0/24AS15359Datto, LLCRPKI Not found8.224.10.0
- 8.224.11.0/24AS36746SymQuest Group. IncRPKI Not found8.224.11.0
- 8.224.32.0/24AS13602I-Evolve Technology ServicesRPKI Not found8.224.32.0
- 8.224.33.0/24AS13602I-Evolve Technology ServicesRPKI Not found8.224.33.0
- 8.224.34.0/24AS13602I-Evolve Technology ServicesRPKI Not found8.224.34.0
- 8.224.49.0/24AS32696Tri State Voice & Data, LLCRPKI Valid8.224.49.0
- 8.224.99.0/24AS26647Movers Specialty ServiceRPKI Not found8.224.99.0
- 8.224.179.0/24AS19951Measurement IncorporatedRPKI Not found8.224.179.0
- 8.225.3.0/24AS23089Hotwire CommunicationsRPKI Not found8.225.3.0
- 8.225.96.0/23AS46450Pilot Fiber, Inc.RPKI Not found8.225.96.0
- 8.225.161.0/24AS36162CONCERGENT, LLCRPKI Not found8.225.161.0
- 8.225.179.0/24AS4966Casella Waste System IncRPKI Not found8.225.179.0
- 8.225.188.0/24AS23089Hotwire CommunicationsRPKI Not found8.225.188.0
- 8.225.193.0/24AS46887Crown Castle Fiber LLCRPKI Not found8.225.193.0
- 8.225.194.0/24AS30372Crown Castle Fiber LLCRPKI Not found8.225.194.0
- 8.225.224.0/24AS30334The Park National CorporationRPKI Not found8.225.224.0
- 8.225.232.0/24AS62821MNX Solutions LLCRPKI Not found8.225.232.0
- 8.225.238.0/24AS13747DONEGAL MUTUAL INSURANCERPKI Not found8.225.238.0
- 8.225.240.0/22AS2731Infinity Fiber LLCRPKI Valid8.225.240.0
- 8.226.0.0/23AS396238FairlawnGig.netRPKI Not found8.226.0.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.