BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
170.169.0.0/16
Announced exactly
- 170.169.0.0/16AS2134Santander Global Technology and Operations, S.L.RPKI Not found170.169.0.0
- Registry
- LACNIC · Mexico · Jul 26, 1994
- Delegated block
- 170.169.0.0 – 170.169.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 170.169.0.0/24AS2134Santander Global Technology and Operations, S.L.RPKI Not found170.169.0.0
- 170.169.32.0/19AS2134Santander Global Technology and Operations, S.L.RPKI Not found170.169.32.0
- 170.169.32.0/24AS2134Santander Global Technology and Operations, S.L.RPKI Not found170.169.32.0
- 170.169.33.0/24AS2134Santander Global Technology and Operations, S.L.RPKI Not found170.169.33.0
- 170.169.34.0/24AS2134Santander Global Technology and Operations, S.L.RPKI Not found170.169.34.0
- 170.169.35.0/24AS2134Santander Global Technology and Operations, S.L.RPKI Not found170.169.35.0
- 170.169.36.0/24AS2134Santander Global Technology and Operations, S.L.RPKI Not found170.169.36.0
- 170.169.37.0/24AS2134Santander Global Technology and Operations, S.L.RPKI Not found170.169.37.0
- 170.169.38.0/24AS2134Santander Global Technology and Operations, S.L.RPKI Not found170.169.38.0
- 170.169.56.0/24AS2134Santander Global Technology and Operations, S.L.RPKI Not found170.169.56.0
- 170.169.57.0/24AS2134Santander Global Technology and Operations, S.L.RPKI Not found170.169.57.0
- 170.169.58.0/24AS2134Santander Global Technology and Operations, S.L.RPKI Not found170.169.58.0
- 170.169.62.0/24AS2134Santander Global Technology and Operations, S.L.RPKI Not found170.169.62.0
- 170.169.63.0/24AS2134Santander Global Technology and Operations, S.L.RPKI Not found170.169.63.0
- 170.169.93.0/24AS2134Santander Global Technology and Operations, S.L.RPKI Not found170.169.93.0
- 170.169.96.0/19AS2134Santander Global Technology and Operations, S.L.RPKI Not found170.169.96.0
- 170.169.97.0/24AS2134Santander Global Technology and Operations, S.L.RPKI Not found170.169.97.0
- 170.169.98.0/24AS2134Santander Global Technology and Operations, S.L.RPKI Not found170.169.98.0
- 170.169.99.0/24AS2134Santander Global Technology and Operations, S.L.RPKI Not found170.169.99.0
- 170.169.100.0/24AS2134Santander Global Technology and Operations, S.L.RPKI Not found170.169.100.0
- 170.169.101.0/24AS2134Santander Global Technology and Operations, S.L.RPKI Not found170.169.101.0
- 170.169.108.0/24AS22908Sixsigma Networks Mexico, S.A. de C.V.RPKI Valid170.169.108.0
- 170.169.109.0/24AS22011Sixsigma Networks Mexico, S.A. de C.V.RPKI Valid170.169.109.0
- 170.169.111.0/24AS2134Santander Global Technology and Operations, S.L.RPKI Not found170.169.111.0
- 170.169.127.0/24AS2134Santander Global Technology and Operations, S.L.RPKI Not found170.169.127.0
- 170.169.128.0/19AS2134Santander Global Technology and Operations, S.L.RPKI Not found170.169.128.0
- 170.169.128.0/24AS2134Santander Global Technology and Operations, S.L.RPKI Not found170.169.128.0
- 170.169.129.0/24AS2134Santander Global Technology and Operations, S.L.RPKI Not found170.169.129.0
- 170.169.130.0/24AS2134Santander Global Technology and Operations, S.L.RPKI Not found170.169.130.0
- 170.169.133.0/24AS2134Santander Global Technology and Operations, S.L.RPKI Not found170.169.133.0
- 170.169.136.0/24AS2134Santander Global Technology and Operations, S.L.RPKI Not found170.169.136.0
- 170.169.137.0/24AS2134Santander Global Technology and Operations, S.L.RPKI Not found170.169.137.0
- 170.169.138.0/24AS2134Santander Global Technology and Operations, S.L.RPKI Not found170.169.138.0
- 170.169.139.0/24AS2134Santander Global Technology and Operations, S.L.RPKI Not found170.169.139.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.