BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
104.224.64.0/19
Announced exactly
- 104.224.64.0/19AS21769Colocation America CorporationRPKI Not found104.224.64.0
- Registry
- ARIN · United States · Oct 20, 2014
- Delegated block
- 104.224.64.0 – 104.224.95.255
Covering routes
No less-specific route covers it.
More-specific routes
- 104.224.64.0/21AS47007Colocation America CorporationRPKI Valid104.224.64.0
- 104.224.72.0/24AS194463Z CanadaRPKI Valid104.224.72.0
- 104.224.73.0/24AS194463Z CanadaRPKI Valid104.224.73.0
- 104.224.74.0/24AS212384INTERNET-3RPKI Valid104.224.74.0
- 104.224.76.0/24AS47007Colocation America CorporationRPKI Valid104.224.76.0
- 104.224.77.0/24AS400409Pulsar Networks IncRPKI Valid104.224.77.0
- 104.224.78.0/24AS194463Z CanadaRPKI Valid104.224.78.0
- 104.224.79.0/24AS11427Charter Communications IncRPKI Valid104.224.79.0
- 104.224.81.0/24AS20001Charter Communications IncRPKI Valid104.224.81.0
- 104.224.82.0/24AS47007Colocation America CorporationRPKI Valid104.224.82.0
- 104.224.83.0/24AS47007Colocation America CorporationRPKI Valid104.224.83.0
- 104.224.84.0/24AS47007Colocation America CorporationRPKI Valid104.224.84.0
- 104.224.86.0/24AS47007Colocation America CorporationRPKI Valid104.224.86.0
- 104.224.87.0/24AS212238CDNEXTRPKI Valid104.224.87.0
- 104.224.88.0/24AS401605Web Host Most, LLCRPKI Valid104.224.88.0
- 104.224.89.0/24AS47007Colocation America CorporationRPKI Valid104.224.89.0
- 104.224.91.0/24AS47007Colocation America CorporationRPKI Valid104.224.91.0
- 104.224.92.0/24AS47007Colocation America CorporationRPKI Valid104.224.92.0
- 104.224.93.0/24AS47007Colocation America CorporationRPKI Valid104.224.93.0
- 104.224.94.0/24AS47007Colocation America CorporationRPKI Valid104.224.94.0
- 104.224.95.0/24AS47007Colocation America CorporationRPKI Valid104.224.95.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.