BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
168.226.0.0/16
Announced exactly
- 168.226.0.0/16AS22927Telefonica de ArgentinaRPKI Valid168.226.0.0
- Registry
- LACNIC · Argentina · Aug 22, 1994
- Delegated block
- 168.226.0.0 – 168.226.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 168.226.35.0/24AS22927Telefonica de ArgentinaRPKI Valid168.226.35.0
- 168.226.39.0/24AS4926Telefonica de ArgentinaRPKI Valid168.226.39.0
- 168.226.40.0/24AS4926Telefonica de ArgentinaRPKI Valid168.226.40.0
- 168.226.41.0/24AS4926Telefonica de ArgentinaRPKI Valid168.226.41.0
- 168.226.42.0/24AS4926Telefonica de ArgentinaRPKI Valid168.226.42.0
- 168.226.43.0/24AS4926Telefonica de ArgentinaRPKI Valid168.226.43.0
- 168.226.44.0/24AS4926Telefonica de ArgentinaRPKI Valid168.226.44.0
- 168.226.45.0/24AS4926Telefonica de ArgentinaRPKI Valid168.226.45.0
- 168.226.46.0/24AS4926Telefonica de ArgentinaRPKI Valid168.226.46.0
- 168.226.47.0/24AS4926Telefonica de ArgentinaRPKI Valid168.226.47.0
- 168.226.48.0/24AS4926Telefonica de ArgentinaRPKI Valid168.226.48.0
- 168.226.49.0/24AS4926Telefonica de ArgentinaRPKI Valid168.226.49.0
- 168.226.55.0/24AS22927Telefonica de ArgentinaRPKI Valid168.226.55.0
- 168.226.64.0/20AS11311Sinectis S.A.RPKI Valid168.226.64.0
- 168.226.80.0/21AS22927Telefonica de ArgentinaRPKI Valid168.226.80.0
- 168.226.88.0/22AS22927Telefonica de ArgentinaRPKI Valid168.226.88.0
- 168.226.92.0/22AS22927Telefonica de ArgentinaRPKI Valid168.226.92.0
- 168.226.214.0/24AS22927Telefonica de ArgentinaRPKI Valid168.226.214.0
- 168.226.217.0/24AS22927Telefonica de ArgentinaRPKI Valid168.226.217.0
- 168.226.218.0/23AS22927Telefonica de ArgentinaRPKI Valid168.226.218.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.