BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
23.248.160.0/19
Announced exactly
- 23.248.160.0/19AS21859Zenlayer IncRPKI Valid23.248.160.0
- Registry
- ARIN · United States · Nov 5, 2013
- Delegated block
- 23.248.160.0 – 23.248.191.255
Covering routes
No less-specific route covers it.
More-specific routes
- 23.248.160.0/24AS21859Zenlayer IncRPKI Valid23.248.160.0
- 23.248.161.0/24AS21859Zenlayer IncRPKI Valid23.248.161.0
- 23.248.162.0/24AS135377UCLOUD INFORMATION TECHNOLOGY (HK) LIMITEDRPKI Valid23.248.162.0
- 23.248.163.0/24AS135377UCLOUD INFORMATION TECHNOLOGY (HK) LIMITEDRPKI Valid23.248.163.0
- 23.248.164.0/24AS21859Zenlayer IncRPKI Valid23.248.164.0
- 23.248.165.0/24AS21859Zenlayer IncRPKI Valid23.248.165.0
- 23.248.166.0/23AS21859Zenlayer IncRPKI Valid23.248.166.0
- 23.248.168.0/22AS21859Zenlayer IncRPKI Valid23.248.168.0
- 23.248.172.0/24AS21859Zenlayer IncRPKI Valid23.248.172.0
- 23.248.173.0/24AS21859Zenlayer IncRPKI Valid23.248.173.0
- 23.248.174.0/23AS135377UCLOUD INFORMATION TECHNOLOGY (HK) LIMITEDRPKI Valid23.248.174.0
- 23.248.176.0/23AS21859Zenlayer IncRPKI Valid23.248.176.0
- 23.248.178.0/24AS21859Zenlayer IncRPKI Valid23.248.178.0
- 23.248.179.0/24AS21859Zenlayer IncRPKI Valid23.248.179.0
- 23.248.180.0/24AS21859Zenlayer IncRPKI Valid23.248.180.0
- 23.248.181.0/24AS21859Zenlayer IncRPKI Valid23.248.181.0
- 23.248.182.0/24AS21859Zenlayer IncRPKI Valid23.248.182.0
- 23.248.183.0/24AS21859Zenlayer IncRPKI Valid23.248.183.0
- 23.248.184.0/24AS135377UCLOUD INFORMATION TECHNOLOGY (HK) LIMITEDRPKI Valid23.248.184.0
- 23.248.186.0/23AS21859Zenlayer IncRPKI Valid23.248.186.0
- 23.248.189.0/24AS21859Zenlayer IncRPKI Valid23.248.189.0
- 23.248.190.0/23AS21859Zenlayer IncRPKI Valid23.248.190.0
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 2.48.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.