BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
195.172.0.0/16
Announced exactly
- 195.172.0.0/16AS3257GTT Communications Inc.RPKI Not found195.172.0.0
- Registry
- RIPE NCC · United Kingdom · Jun 26, 1996
- Delegated block
- 195.172.0.0 – 195.172.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 195.172.0.0/18AS3320Deutsche Telekom AGRPKI Valid195.172.0.0
- 195.172.64.0/19AS3320Deutsche Telekom AGRPKI Valid195.172.64.0
- 195.172.96.0/23AS9009M247 Europe SRLRPKI Valid195.172.96.0
- 195.172.98.0/23AS212238Datacamp LimitedRPKI Valid195.172.98.0
- 195.172.100.0/23AS9009M247 Europe SRLRPKI Valid195.172.100.0
- 195.172.102.0/23AS212238Datacamp LimitedRPKI Valid195.172.102.0
- 195.172.104.0/23AS9009M247 Europe SRLRPKI Valid195.172.104.0
- 195.172.106.0/23AS203020HostRoyale Technologies Pvt LtdRPKI Valid195.172.106.0
- 195.172.108.0/23AS396356Latitude.shRPKI Valid195.172.108.0
- 195.172.110.0/23AS212238Datacamp LimitedRPKI Valid195.172.110.0
- 195.172.112.0/23AS212238Datacamp LimitedRPKI Valid195.172.112.0
- 195.172.114.0/23AS812Rogers Communications Canada Inc.RPKI Valid195.172.114.0
- 195.172.116.0/23AS812Rogers Communications Canada Inc.RPKI Valid195.172.116.0
- 195.172.118.0/23AS396356Latitude.shRPKI Valid195.172.118.0
- 195.172.120.0/24AS48529Quantumbeam Communications LimitedRPKI Valid195.172.120.0
- 195.172.122.0/23AS399468EngineFresh LLCRPKI Not found195.172.122.0
- 195.172.124.0/24AS212238Datacamp LimitedRPKI Valid195.172.124.0
- 195.172.126.0/23AS30058FDCservers.netRPKI Valid195.172.126.0
- 195.172.130.0/23AS55470Cyfuture India Pvt. Ltd.RPKI Valid195.172.130.0
- 195.172.132.0/23AS30058FDCservers.netRPKI Valid195.172.132.0
- 195.172.134.0/23AS212238Datacamp LimitedRPKI Valid195.172.134.0
- 195.172.136.0/22AS216245CYBERJET PTE. LTD.RPKI Valid195.172.136.0
- 195.172.140.0/24AS216211CYBERVERSE LLCRPKI Valid195.172.140.0
- 195.172.141.0/24AS216245CYBERJET PTE. LTD.RPKI Valid195.172.141.0
- 195.172.142.0/23AS216211CYBERVERSE LLCRPKI Valid195.172.142.0
- 195.172.142.0/24AS216211CYBERVERSE LLCRPKI Valid195.172.142.0
- 195.172.143.0/24AS216211CYBERVERSE LLCRPKI Valid195.172.143.0
- 195.172.144.0/24AS6220inContact Inc.RPKI Valid195.172.144.0
- 195.172.145.0/24AS5065Bunny CommunicationsRPKI Valid195.172.145.0
- 195.172.146.0/23AS30058FDCservers.netRPKI Valid195.172.146.0
- 195.172.148.0/23AS30058FDCservers.netRPKI Valid195.172.148.0
- 195.172.150.0/24AS134351Leaseweb Japan K.K.RPKI Valid195.172.150.0
- 195.172.152.0/21AS19211HostingYard LLCRPKI Not found195.172.152.0
- 195.172.192.0/23AS9009M247 Europe SRLRPKI Valid195.172.192.0
- 195.172.194.0/23AS203020HostRoyale Technologies Pvt LtdRPKI Valid195.172.194.0
- 195.172.196.0/23AS812Rogers Communications Canada Inc.RPKI Valid195.172.196.0
- 195.172.198.0/23AS9009M247 Europe SRLRPKI Valid195.172.198.0
- 195.172.200.0/23AS396356Latitude.shRPKI Valid195.172.200.0
- 195.172.202.0/23AS9009M247 Europe SRLRPKI Valid195.172.202.0
- 195.172.204.0/23AS212238Datacamp LimitedRPKI Valid195.172.204.0
- 195.172.206.0/23AS4766Korea TelecomRPKI Valid195.172.206.0
- 195.172.208.0/23AS30058FDCservers.netRPKI Valid195.172.208.0
- 195.172.211.0/24AS134351Leaseweb Japan K.K.RPKI Valid195.172.211.0
- 195.172.212.0/23AS212238Datacamp LimitedRPKI Valid195.172.212.0
- 195.172.214.0/23AS212238Datacamp LimitedRPKI Valid195.172.214.0
- 195.172.216.0/23AS212238Datacamp LimitedRPKI Valid195.172.216.0
- 195.172.218.0/23AS212238Datacamp LimitedRPKI Valid195.172.218.0
- 195.172.220.0/23AS212238Datacamp LimitedRPKI Valid195.172.220.0
- 195.172.222.0/23AS212238Datacamp LimitedRPKI Valid195.172.222.0
- 195.172.224.0/19AS3320Deutsche Telekom AGRPKI Valid195.172.224.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.