BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
23.248.192.0/18
Announced exactly
- 23.248.192.0/18AS138415Yancy LimitedRPKI Valid23.248.192.0
- Registry
- ARIN · United States · Sep 5, 2025
- Delegated block
- 23.248.192.0 – 23.248.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 23.248.199.0/24AS138415Yancy LimitedRPKI Valid23.248.199.0
- 23.248.202.0/24AS138415Yancy LimitedRPKI Valid23.248.202.0
- 23.248.207.0/24AS138415Yancy LimitedRPKI Valid23.248.207.0
- 23.248.209.0/24AS138415Yancy LimitedRPKI Valid23.248.209.0
- 23.248.210.0/24AS138415Yancy LimitedRPKI Valid23.248.210.0
- 23.248.211.0/24AS138415Yancy LimitedRPKI Valid23.248.211.0
- 23.248.212.0/24AS138415Yancy LimitedRPKI Valid23.248.212.0
- 23.248.217.0/24AS138415Yancy LimitedRPKI Valid23.248.217.0
- 23.248.221.0/24AS138415Yancy LimitedRPKI Valid23.248.221.0
- 23.248.222.0/24AS138415Yancy LimitedRPKI Valid23.248.222.0
- 23.248.223.0/24AS138415Yancy LimitedRPKI Valid23.248.223.0
- 23.248.224.0/24AS138415Yancy LimitedRPKI Valid23.248.224.0
- 23.248.225.0/24AS138415Yancy LimitedRPKI Valid23.248.225.0
- 23.248.226.0/24AS138415Yancy LimitedRPKI Valid23.248.226.0
- 23.248.229.0/24AS138415Yancy LimitedRPKI Valid23.248.229.0
- 23.248.230.0/24AS138415Yancy LimitedRPKI Valid23.248.230.0
- 23.248.231.0/24AS138415Yancy LimitedRPKI Valid23.248.231.0
- 23.248.232.0/24AS138415Yancy LimitedRPKI Valid23.248.232.0
- 23.248.233.0/24AS138415Yancy LimitedRPKI Valid23.248.233.0
- 23.248.234.0/24AS138415Yancy LimitedRPKI Valid23.248.234.0
- 23.248.245.0/24AS138415Yancy LimitedRPKI Valid23.248.245.0
- 23.248.246.0/24AS138195MOACK.Co.LTDRPKI Valid23.248.246.0
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 49.224.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.