BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
122.11.128.0/17
Announced exactly
- 122.11.128.0/17AS4657StarHub LtdRPKI Valid122.11.128.0
- Registry
- APNIC · Singapore · Aug 14, 2006
- Delegated block
- 122.11.128.0 – 122.11.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 122.11.128.0/18AS4657StarHub LtdRPKI Valid122.11.128.0
- 122.11.132.0/24AS4657StarHub LtdRPKI Valid122.11.132.0
- 122.11.133.0/24AS4657StarHub LtdRPKI Valid122.11.133.0
- 122.11.134.0/24AS4657StarHub LtdRPKI Valid122.11.134.0
- 122.11.135.0/24AS4657StarHub LtdRPKI Valid122.11.135.0
- 122.11.136.0/24AS4657StarHub LtdRPKI Valid122.11.136.0
- 122.11.137.0/24AS4657StarHub LtdRPKI Valid122.11.137.0
- 122.11.138.0/24AS4657StarHub LtdRPKI Valid122.11.138.0
- 122.11.139.0/24AS4657StarHub LtdRPKI Valid122.11.139.0
- 122.11.140.0/24AS4657StarHub LtdRPKI Valid122.11.140.0
- 122.11.141.0/24AS4657StarHub LtdRPKI Valid122.11.141.0
- 122.11.144.0/24AS4657StarHub LtdRPKI Valid122.11.144.0
- 122.11.146.0/24AS4657StarHub LtdRPKI Valid122.11.146.0
- 122.11.147.0/24AS4657StarHub LtdRPKI Valid122.11.147.0
- 122.11.149.0/24AS4657StarHub LtdRPKI Valid122.11.149.0
- 122.11.150.0/23AS138345StarHub LtdRPKI Valid122.11.150.0
- 122.11.152.0/21AS138345StarHub LtdRPKI Valid122.11.152.0
- 122.11.161.0/24AS4657StarHub LtdRPKI Valid122.11.161.0
- 122.11.163.0/24AS4657StarHub LtdRPKI Valid122.11.163.0
- 122.11.164.0/24AS4657StarHub LtdRPKI Valid122.11.164.0
- 122.11.169.0/24AS138345StarHub LtdRPKI Valid122.11.169.0
- 122.11.170.0/23AS138345StarHub LtdRPKI Valid122.11.170.0
- 122.11.172.0/24AS138345StarHub LtdRPKI Valid122.11.172.0
- 122.11.173.0/24AS4657StarHub LtdRPKI Valid122.11.173.0
- 122.11.174.0/24AS4657StarHub LtdRPKI Valid122.11.174.0
- 122.11.176.0/24AS4657StarHub LtdRPKI Valid122.11.176.0
- 122.11.177.0/24AS4657StarHub LtdRPKI Valid122.11.177.0
- 122.11.178.0/24AS4657StarHub LtdRPKI Valid122.11.178.0
- 122.11.179.0/24AS4657StarHub LtdRPKI Valid122.11.179.0
- 122.11.180.0/24AS4657StarHub LtdRPKI Valid122.11.180.0
- 122.11.181.0/24AS45474Nexusguard Pte. Ltd.RPKI Valid122.11.181.0
- 122.11.183.0/24AS45474Nexusguard Pte. Ltd.RPKI Valid122.11.183.0
- 122.11.184.0/24AS45474Nexusguard Pte. Ltd.RPKI Valid122.11.184.0
- 122.11.185.0/24AS45474Nexusguard Pte. Ltd.RPKI Valid122.11.185.0
- 122.11.186.0/24AS45474Nexusguard Pte. Ltd.RPKI Valid122.11.186.0
- 122.11.192.0/18AS4657StarHub LtdRPKI Valid122.11.192.0
- 122.11.193.0/24AS4657StarHub LtdRPKI Valid122.11.193.0
- 122.11.194.0/24AS4657StarHub LtdRPKI Valid122.11.194.0
- 122.11.195.0/24AS4657StarHub LtdRPKI Valid122.11.195.0
- 122.11.196.0/24AS19551Incapsula IncRPKI Valid122.11.196.0
- 122.11.197.0/24AS138345StarHub LtdRPKI Valid122.11.197.0
- 122.11.199.0/24AS4657StarHub LtdRPKI Valid122.11.199.0
- 122.11.200.0/24AS4657StarHub LtdRPKI Valid122.11.200.0
- 122.11.201.0/24AS4657StarHub LtdRPKI Valid122.11.201.0
- 122.11.202.0/24AS4657StarHub LtdRPKI Valid122.11.202.0
- 122.11.210.0/24AS4657StarHub LtdRPKI Valid122.11.210.0
- 122.11.216.0/24AS138345StarHub LtdRPKI Valid122.11.216.0
- 122.11.217.0/24AS138345StarHub LtdRPKI Valid122.11.217.0
- 122.11.218.0/24AS138345StarHub LtdRPKI Valid122.11.218.0
- 122.11.219.0/24AS138345StarHub LtdRPKI Valid122.11.219.0
- 122.11.220.0/24AS4657StarHub LtdRPKI Valid122.11.220.0
- 122.11.222.0/24AS4657StarHub LtdRPKI Valid122.11.222.0
- 122.11.223.0/24AS4657StarHub LtdRPKI Valid122.11.223.0
- 122.11.230.0/24AS4657StarHub LtdRPKI Valid122.11.230.0
- 122.11.231.0/24AS4657StarHub LtdRPKI Valid122.11.231.0
- 122.11.232.0/24AS4657StarHub LtdRPKI Valid122.11.232.0
- 122.11.233.0/24AS4657StarHub LtdRPKI Valid122.11.233.0
- 122.11.242.0/24AS4657StarHub LtdRPKI Valid122.11.242.0
- 122.11.243.0/24AS4657StarHub LtdRPKI Valid122.11.243.0
- 122.11.244.0/24AS4657StarHub LtdRPKI Valid122.11.244.0
- 122.11.250.0/24AS4657StarHub LtdRPKI Valid122.11.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.