BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
190.140.0.0/16
Announced exactly
- 190.140.0.0/16AS18809Cable OndaRPKI Valid190.140.0.0
- Registry
- LACNIC · Panama · Dec 28, 2006
- Delegated block
- 190.140.0.0 – 190.140.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 190.140.0.0/17AS18809Cable OndaRPKI Valid190.140.0.0
- 190.140.0.0/18AS18809Cable OndaRPKI Valid190.140.0.0
- 190.140.0.0/20AS18809Cable OndaRPKI Valid190.140.0.0
- 190.140.4.0/22AS18809Cable OndaRPKI Valid190.140.4.0
- 190.140.8.0/22AS18809Cable OndaRPKI Valid190.140.8.0
- 190.140.12.0/22AS18809Cable OndaRPKI Valid190.140.12.0
- 190.140.16.0/22AS18809Cable OndaRPKI Valid190.140.16.0
- 190.140.24.0/22AS18809Cable OndaRPKI Valid190.140.24.0
- 190.140.31.0/24AS18809Cable OndaRPKI Valid190.140.31.0
- 190.140.32.0/20AS18809Cable OndaRPKI Valid190.140.32.0
- 190.140.47.0/24AS18809Cable OndaRPKI Valid190.140.47.0
- 190.140.50.0/24AS18809Cable OndaRPKI Valid190.140.50.0
- 190.140.51.0/24AS18809Cable OndaRPKI Valid190.140.51.0
- 190.140.52.0/22AS18809Cable OndaRPKI Valid190.140.52.0
- 190.140.56.0/22AS18809Cable OndaRPKI Valid190.140.56.0
- 190.140.60.0/23AS18809Cable OndaRPKI Valid190.140.60.0
- 190.140.64.0/19AS18809Cable OndaRPKI Valid190.140.64.0
- 190.140.68.0/22AS18809Cable OndaRPKI Valid190.140.68.0
- 190.140.72.0/22AS18809Cable OndaRPKI Valid190.140.72.0
- 190.140.76.0/22AS18809Cable OndaRPKI Valid190.140.76.0
- 190.140.80.0/20AS18809Cable OndaRPKI Valid190.140.80.0
- 190.140.80.0/22AS18809Cable OndaRPKI Valid190.140.80.0
- 190.140.88.0/22AS18809Cable OndaRPKI Valid190.140.88.0
- 190.140.96.0/20AS18809Cable OndaRPKI Valid190.140.96.0
- 190.140.105.0/24AS18809Cable OndaRPKI Valid190.140.105.0
- 190.140.109.0/24AS18809Cable OndaRPKI Valid190.140.109.0
- 190.140.112.0/20AS18809Cable OndaRPKI Valid190.140.112.0
- 190.140.112.0/21AS18809Cable OndaRPKI Valid190.140.112.0
- 190.140.112.0/22AS18809Cable OndaRPKI Valid190.140.112.0
- 190.140.119.0/24AS18809Cable OndaRPKI Valid190.140.119.0
- 190.140.128.0/17AS18809Cable OndaRPKI Valid190.140.128.0
- 190.140.128.0/19AS18809Cable OndaRPKI Valid190.140.128.0
- 190.140.131.0/24AS18809Cable OndaRPKI Valid190.140.131.0
- 190.140.136.0/22AS18809Cable OndaRPKI Valid190.140.136.0
- 190.140.140.0/22AS18809Cable OndaRPKI Valid190.140.140.0
- 190.140.148.0/24AS18809Cable OndaRPKI Valid190.140.148.0
- 190.140.158.0/23AS18809Cable OndaRPKI Valid190.140.158.0
- 190.140.160.0/22AS18809Cable OndaRPKI Valid190.140.160.0
- 190.140.168.0/24AS18809Cable OndaRPKI Valid190.140.168.0
- 190.140.169.0/24AS18809Cable OndaRPKI Valid190.140.169.0
- 190.140.170.0/23AS18809Cable OndaRPKI Valid190.140.170.0
- 190.140.172.0/22AS18809Cable OndaRPKI Valid190.140.172.0
- 190.140.176.0/24AS18809Cable OndaRPKI Valid190.140.176.0
- 190.140.178.0/23AS18809Cable OndaRPKI Valid190.140.178.0
- 190.140.184.0/23AS18809Cable OndaRPKI Valid190.140.184.0
- 190.140.184.0/24AS18809Cable OndaRPKI Valid190.140.184.0
- 190.140.188.0/24AS18809Cable OndaRPKI Valid190.140.188.0
- 190.140.189.0/24AS18809Cable OndaRPKI Valid190.140.189.0
- 190.140.191.0/24AS18809Cable OndaRPKI Valid190.140.191.0
- 190.140.192.0/19AS18809Cable OndaRPKI Valid190.140.192.0
- 190.140.192.0/22AS18809Cable OndaRPKI Valid190.140.192.0
- 190.140.204.0/22AS18809Cable OndaRPKI Valid190.140.204.0
- 190.140.208.0/22AS18809Cable OndaRPKI Valid190.140.208.0
- 190.140.218.0/24AS18809Cable OndaRPKI Valid190.140.218.0
- 190.140.224.0/23AS18809Cable OndaRPKI Valid190.140.224.0
- 190.140.226.0/23AS18809Cable OndaRPKI Valid190.140.226.0
- 190.140.230.0/23AS18809Cable OndaRPKI Valid190.140.230.0
- 190.140.236.0/22AS18809Cable OndaRPKI Valid190.140.236.0
- 190.140.248.0/22AS18809Cable OndaRPKI Valid190.140.248.0
- 190.140.250.0/24AS14709Cable OndaRPKI Valid190.140.250.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.