BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
139.135.128.0/17
Announced exactly
- 139.135.128.0/17AS17639Converge ICT Solutions Inc.RPKI Valid139.135.128.0
- Registry
- APNIC · Philippines · Mar 13, 1990
- Delegated block
- 139.135.128.0 – 139.135.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 139.135.128.0/18AS17639Converge ICT Solutions Inc.RPKI Valid139.135.128.0
- 139.135.128.0/22AS17639Converge ICT Solutions Inc.RPKI Valid139.135.128.0
- 139.135.132.0/22AS17639Converge ICT Solutions Inc.RPKI Valid139.135.132.0
- 139.135.136.0/22AS17639Converge ICT Solutions Inc.RPKI Valid139.135.136.0
- 139.135.140.0/22AS17639Converge ICT Solutions Inc.RPKI Valid139.135.140.0
- 139.135.144.0/22AS17639Converge ICT Solutions Inc.RPKI Valid139.135.144.0
- 139.135.148.0/22AS17639Converge ICT Solutions Inc.RPKI Valid139.135.148.0
- 139.135.152.0/22AS17639Converge ICT Solutions Inc.RPKI Valid139.135.152.0
- 139.135.156.0/22AS17639Converge ICT Solutions Inc.RPKI Valid139.135.156.0
- 139.135.160.0/22AS17639Converge ICT Solutions Inc.RPKI Valid139.135.160.0
- 139.135.164.0/22AS17639Converge ICT Solutions Inc.RPKI Valid139.135.164.0
- 139.135.168.0/22AS17639Converge ICT Solutions Inc.RPKI Valid139.135.168.0
- 139.135.172.0/22AS17639Converge ICT Solutions Inc.RPKI Valid139.135.172.0
- 139.135.176.0/22AS17639Converge ICT Solutions Inc.RPKI Valid139.135.176.0
- 139.135.180.0/22AS17639Converge ICT Solutions Inc.RPKI Valid139.135.180.0
- 139.135.184.0/22AS17639Converge ICT Solutions Inc.RPKI Valid139.135.184.0
- 139.135.188.0/22AS17639Converge ICT Solutions Inc.RPKI Valid139.135.188.0
- 139.135.192.0/22AS56207ComClark Network & Technology CorpRPKI Valid139.135.192.0
- 139.135.196.0/22AS56207ComClark Network & Technology CorpRPKI Valid139.135.196.0
- 139.135.200.0/22AS56207ComClark Network & Technology CorpRPKI Valid139.135.200.0
- 139.135.204.0/22AS56207ComClark Network & Technology CorpRPKI Valid139.135.204.0
- 139.135.208.0/22AS56207ComClark Network & Technology CorpRPKI Valid139.135.208.0
- 139.135.212.0/22AS56207ComClark Network & Technology CorpRPKI Valid139.135.212.0
- 139.135.216.0/22AS56207ComClark Network & Technology CorpRPKI Valid139.135.216.0
- 139.135.224.0/22AS56207ComClark Network & Technology CorpRPKI Valid139.135.224.0
- 139.135.228.0/22AS56207ComClark Network & Technology CorpRPKI Valid139.135.228.0
- 139.135.232.0/22AS56207ComClark Network & Technology CorpRPKI Valid139.135.232.0
- 139.135.236.0/22AS56207ComClark Network & Technology CorpRPKI Valid139.135.236.0
- 139.135.240.0/22AS56207ComClark Network & Technology CorpRPKI Valid139.135.240.0
- 139.135.244.0/22AS56207ComClark Network & Technology CorpRPKI Valid139.135.244.0
- 139.135.248.0/22AS56207ComClark Network & Technology CorpRPKI Valid139.135.248.0
- 139.135.252.0/23AS56207ComClark Network & Technology CorpRPKI Valid139.135.252.0
- 139.135.254.0/24AS56207ComClark Network & Technology CorpRPKI Valid139.135.254.0
- 139.135.255.0/24AS56207ComClark Network & Technology CorpRPKI Valid139.135.255.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.